March 14, 201115 yr Hi, Hopefully somebody can help here, I have tried looking at other posts but can't find the same issue. My cache drive has been filling up for a few weeks as the mover does not seem to be working, I have it set to be used only for my TV, Movies and Sport shares. All other shares are written direct and there is no issue with writing files direct to the array. I have the shares set to use the cache drive, mover enabled and have the cache and the shares set to have min free space of 10 gig (actual 10 gig, not 10 terabytes etc...) Split levels are set to between 4 and 6 as I don't care about files being grouped on the same drive. The array has 9 data drives and each has greater than 100 gig free space. Mover is failing both on the nightly cron and on a manual kick off. Files are generally auto-downloaded by SAB & Sickbeard to .Custom and then placed in /TV, /Movies etc... Looking at the log it is trying to move the files but they are all failing exactly like this one: Mar 14 09:43:04 Cosmos logger: ./TV/Fringe/Season 3/Fringe - S03E16 - Os - HD TV.mkv Mar 14 09:43:05 Cosmos logger: >f+++++++++ TV/Fringe/Season 3/Fringe - S03E16 - Os - HD TV.mkv Mar 14 09:43:05 Cosmos shfs0: shfs_create: create_path: /mnt/disk2/TV/Fringe TV/Fringe/Season 3/Fringe - S03E16 - Os - HD TV.mkv /mnt/disk1/TV/Fringe (30) Read-only file system Mar 14 09:43:33 Cosmos logger: rsync: open "/mnt/user0/TV/Fringe/Season 3/Fringe - S03E16 - Os - HD TV.mkv" failed: Read-only file system (30) Mar 14 09:43:33 Cosmos logger: rsync error: some files could not be transferred (code 23) at main.c(1031) [sender=3.0.2] Mar 14 09:43:33 Cosmos logger: ./TV/Fringe/Season 3 Mar 14 09:43:33 Cosmos logger: ./TV/Fringe Kevin
March 14, 201115 yr Hi, Hopefully somebody can help here, I have tried looking at other posts but can't find the same issue. My cache drive has been filling up for a few weeks as the mover does not seem to be working, I have it set to be used only for my TV, Movies and Sport shares. All other shares are written direct and there is no issue with writing files direct to the array. I have the shares set to use the cache drive, mover enabled and have the cache and the shares set to have min free space of 10 gig (actual 10 gig, not 10 terabytes etc...) Split levels are set to between 4 and 6 as I don't care about files being grouped on the same drive. The array has 9 data drives and each has greater than 100 gig free space. Mover is failing both on the nightly cron and on a manual kick off. Files are generally auto-downloaded by SAB & Sickbeard to .Custom and then placed in /TV, /Movies etc... Looking at the log it is trying to move the files but they are all failing exactly like this one: Mar 14 09:43:04 Cosmos logger: ./TV/Fringe/Season 3/Fringe - S03E16 - Os - HD TV.mkv Mar 14 09:43:05 Cosmos logger: >f+++++++++ TV/Fringe/Season 3/Fringe - S03E16 - Os - HD TV.mkv Mar 14 09:43:05 Cosmos shfs0: shfs_create: create_path: /mnt/disk2/TV/Fringe TV/Fringe/Season 3/Fringe - S03E16 - Os - HD TV.mkv /mnt/disk1/TV/Fringe (30) Read-only file system Mar 14 09:43:33 Cosmos logger: rsync: open "/mnt/user0/TV/Fringe/Season 3/Fringe - S03E16 - Os - HD TV.mkv" failed: Read-only file system (30) Mar 14 09:43:33 Cosmos logger: rsync error: some files could not be transferred (code 23) at main.c(1031) [sender=3.0.2] Mar 14 09:43:33 Cosmos logger: ./TV/Fringe/Season 3 Mar 14 09:43:33 Cosmos logger: ./TV/Fringe Kevin It appears as if your disk2 has been mounted as read-only in response to detected corruption in the file system. You basically need to follow the steps described in the wiki here to fix the file-system on /dev/md2 : http://lime-technology.com/wiki/index.php?title=Check_Disk_Filesystems
March 14, 201115 yr Author Thanks Joe, seems that my Disk 2 is having issues. I followed the guide but the check will not even start due to an unreadable block, anything I can do or is the drive in need of replacement? root@Cosmos:~# reiserfsck --check /dev/md2 reiserfsck 3.6.21 (2009 www.namesys.com) ************************************************************* ** If you are using the latest reiserfsprogs and it fails ** ** please email bug reports to [email protected], ** ** providing as much information as possible -- your ** ** hardware, kernel, patches, settings, all reiserfsck ** ** messages (including version), the reiserfsck logfile, ** ** check the syslog file for any related information. ** ** If you would like advice on using this program, support ** ** is available for $25 at www.namesys.com/support.html. ** ************************************************************* Will read-only check consistency of the filesystem on /dev/md2 Will put log info to 'stdout' Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes bread: End of file, cannot read the block (156282693). Aborted
March 14, 201115 yr Thanks Joe, seems that my Disk 2 is having issues. I followed the guide but the check will not even start due to an unreadable block, anything I can do or is the drive in need of replacement? root@Cosmos:~# reiserfsck --check /dev/md2 reiserfsck 3.6.21 (2009 www.namesys.com) ************************************************************* ** If you are using the latest reiserfsprogs and it fails ** ** please email bug reports to [email protected], ** ** providing as much information as possible -- your ** ** hardware, kernel, patches, settings, all reiserfsck ** ** messages (including version), the reiserfsck logfile, ** ** check the syslog file for any related information. ** ** If you would like advice on using this program, support ** ** is available for $25 at www.namesys.com/support.html. ** ************************************************************* Will read-only check consistency of the filesystem on /dev/md2 Will put log info to 'stdout' Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes bread: End of file, cannot read the block (156282693). Aborted no idea. You can try power cycling, and see if the drive is accessible then. Joe L.
March 14, 201115 yr Author Same thing after a power cycle, but Drive 2 shows as green so it's a bit strange. I guess I can exclude it from use for now but looks like I will need to replace the drive.
March 14, 201115 yr Same thing after a power cycle, but Drive 2 shows as green so it's a bit strange. I guess I can exclude it from use for now but looks like I will need to replace the drive. replacing the drive will not resolve your error. To run reiserfsck you need to stop SAMBA and un-mount the disk. Did you perform those steps? The issue is this, even if you replace the drive, it will be re-constructed with the exact same corrupted file-system. the corruption needs to be fixed. You can try un-assigning disk 2 and then starting the array with it un-assigned. unRAID will simulate it, and the corrupted file-system. You can then stop SAMBA and again try to run reiserfsck --check /dev/md2 Now, it will be able to "read" the simulated disk, and should be able to repair the file-system. Then, you can stop the array, re-assign the disk to slot 2 of the array, and then press "Start" to start the array and begin the re-construction of the repaired file-system onto the physical disk itself. Joe L.
March 14, 201115 yr Author Yes, I did umount and stop samba. It's just finished moving everything that was 'stuck' after I excluded drive2 from the shares so it is just an issue with this one drive, thankfully. I will do as you suggest, thanks for that, will report back. Kevin
March 14, 201115 yr Author Same error. I stopped the array, unassigned drive 2, started the array and then ran the following on Unraid 4.7 final: root@Cosmos:~# samba stop root@Cosmos:~# umount /dev/md2 root@Cosmos:~# reiserfsck --check /dev/md2 reiserfsck 3.6.21 (2009 www.namesys.com) ************************************************************* ** If you are using the latest reiserfsprogs and it fails ** ** please email bug reports to [email protected], ** ** providing as much information as possible -- your ** ** hardware, kernel, patches, settings, all reiserfsck ** ** messages (including version), the reiserfsck logfile, ** ** check the syslog file for any related information. ** ** If you would like advice on using this program, support ** ** is available for $25 at www.namesys.com/support.html. ** ************************************************************* Will read-only check consistency of the filesystem on /dev/md2 Will put log info to 'stdout' Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes bread: End of file, cannot read the block (156282693). Aborted
March 14, 201115 yr Same error. I stopped the array, unassigned drive 2, started the array and then ran the following on Unraid 4.7 final: root@Cosmos:~# samba stop root@Cosmos:~# umount /dev/md2 root@Cosmos:~# reiserfsck --check /dev/md2 reiserfsck 3.6.21 (2009 www.namesys.com) ************************************************************* ** If you are using the latest reiserfsprogs and it fails ** ** please email bug reports to [email protected], ** ** providing as much information as possible -- your ** ** hardware, kernel, patches, settings, all reiserfsck ** ** messages (including version), the reiserfsck logfile, ** ** check the syslog file for any related information. ** ** If you would like advice on using this program, support ** ** is available for $25 at www.namesys.com/support.html. ** ************************************************************* Will read-only check consistency of the filesystem on /dev/md2 Will put log info to 'stdout' Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes bread: End of file, cannot read the block (156282693). Aborted wow, that I did not expect. Makes it FAR less likely for the drive itself to be the cause though.
March 14, 201115 yr Try a different SATA port and power connector. If that does not work then I would put it back into the slot and let it be rebuilt. Problems running reiserfsck on a drive have been encountered before. In some cases, changing the SATA port allowed it to be fixed. In other cases, rebuilding the drive allowed it to be fixed. Did you pull a SMART report off the drive? Peter
March 15, 201115 yr Author Ok, pretty strange going on here. I had already started trying a rebuild of drive 2 which seemed complete OK, however once completed Drive 2 had a green ball next to it but showed as unformatted. I tried to unassign and re-assign again but the same. So I reformatted and rebuilt but drive 2 shows as empty whereas before it was 50% full. I've no idea what data was actually on drive 2 so I'm not sure if it was just reporting as half full but had in fact not been used by the array. Strange. Now the check runs ok and report no files and no corruption: ########### reiserfsck --check started at Tue Mar 15 18:59:08 2011 ########### Replaying journal: Done. Reiserfs journal '/dev/md2' in blocks [18..8211]: 0 transactions replayed Checking internal tree.. finished Comparing bitmaps..finished Checking Semantic tree: finished No corruptions found There are on the filesystem: Leaves 1 Internal nodes 0 Directories 2 Other files 0 Data block pointers 0 (0 of them are zero) Safe links 0 ########### reiserfsck finished at Tue Mar 15 19:00:06 2011 I just need to try to figure out if I have actually lost about 300 gig of data or not? I do have valid parity from a couple of weeks back so do you think it's worth rebuilding from that? Kevin
March 17, 201115 yr You are supposed to run the reiserfsck on the drive after if was rebuilt. You were not to format it. You should have asked when you were not clear. However, Joe did clearly post that having unRAID rebuild the drive (onto the same or a new drive) would not solve the problem. You also posted "reformatted and rebuilt" so what do you mean by this? Did you let the drive rebuild more than once? You must have pressed the format button on the interface? I have no idea what you mean by a valid parity from 3 weeks ago. The unRAID parity is not a snapshot. When you made changes to the data disk, the parity immediately and concurrently changed to match. Every change to the data drive was immediately reflected in the parity drive. If you replaced this disk and rebuilt you'd end up with another blank disk. You will have to try this, it came from Limetech; "Actually, yes there is something you can try. The trick is to use the 'reiserfsck' program specifying the '-scan-whole-partition' option. This will cause the program to look around in unallocated disk space, trying to find files and pieces of files which used to exist. It will put them all into a top-level directory called 'lost+found'. It may or may not preserve the file names, and the files may or may not be complete and/or corrupted." I believe you have to do the samba stop and unmount the drive like the other tests. Good luck. Peter
Archived
This topic is now archived and is closed to further replies.