I’ve just solved a problem after doing a zypper dup from 11.4 to 12.1 that prevented the system booting, quickly noting here in case it helps other installers over the weekend.
The system (laptop) wouldn’t boot and I kept being asked for the root password or Ctrl-D. Confusingly the system was asking me for my crypto partition password at the same time (presumably 'cos the new systemd boot was parallelising the mounts).
I suspected the “nofail” flag (from the release notes) was the problem on the crypto partition, but after modifying /etc/fstab, /etc/crypttab and rebooting a few times I ruled this out. Running dmesg, I saw that the system was complaining about the Windows (I know, we have one proprietary accounting app that means I have to dual boot once a month) partition being hibernated and was whining that it could only be mounted ro. Commenting the /windows/C line out from /etc/fstab let the system boot happily, I suppose it needs the nofail option adding to let
the mount script ignore the whine.
On 2011-11-18 22:56, dmsmd wrote:
>
> I’ve just solved a problem after doing a zypper dup from 11.4 to 12.1
> that prevented the system booting, quickly noting here in case it helps
> other installers over the weekend.
Thanks
> The system (laptop) wouldn’t boot and I kept being asked for the root
> password or Ctrl-D. Confusingly the system was asking me for my crypto
> partition password at the same time (presumably 'cos the new systemd
> boot was parallelising the mounts).
That looks like a bug to, that you should report in Bugzilla.
The first part seems to be the emergency system that enters when there is
an fsck failure or fstab error.
> I suspected the “nofail” flag (from the release notes) was the problem
> on the crypto partition, but after modifying /etc/fstab, /etc/crypttab
> and rebooting a few times I ruled this out. Running dmesg, I saw that
> the system was complaining about the Windows (I know, we have one
> proprietary accounting app that means I have to dual boot once a month)
> partition being hibernated and was whining that it could only be mounted
> ro. Commenting the /windows/C line out from /etc/fstab let the system
> boot happily, I suppose it needs the nofail option adding to let
> the mount script ignore the whine.
Makes a bit of sense
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)
