markz@ssc.UUCP (Mark Zenier) (12/14/88)
A warning for my procedure for partitioning a second disk drive
in <1574@ssc.UUCP>.
If after executing labelit, a couple of lines of cryptic messages
do not appear, and any programs you try to execute are not found,
Ctrl-alt-delete immediately.
I assume the superblock is stepped on, because the root filesystem sure
will be.
This has happened to me using both
labelit /dev/rdsk/1s2 x2 1s2 (as run in the installation script)
and
labelit /dev/dsk/1s2 x2 1s2 (as documented in the release notes)
Sometimes it works, sometimes it doesn't.
The only safe place to run labelit from is a write protected boot floppy.
Mark Zenier uunet!nwnexus!pilchuck!ssc!markz markz@ssc.uucp
uw-beaver!tikal!dave@micropen (David F. Carlson) (12/15/88)
In article <1583@ssc.UUCP>, markz@ssc.UUCP (Mark Zenier) writes: > A warning for my procedure for partitioning a second disk drive > > If after executing labelit, a couple of lines of cryptic messages > labelit /dev/rdsk/1s2 x2 1s2 (as run in the installation script) NO! > labelit /dev/dsk/1s2 x2 1s2 (as documented in the release notes) > Sometimes it works, sometimes it doesn't. > The only safe place to run labelit from is a write protected boot floppy. > Mark Zenier uunet!nwnexus!pilchuck!ssc!markz markz@ssc.uucp I have never damaged a properly made disk with labelit. Run labelit only on the raw disk (/dev/rdsk/...) and never on the block device. Never run labelit on a mounted partition. Good luck. inews fodder inews fodder inews fodder inews fodder inews fodder -- David F. Carlson, Micropen, Inc. micropen!dave@ee.rochester.edu "The faster I go, the behinder I get." --Lewis Carroll
markz@ssc.UUCP (Mark Zenier) (12/17/88)
In article <590@micropen>, dave@micropen (David F. Carlson) writes: > I have never damaged a properly made disk with labelit. Run labelit only > on the raw disk (/dev/rdsk/...) and never on the block device. Never run > labelit on a mounted partition. Good luck. After I recovered the rest of my boot partition, and experimented some more, I found two reasons for only running disk partitioning from a floppy resident microport (286). 1. It's a lot faster. After you run fdisk or divvy off the floppy and it needs to reinitialize the hard disk driver, it just sets some sort of flag and the driver reinitializes itself at the next disk operation. When you're booted off the hard drive, it reboots the whole mess. 2. Labelit is carnivorous, and misdocumented. If it decides to chew on the root file system, It can't do any damage to a write protected floppy. Some further notes on setting up partitions on the second drive. 1. Making fdisk determine the bad tracks would be a good idea :-) 2. After the partition is mounted. go (cd) to the partitions root directory and run the /etc/mklost+found script. Mark Zenier uunet!nwnexus!pilchuck!ssc!markz markz@ssc.uucp uw-beaver!tikal!