I am about to pull drive15 from my server, and was copying files from it. One file would not copy, so as I didn't need it, I tried to delete it, but I am now seeing this error:

 

 

I've recently done a parity check and it's not the files that are read-only, it seems the file system has been flagged as read-only. Other drives don't have this issue.

 

It's not necessarily a big deal, as I'm going to pull the drive and not replace it, but it'd be useful to know what the problem is.

 

Cheers.

I am about to pull drive15 from my server, and was copying files from it. One file would not copy, so as I didn't need it, I tried to delete it, but I am now seeing this error:

 

 

I've recently done a parity check and it's not the files that are read-only, it seems the file system has been flagged as read-only. Other drives don't have this issue.

 

It's not necessarily a big deal, as I'm going to pull the drive and not replace it, but it'd be useful to know what the problem is.

 

Cheers.

For a file-system to be mounted as read-only it usually indicates that file-system corruption was detected when unRAID attempted to mount the file-system as read/write.  To prevent further damage, it mounts it as read-only.

 

You should follow the instructions in the wiki to check and repair your file-system.    You'll need to do this before you replace the drive, as unRAID will re-construct the exact same file-system ( complete with the exact same corruption ) on any replacement drive.  It will only complicate the upgrade/replacement process.

 

The procedure is described here in the wiki:

http://lime-technology.com/wiki/index.php?title=Check_Disk_Filesystems

 

Joe L.

Thanks, Joe. What if I don't need the file and am pulling the drive completely (unassigning it)? Can I just copy the good data and unassign and pull the drive?

Thanks, Joe. What if I don't need the file and am pulling the drive completely (unassigning it)? Can I just copy the good data and unassign and pull the drive?

Un-assigning the drive is treated EXACTLY the same as if the drive failed.  It will be simulated (complete with the corrupt file-system and read-only mount)  You'll still be able to booth read and (not)write to it.   While being simulated you do not have parity protection from a second concurrent disk failure.   To get parity protection back, without the un-assigned drive, you must set a new disk configuration.

 

To remove the disk from the array, and NOT replace it with another, you must set a new disk configuration.  After setting a new disk configuration, unRAID must re-calculate parity on the new disk configuration.

To set a new disk configuration on a older release of unRAID you must

 Stop the array

 Use the "Devices" page to un-assign the disk you are removing.

 Check the checkbox under the button labeled as "Restore"

 Click on the "Restore" button.    (At this point any prior parity calculations are no longer valid)

 Start the array, which will then start the process of Initially Calculating Parity on the new disk configuration.   Once the new parity calculation is complete you will be protected by parity from a disk failure.

On newer releases of unRAID, the button labeled as "Restore" was removed.

(Too many people used it by mistake when trying to re-construct a failed disk, invalidated their parity, and lost the data they were trying to protect)

On newer releases of unRAID to set a new disk configuration there is a exactly equivalent command you must use at the Linux command line instead of the "Restore" button.  It is named initconfig.

 

To set a new disk configuration on a newer release of unRAID you must

Stop the array

 Use the "Devices" page to un-assign the disk you are removing.

 Log in via telnet or on the system console as root.

 Type:

initconfig

 Respond to its prompt by typing "yes"

  (At this point any prior parity calculations are no longer valid)

 On the web-interface browser, press the "Refresh" button.  All the drives should show with a "Blue" indicator.

 Start the array, which will then start the process of Initially Calculating Parity on the new disk configuration.   Once the new parity calculation is complete you will be protected by parity from a disk failure.

 

Joe L.

Yes, that was my plan -- copy the good data from the drive, unassign it and initconfig.