External (USB) Drive having read only errors

Border

Member
I have a problem with a Seagate 1TB USB drive that seems to go into read only mode. The drive is formated FAT32 and only on reboot can I delete files. When I play files it can play them but it does not mark them as read or if interrupted does not remember the resume location.

For some reason two folders appeared -Recycled and System Volume Information... which contain
  1. Recycled (416.0KiB) and
  2. System Volume Information(192.0KiB)
When I use webif to try and delete these folders I get this message :


  • "/media/My Video/usb-drive1/System Volume Information"...Runtime Error: /mod/webif/lib/tdelete:13: rm: can't remove '/media/My Video/usb-drive1/System Volume Information/_restore{772D76XX-3698-438D-B8XX-BA40567216A8}/RP649/change.log': Read-only file system rm: can't remove '/media/My Video/usb-drive1/System Volume Information/_restore{772D76XX-3698-438D-B8XX-BA40567216A8}/RP649': Read-only file system rm: can't remove '/media/My Video/usb-drive1/System Volume Information/_restore{772D76XX-3698-438D-B8XX-BA40567216A8}/RP650/change.log': Read-only file system rm: can't remove '/media/My Video/usb-drive1/System Volume Information/_restore{772D76XX-3698-438D-B8XX-BA40567216A8}/RP650': Read-only file system rm: can't remove '/media/My Video/usb-drive1/System Volume Information/_restore{772D76XX-3698-438D-B8XX-BA40567216A8}': Read-only file system in procedure 'safe_delete' called at file "delete.jim", line 24 in procedure 'tdelete' called at file "/mod/webif/lib/safe_delete", line 51 in procedure 'tdelete' called at file "/mod/webif/lib/tdelete", line 8 at file "/mod/webif/lib/tdelete", line 13

I had undelete installed, removed that but it made no difference. I was using seriesfiller and that moves recordings onto the USB drive once recorded. (It used to put the old files in the undelete folders but I unstalled undelete).

I also have set the folders on the USB drive to autodedup maybe this is contributing to the problem.

From reading the forums I have read that sometimes this type of error occurs when a hard drive is failing, so perhaps the USB hard drive is packing in. The diagnostics on the hummy customised firmware will only check the state of the internal hard drive and fix them but any ideas why this is happening or what to do?
 
Top