June 18, 201313 yr This is messy. Move to separate support post or leave here? Just upgraded RC13 to 15 last night and have slight chaos. Back story: RC13 had been working well though I had never tried shutting it down. Had to leave town for a week so shut it down via GUI without visible problem. Returned yesterday to see RC15 released. Powered up server (first time since trip) but smb wasn't responding. Shut down via gui, moved flash drive to desktop and copied new image/root/cfg directly. Returned flash drive to server and booted. Gui and SMB both responding normally. Started a nc parity check. Great speeds. Returned a bit ago to find the summary: Last checked on Tue Jun 18 09:25:46 2013 PDT, finding 2 errors. Yet in the drive list above, all of the drives show 0 errors. It's been a very long time since I've seen errors after a parity check. Should the individual drive counts reflect the errors? Looking in syslog I see many identical errors for md6: Jun 18 00:xx:xx Tower1 kernel: REISERFS error (device md6): vs-5150 search_by_key: invalid format found in block 14453855. Fsck? There are hundreds of lines for every advancing second, all for the same block, making for a 130MB syslog. I've trimmed most of it in the attached log. Checking disk6 settings from the GUI shows Partition Format: unknown. I've stopped the array and could use suggestions. Unmenu is running. Hardware: Supermicro MBD-X9SCL-F-O MB, i3-2100 CPU, 4GB RAM, Supermicro AOC-SASLP-MV8 card, medley of drives syslog.txt
June 18, 201313 yr If there are no errors in the drives column, the errors are almost certainly on the parity drive. I'd simply run a correcting check to resolve them. If you want to feel more comfortable about it, you could run another nc check and confirm that you still get 2 errors -- THEN run the correcting check. The "file system: unknown" is the way v5 works when the array is stopped. This is confusing, but it's simply what it shows. With the array stopped, click on ANY of your drives and that's what you'll see.
June 18, 201313 yr This is messy. Move to separate support post or leave here? Yes, please move to "General Support [unRAID OS 5.0-rc]"
June 18, 201313 yr Author garycase: array was running when disk6 format showed as unknown, hence my concern. Other drives showed normal MBR: 4K-aligned. BTW, drives are: 3TB parity, d1-d9 all 2TB, and a 500GB cache. Could a mod please move my post and replies?
June 18, 201313 yr garycase: array was running when disk6 format showed as unknown, hence my concern. Other drives showed normal MBR: 4K-aligned. BTW, drives are: 3TB parity, d1-d9 all 2TB, and a 500GB cache. Could a mod please move my post and replies? Ahh --on a running array that's a LOT different !! I'll wait until this thread is moved before adding more. But it definitely sounds like a reiserfsck check is in order
June 19, 201313 yr Author I rebooted . The array starts on its own but Disk6 still comes up: Partition format: unknown File sytem type: reiserfs The other disks look normal with "Partition format: MBR: 4K-aligned" If I stop and start the array, Disk6 changes to format:MBR: 4K-aligned. A reiserfsck check on Disk6 says: No corruptions found There are on the filesystem: Leaves 494905 Internal nodes 2979 Directories 20601 Other files 178043 Data block pointers 469501241 (179201 of them are zero) Safe links 0 ########### reiserfsck finished at Tue Jun 18 14:07:58 2013 ########### Scratching my head here. I'm tempted to start another nc parity check but will wait for more experienced input. Last thing I want is more magic.
June 19, 201313 yr Author Interesting. Started another nc parity check. Those errors show up almost immediately. Total size: 3 TB Current position: 2.58 GB (0%) Estimated speed: 73.62 MB/sec Estimated finish: 679 minutes Sync errors corrected: 2 Again, the Device Status Errors column above is all zeroes.
June 19, 201313 yr Since the file type changed as expected, I'd simply run a correcting check ... then, after it completes, run it again to confirm you get all zeroes. Hard to say just what went wrong, but it seems all is well now & you just need to do the corrections.
June 19, 201313 yr Author Well, I had a seizure and ran that as a CORRECTING check. So, no more errors detected, whatever they were. The massive error log from last night still has me concerned. Would be nice to have some idea what might have caused the avalanche that vanished just as quickly. How much of a deal would 2 errors be? Depends on the errors, no?
Archived
This topic is now archived and is closed to further replies.