March 29, 20179 yr I recently upgraded from 4.5 to the latest version 6. In doing so it seems many directories and files have been set to read only. I'm in the process of moving lots of files from old drives onto new ones and would then like to delete the files off the original drive. I first tried the mv command but that was failing. I then used the "new permissions" tool and it also failed because these files are set as read only. How do I remove this read only flag...?
March 29, 20179 yr Community Expert If you were using mv command I assume you were working at the command line on your unRAID server. If so, you should be logged in as root so I don't think it's a permissions issue. Possibly the disk is read-only due to filesystem corruption. Go to Tools - Diagnostics and post the complete zip.
March 29, 20179 yr 3 minutes ago, rharvey said: How do I remove this read only flag...? Since you didn't post the diagnostics zip file that is requested I can only guess what the issue is. Most likely candidate would be that a disk has some corruption that is causing it to be mounted as read only, which usually can be fixed by checking the filesystem in maintenance mode.
March 30, 20179 yr Author Oh boy I'm in trouble now. I put the system in maintenance mode and ran the disk check from the GUI, it finished with a ton of errors all suggesting that I needed to do a -rebuilt-tree which I did. It ran for several hours and ended before it completed with these errors. 0%....20%....40%..block 368996707: The number of items (4096) is incorrect, should be (1) - corrected block 368996707: The free space (49152) is incorrect, should be (4048) - corrected pass0: vpf-10110: block 368996707, item (0): Unknown item type found [514 570430216 0x6f1 (15)] - deleted Segmentation fault If I run the check again it quickly comes back with reiserfsck --check started at Thu Mar 30 15:49:46 2017 ########### Replaying journal: Done. Reiserfs journal '/dev/md4' in blocks [18..8211]: 0 transactions replayed Checking internal tree.. Bad root block 0. (--rebuild-tree did not complete) I just attempted to start the array normally and it is seeing the drive needed to be formatted. Of course I did not back it up, really hard to back up 3TB's of data. Have I lost everything...? I says parity is still good.
March 30, 20179 yr Community Expert There's an issue with reiserfsck included with v.6.3.x, you need to downgrade to v6.2.4, fix your disk and then upgrade again.
March 30, 20179 yr Community Expert One more thing, the disk with filesystem issues has a very high number of UDMA CRC errors, especially for the number of power on hours, these are usually a sign of a bad SATA cable, consider replacing it or at least monitor the value, an increase of 2 or more for that attribute means there's still a problem: Quote Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 100 064 044 Pre-fail Always - 253495 3 Spin_Up_Time 0x0003 089 089 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 20 5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 074 060 045 Pre-fail Always - 22463665 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 268 (204 86 0) 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 20 184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0 188 Command_Timeout 0x0032 100 098 000 Old_age Always - 2 189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0 190 Airflow_Temperature_Cel 0x0022 068 055 040 Old_age Always - 32 (Min/Max 28/36) 191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 783 192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 14 193 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 486 194 Temperature_Celsius 0x0022 032 045 000 Old_age Always - 32 (0 18 0 0 0) 195 Hardware_ECC_Recovered 0x001a 100 001 000 Old_age Always - 253495 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 1068 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 97 (201 30 0) 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 11417124904 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 27799433710
March 30, 20179 yr Author I still have good parity so would't the safest thing to do is install a new drive, let it rebuild the data and then re-format this troubled drive...?
March 30, 20179 yr Community Expert Parity can't fix filesystem corruption, your only option is to run reiserfsck (also format is never an option before/during or after a rebuild as it will delete all data on that disk and update parity to reflect that)
March 30, 20179 yr Author So said another way, if I did re-build the data from parity that the result would be the exact same corruption on the new disk...?
March 30, 20179 yr Author OK so saving the data has become priority number one, what's the best way to do that. If I need to boot a lower version of UNRAID to successfully fix the corruption I would rater use a new USB drive and not mess with this one as it has a couple of VM's and Dockers too.
March 30, 20179 yr Community Expert You'd be complicating things with a new USB drive, you can disable both docker and VM service before downgrading to make sure there aren't any issues, or if you prefer, you can wait a little for the v6.3.3 release, it will use the same reiserfsprogs as v6.2.4
March 31, 20179 yr Community Expert 2 hours ago, johnnie.black said: you can wait a little for the v6.3.3 release Looks like the wait is over
March 31, 20179 yr Author Upgraded to 6.3.3 last night and started the "rebuild-tree" proves before going to bed. This morning it's done and things are looking good. The report does suggest that a few files were placed in lost+found so I have some work to do but all is good again. Is there a way to see (from the GUI) if any of the other drives are getting mounted in "read only"..?
March 31, 20179 yr Community Expert Install the Fix Common Problems plugin, it will alert you for those and many other common issues:
March 31, 20179 yr Author Hmm.....I have that plugin installed (have for a long while) and it never told me that my disk 4 was mounted read only.
March 31, 20179 yr Community Expert It should...you can also start the array in maintenance mode and run a check on each disk from the WebGUI, any filesystem issues are usually reported. Edited March 31, 20179 yr by johnnie.black
March 31, 20179 yr It should...you can also start the array in maintenance mode and run a check on each disk from the WebGUI, any filesystem issues are usually reported.If it gets mounted as read only then it will. If it mounts fine and then due to corruption gets remounted as read only then it will not but the write tests should catch it if the drive isn't spin down at time of the testSent from my LG-D852 using Tapatalk
Archived
This topic is now archived and is closed to further replies.