September 7, 201213 yr Hello, I am running latest rc5 and have been a happy unraid user for 2 years, very few issues. I have developed a problem in the last two weeks that I cannot seem to fix. I have 7 2Tb WD Green drives and 1 WD Black as my parity. If i run a Parity Sync it all starts and seems to run - but somewhere between 60 and 100% the system becomes unresponsive. If I reboot, then (sometimes) the web page will start, but most often it will not. The shares are active however. After trying many things to resolve the issue, I totally reset my USB stick to clean install and reconfigured unraid without any add ons or extras. I ran a parity sync, but the following morning - same issue - and now if i reboot i cannot get into the web page, and the shares are there on SMB but not NFS. I tried unmounting the drives so I would do a reisercheck on each drive, but i cannot unmount. When I type /usr/bin/fuser -mv /mnt/disk* /mnt/user/* to see why i can't umount, i get this for each share - seems to be a lot of connections, but no idea at all why /mnt/user/Software: nobody 7891 ..c.. smbd nobody 7892 ..c.. smbd nobody 7893 f.c.. smbd nobody 7894 ..c.. smbd nobody 7895 ..c.. smbd nobody 7896 f.c.. smbd nobody 7897 ..c.. smbd nobody 7898 ..c.. smbd xbmc 7999 F.c.. smbd xbmc 8004 ..c.. smbd xbmc 8005 ..c.. smbd xbmc 8023 ..c.. smbd xbmc 8024 ..c.. smbd nobody 8073 ..c.. smbd nobody 8074 ..c.. smbd nobody 8075 f.c.. smbd nobody 8076 ..c.. smbd nobody 8077 ..c.. smbd nobody 8078 f.c.. smbd nobody 8079 ..c.. smbd nobody 8080 ..c.. smbd nobody 8191 ..c.. smbd nobody 8192 ..c.. smbd nobody 8193 f.c.. smbd nobody 8194 ..c.. smbd nobody 8195 ..c.. smbd nobody 8196 f.c.. smbd nobody 8197 ..c.. smbd nobody 8198 ..c.. smbd nobody 8309 ..c.. smbd nobody 8310 ..c.. smbd nobody 8311 f.c.. smbd nobody 8312 ..c.. smbd nobody 8313 ..c.. smbd nobody 8314 f.c.. smbd nobody 8315 ..c.. smbd nobody 8316 ..c.. smbd Could anyone advise me how to proceed with troubleshooting so i can get my unraid working perfectly again? Thanks Jon
September 8, 201213 yr Author Yeah, and i can't understand why - I have 5 XBMC clients and then a couple of VMs - but nothing like that much access - and all my access is now NFS. Jon
September 8, 201213 yr Author Ok, I installed version: 5.0-rc6-r8168-test last night and have now got the array up in Maintenance mode and am running through reiser checking all my drives. Jon
September 8, 201213 yr Author Looks like md3 is failing - busy copying everything off it now.... reiserfsck --fix-fixable started at Sat Sep 8 10:04:39 2012 ########### Replaying journal: Done. Reiserfs journal '/dev/md3' in blocks [18..8211]: 0 transactions replayed Checking internal tree.. finished Comparing bitmaps..finished Checking Semantic tree: ... l Girl/Season 02/Secret Diary of a Call Girl - 2x05 - Episode 5 - HD TV.mkv The problem has occurred looks like a hardware problem. If you have bad blocks, we advise you to get a new hard drive, because once you get one bad block that the disk drive internals cannot hide from your sight,the chances of getting more are generally said to become much higher (precise statistics are unknown to us), and this disk drive is probably not expensive enough for you to you to risk your time and data on it. If you don't want to follow that follow that advice then if you have just a few bad blocks, try writing to the bad blocks and see if the drive remaps the bad blocks (that means it takes a block it has in reserve and allocates it for use for of that block number). If it cannot remap the block, use badblock option (-B) with reiserfs utils to handle this block correctly. bread: Cannot read the block (487983026): (Input/output error). Aborted
Archived
This topic is now archived and is closed to further replies.