mkarandi@bobcat.Berkeley.EDU (Mangesh Karandikar 291-90-7759 ME) (01/10/91)
Keywords: Hi Yesterday our department got new 760Mb hard drive for the NeXT computer. We are having problem in building that hard drive. We tried the Build Application to build that hard drive. The error msg the Builddisk applicatoion gave are as follows : FUJISTU M2263S-512 : unknowndisk name Build Disk : Disk initialization failed Build of /dev/sd0 aborted For the "bsd" command in ROM monitor, follwoing display appered: boot sd(0,0,0) booting SCSI target 2, lun 0 Bad version 0x110001 Bad version 0x28300 Bad version 0xffff0000 Bad version 0x50414345 Bad lable Does anybody knows what the problem is. Plese email me or post an article here. Thanks, Mangesh...
lacsap@media-lab.MEDIA.MIT.EDU (Pascal Chesnais) (01/10/91)
In article <2765@oucsace.cs.OHIOU.EDU>, mkarandi@bobcat.Berkeley.EDU (Mangesh Karandikar 291-90-7759 ME) writes: > We are having problem in building that hard drive. We tried the Build > Application to build that hard drive. > The error msg the Builddisk applicatoion gave are as follows : > FUJISTU M2263S-512 : unknowndisk name > Build Disk : Disk initialization failed > Build of /dev/sd0 aborted > > For the "bsd" command in ROM monitor, follwoing display appered: > boot sd(0,0,0) > booting SCSI target 2, lun 0 > Bad version 0x110001 ... > Bad label > Ugh I hate doing this, however this is one of those type of problems that you answer from experience not remembering all the details, and not knowing exactly where this may be documented. First READ THE MANUALS "Network and System Administration" and "User's Manual". They detail how to physically connect the drive to the machine, and explain conceptually what the drive looks like to the mach operating system. Now for my experiences on the subject. BuildDisk assumes that the disk has had a low level format, and a NeXT label written out to it. The first should have happened at the factory, the second is information that is written to the disk which the operating system will use to use to know how the disk is partitioned logically.... The low level formatting is not the same thing as what NeXT calls "Initializing" a disk (they mean the equivalent here of putting down a filesystem...) The clue as to why Builddisk failed in your case is when you tried booting from the disk and got the bad label message... So boot from your OD, you will get errors about the disk again... Note to see if it is the first disk encountered (which would assign it a device name of sd0) or the second (then it would be sd1, really read the Network and system administrators manual here!)... once you have that, use the disk command interactively... /etc/disk /dev/rsd0a **** NOTE THAT THE DEVICE NUMBER DEPENDS **** ON THE SCSI ID NUMBER... Use the label command to write out the new label... Once that is done reboot the machine off of OD again, see if the disk is found with the right label... If not this may mean that the disk did not have a low level format, or a misconnection, or a faulty drive!... If the disk is recognized, then you can do a builddisk ONLY IF THE SCSI DRIVE IS ASSIGNED THE sd0 DEVICE NUMBER!!!! If this is not the case, and you want to use builddisk, then you need to use /usr/etc/builddisk script directly (not really advisable unless you really know what you are doing, since I have not found a man page for it), or you need to disable the other scsi drives from the system while you are performing a builddisk... All the above is based from my experiences a MONTH AGO, allow for senility and just plain stupidity... Good luck, pasc -- Pascal Chesnais, Research Specialist, Electronic Publishing Group Media Laboratory, E15-348, 20 Ames Street, Cambridge, Ma, 02139 (617) 253-0311 email: lacsap@plethora.media.mit.edu (NeXT)