On Wed, Apr 8, 2015 at 5:45 PM, Michael Tiernan <[email protected]> wrote: > On 4/8/15 11:23 AM, Robert Hajime Lanning wrote: >>> could you poll for the UUID assigned to the file system on the drives? >>> blkid i think is the command... >> I would not trust that. Aside from having to know the UUID up-front, >> what happens when there is no filesystem. > Precicely. >> I believe he wants to error out if the drive in slot 0 is missing or >> not responding without touching any other drives. > Exactly. >> Problem is that this is machine model specific. You have to know the >> channel path to slot 0. > This isn't an issue as far as I'm concerned, the environment is pretty > controlled so I can script that part pretty easily. > > It seems that this isn't a common issue so that's fine, i'll keep > hammering away. > Just signed up for ServerFault finally so I'll keep pursuing that route. > > Thanks for everyon'es time.
This seems related to why modern Linux systems use UUIDs to identify disks rather then disk/partition names. I seem to recall the problem was that depending on the hardware, bios, versions and timing; the system might enumerate the disks in a different order and therefore assign them different /dev/sdX names. Not sure if /sys/devices/pci.... will stay consistent or not. If it does, that would seem to be a good bet. Alternatively, you might see about remembering and comparing the serial number of the disk in slot0 and seeing if it has changed. Unless the drive manufacturer has really screwed up, that should work. Bill Bogstad _______________________________________________ Discuss mailing list [email protected] https://lists.lopsa.org/cgi-bin/mailman/listinfo/discuss This list provided by the League of Professional System Administrators http://lopsa.org/
