Re: Fedora 15 + scsi tape drive

On 16Oct2011 20:15, Chris Adams <cmadams@xxxxxxxxxx> wrote:
| Once upon a time, Cameron Simpson <cs@xxxxxxxxxx> said:
| > I'm all ok with providing sda/hda as discovered, _provided_ one also has
| > nice bus/id type names as well. Solaris' bus/id/partition drive names
| > looked long and complicated but they were reliable - you could look at
| > the device ids and know what the OS would call them.
|
| See /dev/disk/by-{id,path,uuid}.

And does this work _before_ boot, in the root= kernel command line, via
grub.conf?

| This is also an advantage of LVM; it
| knows how to find the physical volumes, and you generally don't have to
| care (/dev/vg_foo is always /dev/vg_foo). Even Solaris' bus number
| wasn't stable in the face of card changes IIRC.

Yeah, but that is at least infrequent.

With my problem system, the hardware RAID appears before the SATA boot
drives. If RAID volumes are missing (totally failed, for example - there's
some weak hardware involved here) then my boot drive can be any of sda, sdb
or sdc. Normally it is sdc because the RAID has two volumes which land at
sda and sdb.

| The problem with enumerating devices by HBA/bus/ID/LUN is that today's
| storage is more dynamic. USB ports are "SCSI" (protocol); how do you
| number those? IIRC USB ports on a hub are not deterministically
| ordered, so a flash card reader on a hub may come before a thumb drive
| on one boot and after on the next.

I would at least number then _last_! (I know this is slightly
simplistic.)

But I'd be happy if linux presented /dev/usb0/node2/part1, for example.
I don't _care_ about the protocol, and few users of the device _by_name_
care either. As far as that level of user is concerned it is a block
storage device; the protocol is the kernel's problem, not the user's.

Cheers,
--
Cameron Simpson <cs@xxxxxxxxxx> DoD#743
http://www.cskk.ezoshosting.com/cs/

One rider (Kenny Roberts?) described The CorkScrew as:
It's like driving your bike into a phone booth, and then
having the phone booth dropped down an elevator shaft!
--
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines

Relevant Pages

  • Re: Problems with software RAID on SATA
    ... Connected to this are two 320GB drives ... >>which I want to turn into a RAID1 array. ... >>I'm almost certain it's a problem with initting the RAID arrays at boot. ...
    (Debian-User)
  • Re: Debian machine not booting
    ... hard drives and added them. ... moved house and rebooted and now it doesn't boot. ... My 4 harddrives are organised in pairs of RAID 1 with LVM ... After doing what needs doing you can reboot to ...
    (Debian-User)
  • Re: Paul and Old Man: Cannot fix RAID5 failure ...
    ... I removed the drive reported in error, no boot or rebuild. ... I tried Universal Boot Disc but it won't load the RAID driver ... I was considering a parallel WinXP installation on a 4th disk, ... Maybe like in my case, actually 2 drives failed, while the RAID bios ROM ...
    (alt.comp.periphs.mainboard.asus)
  • Re: [SLE] please!! help me, completly lost!
    ... >machine which was equipped with hard drives configured as RAID.. ... or else to boot from a floppy. ... This is due to a bug in grub. ... Once booted you can switch to grub and setup the MBR on both drives. ...
    (SuSE)
  • Re: M2N-SLI Deluxe Raid setup questions
    ... I had assumed that since Windows recognized my array at one time that it should work. ... For #4, After I built the RAID array, I had to unplug the IDE drive (the original boot drive) for the RAID array to boot. ... Then I added two WD 250 GB SATA drives and after a little futzing around I got them configured. ...
    (alt.comp.periphs.mainboard.asus)