April 20, 201610 yr So basically my power went out when the server was running, when I started it up again the drive would no longer be mountable. So I took the drive out of there and connected it to a Ubuntu PC. The result when trying to mount it is the following : Error mounting /dev/sdb1 at /media/claudia/28700235-19de-48a7-b96d-6f1a845a13ef: Command-line `mount -t "btrfs" -o "uhelper=udisks2,nodev,nosuid" "/dev/sdb1" "/media/brian/28700235-19de-48a7-b96d-6f1a845a13ef"' exited with non-zero exit status 32: mount: wrong fs type, bad option, bad superblock on /dev/sdb1, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so. The disk outputs this SMART data: smartctl 6.4 2014-10-07 r4002 [x86_64-linux-4.2.0-16-generic] (local build) Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Toshiba 3.5" HDD DT01ACA... Device Model: TOSHIBA DT01ACA100 Serial Number: 53PXVK0NS LU WWN Device Id: 5 000039 ff6db358e Firmware Version: MS2OA750 User Capacity: 1.000.203.804.160 bytes [1,00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate: 7200 rpm Form Factor: 3.5 inches Device is: In smartctl database [for details use: -P show] ATA Version is: ATA8-ACS T13/1699-D revision 4 SATA Version is: SATA 3.0, 6.0 Gb/s (current: 3.0 Gb/s) Local Time is: Wed Apr 20 18:14:18 2016 CEST 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: (0x04) Offline data collection activity was suspended by an interrupting command from host. 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: ( 7215) 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: ( 1) minutes. Extended self-test routine recommended polling time: ( 121) minutes. SCT capabilities: (0x003d) 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 0x000b 100 100 016 Pre-fail Always - 0 2 Throughput_Performance 0x0005 141 141 054 Pre-fail Offline - 72 3 Spin_Up_Time 0x0007 139 139 024 Pre-fail Always - 161 (Average 169) 4 Start_Stop_Count 0x0012 100 100 000 Old_age Always - 3928 5 Reallocated_Sector_Ct 0x0033 100 100 005 Pre-fail Always - 0 7 Seek_Error_Rate 0x000b 100 100 067 Pre-fail Always - 0 8 Seek_Time_Performance 0x0005 115 115 020 Pre-fail Offline - 34 9 Power_On_Hours 0x0012 100 100 000 Old_age Always - 6085 10 Spin_Retry_Count 0x0013 100 100 060 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 2260 192 Power-Off_Retract_Count 0x0032 096 096 000 Old_age Always - 5578 193 Load_Cycle_Count 0x0012 096 096 000 Old_age Always - 5578 194 Temperature_Celsius 0x0002 171 171 000 Old_age Always - 35 (Min/Max 15/54) 196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 0 197 Current_Pending_Sector 0x0022 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0008 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x000a 200 200 000 Old_age Always - 955 SMART Error Log Version: 1 ATA Error Count: 964 (device log contains only the most recent five errors) 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 964 occurred at disk power-on lifetime: 4766 hours (198 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 11 0f 08 00 01 Error: UNC at LBA = 0x0100080f = 16779279 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 60 08 10 10 08 00 41 ff 00:04:27.612 READ FPDMA QUEUED 60 08 c0 80 ff ff 40 08 00:04:27.605 READ FPDMA QUEUED 60 20 b8 00 08 00 40 08 00:04:27.605 READ FPDMA QUEUED 60 08 b0 40 65 70 40 08 00:04:27.605 READ FPDMA QUEUED 60 08 a8 b8 63 70 40 08 00:04:27.605 READ FPDMA QUEUED Error 963 occurred at disk power-on lifetime: 4305 hours (179 days + 9 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 -- -- -- -- -- -- -- 84 51 01 e7 b0 60 00 Error: ICRC, ABRT at LBA = 0x0060b0e7 = 6336743 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 60 08 00 e7 b0 60 40 ff 00:05:57.768 READ FPDMA QUEUED 60 08 58 e0 b0 60 40 00 00:05:57.748 READ FPDMA QUEUED 60 08 50 18 b1 60 40 00 00:05:57.748 READ FPDMA QUEUED 60 08 48 d8 b0 60 40 00 00:05:57.748 READ FPDMA QUEUED 60 08 40 90 1b 61 40 00 00:05:57.747 READ FPDMA QUEUED Error 962 occurred at disk power-on lifetime: 4298 hours (179 days + 2 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 -- -- -- -- -- -- -- 84 51 41 f7 29 a9 0b Error: ICRC, ABRT at LBA = 0x0ba929f7 = 195635703 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 60 90 40 f9 29 a9 4b ff 00:03:48.517 READ FPDMA QUEUED 60 90 a8 38 2f a9 40 00 00:03:48.496 READ FPDMA QUEUED 60 00 a0 38 2e a9 40 00 00:03:48.496 READ FPDMA QUEUED 60 00 98 38 2d a9 40 00 00:03:48.496 READ FPDMA QUEUED 60 00 90 38 2c a9 40 00 00:03:48.496 READ FPDMA QUEUED Error 961 occurred at disk power-on lifetime: 2094 hours (87 days + 6 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 -- -- -- -- -- -- -- 84 51 31 79 da d4 02 Error: ICRC, ABRT 49 sectors at LBA = 0x02d4da79 = 47503993 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 40 6a da d4 40 00 00:00:34.697 READ DMA EXT 60 40 48 6a da d4 40 00 00:00:34.696 READ FPDMA QUEUED 60 20 40 ba 6c 65 40 00 00:00:34.694 READ FPDMA QUEUED 60 40 38 a2 67 65 40 00 00:00:34.694 READ FPDMA QUEUED 60 40 30 fa d5 e0 40 00 00:00:34.694 READ FPDMA QUEUED Error 960 occurred at disk power-on lifetime: 1904 hours (79 days + 8 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 -- -- -- -- -- -- -- 84 51 11 cf 0f 60 00 Error: ICRC, ABRT 17 sectors at LBA = 0x00600fcf = 6295503 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 20 c0 0f 60 e0 00 00:22:53.619 READ DMA EXT ea 00 00 00 00 00 a0 00 00:22:52.978 FLUSH CACHE EXT 35 00 08 20 3f 5e e0 00 00:22:52.978 WRITE DMA EXT 35 00 20 a0 0f 60 e0 00 00:22:52.977 WRITE DMA EXT 35 00 20 c0 3d 06 e0 00 00:22:52.977 WRITE DMA EXT 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. The command "sudo btrfs-show-super /dev/sdb" gave me this result: superblock: bytenr=65536, device=/dev/sdb --------------------------------------------------------- ERROR: bad magic on superblock on /dev/sdb at 65536 I have no experience when it comes to data recovery so please just tell me if you need any more information. Thank you beforehand, your help is really appreciated Brian
Archived
This topic is now archived and is closed to further replies.