January 17, 201115 yr OK, It seems like I may have a bad spot / sector on one of my drives. When copying files to the disk1/Movies folder it stalls after 100 or so files. I made a disk1/Movies II folder, and files copy fine there. It seems like right after the last file copied to disk1/Movies is where the bad sector is located. It bombs out every time. Is there a program (defrag) or something that can mark that spot bad and unusable so I can finish copying in the disk1/Movies folder?
January 17, 201115 yr OK, It seems like I may have a bad spot / sector on one of my drives. When copying files to the disk1/Movies folder it stalls after 100 or so files. I made a disk1/Movies II folder, and files copy fine there. It seems like right after the last file copied to disk1/Movies is where the bad sector is located. It bombs out every time. Is there a program (defrag) or something that can mark that spot bad and unusable so I can finish copying in the disk1/Movies folder? most likely is a corrupted file system. Follow the steps here: http://lime-technology.com/wiki/index.php?title=Check_Disk_Filesystems Use reiserfsck on /dev/md1 Other than that, the specific reason for the 4.7 release is to fix a bug where copying large numbers of files from Windows7 fail. Are you using it? What version are you using of unRAID? For any other help, you'll need to supply a syslog for analysis. Instructions are under troubleshooting in the wiki. Joe L.
January 17, 201115 yr Author OK, It seems like I may have a bad spot / sector on one of my drives. When copying files to the disk1/Movies folder it stalls after 100 or so files. I made a disk1/Movies II folder, and files copy fine there. It seems like right after the last file copied to disk1/Movies is where the bad sector is located. It bombs out every time. Is there a program (defrag) or something that can mark that spot bad and unusable so I can finish copying in the disk1/Movies folder? most likely is a corrupted file system. Follow the steps here: http://lime-technology.com/wiki/index.php?title=Check_Disk_Filesystems Use reiserfsck on /dev/md1 Other than that, the specific reason for the 4.7 release is to fix a bug where copying large numbers of files from Windows7 fail. Are you using it? What version are you using of unRAID? For any other help, you'll need to supply a syslog for analysis. Instructions are under troubleshooting in the wiki. Joe L. Thanks Joe L. I will post the syslog in a few. I'm using unRAID version 4.6 and copying from a Mac not Windows 7. I think it's using SMB.
January 17, 201115 yr Author OK, It seems like I may have a bad spot / sector on one of my drives. When copying files to the disk1/Movies folder it stalls after 100 or so files. I made a disk1/Movies II folder, and files copy fine there. It seems like right after the last file copied to disk1/Movies is where the bad sector is located. It bombs out every time. Is there a program (defrag) or something that can mark that spot bad and unusable so I can finish copying in the disk1/Movies folder? most likely is a corrupted file system. Follow the steps here: http://lime-technology.com/wiki/index.php?title=Check_Disk_Filesystems Use reiserfsck on /dev/md1 Other than that, the specific reason for the 4.7 release is to fix a bug where copying large numbers of files from Windows7 fail. Are you using it? What version are you using of unRAID? For any other help, you'll need to supply a syslog for analysis. Instructions are under troubleshooting in the wiki. Joe L. Joe L.The syslog is attached. syslog-2011-01-17.txt
January 18, 201115 yr I am fairly certain that those drives are good. I did 3 cycles of preclear on them all and they passed without issue. I also copied around 250GB of content (music, movies, etc) from my server to yours when I was setting it up and did not have a problem. I took a look at the syslog and unless I glanced at it to quickly and overlooked something it appears to be OK. There was a hard shutdown in there and a lot of transactions were replayed by the ReiserFS. JoeL's. suggestion above about checking for corruption is a good idea. Follow the instructions he linked to and let us know what is reported.
January 18, 201115 yr If there really is a true "read error" on a disk, the number in the error column of the drive table will increment to 1 to let you know. But behind the scenes, unRAID will do a number of things that should fix the problem permanently. First it will read the corresponding values from all of the other drives at that location, and use that information to reconstruct what it should have been able to read from the disk. It will then WRITE that sector back to the disk that gave the error. This should cause the SMART system on the drive to remap the old sector, map in a spare sector, and copy the correct data to that newly remapped sector. Net effect - unRAID will correct the issue with no data loss or corruption. The next time that sector is accessed on the disk it will access the remapped sector. So if the error column shows a value of 1 once in a blue moon, don't freak. unRAID has already done its job and all is fine.
Archived
This topic is now archived and is closed to further replies.