disk controller problem?
Tony Alfrey
tonyalfrey
Mon May 17 11:43:42 PDT 2004
On Thursday 30 January 2003 08:28 am, Tony Alfrey wrote:
> On Thursday 30 January 2003 05:39 am, Net Llama! wrote:
<snip>
> >
> > What kind of controller,
>
> The canonical Symbios 53C875 Ultra SCSI chipset
>
> > and what kind of disks?
>
> Two 9 GB Seagates and an 18 GB Seagate.
>
> > When its missing
> > some disks, is it reassigning the SCSI IDs accordingly to the disks
> > that it does see, or does it remember that the 'missing' ones
> > exist, and keep the ID assignments the same?
>
> I'm not sure. It's hard for me to see SCSI ID assignments if I don't
> boot an OS so I can then run fdisk.
Next time it happens, I'll boot from a floppy and see if I can get fdisk
running that way.
> I'll try a setup screen on
> boot-up but the bios setup does not "know" about SCSI, only IDE. The
> bios diagnostic screen on boot-up does not show SCSI ID numbers, just
> info about sectors, model number, etc.
>
> > Are you seeing errors, or just
> > that sda is not being detected? Do you need all the disks to boot
> > up?
>
Lonni, while it is not acting up now, when I try to use the SCSI
configuration utility that can be entered on boot-up, it seems to not
be functioning properly, I cannot access all of the features that are
supposed to be available and menus seem to be incomplete. It looks
like some kind of ROM problem associated with the controller. I will
see if there is some obvious ROM that goes with the controller and see
if I can get another??
On SCSI controller boot-up (after bios boot), I see SCSI ID numbers (the
jumper selections on the SCSI connector) but nowhere do I see a
graphical display of SCSI IDs such as sda, sdb, etc. Isn't that part
of the kernel??
--
Tony Alfrey
tonyalfrey at earthlink.net
"I'd Rather Be Sailing"
More information about the Linux-users
mailing list