I've moved from:
md=4,/dev/sdf5,/dev/sdg5
to:
md=4,/dev/scsi/host0/bus0/target30/lun0/part5,\
/dev/scsi/host0/bus0/target32/lun0/part5
And now get:
md: Unknown device name,\
/dev/scsi/host0/bus0/target30/lun0/part5,\
On Saturday June 2, [EMAIL PROTECTED] wrote:
I've moved from:
md=4,/dev/sdf5,/dev/sdg5
to:
md=4,/dev/scsi/host0/bus0/target30/lun0/part5,\
/dev/scsi/host0/bus0/target32/lun0/part5
And now get:
md: Unknown device name,\
Neil Brown wrote:
md_setup() is displaying the error due to failing on name_to_kdev_t().
root_dev_setup() calls name_to_kdev_t() with a long devfs name without a
problem, so that's not the issue directly.
Yes... this is all very ugly.
root_dev_setup also stores the device name in
I put this together last night, and it's working ok on my servers.
YMMV.
It handles the job of first starting any dependent md devices
(IE for raid 0+1) for md devices in fstab set to mount at boot.
Might not be 100% fool proof if you have a VERY complex raidset.
Requires only bash/ash and sed.
