weis@netmbx.UUCP (Dietmar Weis) (06/05/91)
I think problems with the Fujitsu M2266S-512 were discussed somewhere a little time ago. Unfortunately I did not get it all. So I hope someone could enlighten me with the following problem: DECsystem 5100 with Ultrix 4.1 won't recognize the disk upon loading vmunix. At console mode it is recognized as M2266S-512, 1029 MByte with correct SCSI ID 3, scsi "test 0x6" gives no error. The set of "scsi" commands is bad documented, so I don't know if they passed correctly. But after booting, when the system is loading vmunix and scanning the hardware configuration it gives: SCSI bus 0: command aborted (#0), ID=3 cmd 0x12 and the disk will never show up again until next consol mode. There was sth in the discussion about the adressing of drives larger than 1 GB. Is it this? Any suggestions? Thank you Dietmar -- weis@netmbx.UUCP | Dietmar Weis DONOP CONSULT GmbH Voice: 030/884 28 54-0 | Uhlandstrasse 179/180 Fax: 030/882 55 29 | D - 1000 Berlin 12
parker@mprgate.mpr.ca (Ross Parker) (06/06/91)
In article <2377@netmbx.UUCP>, weis@netmbx.UUCP (Dietmar Weis) writes: |> I think problems with the Fujitsu M2266S-512 were discussed somewhere |> a little time ago. Unfortunately I did not get it all. |> So I hope someone could enlighten me with the following problem: |> |> DECsystem 5100 with Ultrix 4.1 won't recognize the disk upon loading |> vmunix. ... |> There was sth in the discussion about the adressing of drives larger than |> 1 GB. Is it this? Any suggestions? It sounds to me like your problem is not related to the 1GB restriction. That restriction doesn't prevent the disk from being seen at boot time, it will just cause the disk to be trashed sometime later. One thing you might check - the Fujitsu disk supports synchronous SCSI, the DECstation (with Ultrix 4.1) doesn't. You can set a jumper on the drive to disable synchronous SCSI. You should also set the SCSI-1 jumper. When you partition the disk, make sure you don't use the whole disk. You can use up to 1Gb, but no more. That translates to 2,097,152 sectors that you can allocate with chpt. If you don't follow this restriction and try to use the whole disk, the disk will end up being corrupted. -- Ross Parker | Why do they put me down? | Make out that I'm a clown? parker@mprgate.mpr.ca | I drink scotch whisky all day long uunet!ubc-cs!mprgate!parker | Yeah I'm gonna save my money | (gonna put it all away...) (604)293-5495 | 'Cause I'm a Scotsman
amirosh@shakespyr.Pyramid.COM (Alex Miroshnichenko) (06/06/91)
I have already send mail about it, but ... This looks like a long reset time for the disk. The Ultrix SCSI driver resets the bus and than begins polling all addresses with the INQUIRY. If a device has not recovered form the reset yet, it won't be recognized and configured. I saw a lot of this with the optical devices and jukeboxes. Solution : insert a small (~3-5sec) delay after reset in the probe routine.