Re: Raid, fsck, superblock could not be found
hi ya
On Mon, 11 Apr 2005, rds wrote:
some details in the posts.. but all the important data is NOT in the post
> Loading modules...
> ide_cd
> ide_detect
> FATAL: Module ide_detect not found.
dont care about these if you're usind /dev/sdxxx
> If I continue with CONTROL-D, the system will boot but /boot is not mounted and
> /dev/md1 is not started and needs to be assembled.
tah dah .. :-)
my dumb question is:
what is /dev/md1 ?? is it raid1 or raid5
if it raid5, i think you're screwed if you are booting off
/dev/md0 instead of a boot floppy or boot cd or
boot-any-other-media
if /dev/md1 is raid1, than how are you booting??
with grub or lilo or ???
what's the content of grub.conf or lilo.conf
in either case, you should have:
boot=/dev/md2
root=/dev/md2
- what is the partition type.. ( fdisk -l /dev/hda or /dev/sda )
it should be "FD"
> # cat /etc/fstab
> # <file system> <mount point> <type> <options> <dump> <pass>
> proc /proc proc defaults 0 0
> /dev/md1 /boot ext3 defaults,errors=remount-ro 0 2
md1 is raid1 or raid5 ??
> /dev/md2 / ext3 defaults,errors=remount-ro 0 1
> /dev/md3 none swap sw 0 0
> # cat /proc/mdstat
> Personalities : [raid0] [raid1] [raid5]
> md2 : active raid5 sda2[0] sdc2[2] sdb2[1]
> 486351616 blocks level 5, 64k chunk, algorithm 2 [3/3] [UUU]
good
> md3 : active raid5 sda3[0] sdc3[2] sdb3[1]
> 1959680 blocks level 5, 64k chunk, algorithm 2 [3/3] [UUU]
good
> # mdadm --assemble /dev/md1 /dev/sd[abc]1
> mdadm: /dev/md1 has been started with 3 drives.
good
> # fsck.ext3 /dev/md1
> e2fsck 1.35 (28-Feb-2004)
> /dev/md1: clean, 27/10040 files, 17051/40064 blocks
good
> So, it appears that fsck fails because /dev/md1 is not started when fsck runs
> against it. But /dev/md2 does not appears to have any problems with fsck on
> reboot.
raid5 usually cannot be used to boot ( /boot )
c ya
alvin
Reply to: