[COLUG] Is the drive dead or not?

[Kent Broestl]

Booted system with live CD: same result when trying to un/mount the drive.

from the fsck log:

fsck 1.40-WIP (14-Nov-2006)
Checking all file systems.
[/sbin/fsck.ext3 (1) -- /boot] fsck.ext3 -a -C0 /dev/hda1
[/sbin/fsck.vfat (2) -- /mnt/usb] fsck.vfat -a /dev/sda1
[/sbin/fsck.ext3 (3) -- /storage] fsck.ext3 -a /dev/hdf1
fsck.ext3: Device or resource busy while trying to open /dev/hdf1
Filesystem mounted or opened exclusively by another program?
open /dev/sda1:No such file or directory
dosfsck 2.11, 12 Mar 2005, FAT32, LFN
/boot: clean, 50/610432 files, 33786/1220932 blocks
[/sbin/fsck.ext3 (1) -- /home] fsck.ext3 -a -C0 /dev/hda6
/home: clean, 89881/6471680 files, 915382/12940349 blocks
[/sbin/fsck.ext3 (1) -- /usr] fsck.ext3 -a -C0 /dev/hda5
/usr: clean, 193539/1221600 files, 1008798/2441872 blocks
fsck died with exit status 9


I'm concerned that the drive appears to be busy at boot (!), and that 
fsck is exiting with status 9 ("errors corrected" + "Operational Errors" 
???)


Kent Broestl wrote:
> # umount /dev/hdf1
> umount: /dev/hdf1: not mounted
>
> mount and df both don't list /dev/hdf1
>
> but if I try
> # mount /dev/hdf1 /storage
> /dev/hdf1 already mounted or storage busy
>
>
> Rob Funk wrote:
>> Kent Broestl wrote:
>>  
>>> After a very hard reboot (my son _kicked_ the computer), one of my
>>> drives is now inaccessible. (Q: Head crash?)
>>>
>>> mount /dev/hdf1 /storage
>>> /dev/hdf1 already mounted or /storage busy
>>>     
>>
>> What happens when you "umount /dev/hdf1", and what do "df" or plain 
>> "mount" say?
>>
>>
>>   
> _______________________________________________
> colug432 mailing list colug432 at colug.net
> http://www.colug.net/mailman/listinfo/colug432
>