spenton@ssl.berkeley.edu (02/01/91)
Ok, so I fucked up. Here's what happened on my NeXTstation. I was all set to initialize a floppy, when some mail arrived. I answered the mail, then went up to disk-> Initialize Well, since the floppy wasn't the active disk, I was soon horrified to see the "Initializing Internal Hard Disk" message. Panic set in as I did the old command~. Now when I boot, I get the following error message: boot sd(0,0,0) booting SCSI target 1, lun 0 blk0 boot: sd()sdmach Booting from SCSI target 1 lun0 sd()sdmach: read error Booting from SCSI target 1 lun0 sd()sdmach: read error Can't load blk0 boot Any ideas ? Sounds to me like I nuked blk0. Help!!!! Steve Penton spenton@ssl.berkeley.edu 415-643-5645 .
datran2 (02/01/91)
In article <1991Jan31.184712.3159@agate.berkeley.edu> spenton@ssl.berkeley.edu () writes: >Ok, so I fucked up. Here's what happened on my NeXTstation. > >Well, since the floppy wasn't the active disk, I was soon >horrified to see the "Initializing Internal Hard Disk" message. > You have indeed initialized some portion of your hard disk. I had the same bad experience a week after upgrading to 2.0. I had to rebuild from scratch. (ouch). I'll certainly be more careful NeXT time, but I must confess that I fail to see the utility of an option to reinitialize the boot hard drive. I would strongly recommend that this be changed before too many people shoot themselves in the foot. Steve -- #====#====#====#====#====#====#====#====#====#====#====#====#====#====#====# # Steve Boker # "Badgers, we don't have no stinking badgers" # # datran2!smb@csn.org # -from Treasure of the Sierra Madre Zoo # #====#====#====#====#====#====#====#====#====#====#====#====#====#====#====#
GHISLAIN@SLACVM.SLAC.STANFORD.EDU (Ghislain J. ROY) (02/01/91)
In article <1991Jan31.200838.20947@csn.org!datran2>, smb@csn.org!datran2 says: > >In article <1991Jan31.184712.3159@agate.berkeley.edu> spenton@ssl.berkeley.edu >() writes: >>Ok, so I fucked up. Here's what happened on my NeXTstation. >> >>Well, since the floppy wasn't the active disk, I was soon >>horrified to see the "Initializing Internal Hard Disk" message. >> >but I must confess that I fail to see the utility of an option to >reinitialize the boot hard drive. I would strongly recommend that >this be changed before too many people shoot themselves in the foot. > >Steve > Count me in! It happened as I wanted to reinitialize an external HD. I call this the suicide of the NeXT. (OK so I helped a bit :-) But if I remember correctly, my Mac just says NO to initializing a boot disk. Any fix we can apply to prevent this kind of disaster?? Any chance that NeXT fixes that soon? Or is there a strong reason for this to exist besides trapping naive or inattentive users? -Ghislain The views and opinions expressed here do not necessarily reflect those of Stanford University or the DoE.
louie@sayshell.umd.edu (Louis A. Mamakos) (02/01/91)
In article <1991Jan31.200838.20947@csn.org!datran2> smb@csn.org!datran2 writes: >I'll certainly be more careful NeXT time, >but I must confess that I fail to see the utility of an option to >reinitialize the boot hard drive. I would strongly recommend that >this be changed before too many people shoot themselves in the foot. This isn't a problem if you don't log in as "root." You should only have root privs. to perform system administration functions, and not routine use of the system. Its too easy (as you've found out) to do awful damage before you notice what you've done. Don't "fix" a problem that really isn't there. louie
datran2 (02/01/91)
In article <1991Jan31.230434.12627@ni.umd.edu> louie@sayshell.umd.edu (Louis A. Mamakos) writes: >In article <1991Jan31.200838.20947@csn.org!datran2> smb@csn.org!datran2 writes: >>I'll certainly be more careful NeXT time, >>but I must confess that I fail to see the utility of an option to >>reinitialize the boot hard drive. I would strongly recommend that >>this be changed before too many people shoot themselves in the foot. > >This isn't a problem if you don't log in as "root." You should only have >root privs. to perform system administration functions, and not routine >use of the system. Its too easy (as you've found out) to do awful damage >before you notice what you've done. I thought about it from this angle. I think that the trouble is that it is too close to another similar operation. I know one should never ever be root, but in practice as a system admin, I often am. If a common command such as rm -rf seems risky, one might alias rm to provide interactive checking. If I could set the permissions for formatting the boot drive from the workspace so that not even root could do so, I would. Unfortunately this is not an option. I think my basic point is that there is a pot-hole in the sidewalk. All of the arguments that one should watch where one is going does not mean that life would be easier without the pot-hole. Steve. -- #====#====#====#====#====#====#====#====#====#====#====#====#====#====#====# # Steve Boker # "Badgers, we don't have no stinking badgers" # # datran2!smb@csn.org # -from Treasure of the Sierra Madre Zoo # #====#====#====#====#====#====#====#====#====#====#====#====#====#====#====#