September 1, 201411 yr Unraid 5.0 - Pro I have a disk that reported offline for weeks. I replaced the drive and rebuilt using parity information and the drive now reports online. However, when I try to delete any files on disk I get permissions errors from Windows and when I telnet into the unraid server and try to delete manually the drive reports it is read only. I've run reiserfsck and I get a message saying to use the --rebuild-tree flag. Every file I've accessed on disk2 appears to be fine. What should I do next? Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes ########### reiserfsck --check started at Mon Sep 1 22:54:11 2014 ########### Replaying journal: Trans replayed: mountid 57, transid 171494, desc 6308, len 1, commit 6310, next trans offset 6293 Trans replayed: mountid 57, transid 171495, desc 6311, len 1, commit 6313, next trans offset 6296 Trans replayed: mountid 57, transid 171496, desc 6314, len 2, commit 6317, next trans offset 6300 Trans replayed: mountid 57, transid 171497, desc 6318, len 1, commit 6320, next trans offset 6303 Trans replayed: mountid 57, transid 171498, desc 6321, len 1, commit 6323, next trans offset 6306 Replaying journal: Done. Reiserfs journal '/dev/md2' in blocks [18..8211]: 5 transactions replayed Checking internal tree.. \/ 11 (of 36\/ 72 (of 164/block 236757010: The level of the node (0) is not correct, (2) expected the problem in the internal node occured (236757010), whole subtree is skipped finished Comparing bitmaps..vpf-10640: The on-disk and the correct bitmaps differs. Bad nodes were found, Semantic pass skipped 1 found corruptions can be fixed only when running with --rebuild-tree ########### reiserfsck finished at Mon Sep 1 23:07:31 2014 ########### root@FileServer:~#
September 2, 201411 yr It looks as if there is some sort of file system corruption and as a result the disk is being mounted in read-only mode. You are almost certainly going to have to run reiserfsck with the --rebuild-tree option to get this issue fixed. If you have the space available, I would first back up the files from that drive to another location. If you are prepared to take a risk with the data you can simply proceed without doing the backup first. In my experience as long as there is no problem with the drive, the --rebuild-tree can be expected to complete without any issues, but if it does not complete successfully you will then have trouble rescuing any data from the drive. You have to decide if you want to risk this? It will probably depend on whether you have backups of the data (I have backups available so I let it go ahead!).
September 2, 201411 yr +1 on backing up the data before doing anything to the drive (if you don't already have backups) Always a good idea to have backups, but if you don't, then at least backup the drive you're having issues with before doing things that will alter the file system on the drive !
Archived
This topic is now archived and is closed to further replies.