opensuse 13.2 will not boot anymore

English Install/Boot/Login
1

Hello,

I have a 13.2 installation on a multiboot system that I still use some. This is a multiboot box with windows XP and CentOS 7. I know that the opensuse install was working because I used yast to configure the bootloader to add CentOS when I installed it.

I have made some changes to the drive with the /root, /home, and /swap partitions but the added partitions are after the opensuse ones. I checked the UUID of the boot partition from the journalctl -xb output and it matches the UUID of /root in the partition table. I couldn’t figure out what the issue was by looking at the journal output.

There is one partition that could not be found because it was on a drive that I replaced with a new (larger) drive. It was mounted using /dev/disk/by-id/, so that entry would definitely fail. This is just a shared data drive, so I am not sure why the drive not being found would cause the boot to fail.

I could mount the /root partition in CentOS and edit the fstab if that is the problem but I don’t want to just guess. I am tempted to comment out all of the entries in the opensuse fstab except /root, /home, and /swap and see if I can get in.

If this is not the issue, how do I go about tracking it down. Can I save the journal somewhere so I can look at it more closely?

LMHmedchem

2

This is not an answer that will repair your out of date openSUSE system, but to be pedantic, you most probably does not mean the /root partition (file system), but the / partition (which is often called “root partition” because it is mounted on the root of the directory tree: /)

There is also /root, but that is a different directory that contains the home directory of user root and that should never be made a separate file system.

3

And when “it will not boot” anymore, you could deliver a more detailed description. What happpens exactly after you choose the system from the Grub menu? Any output when you hit Esc, etc.

4

Most likely the fstab still contains the entry for the removed disk/partitions. Commenting those out should work.

5

You could do that, but better to add the nofail option to the non-essential filesystems, and change their 1 2 or 0 2 tails to 0 0. This way if only one filesystem is blocking it should be readily apparent which it is by not being mounted.