Re: [Bug-ddrescue] Logfile won't write: claims drive is read-only

[Antonio Diaz Diaz]

Hello Jeffrey,

Jeffrey Carlson wrote:
> I believe that the drive to which the file was output was temporarily
> unplugged (it was jostled, at least, near to when the error occurred), and
> this caused the error. I cannot be sure of anything though. When I
> replugged it, it came back as read-only. When I fixed that, there also
> wasn't very much space. I freed up 2 GB on the partition by lessening the
> proportion reserved for root using tune2fs.
>
> The "Read-only file system error" persisted through all this. It was true
> the first time, but all the tools I know indicate it is no longer true.
> [...]
> I mean that everything on my computer except ddrescue indicates this file
> is writeable but despite my having fixed all imaginable obstacles ddrescue
> still says
>
> ddrescue: Error opening logfile 'baby3.logfile' for writing.: Read-only
> file system
> Fix the problem and press ENTER to retry, or Q+ENTER to abort.
>
> again every time I hit enter.

If I understand this correctly, the output drive was unmounted and then 
mounted again while ddrescue was running from a directory in the file 
system of that drive, right?

In this case most probably ddrescue can no longer access files in its 
current working directory. You will need to quit ddrescue, losing the 
progress made since the last time ddrescue was able to write the logfile.

I think it would be a good idea to run ddrescue next time from a safe 
directory (one that won't be accidentally unmounted), for example your 
home directory:

$ ddrescue -n -d -r1 /dev/sdc2 
/media/jeff/f1611274-1f7d-4b32-9475-1ac91c0da6d2/baby3.img 
/media/jeff/f1611274-1f7d-4b32-9475-1ac91c0da6d2/baby3.logfile


Best regards,
Antonio.