home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.sys.sun.hardware:5648 alt.sys.sun:3389
- Path: sparky!uunet!dtix!darwin.sura.net!spool.mu.edu!agate!ames!nsisrv!news2!roten
- From: roten@CUBA.gsfc.nasa.gov (Charles Roten)
- Newsgroups: comp.sys.sun.hardware,alt.sys.sun,um.sun
- Subject: More problems with a Maxstor XT 8760 S SCSI drive ... help !!
- Message-ID: <ROTEN.92Nov15234059@CUBA.gsfc.nasa.gov>
- Date: 16 Nov 92 04:40:59 GMT
- References: <ROTEN.92Nov11184744@CUBA.gsfc.nasa.gov>
- Sender: usenet@nsisrv.gsfc.nasa.gov (Usenet)
- Organization: /cuba_b/dirbe/roten/.organization
- Lines: 71
- In-Reply-To: roten@CUBA.gsfc.nasa.gov's message of Wed, 11 Nov 1992 23: 47:44 GMT
- Nntp-Posting-Host: cuba.gsfc.nasa.gov
- X-Newsreader: GNU Emacs 18.57.1, GNUS 3.13, NNTP 3.10
-
- In article <ROTEN.92Nov11184744@CUBA.gsfc.nasa.gov>
- roten@CUBA.gsfc.nasa.gov (Charles Roten) writes:
-
- >Last week, I purchased a Maxstor XT 8760 S, as a replacement for a
- >dead CDC Wren IV. It was to be installed on a Sun 386i/250, running
- >SunOS 4.0.2.
- >
- >The 'format' command performed a surface analysis successfully, and
- >reported the disk had no defective sectors. It formatted just fine.
- >
- >But when I tried to make a filesystem ... :-(
- >
- >{vulcan:5} newfs /dev/rsd0c
- >preposterous size 0
- >
- >I have tried two different sets of formatting parameters, one from
- >the Maxstor tech. support folks, and another from a Sun 4 format.dat
- >file. Same bad news both times.
- >
- >Can someone tell me what gives ? I am at my wit's end !
-
- Well, the folks who advised me to check the partitioning were right.
- I had formatted the disk placing all the available space in the 'a'
- partition. So,
-
- newfs /dev/rsd0a
- ^
-
- got the job done. Then, after
-
- mkdir /files1
-
- with the line
-
- /dev/sd0a /files1 4.2 rw 1 3
-
- added to /etc/fstab,
-
- mount /files1
-
- added 620 beautiful megabytes to my filesystem. I dumped about 60 Mb of
- data to the new disk.
-
- Then things got wierd. I shut the system down, and on reboot, the new
- disk would not mount. Attempts to do so by hand produce the following
- result ...
-
- {vulcan:32} mount /files1
- mount: /dev/sd0a on /files1: No such device or address
- mount: giving up on:
- /files1
-
- even though
-
- {vulcan:33} ll /dev/sd0a
- brw-r----- 1 root operator 7, 0 Nov 16 1988 /dev/sd0a
- {vulcan:34} ll -d /files1
- drwxrwsr-x 2 root wheel 512 Apr 30 1989 /files1/
-
- shows them both to be present. Can anyone point me in the right
- direction ?!?
-
- Reformatting and making a new filesystem each time I reboot is NOT an
- attractive option !!!! And that seems to be the only way this thing
- wants to work !!
-
- --
- Charles Roten | Hughes-STX, Incorporated |
- roten@cuba.gsfc.nasa.gov | 'Use the Source, Luke!'
- 7601 Ora-Glen Dr., Greenbelt, MD 20706 |
- 301-513-7805 (w), 301-317-0872 (h) | Obi-Wan Stallman
-