Holender Posted December 18, 2017 Share Posted December 18, 2017 Hi All, Please feel free to call me a whatever, I have buggered my array pretty badly and it's because I was rushing. Two weeks ago I lost a drive, for a number of reasons I couldn't get a replacement drive until early last week and because it's one of the primary media sources in the house the down time was getting on everyone's nerves. Got the replacement drive, ran the pre-clear which finished the night before I was leaving on a three day course. Perfect I thought, this will be up and running before I leave and I won't continue to hear complaining. Well, it had been a few years since I lost a drive and was sure I knew what I was doing (WRONG).When I mounted the new drive it came up as "drive is unmountable". Shoot... now what did I miss? Oh the "Format" button, I must have to do that before rebuilding the disk. Well.... as you all know I formated the data from my Disk 5 right off the parity drive too. Wasn't until I came back last night that my wife let me know a bunch of things were missing that I put it all together. Am I SOL? Version 6.3.5 File system on the drive was xfs I do have the old disk, which also was "drive is unmountable". I tried a couple things to get it back up and running, new cable and eviewed the SMART report (said nothing was wrong) but with limited time figured I'd buy a new drive, use it to replace the unmountable one and when I had some free time after the holiday's I'd see if I could do anything with it. Even if I could get the original disk to be recognized, because the parity data is gone can I use that disk to rebuild? Thanks in advance. Link to comment
JorgeB Posted December 18, 2017 Share Posted December 18, 2017 Post a SMART report for the old disk. Link to comment
Holender Posted December 18, 2017 Author Share Posted December 18, 2017 tower-smart-20171218-1343.zip Wasn't sure of format, so I did all of them. Thank you! smartctl 6.5 2016-05-07 r4318 [x86_64-linux-4.9.30-unRAID] (local build) Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Seagate Desktop HDD.15 Device Model: ST4000DM000-1F2168 Serial Number: Z304T7JJ LU WWN Device Id: 5 000c50 086d56e13 Firmware Version: CC54 User Capacity: 4,000,787,030,016 bytes [4.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate: 5900 rpm Form Factor: 3.5 inches Device is: In smartctl database [for details use: -P show] ATA Version is: ACS-2, ACS-3 T13/2161-D revision 3b SATA Version is: SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s) Local Time is: Mon Dec 18 13:44:23 2017 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: ( 107) seconds. Offline data collection capabilities: (0x73) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. No 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: ( 1) minutes. Extended self-test routine recommended polling time: ( 508) minutes. Conveyance self-test routine recommended polling time: ( 2) minutes. SCT capabilities: (0x1085) SCT Status supported. SMART Attributes Data Structure revision number: 10 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 115 099 006 Pre-fail Always - 1841752 3 Spin_Up_Time 0x0003 093 092 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 097 097 020 Old_age Always - 3082 5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 078 060 030 Pre-fail Always - 59420851 9 Power_On_Hours 0x0032 082 082 000 Old_age Always - 16580 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 97 183 Runtime_Bad_Block 0x0032 100 100 000 Old_age Always - 0 184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0 188 Command_Timeout 0x0032 100 100 000 Old_age Always - 0 0 0 189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0 190 Airflow_Temperature_Cel 0x0022 074 052 045 Old_age Always - 26 (Min/Max 23/26) 191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 0 192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 702 193 Load_Cycle_Count 0x0032 042 042 000 Old_age Always - 116362 194 Temperature_Celsius 0x0022 026 048 000 Old_age Always - 26 (0 11 0 0 0) 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 10530h+55m+33.240s 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 25458218144 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 177882296397 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. ST4000DM000-1F2168_Z304T7JJ-20171218-1343.txt Link to comment
JorgeB Posted December 18, 2017 Share Posted December 18, 2017 SMART looks fine, assuming you have it connect but unassigned you can run xfs_repair on it and if successful mount with the UD plugin, then copy all data to the new disk: xfs_repair -v /dev/sdX1 replace X with the correct letter, don't forget the 1 in the end. Link to comment
pwm Posted December 18, 2017 Share Posted December 18, 2017 The file system might be broken, but there isn't anything wrong physically with the drive. So there is a good chance that you may be able to repair the file system and recover all or much of the files. Preferably I would recommend making a binary copy of the data before starting the repair/recover process since I get the feeling the drive contains information you don't have backup of. Link to comment
Holender Posted December 18, 2017 Author Share Posted December 18, 2017 17 minutes ago, johnnie.black said: SMART looks fine, assuming you have it connect but unassigned you can run xfs_repair on it and if successful mount with the UD plugin, then copy all data to the new disk: Well....here comes some more stupidity (can't solve stupid I know). Before posting I read a couple things and put the old drive in, assigned it to it's old location and started the array which instantly went into a check. I canceled it , shut down the array and started in maintenance mode which is where it currently sits. Have i ruined my chances of running xfs_repair? Also: I'm guessing the "UD plugin" is the "unassigned device" plugin which I've installed. Are there any specific instructions? because it looks like a dummy like me can do more harm than good with that tool. 27 minutes ago, pwm said: Preferably I would recommend making a binary copy of the data before starting the repair/recover process since I get the feeling the drive contains information you don't have backup of. Can't seem to find any into on making a "binary copy", is there a tool or a guide? and.... THANK YOU both of you! I'm not normally this destructive and impulsive with my server. Link to comment
pwm Posted December 18, 2017 Share Posted December 18, 2017 The traditional way to repair if you really worry about the contents of a disk is to use live CD/USB Linux distribution and boot with and to copy all the data to a USB drive. Then do all the repair attempts on the USB drive. In the majority of cases, this extra step isn't needed and just wastes lots of time. But sometimes it's better to have that additional safety margin and performing the recovery operations on a backup copy of the data. Link to comment
Holender Posted December 18, 2017 Author Share Posted December 18, 2017 12 minutes ago, pwm said: The traditional way to repair if you really worry about the contents of a disk is to use live CD/USB Linux distribution and boot with and to copy all the data to a USB drive. Then do all the repair attempts on the USB drive. Does it need to be a live CD/USB? I run ubuntu on my desktop. Could I simply install the drive in there and copy the files to a USB? I really don't need much off the drive, the media can be replaced, it's the pictures of my kids I'm trying to recover (which is why I run an unraid server in the first place, unfortunately it doesn't have a idiot filter built in) Link to comment
pwm Posted December 18, 2017 Share Posted December 18, 2017 It's a question of available tools. unRAID itself has enough tools to make a backup copy - assuming the hardware has a suitable USB port. It's just that there exists disc duplication/recovery installations like SystemRescueCd, Gparted that contains a number of useful tools already installed. Link to comment
JorgeB Posted December 18, 2017 Share Posted December 18, 2017 31 minutes ago, Holender said: Well....here comes some more stupidity (can't solve stupid I know). Before posting I read a couple things and put the old drive in, assigned it to it's old location and started the array which instantly went into a check. I canceled it , shut down the array and started in maintenance mode which is where it currently sits. Have i ruined my chances of running xfs_repair? Most likely, it depends for how long it ran, but a few seconds are enough to make almost impossible to recover with xfs_repair, and if it doesn't your best bet it to use a file recover utility like UFS Explorer. 34 minutes ago, Holender said: Also: I'm guessing the "UD plugin" is the "unassigned device" plugin which I've installed Yes, but only if xfs_repair works Link to comment
JonathanM Posted December 18, 2017 Share Posted December 18, 2017 If I read the subtext correctly, he's already got an almost complete binary copy of the unmountable drive that was built when he replaced the old drive. For data recovery purposes, formatting is just another hurdle, most if not all of the data is probably there. I'd start by running recovery tools on the new rebuilt disk to see if there was something of value there. Link to comment
Holender Posted December 18, 2017 Author Share Posted December 18, 2017 I ran xfs_repair and then used the UD Plugin to view what is on the disk. It appears when I mounted the old disk for those few seconds it repaired it as the new disk, as johnnie.black had predicted. There was only 6GB of files on there and all new since me replacing the drive and later realizing my error. I"ll admit, I'm fairly Linux illiterate so I don't know if some of the other suggestions above can still help me. Should I be looking at something like UFS Explorer to recover my files as johnnie.black suggested? You guys are awesome, thank you! Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.