I just updated an existing installation of OpenSUSE 13.1 to 13.2 and after that the system refuses to boot. When pushing the arrow keys to get rid of the stuck boot splash I see that the boot procedure appears to wait indefinitely for the system disk (Samsung 850 Pro SSD) to initialize. The same problem appears to persist when booting from DVD/USB. I tried advanced options -> older kernels to no avail. So how should I proceed?
On Wed, 05 Nov 2014 22:36:01 GMT, Ipred <Ipred@no-mx.forums.opensuse.org>
wrote:
>
>I just updated an existing installation of OpenSUSE 13.1 to 13.2 and
>after that the system refuses to boot. When pushing the arrow keys to
>get rid of the stuck boot splash I see that the boot procedure appears
>to wait indefinitely for the system disk (Samsung 850 Pro SSD) to
>initialize. The same problem appears to persist when booting from
>DVD/USB. I tried advanced options -> older kernels to no avail. So how
>should I proceed?
Completely power the unit down then while really off
check the SSD disk cables, make they are fully seated
check the rest of the cables since it is a good opportunity
power the system up again and see if it boots
If that fails, remove the SSD and try it on another machine or a USB
enclosure if you have one. It could have died on you.
Finally recheck how the partitions are addressed by grub and /etc/fstab
not all combinations are comparable.
HTH
?-)
I see no reason to believe that anything is wrong with the cable, both 13.1 to which I have just downgraded and Windows work just fine.
When interrupting the stuck boot procedure I’m urged to login as root and issue a certain command to check logs, or press ctrl+d to continue. Here is the first few error entries I found in this log:
…
[date] linux-wybb lvm[1244]: No volume groups found
[date] linux-wybb lvm[1248]: No volume groups found
[date] linux-wybb systemd[1]: (RED)Dependency failed for /dev/disk/by-id-ata-Samsung_SSD_850_PRO_256GB_[serial id]-part5(/RED)
– Subject: Unit dev-disk-by\x2did-ata\x2dSamsung_SSD_850_…\x2dpart5.swap has failed.
– Defined-By: systemd – Support: …freedesktop.org … /systemd-devel
– Unit swap.target has failed.
– The result is dependency. [date] linux-wybb systemd[1]: (WHITE)Job dev-disk-by\x2did-ata\x2dSamsung_SSD_850_…\x2dpart7.device/start timed out.(/WHITE)
[date] linux-wybb systemd[1]: (RED)Timed out waiting for device dev-disk-by\x2did-ata\x2dSamsung_SSD_850_…\x2dpart7.device.(/RED)
– Subject: Unit dev-disk-by\x2did-ata\x2dSamsung_SSD_850_…\x2dpart7.device has failed … I cannot divulge the rest right now as I don’t have the system with me.
MMM you did not mention you had a LVM setup. Or at least the installer thinks you do maybe.
EFI or MBR format on the drive. Did you ever have both?? Or did you ever change from one to the other not not do a complete wipe of the drive first track.
The BIOS is non-UEFI and when I first installed Windows I had in mind to make sure that the hard drive is MBR for compatibility reasons, I cannot see how a Windows installer would use the GPT partitioning scheme on a system with non-UEFI BIOS.
<br><br>
During the installation process, the installer created two primary partitions (even though I had chosen to install it on one partition). When I proceeded to install OpenSUSE 13.1, the installer created a third extended partition with three sub partitions; one for /, one for swap and one for /home. In other words, I followed the default settings for the OpenSUSE 13.1 installer. I’m not sure if that means that the hard drive uses LVM. I actually thought that several sub-partitions in an extended MBR-partition means that LVM is being used.<br><br>
I first tried to update to 13.2 by using a UUI+extra data made from the full DVD-ISO but it failed too boot, most likely due to the reasons explained above. So I updated by zypper dup:ing after changing to the 13.2 repositories. Then the updated system failed to boot (from which the error messages in my prior post come). Then I did a clean install back to OpenSUSE 13.1 by once again using a UUI+extra data. By ‘extra data’ I mean that I copied the rest of the data files from the DVD-ISO into the USB stick after the UUI was made to make sure that it is just as complete as the DVD itself.
The first sentence in the second paragraph should be moved up to the first paragraph as I’m still talking about the Windows installer here. Also I have a serious problem getting the line-feed/carriage-return to work the way I want to in this web-interface for these forums. Sometimes I get new lines, other times I need to add the <br> html-tag.
No there is no LVM unless you chose it. LVM is a special container that can bu used to extend a single (or multiple partitions) across multiple drives. Also an easy way to set up a encrypted machine. It is not something that just happens. It has nothing at all to do with extended partitions.
Ok you problem I suspect is UUI I guess that this changes the iso and that is where the problem is. The openSUSE iso is out of the box ready to just be binary copied to the USB device. Doing anything but will not work. I actually use the copy command ie
cp name.iso /dev/sdX
Where sdX is the USB device. Note I copy direct to the device not a partition
But you can also use dd or use imagewriter
Full instructions here
http://en.opensuse.org/Live_USB_stick
I just received some additional information that might be useful. Here’s what the boot screen looks like when it’s stuck:
[HR][/HR] OK ] Started Show Plymouth Boot Screen
OK ] Reached target paths.
OK ] Reached target Sound Card (the only ‘sound card’ on the system is the GPU’s HDMI output)
Starting Entropy Daemon based on the HAVEGE algorithm…
OK ] Started Entropy Daemon based on the HAVEGE algorithm.
OK ] Started udev Wait for Complete Device Initialization.
Starting Activation of LVM2 logical volumes…
OK ] Started Activation of LVM2 logical volumes.
OK ] Reached target Encrypted Volumes…
Starting Activation of LVM2 logical volumes…
OK ] Started Activation of LVM2 logical volumes.
-
] (1 of 2) A start job is running for dev-disk-by\s2did-ata\x2dSamsung_SSD_850_PRO_256GB_...
[HR][/HR]
and then later the last line changes to
[HR][/HR] *] (1 of 2) A start job is running for dev-disk-by\s2did-ata\x2dSamsung_SSD_850_PRO_256GB_…
[HR][/HR]
and another little later the line is replaced with
[HR][/HR] TIME ] Timed out waiting for device dev-disk-by\x2did-ata\x2dSamsung_SSD…\x2dpart5.device
[DEPEND] Dependency failed for /dev/disk/by-id/ata-Samsung_SSD_… -part5
[DEPEND] Dependency failed for Swap.
TIME ] Timed out waiting for device dev-disk-by\x2did-ata\x2dSamsung_SSD…\x2dpart7.device
[DEPEND] Dependency failed for /home.
[DEPEND] Dependency failed for Local File Systems.
[DEPEND] Dependency failed for Postfix Mail Transport Agent.
[HR][/HR]
I’ve fetched some additional lines in the boot log and the additional error lines look pretty much the same but with
[HR][/HR]…
– Unit swap.target has failed.
…
– Unit home.mount has failed.
…
– Unit local-fs.target has failed.
…
[HR][/HR]
On Fri, 07 Nov 2014 23:06:02 GMT, Ipred <Ipred@no-mx.forums.opensuse.org>
wrote:
>
>I see no reason to believe that anything is wrong with the cable, both
>13.1 to which I have just downgraded and Windows work just fine.
>
>When interrupting the stuck boot procedure I’m urged to login as root
>and issue a certain command to check logs, or press ctrl+d to continue.
>Here is the first few error entries I found in this log:
>
>…
>[date] linux-wybb lvm[1244]: No volume groups found
>[date] linux-wybb lvm[1248]: No volume groups found
>[date] linux-wybb systemd[1]: (RED)Dependency failed for
>/dev/disk/by-id-ata-Samsung_SSD_850_PRO_256GB_[serial id]-part5(/RED)
>-- Subject: Unit
>dev-disk-by\x2did-ata\x2dSamsung_SSD_850_…\x2dpart5.swap has failed.
>-- Defined-By: systemd – Support: …freedesktop.org … /systemd-devel
>
>–
>-- Unit swap.target has failed.
>–
>-- The result is dependency. [date] linux-wybb systemd[1]: (WHITE)Job
>dev-disk-by\x2did-ata\x2dSamsung_SSD_850_…\x2dpart7.device/start timed
>out.(/WHITE)
>[date] linux-wybb systemd[1]: (RED)Timed out waiting for device
>dev-disk-by\x2did-ata\x2dSamsung_SSD_850_…\x2dpart7.device.(/RED)
>-- Subject: Unit
>dev-disk-by\x2did-ata\x2dSamsung_SSD_850_…\x2dpart7.device has failed
>… I cannot divulge the rest right now as I don’t have the system with
>me.
Please provide
CODE
fdsik -l
cat /etc/fstab
From your problem machine in a code block as indicated.
?-)