EXT2 Superblock Not Found After Patching Up To Support Pack 3 on SLES 9 On PowerPC64

  • 3380912
  • 19-Feb-2007
  • 27-Apr-2012

Environment

Novell SUSE Linux Enterprise Server 9 (SLES 9)

Situation

After an upgrade from SLES 9 Shipping to SLES 9 SP3 on an IBM i-series, the server drops to a root console prompt after boot.rootfsck fails. The boot.rootfsck sees /dev/shm/root as a ext2 partition rather than a reiser partition, which means it can't find a ext2 superblock because it isn't there. When fscking the device node (/dev/iseries/vda3) fsck passes it to reiser.fsck as normal, but when running fsck on/dev/shm/root, fsck passes to e2fsck.

Resolution

After boot.clock runs, /dev/shm/root presents itself to fsck as a reiserfs and fsck passes it to reiserfsck. In order to have the system boot, move boot.clock up in order in/etc/init.d/boot.d/. In this example it was moved from S10boot.clock to S02boot.clock.

Feedback service temporarily unavailable. For content questions or problems, please contact Support.