I'm getting kernel panics trying to mount my root filesystem on boot:
EXT3-fs: unable to read superblock
EXT2-fs: unable to read superblock
iofs_read_super: bread failed, dev=09:01, iso_blknum=16, block=32
XFS: bad magic number
XFS: SB validate failed
Kernel panic: VFS: Unable to mount root fs on 09:01
Which I understand means that my superblock is missing XFS information
or is corrupted... trouble is, the filesystem is ext3! It used to be
XFS before I realised that I couldn't install LiLo into the superblock
along with XFS, so I made an ext3 filesystem on the partition expecting
the XFS information to be overwritten and then installed LiLo on the
superblock again, same thing. So then I deleted all my partitions and
used 'dd if=/dev/zero of=/dev/hde' and 'dd if=/dev/zero of=/dev/hde' to
wipe the start of the disks, recreated the partitions, formatted the
root partition ext3, reinstalled LiLo, rebooted, same problem.
The same kernel successfully boots off another disk (ext3) and can mount
the new root partition once the machine is booted as well as any XFS
partition I ask it to. All filesystem support that is needed is
compiled into the kernel. Can anyone explain what's going on here? I'm
completely out of ideas since I thought that the 'dd' was going to give
me a completely blank disk I can't imagine what's happening.
In case this is relevant (it might be) I'm trying to boot a software
raid with the two disks connected to a Promise 20276 controller. The
kernel is detecting this and I'm using the controller to access the
disks seperately (ie, disabling the hardware raid so the disks become
hde and hdg rather than ataraid/d0).
Thanks in advance.