mchinni@pica.army.mil (Michael J. Chinni, SMCAR-CCS-E) (07/07/89)
System config.: DEC VAX 8600 running ULTRIX 3.0 w/ RL02 disk for bootstrap and
6 RA81 disks for unix filesystems.
Background: drive #3 was accidentally de-engaged (i.e. the button marked B on
the front of the drive was un-depressed). This happened when the system was up
in multi-user mode. I brought the drive down, re-depressed the B button (all
the other RA81 had B depressed), and brought the drive back up. This was done
from single-user mode with all filesystems unmounted.
The de-engagement was discovered when any attempt to talk to the drive
caused an error (ls on the filesystem on the drive - I/O error; mount/fsck on
the drive device - No such device or address).
Since re-engaging the drive I can talk to it via fsck.
Problem: I cannot re-mount the filesystem that was on the drive.
I say:
# /etc/mount /dev/ra3c /mnt
System says:
ufs_mount: fs /dev/ra3c not cleaned -- please fsck
ufs_mount: /dev/ra3c on /mnt: Invalid argument
so I obediently fsck the device with "fsck /dev/rra3c" since the drive was
configured with only c partition in use for the entire space on the disk.
Fsck finds no problems and no complaints. I try to re-mount now and I get the
same error:
ufs_mount: fs /dev/ra3c not cleaned -- please fsck
ufs_mount: /dev/ra3c on /mnt: Invalid argument
Question: How can I get the system to let me mount the filesystem and get at
the info. on the drive (w/ ls, cp, mv, etc.) WITHOUT 'newfs'ing the drive?
/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/
Michael J. Chinni
Chief Scientist, Simulation Techniques and Workplace Automation Team
US Army Armament Research, Development, and Engineering Center
User to skeleton sitting at cobweb () Picatinny Arsenal, New Jersey
and dust covered workstation () ARPA: mchinni@pica.army.mil
"System been down long?" () UUCP: ...!uunet!pica.army.mil!mchinni
/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/graham@fuel.dec.com (kris graham) (07/11/89)
>Problem: I cannot re-mount the filesystem that was on the drive. ># /etc/mount /dev/ra3c /mnt ufs_mount: fs /dev/ra3c not cleaned -- please fsck ufs_mount: /dev/ra3c on /mnt: Invalid argument >so I obediently fsck the device with "fsck /dev/rra3c" since the drive >was configured with only c partition in use for the entire space on the >disk. >Fsck finds no problems and no complaints. I try to re-mount now and I >get the >ufs_mount: fs /dev/ra3c not cleaned -- please fsck >ufs_mount: /dev/ra3c on /mnt: Invalid argument >Question: How can I get the system to let me mount the filesystem and >get at the info. on the drive (w/ ls, cp, mv, etc.) WITHOUT 'newfs'ing >the drive? Looks like you need to give a more detailed description of your problem. I spoke to a very experienced Digital Ultrix system manager (Alan From: nabeth::alan To: fuel::graham Subject: Re: ultrix disk problem (USENET) I don't read comp.unix.questions, so go ahead and repost my reply if you want. I've only seen the problem on V2.x though. The important thing to check for is if the disk was write-protected when fsck ran. The applicatable DSA specs require the be write-protected if RCT isn't in the correct state. If you watch the disk the light will even come on when this happens. Insufficient information. It's possible that the time the drive spent offline caused BBR to start and after coming back online left the RCT in an inconsistant state. Usualy fsck till say that it can't write on the disk (NO WRITE) when it starts. That would prevent it from rewritting the clean byte when fsck(8) was done. There are two possible fixes: 1. Run radisk. That may be able to clean up the RCT. 2. Backup the disk and get field service to reformat. Christopher Graham Digital Equipment Corp Ultrix Resource Center Internet: graham@fuel.dec.com 2 Penn Plaza UUCP: ...!decwrl!fuel.dec.com!graham New York City Disclaimer: Above statements are really my own views..