August 3, 201411 yr Hi there, I have a huge problem, whereby a rebuilt was not successful because another drive was giving lots of error messages. Unbeknown to me I then started to replace the second drive thinking that the first rebuild was successful. So I now shutdown my array and I have put the drive which was red balled into another machine and powered it up with the same version of unRaid 6 Beta 6 and it appears that I can access that data when I mount it from unMenu. The original drive where the rebuild never completed does not exist anymore, so I cannot start that rebuild anymore. So I am quite sure I have lost 2 tb of data, but any help is greatly appreciated. === START OF INFORMATION SECTION === Model Family: SAMSUNG SpinPoint F4 EG (AF) Device Model: SAMSUNG HD204UI Serial Number: S2HGJ1AZ801622 LU WWN Device Id: 5 0024e9 003e6b86d Firmware Version: 1AQ10003 User Capacity: 2,000,398,934,016 bytes [2.00 TB] Sector Size: 512 bytes logical/physical Rotation Rate: 5400 rpm Device is: In smartctl database [for details use: -P show] ATA Version is: ATA8-ACS T13/1699-D revision 6 SATA Version is: SATA 2.6, 3.0 Gb/s Local Time is: Sun Aug 3 08:09:52 2014 PDT ==> WARNING: Using smartmontools or hdparm with this drive may result in data loss due to a firmware bug. ****** THIS DRIVE MAY OR MAY NOT BE AFFECTED! ****** Buggy and fixed firmware report same version number! See the following web pages for details: http://knowledge.seagate.com/articles/en_US/FAQ/223571en http://sourceforge.net/apps/trac/smartmontools/wiki/SamsungF4EGBadBlocks 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: ( 121) The previous self-test completed having the read element of the test failed. Total time to complete Offline data collection: (21420) seconds. Offline data collection capabilities: (0x5b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. No 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: ( 357) minutes. SCT capabilities: (0x003f) 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 100 100 051 Pre-fail Always - 4 2 Throughput_Performance 0x0026 252 252 000 Old_age Always - 0 3 Spin_Up_Time 0x0023 067 066 025 Pre-fail Always - 10162 4 Start_Stop_Count 0x0032 095 095 000 Old_age Always - 5854 5 Reallocated_Sector_Ct 0x0033 252 252 010 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 252 252 051 Old_age Always - 0 8 Seek_Time_Performance 0x0024 252 252 015 Old_age Offline - 0 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 6647 10 Spin_Retry_Count 0x0032 252 252 051 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 252 252 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 183 181 Program_Fail_Cnt_Total 0x0022 100 100 000 Old_age Always - 320352 191 G-Sense_Error_Rate 0x0022 100 100 000 Old_age Always - 1432 192 Power-Off_Retract_Count 0x0022 252 252 000 Old_age Always - 0 194 Temperature_Celsius 0x0002 064 054 000 Old_age Always - 31 (Min/Max 15/47) 195 Hardware_ECC_Recovered 0x003a 100 100 000 Old_age Always - 0 196 Reallocated_Event_Count 0x0032 252 252 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 100 100 000 Old_age Always - 1 198 Offline_Uncorrectable 0x0030 252 252 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0036 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x002a 100 100 000 Old_age Always - 2 223 Load_Retry_Count 0x0032 252 252 000 Old_age Always - 0 225 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 5876 SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Completed: read failure 90% 6647 2374234896 # 2 Short offline Completed: read failure 90% 6647 2374234896 SMART Selective self-test log data structure revision number 0 Note: revision number not 1 implies that no selective self-test has ever been run SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1 0 0 Completed_read_failure [90% left] (0-65535) 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.
August 3, 201411 yr The simplest (not rigorous or thorough) way to get back operational would be to set a new configuration, and let it rebuild parity with whatever it can read. Are the rest of the drives healthy?
August 3, 201411 yr At this point, I'd agree with jonathanm => set a New Config which does NOT include either of your failed drives; let it build parity so the array is protected; then do a parity check to confirm that was all successful; and THEN start data recovery from your failed drives. IF you happen to have backups [You should of course, but many folks don't ... you may want to read this: http://lime-technology.com/forum/index.php?topic=31020.0 ], the "recovery" is trivial: just copy the missing data from your backups. I gather from your comments ("... have a huge problem." and "... I am quite sure I have lost 2 tb of data") that you do NOT have backups; so what you'll want to do after you have a good array is connect the drive that still has data on it to a Windows PC, install the free Linux Reader [ http://www.diskinternals.com/linux-reader/ ], and then copy the files from that drive back to your server [if you need more disk space, you'll have to first add another data drive to the server]. You may want to re-think your backup strategy so this doesn't happen again
August 3, 201411 yr Note: If you don't have a Windows PC to use, you can also attach the drive with the data you want to copy to any other old spare PC; boot a free version of UnRAID and assign that drive to that version as a data drive (with no parity drive) ... and then just copy the data from that UnRAID server to your primary one. Note that if you do this, you need to be sure you change the name of the UnRAID server [You can't have two "Tower" systems]
September 8, 201411 yr Author ok I have now started the new configuration with 3 drives removed and 3 new drives inserted and started the rebuild, which has started. but am I meant to see the contents of my shares? I see see on under /diskxx the data but not under //tower/sharename... is that normal? is this normally caused by cable issues? Sep 8 12:47:59 Tower kernel: REISERFS error (device md14): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [7175 10213 0x0 SD] Sep 8 12:47:59 Tower kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 14247 does not match to the expected one 3 Sep 8 12:47:59 Tower kernel: REISERFS error (device md14): vs-5150 search_by_key: invalid format found in block 373216999. Fsck? Sep 8 12:47:59 Tower kernel: REISERFS error (device md14): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [9874 9875 0x0 SD] Sep 8 12:47:59 Tower kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 25565 does not match to the expected one 2 Sep 8 12:47:59 Tower kernel: REISERFS error (device md14): vs-5150 search_by_key: invalid format found in block 353699823. Fsck? Sep 8 12:47:59 Tower kernel: REISERFS error (device md14): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [7175 10213 0x0 SD] Sep 8 12:47:59 Tower kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 14247 does not match to the expected one 3 Sep 8 12:47:59 Tower kernel: REISERFS error (device md14): vs-5150 search_by_key: invalid format found in block 373216999. Fsck? Sep 8 12:47:59 Tower kernel: REISERFS error (device md14): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [9874 9878 0x0 SD] should I be stopping parity sync Sep 8 12:31:51 Tower shfs/user: shfs_readdir: fstatat: Boss (13) Permission denied (Drive related) Sep 8 12:31:51 Tower shfs/user: shfs_readdir: readdir_r: /mnt/disk14/series (13) Permission denied Sep 8 12:31:51 Tower kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 31632 does not match to the expected one 1 (Minor Issues) Sep 8 12:31:51 Tower kernel: REISERFS error (device md14): vs-5150 search_by_key: invalid format found in block 301802752. Fsck? (Errors) Sep 8 12:31:51 Tower kernel: REISERFS error (device md14): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [723 1108 0x0 SD] (Errors) Sep 8 12:33:01 Tower shfs/user: shfs_readdir: fstatat: Boss (13) Permission denied (Drive related) Sep 8 12:33:01 Tower shfs/user: shfs_readdir: readdir_r: /mnt/disk14/series (13) Permission denied Sep 8 12:33:01 Tower kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 31632 does not match to the expected one 1 (Minor Issues) Sep 8 12:33:01 Tower kernel: REISERFS error (device md14): vs-5150 search_by_key: invalid format found in block 301802752. Fsck? (Errors) Sep 8 12:33:01 Tower kernel: REISERFS error (device md14): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [723 1108 0x0 SD] (Errors) Sep 8 12:33:54 Tower sshd[4302]: Accepted password for root from 192.168.0.7 port 55712 ssh2 Sep 8 12:34:35 Tower shfs/user: shfs_readdir: fstatat: Boss (13) Permission denied (Drive related) Sep 8 12:34:35 Tower shfs/user: shfs_readdir: readdir_r: /mnt/disk14/series (13) Permission denied how can it get permission denied? syslog-2014-09-08.zip
Archived
This topic is now archived and is closed to further replies.