Article View: comp.sys.next.hardware
Article #811Follow-up to Maxtor 660 Disk Problems
From: hitam.Princeton.EDUoberst Daniel...
Date: Fri, 09 Oct 1992 20:02
Date: Fri, 09 Oct 1992 20:02
69 lines
3077 bytes
3077 bytes
I had this posted a month or so ago and never got any feedback. It took over a month for me to get a check (they don't accept PO's) to Maxtor, but I finally got the board in last week, had our Tech Support people swap out the old board and put in the new one. I did an fsck and I'm back in shape without anything (so far) missing. One thing I did learn during the month is that a cube with an OD (*and* 32 MB of RAM) is a usable machine. I ran off the 2.0 Distribution OD, set up an account for my self, and ran a combination of local and NSF-mounted apps. I get 100+ pieces of mail a day, (locally) and run a number of apps (like NewsGrazer) off a central NFS server, but I found it quite a useful machine. Long Live the OD and the Cube!! > I have a NeXT (Maxtor) 660 MB drive that has given up the > ghost as a result of a couple power hits while I was away on > vacation. Here are the symptoms: > > When I try to boot off the drive, I get the following as part > of the boot sequence: > > READ CAPACITY: sdcmd bad state:0 dev blk len? > > I was able to boot off the OD, and get the following: > > SCSI 53C90A Controller, Target 7, as sc0 at 0x2114000 > MAXTOR XT-8760S as sd0 at sc0 target 0 lun 0 sd0 (0,0): > ERROR op:0x25 sd_state:7 scsi status:0x0 ERROR: Can't > read device capacity ERROR op:0x1a sd_state:7 scsi > status:0x0 DISK UNFORMATTED Generic SCSI Device as sg0 > at sc0 target 7 lun 7 > > and then: > > sd0 (0,0): scsi_timer: timeout op:0x8 sd_state:0 scsi > status:0x0 > > and > > SCSI Block in error = 0 (no valid label) > > When I try mounting it I just get an I/O error > > mount: /dev/sd0a on /mnt: I/O error > > Of course I have data that was not backed up on the disk, > that I would like to retrieve. :-( > > Maxtor will sell me a PCBA board controller for the disk > for $450 (cheaper than the NeXT repair charge, and the > estimates I have had for salvaging data off the disk). > Anyone have an idea if this *might* fix things? Could the > problem be in the controller and not the media? Any other > suggestions? Anyone seen a Norton UtilitiesLook-Alike > for a NeXT? > -- Daniel J. Oberst Director, Advanced Technology and Applications Computing and Information Technology Princeton University 116 Prospect Avenue Princeton, NJ 08544-2089 Phone: (609) 258-6023 Fax: (609) 258-1004 Email: oberst@hitam.princeton.edu (NeXT-mailable) -- Daniel J. Oberst Director, Advanced Technology and Applications Computing and Information Technology Princeton University
Technical Details
Message-ID:
<1992Oct9.200229.21737@Princeton.EDU>Path:
arc1-ca.pugleaf.net!sparky!uunet!ukma!darwin.sura.net!jvnc.net!princeton!hitam.Princeton.EDU!oberstShow Full Headers
Complete Article Headers
Newsgroups: comp.sys.next.hardware Path: arc1-ca.pugleaf.net!sparky!uunet!ukma!darwin.sura.net!jvnc.net!princeton!hitam.Princeton.EDU!oberst From: hitam.Princeton.EDU!oberst (Daniel J. Oberst) Subject: Follow-up to Maxtor 660 Disk Problems Message-ID: <1992Oct9.200229.21737@Princeton.EDU> Originator: news@nimaster Sender: news@Princeton.EDU (USENET News System) Nntp-Posting-Host: hitam.princeton.edu Organization: Princeton University Date: Fri, 9 Oct 1992 20:02:29 GMT Lines: 69