Mark Everett <[EMAIL PROTECTED]> wrote:
>Aarrgh - it was a hardware failure.
Hardware failure - how boring!
><excuses>
>As this disk was fresh out of the box, I did not give much
>consideration to the possibility it was the source of the
>problem. More exotic sources of failure were so much more
>tempting. :) Also, I did not have access to a replacement
>until just yesterday.
></excuses>
Been there, done that myself. I guess we just *assume* that new hardware
is going to work for a least a little while before it fails. I had a
similar problem with a server that has 4 network cards in it. Two of them
were bad out of the box, but I had *assumed* that it must be me doing
something wrong, even though I'm reasonably competent. (Most days
anyway.) Guess we know what happens when we assume, eh? ;-) Next time
try to come up with a bit more exciting solution than hardware failure,
ok? <grin>
>The new disk (an identical model, also fresh out of the shrink
>wrap) was recognized properly at all levels. This time, during
>device discovery, the new disk (scsi1:0:1:0) was automatically
>mapped to the sdb device file name. I subsequently was able
>to partition it and create and mount a filesystem.
>
>For the record, I did try moving the SCSI id of the original
>disk from '0' to '1', but with no effect. I did not try the new
>disk at '0'.
>
>Scrutiny of the dmesg output below will show that Linux relocated
>my pre-existing external disk (scsi2:0:1:0) from sdb to sdc, due
>to the hierarchy of device mapping and SCSI id values. Brief
>panic ensued on boot when the OS tried and failed to mount the
>filesystem of this other disk to its 'old' device (sdb).
Actually it's the order the SCSI cards are discovered in, then SCSI ID.
Eric Sisler
Library Computer Technician
Westminster Public Library
Westminster, CO, USA
[EMAIL PROTECTED]
Linux - don't fear the Penguin.
Want to know what we use Linux for?
Visit http://gromit.westminster.lib.co.us/linux
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
