Anonymous@mrcnext.cso.uiuc.edu (05/29/90)
hard disk problem We've been having some problems trying to add a Wren VI to our system. We presently have a 330 Mb drive from which we want to continue to boot. We used Ronald Antony's formatting program and we used "disk" to install a filesystem The problem is that we are unable to mount the filesystem. We added an entry to /private/etc/fstab and it now looks like /dev/sdoa / 4.3 rw,noquota,noauto 0 1 /dev/sd1a /newdisk 4.3 rw,noquota,noauto 0 2 We tried to mount using /usr/etc/mount /dev/sd1a /newdisk but we get a message "Device is busy. Giving up on /newdisk." The filesystem seems to be mounted (we can read and write to it), but Disk Info in the Workspace Manager doesn't work. Furthermore, when we reboot, the system spends a long time checking the 330Mb drive and tells us that it has made repairs. Perhaps this is because we didn't unmount before rebooting? Can anyone help? Please send any suggestions to cfcgf@ecncdc.bitnet if possible. Thanks. .
rca@cs.brown.edu (Ronald C.F. Antony) (05/29/90)
+We've been having some problems trying to add a Wren VI to our system. We +presently have a 330 Mb drive from which we want to continue to boot. We used +Ronald Antony's formatting program and we used "disk" to install a filesystem +The problem is that we are unable to mount the filesystem. We added an +entry to /private/etc/fstab and it now looks like +/dev/sdoa / 4.3 rw,noquota,noauto 0 1 +/dev/sd1a /newdisk 4.3 rw,noquota,noauto 0 2 +We tried to mount using /usr/etc/mount /dev/sd1a /newdisk but we get a +message "Device is busy. Giving up on /newdisk." The filesystem seems to be +mounted (we can read and write to it), It seems to me that you have rebooted the machine to have the /etc/fstab take effect. As a result the machine aotomatically mounts the disk with the startup scripts as it consults the /etc/fstab file. Thus you get the message device busy. + but Disk Info in the Workspace Manager +doesn't work. Is the active file on the new disk? WS just shows the current drive. Use also df or mount (without parameters) to get info on filesystems and their status. +Furthermore, when we reboot, the system spends a long time +checking the 330Mb drive and tells us that it has made repairs. As I guess your drive have different scsi-targets (otherwise you would not have gotten this far) I have no clue why you get this error. Is it consistent? Do you also get it if you are not trying to mount the drive manually? Ronald ------------------------------------------------------------------------------ "The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man." Bernhard Shaw | rca@cs.brown.edu or antony@browncog.bitnet