February 5, 201511 yr I have a problem that appears virtually identical to this one: http://lime-technology.com/forum/index.php?topic=36623.msg340350#msg340350 However, i didn't end up replacing the drive, but since it passed a long smart test, i decided to rebuild the drive. It seemed ok for the first couple of days, but now i have come to see that there is a whole share that's empty (that is, the share reports 0 files, but when i navigate to each of my 5 drives, i can see the files on each). I had thought that i needed to replace the drive, so i bought a spare and can swap it in right away if needed. I following the guidance in the link above, first trying to reset the the permissions (didn't help.) I then restarted the array in maintenance mode and ran the "reiserfsck --check /dev/md2" command. Output attached. (it's actually still running, but the output is clear to me that there is a problem.) so...any thoughts if this drive is just borked and should be tossed? Or is there anything to do to try to fix it? I assume that I can drop in a new replacement drive and i'll render these errors moot, but please let me know if i need to do anything when swapping drives to get things to work right. thanks Matt syslog-2015-02-04.zip reiserfsck.txt
February 7, 201511 yr Author Hi - thanks. I captured as much of the output as I could. The first part was lost (couldn't scroll back far enough to get it), but hopefully the last part is what you need. Matt reiserfsck.txt
February 7, 201511 yr Author OK, it's running now and seeming to correct things. What will be the next step(s) when it's done?
February 8, 201511 yr Author ok, thanks for the help. Will do. Question - is it likely that this drive will continue to have problems? Or can this procedure fix things up "good as new"? As I mentioned, I do have another drive that is precleared and ready to go, and I could just swap that one in and let unraid rebuild it. If it's likely that going through this will get things back to normal, then that's fine. However, I'm just wondering if it's worth the effort if it's still going to be a problem drive. I know you don't have a crystal ball; just looking for gut reaction. thanks again, Matt
February 8, 201511 yr Author OK, looks like it finished up. There is a small list of files that had issues, it appears, but none of which would appear to be a problem for me if they were lost. Tower login: root Linux 3.9.6p-unRAID. root@Tower:~# reiserfsck --rebuild-tree /dev/md2 reiserfsck 3.6.21 (2009 www.namesys.com) ************************************************************* ** Do not run the program with --rebuild-tree unless ** ** something is broken and MAKE A BACKUP before using it. ** ** If you have bad sectors on a drive it is usually a bad ** ** idea to continue using it. Then you probably should get ** ** a working hard drive, copy the file system from the bad ** ** drive to the good one -- dd_rescue is a good tool for ** ** that -- and only then run this program. ** ** 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 rebuild the filesystem (/dev/md2) tree Will put log info to 'stdout' Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes Replaying journal: Done. Reiserfs journal '/dev/md2' in blocks [18..8211]: 0 transactions replayed ########### reiserfsck --rebuild-tree started at Sat Feb 7 14:08:28 2015 ########### Pass 0: ####### Pass 0 ####### Loading on-disk bitmap .. ok, 550011139 blocks marked used Skipping 30567 blocks (super block, journal, bitmaps) 549980572 blocks will be read 0%block 5325570: The number of items (15) is incorrect, should be (1) - corrected block 5325570: The free space (0) is incorrect, should be (208) - corrected pass0: vpf-10110: block 5325570, item (0): Unknown item type found [0 65280 0x11 (15)] - deleted block 5332624: The number of items (65279) is incorrect, should be (1) - corrected block 5332624: The free space (65519) is incorrect, should be (4048) - corrected pass0: block 5332624, item 0: StatData item of wrong length found 1044464 16711680 0x0 SD (0), len 0, location 4096 entry count 0, fsck need 14, format BAD - deleted .block 436313337: The number of items (4080) is incorrect, should be (1) - corrected block 436313337: The free space (0) is incorrect, should be (3792) - corrected pass0: vpf-10110: block 436313337, item (0): Unknown item type found [268435456 16777247 0x101020 (15)] - deleted block 436318802: The number of items (4096) is incorrect, should be (1) - corrected block 436318802: The free space (0) is incorrect, should be (4048) - corrected pass0: vpf-10110: block 436318802, item (0): Unknown item type found [15728880 16 0xf00f0000 (15)] - deleted block 436329816: The number of items (4079) is incorrect, should be (1) - corrected block 436329816: The free space (8720) is incorrect, should be (3792) - corrected pass0: vpf-10210: block 436329816, item 0: The item with wrong offset or length found [4043312912 15786208 0x1100e0f0001011 DRCT (2)], len 256 - deleted block 436332449: The number of items (4096) is incorrect, should be (1) - corrected block 436332449: The free space (4127) is incorrect, should be (4047) - corrected pass0: vpf-10110: block 436332449, item (0): Unknown item type found [4026531841 287310560 0xef00f00 (15)] - deleted block 436336723: The number of items (3840) is incorrect, should be (1) - corrected block 436336723: The free space (0) is incorrect, should be (208) - corrected pass0: vpf-10200: block 436336723, item 0: The item [983040 268435456 0x10000fe00000100 IND (1)] with wrong offset is deleted block 436338366: The number of items (15) is incorrect, should be (1) - corrected block 436338366: The free space (0) is incorrect, should be (3792) - corrected pass0: vpf-10110: block 436338366, item (0): Unknown item type found [4026531855 65280 0x1 (15)] - deleted block 436339793: The number of items (4112) is incorrect, should be (1) - corrected block 436339793: The free space (240) is incorrect, should be (4048) - corrected pass0: block 436339793, item 0: StatData item of wrong length found 1048816 983041 0x0 SD (0), len 0, location 4096 entry count 4352, fsck need 0, format new - deleted block 436353755: The number of items (4128) is incorrect, should be (1) - corrected block 436353755: The free space (4353) is incorrect, should be (208) - corrected pass0: vpf-10200: block 436353755, item 0: The item [252645360 268443408 0x1210000f0e0ff0f IND (1)] with wrong offset is deleted block 436355481: The number of items (4097) is incorrect, should be (1) - corrected block 436355481: The free space (3840) is incorrect, should be (4048) - corrected pass0: block 436355481, item 0: StatData item of wrong length found 269488112 15728640 0x0 SD (0), len 0, location 4096 entry count 0, fsck need 0, format BAD - deleted block 436363087: The free space (240) is incorrect, should be (4048) - corrected pass0: vpf-10110: block 436363087, item (0): Unknown item type found [61440 0 0x10010 (15)] - deleted block 436371910: The number of items (256) is incorrect, should be (1) - corrected block 436371910: The free space (0) is incorrect, should be (208) - corrected pass0: vpf-10110: block 436371910, item (0): Unknown item type found [16715536 4042260480 0x1121100f (15)] - deleted block 436373695: The number of items (288) is incorrect, should be (1) - corrected block 436373695: The free space (1) is incorrect, should be (3792) - corrected pass0: vpf-10110: block 436373695, item (0): Unknown item type found [33751552 536875025 0xd0d00210100000f (14)] - deleted block 436374079: The number of items (4097) is incorrect, should be (1) - corrected block 436374079: The free space (16) is incorrect, should be (4048) - corrected pass0: vpf-10110: block 436374079, item (0): Unknown item type found [4042260480 987152 0xf000 (15)] - deleted block 436390128: The number of items (4079) is incorrect, should be (1) - corrected block 436390128: The free space (4096) is incorrect, should be (3792) - corrected pass0: vpf-10200: block 436390128, item 0: The item [536936494 32633072 0x100100e301000 IND (1)] with wrong offset is deleted block 436395115: The number of items (3840) is incorrect, should be (1) - corrected block 436395115: The free space (0) is incorrect, should be (3792) - corrected pass0: vpf-10110: block 436395115, item (0): Unknown item type found [285216527 4042260497 0x10000 (15)] - deleted block 436396314: The number of items (7951) is incorrect, should be (1) - corrected block 436396314: The free space (0) is incorrect, should be (4048) - corrected pass0: vpf-10110: block 436396314, item (0): Unknown item type found [65794 16781312 0x101f1 (15)] - deleted block 436403978: The number of items (61441) is incorrect, should be (1) - corrected block 436403978: The free space (1) is incorrect, should be (4048) - corrected pass0: vpf-10110: block 436403978, item (0): Unknown item type found [66049 268435456 0x10001 (15)] - deleted block 436413876: The number of items (14) is incorrect, should be (1) - corrected block 436413876: The free space (241) is incorrect, should be (208) - corrected pass0: vpf-10150: block 436413876: item 0: Wrong key [1052673 0 0x110 SD (0)], deleted block 436415990: The number of items (241) is incorrect, should be (1) - corrected block 436415990: The free space (65535) is incorrect, should be (208) - corrected pass0: vpf-10110: block 436415990, item (0): Unknown item type found [31 251658513 0x10000000 (15)] - deleted block 436417997: The number of items (7936) is incorrect, should be (1) - corrected block 436417997: The free space (4096) is incorrect, should be (4048) - corrected pass0: vpf-10110: block 436417997, item (0): Unknown item type found [4026593520 1052687 0xff00 (15)] - deleted block 436428393: The number of items (4097) is incorrect, should be (1) - corrected block 436428393: The free space (0) is incorrect, should be (4048) - corrected pass0: vpf-10110: block 436428393, item (0): Unknown item type found [15 269484032 0xf100 (15)] - deleted left 0, 27185 /secc 39380 directory entries were hashed with "r5" hash. "r5" hash is selected Flushing..finished Read blocks (but not data blocks) 549980572 Leaves among those 545775 - leaves all contents of which could not be saved and deleted 32 Objectids found 39382 Pass 1 (will try to insert 545743 leaves): ####### Pass 1 ####### Looking for allocable blocks .. finished 0%....20%....40%....60%....80%....100% left 0, 64 /sec Flushing..finished 545743 leaves read 545669 inserted - pointers in indirect items pointing to metadata 6 (zeroed) 74 not inserted non-unique pointers in indirect items (zeroed) 8847 ####### Pass 2 ####### Pass 2: 0%....20%....40%....60%....80%....100% left 0, 1 /sec Flushing..finished Leaves inserted item by item 74 Pass 3 (semantic): ####### Pass 3 ######### /TVrebuild_semantic_pass: The entry [175 28123] ("StorageWars-WhoLettheDavesOut-19844865-0.incommercial") in directory [2 175] points to nowhere - is removed /TooCute-FluffyPuppiesandBabyGoats-20280116-0.mpgvpf-10680: The file [175 28249] has the wrong block count in the StatData (6907232) - corrected to (6906768) /StorageWars-ASanMarcosMitzvah-19281570-0.mpgvpf-10680: The file [175 4138] has the wrong block count in the StatData (1456792) - corrected to (464) /TV/AlaskaBattleontheBay-LettheBattleBegin-20012754-0.mpgvpf-10680: The file [175 4105] has the wrong block count in the StatData (1732808) - corrected to (1701768) /TV/NBCNightlyNews-20151645-0.mpgvpf-10680: The file [175 28256] has the wrong block count in the StatData (6679680) - corrected to (6675784) /TV/TooCute-PuppyLove-20280110-0.mpgvpf-10680: The file [175 26716] has the wrong block count in the StatData (7051272) - corrected to (7032584) /AlaskaBattleontheBay-LettheBattleBegin-20012754-0.incommercialvpf-10670: The file [175 26763] has the wrong size in the StatData (3) - corrected to (6948339712) vpf-10680: The file [175 26763] has the wrong block count in the StatData ( - corrected to (4602712) /TVvpf-10650: The directory [2 175] has the wrong size in the StatData (107696) - corrected to (107688) /Personal/PBX/bulkext__1409524457192.168.1.5.csvvpf-10680: The file [683 4081] has the wrong block count in the StatData ( - corrected to (0) /Personal/SonosInstallv1.0.0.117.ziprewrite_file: 2 items of file [683 4055] moved to [683 27112] vpf-10680: The file [683 27112] has the wrong block count in the StatData (3904) - corrected to (3896) The entry [683 4055] ("SonosInstallv1.0.0.117.zip") in directory [2 683] updated to point to [683 27112] Flushing..finished Files found: 38443 Directories found: 937 Broken (of files/symlinks/others): 1 Files with fixed size: 1 Names pointing to nowhere (removed): 1 Objects having used objectids: 1 files fixed 1 Pass 3a (looking for lost dir/files): ####### Pass 3a (lost+found pass) ######### Looking for lost directories: Flushing..finished02, 47 /sec Pass 4 - finished done 546706, 37 /sec Deleted unreachable items 1 Flushing..finished Syncing..finished ########### reiserfsck finished at Sun Feb 8 02:16:03 2015 ########### root@Tower:~#
February 8, 201511 yr Author OK, looks good (to me). Do I now restart the array? 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 ########### reiserfsck --check started at Sun Feb 8 13:50:35 2015 ########### 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 546833 Internal nodes 3421 Directories 937 Other files 38444 Data block pointers 550559190 (1127795 of them are zero) Safe links 0 ########### reiserfsck finished at Sun Feb 8 15:43:24 2015 ########### root@Tower:~#
February 9, 201511 yr Author OK, thanks. Seems like everything is back in place now. thanks for all your help. Did you have any thoughts about the questions previously regarding whether or not this is signaling some impending doom on this drive?
February 10, 201511 yr Author MyMain Syslog smartctl -a -d ata /dev/sdg (disk2) smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build) Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Device Model: WDC WD30EFRX-68AX9N0 Serial Number: WD-WMC1T3159706 Firmware Version: 80.00A80 User Capacity: 3,000,592,982,016 bytes Device is: Not in smartctl database [for details use: -P showall] ATA Version is: 9 ATA Standard is: Exact ATA specification draft version not indicated Local Time is: Mon Feb 9 19:56:21 2015 EST SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x00) Offline data collection activity was never started. Auto Offline Data Collection: Disabled. Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: (39720) seconds. Offline data collection capabilities: (0x7b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. Conveyance Self-test supported. Selective Self-test supported. SMART capabilities: (0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability: (0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time: ( 2) minutes. Extended self-test routine recommended polling time: ( 255) minutes. Conveyance self-test routine recommended polling time: ( 5) minutes. SCT capabilities: (0x70bd) SCT Status supported. SCT Error Recovery Control supported. SCT Feature Control supported. SCT Data Table supported. SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 1 3 Spin_Up_Time 0x0027 179 179 021 Pre-fail Always - 6025 4 Start_Stop_Count 0x0032 098 098 000 Old_age Always - 2465 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 9 Power_On_Hours 0x0032 082 082 000 Old_age Always - 13283 10 Spin_Retry_Count 0x0032 100 100 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 44 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 14 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 2450 194 Temperature_Celsius 0x0022 120 112 000 Old_age Always - 30 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 100 253 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 100 253 000 Old_age Offline - 0 SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 1 No self-tests have been logged. [To run self-tests, use: smartctl -t] SMART Selective self-test log data structure revision number 1 SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1 0 0 Not_testing 2 0 0 Not_testing 3 0 0 Not_testing 4 0 0 Not_testing 5 0 0 Not_testing Selective self-test flags (0x0): After scanning selected spans, do NOT read-scan remainder of disk. If Selective self-test is pending on power-up, resume after 0 minute delay.
February 10, 201511 yr Nothing seems to be throwing up red flags in that SMART report. I would think that the drive is safe to use.
February 10, 201511 yr Nothing seems to be throwing up red flags in that SMART report. I would think that the drive is safe to use. +1
Archived
This topic is now archived and is closed to further replies.