[hblug] read only HDD

[Michael Adams]

On Fri, 09 Mar 2007 16:09:49 +1300
chris morris wrote:

> 
> >> "rm -r *" is a bit like "format C:\". The directory you were
> >removing was IN the drive, not the drive directory itself, correct?
> >If not then you may need to"mkdir" the directory again.

> Hmmm I've always used rm -r to delete large directories, I thought it 
> meant "remove recursively" eg; this folder and everything in it.
> If you just delete them linux tries to put it all (20gb+) into the
> trash bin :(
> But if there is an easier way to remove large amounts of data without 
> sending it to the trash I'd like to know.
> 

Thats exactly right. It's just that it comes with similar warnings to
"format C:". If you had cd'd into the drive first you should have had no
problems.

> I did try mkdir folder , but got the same read-only error even as
> root.
> 
> I then booted up on a live cd to eliminate any OS problems that might
> be lurking.
> Mounted the drive and tried to create a folder - no go, same error
> >>
> >> QTparted should still see the disk /dev/hdX even if it doesn't see
> >the> partition. I don't know if it sees mounted partitions, never
> >used it.>
> >>     
> Yes QTparted can see all the other mounted drives in the system but
> not /dev/hdf1 ( and it used to see it)
> The system could still see and read /media/hdf1 but could not write to
> it.
> 
> I've just ripped the drive out and will hang it in a Windoze box and
> see if that can see it ( I know it wont access ext3 but at least it
> might insist I format it.
> 

Ok so it looks as if the directory stub was definately visible, but not
the disk. At least we can guarantee the disk is not there now. It looks
like you are on the right track to me (he says as knowledge runs out).
Unless you have a replacement disk don't forget to remove the /etc/fstab
entry for it.

-- 
Michael
Linux: The OS people choose without $200,000,000 of persuasion.