On Thu, 30 Jan 2003, Tony Alfrey wrote: > > 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.
fdisk really has no part in this process. This isn't an OS level issue. > > 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?? That might be the problem, although i'd be equally concerned if the SCSI BIOS got corrupted. > 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?? I'm referring to the SCSI IDs, not OS level disk name nomenclature. -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Lonni J Friedman [EMAIL PROTECTED] Linux Step-by-step & TyGeMo http://netllama.ipfox.com _______________________________________________ Linux-users mailing list [EMAIL PROTECTED] Unsubscribe/Suspend/Etc -> http://www.linux-sxs.org/mailman/listinfo/linux-users
