May 19, 201610 yr Community Expert Check lost+found folder, but depending on how bad corruption was there's always the chance of some data loss.
May 19, 201610 yr But what if I didn't have access to the webgui and only have the diagnostics zip file? How would I go about deciphering it? Sometimes it is straightforward, but often it's difficult, even for the most experienced. If you are interested, you can read Drive Symbols for an introduction, but it is incomplete. Currently, it's easiest to read the lsscsi report, in the system folder of the diagnostics zip. *If* the drive controller uses the ATA subsystem, then you can find the ata number in the path associated with the drive info. But many SAS and a few other controllers do not use ATA, so they don't have ata numbers and their error info is cryptic.
May 20, 201610 yr Author Thanks, will look it up.. This is the result from the long extended test, I think it completed without errors smartctl 6.2 2013-07-26 r3841 [x86_64-linux-4.1.18-unRAID] (local build) Copyright © 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Device Model: WDC WD40EFRX-68WT0N0 Serial Number: WD-WCC4EM0WN6HS LU WWN Device Id: 5 0014ee 20a945045 Firmware Version: 80.00A80 User Capacity: 4,000,787,030,016 bytes [4.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate: 5400 rpm Device is: Not in smartctl database [for details use: -P showall] ATA Version is: ACS-2 (minor revision not indicated) SATA Version is: SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s) Local Time is: Fri May 20 08:59:57 2016 SGT 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: (52680) 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: ( 527) minutes. Conveyance self-test routine recommended polling time: ( 5) minutes. SCT capabilities: (0x703d) 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 - 0 3 Spin_Up_Time 0x0027 215 182 021 Pre-fail Always - 6250 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 255 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 083 083 000 Old_age Always - 12649 10 Spin_Retry_Count 0x0032 100 100 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 100 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 102 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 66 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 1288 194 Temperature_Celsius 0x0022 116 103 000 Old_age Always - 36 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 200 200 000 Old_age Offline - 0 SMART Error Log Version: 1 ATA Error Count: 3 CR = Command Register [HEX] FR = Features Register [HEX] SC = Sector Count Register [HEX] SN = Sector Number Register [HEX] CL = Cylinder Low Register [HEX] CH = Cylinder High Register [HEX] DH = Device/Head Register [HEX] DC = Device Command Register [HEX] ER = Error register [HEX] ST = Status register [HEX] Powered_Up_Time is measured from power on, and printed as DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes, SS=sec, and sss=millisec. It "wraps" after 49.710 days. Error 3 occurred at disk power-on lifetime: 12566 hours (523 days + 14 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 78 00 f3 24 e1 Error: UNC 120 sectors at LBA = 0x0124f300 = 19198720 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- c8 00 78 00 f3 24 e1 00 6d+00:36:58.947 READ DMA c8 00 80 f0 f0 24 e1 00 6d+00:36:58.947 READ DMA c8 00 08 10 66 22 e1 00 6d+00:36:58.924 READ DMA c8 00 60 58 41 23 e1 00 6d+00:36:58.882 READ DMA Error 2 occurred at disk power-on lifetime: 12566 hours (523 days + 14 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 20 90 0a b5 eb Error: UNC 32 sectors at LBA = 0x0bb50a90 = 196414096 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- c8 00 20 90 0a b5 eb 00 6d+00:35:47.124 READ DMA c8 00 c0 78 35 b5 eb 00 6d+00:35:47.117 READ DMA c8 00 98 48 1f b5 eb 00 6d+00:35:47.116 READ DMA c8 00 08 20 1f b5 eb 00 6d+00:35:47.112 READ DMA c8 00 30 d0 0a b5 eb 00 6d+00:35:47.111 READ DMA Error 1 occurred at disk power-on lifetime: 12566 hours (523 days + 14 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 30 c0 d8 be eb Error: UNC 48 sectors at LBA = 0x0bbed8c0 = 197056704 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- c8 00 30 c0 d8 be eb 00 6d+00:34:17.937 READ DMA c8 00 28 60 cf be eb 00 6d+00:34:17.934 READ DMA c8 00 70 28 ca be eb 00 6d+00:34:17.932 READ DMA c8 00 28 d8 c8 be eb 00 6d+00:34:17.929 READ DMA c8 00 40 78 c4 be eb 00 6d+00:34:17.919 READ DMA SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Extended offline Completed without error 00% 12647 - # 2 Short offline Completed without error 00% 12637 - # 3 Short offline Completed without error 00% 12594 - 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. No errors in the disk log, so I'm going to try do a check now
May 20, 201610 yr Author Just completed the disk2 check , seems ok: ########### reiserfsck --check started at Fri May 20 09:03:23 2016 ########### 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 992369 Internal nodes 6204 Directories 225601 Other files 344023 Data block pointers 956401054 (929359 of them are zero) Safe links 0 ########### reiserfsck finished at Fri May 20 10:11:54 2016 ########### I'm going to maintenance mode and start the array to view the lost+found folder, see what I can restore. Looks like there are tons of random number files, worth 40GB. Are the files actually valid? Or are these corrupted files that has been removed from the original location? Also, seems like my TV Series folder is affected. For some reason I can't view them in SMB but I can see them within the console. Since I'm using /mnt/user/ I should still be able to see the folder from other disks as well, except maybe some from disk2. Any idea why?
May 21, 201610 yr I'm going to maintenance mode and start the array to view the lost+found folder, see what I can restore. Looks like there are tons of random number files, worth 40GB. Are the files actually valid? Or are these corrupted files that has been removed from the original location? Also, seems like my TV Series folder is affected. For some reason I can't view them in SMB but I can see them within the console. Since I'm using /mnt/user/ I should still be able to see the folder from other disks as well, except maybe some from disk2. Any idea why? Take a look at the Additional comments section. It has comments about that, and a couple of links to posts about dealing with lost+found.
May 21, 201610 yr Author I've read that, and from what I'm able to understand, the files in lost+found might not be 100% original intact file, is that right? Also, the ones in the folders are very easy to understand since the filenames are intact, but the ones at the topmost level are undecipherable, it's all numbers without file extensions (Ok, at least they grouped them together in the same number, so I know it's from that folder content or similar, not that bad!) And for some reason I can view my TV Series folder now (yay!), I think maybe it is SMB caching contents? Not sure how that works..
Archived
This topic is now archived and is closed to further replies.