Henrik Holst wrote:
Bryce wrote:
Gosh, where to start,..
Ok general setup
I'm using kernel version 2.6.17-rc5 and Raid 5 over 5 500Gb SATA disks
You have just upgraded to udev havn't you? :-)
[snip!]
Hum ho,.. I survived the horror but umm, well, I'll leave the above as
a story to frighten young sysadmins with.
The same happened to me with eth0-2. I _could_ not for my life
understand why I didn't get internet connect to work. But then I
realized that eth0 and eth1 had been swapped after I upgraded to udev.
Please advice your distribution udev documentation how to "lock down"
scsi and network cards to specific kernel names.
Regards,
Henrik Holst
Ah,.. yes,, udev has helpfully remapped where all the drives I have
were,.. and of course I've misread the log because my brain is so
fixated on expecting drives to be where they should
curse you UDEV!!
Phil
=--=
Move along, nothing to see here except an overstressed worker...
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
