Article View: comp.sys.next.sysadmin
Article #66IBM OEM drive (E15) as boot device
From: paul buster
Date: Sun, 01 Nov 1992 21:07
Date: Sun, 01 Nov 1992 21:07
39 lines
1703 bytes
1703 bytes
I've been working with IBM 1GB OEM drives (0663 H12 and E15) They seem to work fine if they're not being used as boot devices. I followed the instructions about modifying the proprietary mode select sense page number 0, but when I try to boot from the IBM drive, I get the following (with the IBM as SCSI ID 1 and the NeXT internal drive as SCSI ID 2): Boot command: sd boot sd(0,0,0) SCSI unexpected msg: 1 sc: Unexpected msg SCSI unexpected msg: 1 sc: Unexpected msg SCSI unexpected msg: 1 sc: Unexpected msg booting SCSI target 2, lun 0 blk0 boot: sd()sdmach SCSI unexpected msg: 1 sc: Unexpected msg sd: target 1 lun 0 opcode 18 sd: addr 0x43bbf10 bcount 66 rdflag 1 sd: sdstatus 0 sdstate 0 resid 66 sc: s5c state 7 status 0x87 sc: intrstatus 0x8 seqstep 0x4 sc: fifo level = 0 transfer count 0 sc: command 0x10 config 0x57 on one 25Mhz machine, it goes ahead and boots, but on another 25MHz system it just hangs. It _acts_ like it's not getting a boot block from the IBM drive, finds one on the NeXT drive, then returns to find mach on the IBM drive. I've tried playing with disk -i and disk -b but with no progress. can anyone in netland tell me what's going on and if there's a fix ? thanks -paul buster buster@mongrel.Colorado.EDU
Technical Details
Message-ID:
<1992Nov1.210746.2846@colorado.edu>Path:
arc1-ca.pugleaf.net!sparky!uunet!stanford.edu!agate!boulder!newsShow Full Headers
Complete Article Headers
Newsgroups: comp.sys.next.sysadmin Path: arc1-ca.pugleaf.net!sparky!uunet!stanford.edu!agate!boulder!news From: buster@mongrel.Colorado.EDU (paul buster) Subject: IBM OEM drive (E15) as boot device Message-ID: <1992Nov1.210746.2846@colorado.edu> Sender: news@colorado.edu (The Daily Planet) Nntp-Posting-Host: mongrel.colorado.edu Organization: University of Colorado, Boulder Date: Sun, 1 Nov 1992 21:07:46 GMT Lines: 39