On Sunday 29 July 2001 19:23, Bruce Marshall wrote:
All of the above tells me this is a hardware problem. How about termination?
The controller has internal termination, and from there a high quality LVD cable runs to the two drives. I am using the same active LVD/SE terminator after the drives that I used with only one drive. I have tried with and without termpower supply from the second drive.
What scsi controller are you using? (not that it should really matter)
The controller is an onboard dual-channel sym53c1010 using the driver sym53c8xx. The two Ultra160 channels are completely separated, so that one can run Ultra160 on one and have single-ended devices on the other. The drives that I use are IBM 36LZX 18.3 GB Ultra160. After the last installation I have ID7 on the controller, ID0 on the installed drive and ID2 on the drive that I cannot get attached. That way, the second drive should appear as /dev/sdb and the installed drive still be /dev/sda if I ever succeed in getting the second drive attached to a running system. Oh, and I have a DVD-ROM drive on the other bus. I have tried disconnecting that, but to no avail.
Does the controller show you the two drives (and their ID's) at boot up?
Yes, the drives are both visible from the controllers ROM configuration tool, and I can low-level format and verify both of them.
Assuming you can only use one drive, would either one of them have worked for your re-install? (that is, by themselves, they both work fine?)
Yes, the new installation has been made on the new drive and the old drive, which also worked, is now low-level formatted and unattached to the bus. Best regards, David List
David List wrote:
On Sunday 29 July 2001 19:23, Bruce Marshall wrote:
All of the above tells me this is a hardware problem. How about termination?
The controller has internal termination, and from there a high quality LVD
That termination is for the other end of the scsi bus, the one you access at the back of the computer. Your problems seem at the other end of the bus.
cable runs to the two drives. I am using the same active LVD/SE terminator after the drives that I used with only one drive. I have tried with and without termpower supply from the second drive.
If you have an external terminator, the other drives don't need to have termination or termination power enabled. Bruce Marshall wrote:
On Saturday 28 July 2001 13:34, David List wrote:
In the process of adding a scsi-disk to my SuSE Linux 7.1 system, I have encountered some problems. The first was the changing of drive-names. I solved that by changing scsi-id's on the drives. Now, when I boot from a boot-floppy, I see the correct drive-names for the drives (/dev/sda for the
does it boot completely and you see both drives?
old disk and /dev/sdb for the new disk), but when I boot from the lilo configuration I normally use, I get 'LI' and nothing else.
Where are you installing linux? Does the BIOS of your scsi adapter let you configure from which device to boot? If so, you may need to specify the device ID of the disk you want to boot from. On my system, I also need to put this on my lilo.conf: disk = /dev/sda # The first SCSI disk ... bios = 0x80 # ... is the first one at boot time disk = /dev/sdb # The second SCSI disk ... bios = 0x81 # ... is the second one at boot time I've linux installed in sda. rafael
On Monday 30 July 2001 13:31, Rafael Herrera wrote:
That termination is for the other end of the scsi bus, the one you access at the back of the computer. Your problems seem at the other end of the bus.
The bus is now: Controller (terminated) to Drive1 to Active LVD/SE terminator To me, it seems a natural thing to terminate the controller.
cable runs to the two drives. I am using the same active LVD/SE terminator after the drives that I used with only one drive. I have tried with and without termpower supply from the second drive.
If you have an external terminator, the other drives don't need to have termination or termination power enabled.
I know it ought to be that way, but I had to try.
Where are you installing linux? Does the BIOS of your scsi adapter let you configure from which device to boot? If so, you may need to specify the device ID of the disk you want to boot from. On my system, I also need to put this on my lilo.conf:
disk = /dev/sda # The first SCSI disk ... bios = 0x80 # ... is the first one at boot time disk = /dev/sdb # The second SCSI disk ... bios = 0x81 # ... is the second one at boot time
I've linux installed in sda.
I tried that specification in lilo.conf, before reinstalling. It didn't work then, but I think I should try it again. I have lilo on the MBR of /dev/hda, linux partitions /, /boot and swap on /dev/sda and I would like to add /dev/sdb when I succeed in getting the second drive attached to a running system. Best regards, David List
On Sunday 29 July 2001 15:14, David List wrote:
On Sunday 29 July 2001 19:23, Bruce Marshall wrote:
All of the above tells me this is a hardware problem. How about termination?
The controller has internal termination, and from there a high quality LVD cable runs to the two drives. I am using the same active LVD/SE terminator after the drives that I used with only one drive. I have tried with and without termpower supply from the second drive.
I'm beginning to think this is not a hardware problem... Lilo can get fussy. I'd use Tom's rootboot or some other way to boot into a linux system. You said you ran lilo at one point so maybe you booted in with a floppy. Did the drives seem ok (both online) at the time? Ever tried a grub boot floppy? Grub is easy to work with and allows you to make changes to the boot config on the fly so you can test various things. Could send you an image for a grub boot floppy. -- +----------------------------------------------------------------------------+ + Bruce S. Marshall bmarsh@bmarsh.com Bellaire, MI 07/30/01 12:49 + +----------------------------------------------------------------------------+ "Half this game is ninety percent mental." -Philadelphia Phillies manager Danny Ozark
On Monday 30 July 2001 18:53, Bruce Marshall wrote:
I'm beginning to think this is not a hardware problem... Lilo can get fussy.
I'd use Tom's rootboot or some other way to boot into a linux system.
You said you ran lilo at one point so maybe you booted in with a floppy. Did the drives seem ok (both online) at the time?
Yes. I could fdisk and format the /dev/sdb.
Ever tried a grub boot floppy? Grub is easy to work with and allows you to make changes to the boot config on the fly so you can test various things.
Could send you an image for a grub boot floppy.
Yes, please do when you can spare the time. But how about loading the necessary sym53c8xx module. How does one go about that with grub? Best regards, David List
Hello I installed 7.2 after succesfull living with 7.0. Now my ADSL line keeps hanging quite randomly, and I can't find any reason from logs etc.. I have the "new" 2.4.5 kernel installed with SuSEfirewall2. Installation is "out-of-the-box". Symptom is, that suddenly there is no communication to outside word, no pings get thru etc.. Still ifconfig and route gives "normal" output. By running "/etc/rc.d/dhclient restart" things starts to work normally again... It seems that getting newgroup listing is the most effective way to shut that line down :-( Line might stay up for hours, or just few seconds, and I have not found any relation to any software excpect the newgroup listing. I moved back to 2.2.19 kernel, and now the line stays open like before. At the same time I went back to SuSEfirewall. I remember seeing somewhere a document about new 2.4.x kernel sometimes having problems keeping xDSL line open. Does someone remember where to find the document, or give some points where to look the problem? J. Tamminen
On Monday 30 July 2001 16:34, David List wrote:
On Monday 30 July 2001 18:53, Bruce Marshall wrote:
I'm beginning to think this is not a hardware problem... Lilo can get fussy.
I'd use Tom's rootboot or some other way to boot into a linux system.
You said you ran lilo at one point so maybe you booted in with a floppy. Did the drives seem ok (both online) at the time?
Yes. I could fdisk and format the /dev/sdb.
Ever tried a grub boot floppy? Grub is easy to work with and allows you to make changes to the boot config on the fly so you can test various things.
Could send you an image for a grub boot floppy.
Yes, please do when you can spare the time. But how about loading the necessary sym53c8xx module. How does one go about that with grub?
Grub doesn't do any module handling.... what it does is start up your kernel which then would load the modules you need with initrd if they aren't compiled in. What I could do for you is to set up an entry on the grub boot floppy so you don't have to edit one in. Wanna send me your lilo.conf? and point out which entry you want for grub? I think it would have all the info I need. +----------------------------------------------------------------------------+ + Bruce S. Marshall bmarsh@bmarsh.com Bellaire, MI 07/30/01 17:39 + +----------------------------------------------------------------------------+ "The minute a man is convinced that he is interesting, he isn't."
On Monday 30 July 2001 23:40, Bruce Marshall wrote: ..... The problem is solved now. I turned out that I had overlooked that the scsi-BIOS output shown during system-boot had told me all the time that the CD-ROM drive on the other bus was detected before the scsi harddrives. Therefore I had to write these lines in /etc/lilo.conf: disk=/dev/hda bios=0x80 disk=/dev/sr0 bios=0x81 disk=/dev/sda bios=0x82 disk=/dev/sdb bios=0x83 When I got these lines right, and ran /sbin/lilo, I was suddenly able to boot all the way up with both scsi-disks attached. Thank you so much to you and all the other guys who posted suggestions to me during my hardware fight. It seems to me that disk- and INT13-entries in /etc/lilo.conf could be pretty important when running a combined IDE and SCSI system, so I hope that this information might help somebody else reading through the postings in this mailing list some time. Best regards, David List
On Tuesday 31 July 2001 16:32, David List wrote:
On Monday 30 July 2001 23:40, Bruce Marshall wrote:
.....
The problem is solved now. I turned out that I had overlooked that the scsi-BIOS output shown during system-boot had told me all the time that the CD-ROM drive on the other bus was detected before the scsi harddrives. Therefore I had to write these lines in /etc/lilo.conf: disk=/dev/hda bios=0x80 disk=/dev/sr0 bios=0x81 disk=/dev/sda bios=0x82 disk=/dev/sdb bios=0x83
When I got these lines right, and ran /sbin/lilo, I was suddenly able to boot all the way up with both scsi-disks attached.
Thank you so much to you and all the other guys who posted suggestions to me during my hardware fight. It seems to me that disk- and INT13-entries in /etc/lilo.conf could be pretty important when running a combined IDE and SCSI system, so I hope that this information might help somebody else reading through the postings in this mailing list some time.
Best regards, David List
Strange, because I currently have two scsi HD's and two CD's on the same controller and have never had this problem. -- +----------------------------------------------------------------------------+ + Bruce S. Marshall bmarsh@bmarsh.com Bellaire, MI 07/31/01 16:50 + +----------------------------------------------------------------------------+ "To each his own and to you so long."
On Tuesday 31 July 2001 22:51, Bruce Marshall wrote:
Strange, because I currently have two scsi HD's and two CD's on the same controller and have never had this problem.
Apparently it all depends on which drives the scsi-BIOS detects first. Best regards, David List
participants (4)
-
Bruce Marshall -
David List -
Jaakko Tamminen -
Rafael Herrera