No more boot ?

Hi all;)

I added a 4th sata hard disk on my desktop pc, it seems it changed the name of the others and impeded the boot process.
Or maybe there was a different problem linked with the filesystem check while booting the OS.
Anyway, i’m left in maintenance mode with the following error msg :

error on stat() /dev/disk/by-id/ata-ST3320620AS_9QF5PH60-part1 : no such file or directory

fsck.ext3 : no such file or directory while trying to open /dev/disk/by-id/ata-ST3320620AS_9QF5PH60-part1

/dev/disk/by-id/ata-ST3320620AS_9QF5PH60-part1 :
the superblock could not be read or does not describe a correct ext2 filesystem.
If the device is valid and it really contains an ext2 filesystem (and not swap or something else), the the superblock is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>

/dev/disk/by-id/ata-ST3320620AS_9QF5PH60-part1 : clean, 1235/9773056 files , … blocks
blogd: no message logging beacause /var/file system is not accessible
ehci-hcd ohci-hcd uhci-hcd usb-ohci usb-uhci
fsck failed for at least one filesystem (not /).
Please repair manually and reboot
the root file system is already mounted read-write

attention only control-d will reboot the system in this maintenance mode , shutdown or reboot will not work

df only gives /dev/sdb2.

with fdisk i can see it looks like to be the boot flagged partition (on 4 disks that’s not a lot , my new disk is recognised even if still empty).

i tried with openSUSE 11.1 dvd to repair the installed system, and then repair the install , there choosing not to check the filesystem whle booting does not help.

WHat happened ?
What shall i repair ?

i have an xfs partition but too bad i have not written down an up to date partition scheme… so i’m not quite sure which one is xfs (moreothere disk names have changed)

it looks like 3 disks only can be seen with fdisk :frowning:

Thanks for your help :wink:

I have same problem, but mine just says there’s something wrong with the file system, and invites me to manually fix the file system.

but I have no idea how to proceed with that, so anyone got any advice?

This message is potentially good news:

Please repair manually and reboot
the root file system is already mounted read-write

You can edit /etc/fstab and comment out the filesystems you don’t absolutely need, just keeping root and home, then try rebooting. That might get you into openSUSE.

[unless the bootloader’s menu.lst or other Grub pointers are now pointing to the wrong partition, in that case you can manually boot if you get a grub screen at the beginning]

when i comment out in /etc/fstab the line with /dev/disk/by-id/ata-ST3320620AS_9QF5PH60-part1
it then tells me part2 as the same problem.

Part1 is in ext3 , and part2 in xfs, is this a problem ?

I also noticed in fstab that part1 as a different option than others ext3 partition : “defaults” instead of “acl, usr_xattr”

All you need in fstab is the root partition (identified by the “/” mount), but if possible it’s a good idea to keep the home partition too (identified by the “/home” mount) – just alterations until you get booting going again – then you can remount the partitions (that you commented out) with the Yast partitioner and let the partitioner decide initially what are appropriate options to put in the mount line for each extra partition – just a way to get you going again.

edit :
i’m now repairing the filesystem with the dvd, it seems it was not contiguous …
Repair is a success, but where is this coming from ?
How can i avoid this kind of problem in the future ?

By the way : How can i have a scheme that will not be disturbed when introducing a new device ?

Why is now fstab using by-id ? (e.g /dev/disk/by-id/ata-ST3320620AS_9QF5PH60-part1 )

This is not just now, it’s already been so since a couple of years. One reason I can think of is this:
In the “old” situation adding a disk could mean, that your /dev/sdd1 became /dev/sde1 (i’ve met this situation). In the ‘new’ situation all disks/partitions are mounted by their unique ID, which means that errors/mistakes like mentioned cannot occur.

It would be good if sort of the same was done to GRUB’s, to avoid mistakes on multi-disk systems