[comp.sys.next] 2263SA initialization problems...

ice@wang.com (Fredrik Nyman) (04/18/91)

Hi!

Well, I got my 2263SA today, and I think I managed to screw something
up :-(

I followed Izumi Ohzawa's directions:
1/ I set the disk to SCSI ID #1 on CN9
2/ I removed the INQUIRY DATA and Synchronous Mode Transfer jumpers
   from CNH2
3/ I installed the disk in my cube.

I then booted from OD, logged in as root and ran scsimodes:

# scsimodes /dev/rsd0a

The information I got was exactly the same that was listed in Izumi's
directions:
Drive Type FUJITSU M2263S-512
512 bytes per sector
53 sectors per track
15 tracks per cylinder
1658 cylinders per volume
3 spare sectors per cylinder
15 alternte tracks per volume
1312343 usable sectors on volume

Happy that everything was working so well, I now ran Rory Bolt's
formatter (ver 1.2).  After having read the directions, I clicked on
SCSI ID 1.  It showed me various information about the disk, and
reassured that everything was OK, I clicked on Format.

This is where I got into trouble.  Formatter yelled about "Error
occured during format", and since then nothing has worked properly
with the disk.  scsimodes now sometimes tells me that the 2263SA has
512 bytes per sector, and sometimes that it has 1024 bytes per sector.
What it *always* does say is that the disk has ** 0 ** usable
sectors on volume.

HELP!!!!
-- 
Fredrik Nyman - Politically Chaotic and Proud.  Internet: <ice@wang.com>
Global Adaptation Center, Wang, M/S 019-490,    NeXT: <ice@red-zinger.wang.com>
One Industrial Ave., Lowell MA 01851, USA       BITNET: <ice@drycas>

ice@wang.com (Fredrik Nyman) (04/18/91)

Some more information...

- I have an old '030 cube with OD.  No other disks.  The 2263SA is
  mounted internally in the cube.

- I have NS 1.0a

When booting from the ROM monitor (to be able to see all error
messages), the following is displayed:

Apr 17 23:32:55 red-zinger mach: Bad disk label magic number
Apr 17 23:32:55 red-zinger mach: Target 1: MEDIA ERROR; block 0H retry 1
Apr 17 23:32:55 red-zinger mach: Target 1: MEDIA ERROR; block 0H retry 2
Apr 17 23:32:55 red-zinger mach: Target 1: MEDIA ERROR; block 0H retry 3
Apr 17 23:32:55 red-zinger mach: Target 1: MEDIA ERROR; block 0H retry 4
Apr 17 23:32:55 red-zinger mach: Target 1: MEDIA ERROR; block 0H retry 5
Apr 17 23:32:55 red-zinger mach: Target 1: MEDIA ERROR; block 0H retry 6
Apr 17 23:32:55 red-zinger mach: Target 1: MEDIA ERROR; block 0H retry 7
Apr 17 23:32:55 red-zinger mach: Target 1: MEDIA ERROR; block 0H retry 8
Apr 17 23:32:55 red-zinger mach: Target 1: MEDIA ERROR; block 0H retry 9
Apr 17 23:32:55 red-zinger mach: sd0 (1,0): sense key:0x3  additional
sense code:0x31
Apr 17 23:32:55 red-zinger mach:     SCSI Block in error = 0 (no valid label)
Apr 17 23:32:55 red-zinger mach: Bad disk label magic number
Apr 17 23:32:55 red-zinger mach:        UNABLE TO READ DISK LABEL

----------------------------------------------------------------------

Again, I'll be most grateful for any help the net can give me.
-- 
Fredrik Nyman - Politically Chaotic and Proud.  Internet: <ice@wang.com>
Global Adaptation Center, Wang, M/S 019-490,    NeXT: <ice@red-zinger.wang.com>
One Industrial Ave., Lowell MA 01851, USA       BITNET: <ice@drycas>