Re: RAID1 on sarge fail on boot, work manually postboot.
hi ya
On Thu, 7 Apr 2005, Clive Menzies wrote:
> I'm not the OP, however, I've had a similar problem and /dev/md0
> certainly does exist because if you try to recreate it with
> mdadm --create a warning says that the devices are already part of an
> array.
if it thinks its already created byt you cannot fsck it or mount it,
than stop/disassemble the raid and start over
> > > > > mdrun
come to think of it .. mdrun/mdstop etc is part of the old
raidtool/raidtools2 commands ... mdadm is newer set of tools
and if you mix and match commands.. you'd probably confuse it
commands to build raid .. and other debugging gotchas
http://1u-raid5.net/HowTo/mdadm.txt
raid is working when you can boot, hands off, after removing
any and all of the disks one at a time .. and that the
data resync's automatically if you wrote data to the degraded
array
> When running e2fsck it complains of a bad superblock and suggests:
> e2fsck -b 8193 but it barfs on that too.
those are either real or bogus error messages that reflects other
problems
> I've not tried it but I suspect if you run fsck once it's reassembled,
> it will be fine. I think the issue is that the ide driver modules
> aren't loaded when raid starts ... but I'm new to all this and may be
> way off track ;)
if you want the raid stuff... and if one was silly enough to use
ide as modules ... than the system should be smart enough to load
all the dependencies for the raid ... assuming that you ahve
an initrd for building the raid
whenver you use modprobe something, it will automatically load
all its dependencies, other things "something" wants to have loaded too
c ya
alvin
Reply to: