October 23, 200718 yr I'm having a problem with one of the disks on my array locking up. Anytime I try to access the disk through windows explorer I can see the file structure (Ie all the folders) but when I click on any folder the whole system locks up. This does not happen with the other disk I have running. By locks up I mean that windows explorer totally locks and after a period of time (2 to 3 mins) a pop up comes up telling me an error has occurred and I need to shutdown explorer. Of course then I have to restart the machine I am using when I accessed unraid. This disk has worked fine in the recent past and as far as I know there wasn't anything that happened to the disk to make it go screwy. I can access the web interface and it shows no errors for the problem disk. Please take a look at my syslog and let me know if there is anything out of normal. Thanks! Chris
October 23, 200718 yr Author Can't seem to upload the syslog... Here is a link: http://www.4shared.com/dir/4308078/eae84a24/sharing.html
October 24, 200718 yr Howdy Chris, I took a quick look. You booted the current session on August 30 and it ran happily until September 15 1:55am. At that time, a serious problem with the Reiser file system occurred, but it is not evident that your unRAID 4.0 was aware of it, and the drive involved is not displayed. It seemed to recover, because normal spindowns occurred, and the system continued, apparently happy, until October 21 5:30am, when an Emask Device error occurred on Disk2 (sdc). Then it ran apparently fine to the end, the next day at 12:26pm when you began connecting. There's no other indication of trouble. The problem on September 15 looks very much like a problem Tom has identified in the ReiserFS system. It looks like a fix has been found, and we will probably see a corrected version in a coming unRAID release. This problem was associated with memory corruption, and seemed to leave the system unstable, as well as possibly causing corruption of the ReiserFS structures on the disk. I think just rebooting your system will reload a fresh stable unRAID, but I would recommend running reiserfsck on each of the 2 data drives, after a reboot and stop, before starting the array again.
October 25, 200718 yr Author Thank you for your help! I ran reiserfsck as you suggested and it found 577 errors! They were all the same error "The objectid <####> is marked free, but used by an object". I'm running the --fix-fixable utility now. Thanks! Chris
October 25, 200718 yr Author Ok, so I ran the fix-fixable program and it fixed my errors. After remounting everything as per the instructions in the wiki I went back into windows explorer and looked at my disk and it seemed to be back up and running fine. However I found that if I "bounced" around from folder to folder just opening the folder then going to the next one it would take a while to go from one folder to the next until finally it locked up again just as it had before. I'm going to restart the unraid box and my local computer to see if that changes anything. Chris
November 1, 200718 yr Author Here is some more information. What I have found is that I can access Disk 1 and open most folders with out major problems. However if I open the folder that I have most of my riped movies on (located on disk 1) my explorer locks up. Explorer.exe goes to 50% CPU use then slowly builds up to 99% CPU. I first assumed that I had a problem with the desktop that I was accessing unraid from, so I tried 2 other computers in the house and got the same results. I started memtest last night just to rule out bad memory. When I get home tonight I'll stop memtest and print off the syslog. Has anyone ever seen anything like this?
Archived
This topic is now archived and is closed to further replies.