December 3, 20223 yr I have had a 4TB on my main desktop Hackintosh for 5-10 yrs that has failed while I updated the macOS from Mojave to Monterey. I unplugged the drive until I got the boot drive working well and then tried to hook it back up. I got a message that was something like "Disk is not readable, unable to initialize." Luckily I mounted it on Unraid and backed it up a few months ago. Do you know if I can repair it or recover the data? --- I can't quite remember, but I think it is formatted as HFS+ (Journalled), or APFS. I am a noobie with Unraid, but I have looked at it in "scrutiny" and Tools->UnraidOS->Dianostics & System Devices In Main (there is no option to mount this disk, only an option to format). I have the feeling that there are a lot more tools, apps, and plugins that might be able to help. Is there any possibility to get the drive working again or to recover the data from these last few months? Thanks --- I go to Main Dev 1 -> Self-Test - > Download SMART Report and click Download and it gives me this txt below the "---": --- smartctl 7.3 2022-02-28 r5338 [x86_64-linux-5.19.14-Unraid] (local build) Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Device Model: ST4000DM005 Serial Number: ZDH0ZL81 LU WWN Device Id: 5 000c50 0a2390001 Firmware Version: 0001 User Capacity: 4,000,787,030,016 bytes [4.00 TB] Sector Size: 512 bytes logical/physical Rotation Rate: 7200 rpm Device is: Not in smartctl database 7.3/5405 ATA Version is: ATA8-ACS T13/1699-D revision 4 SATA Version is: SATA 3.0, 6.0 Gb/s Local Time is: Sat Dec 3 07:29:36 2022 PST SMART support is: Available - device has SMART capability. SMART support is: Enabled AAM feature is: Unavailable APM feature is: Unavailable Rd look-ahead is: Enabled Write cache is: Enabled DSN feature is: Unavailable ATA Security is: Disabled, NOT FROZEN [SEC1] Read SCT Status failed: scsi error badly formed scsi parameters Wt Cache Reorder: Unknown (SCT Feature Control command failed) Read SMART Data failed: scsi error badly formed scsi parameters === START OF READ SMART DATA SECTION === SMART Status command failed: scsi error badly formed scsi parameters SMART overall-health self-assessment test result: UNKNOWN! SMART Status, Attributes and Thresholds cannot be read. Read SMART Log Directory failed: scsi error badly formed scsi parameters ATA_READ_LOG_EXT (addr=0x00:0x00, page=0, n=1) failed: scsi error badly formed scsi parameters Read GP Log Directory failed SMART Extended Comprehensive Error Log (GP Log 0x03) not supported Read SMART Error Log failed: scsi error badly formed scsi parameters SMART Extended Self-test Log (GP Log 0x07) not supported Read SMART Self-test Log failed: scsi error badly formed scsi parameters Selective Self-tests/Logging not supported Read SCT Status failed: scsi error badly formed scsi parameters Read SCT Status failed: scsi error badly formed scsi parameters SCT (Get) Error Recovery Control command failed Device Statistics (GP/SMART Log 0x04) not supported Pending Defects log (GP Log 0x0c) not supported ATA_READ_LOG_EXT (addr=0x11:0x00, page=0, n=1) failed: scsi error badly formed scsi parameters Read SATA Phy Event Counters failed
December 3, 20223 yr Author I'll give it a go because I got a replacement drive. I could copy it onto that. Might there be a way to determine precisely what file system the broken drive is? That way, I can format the new drive, so it's the same. Or should I always go for APFS if I am above only using macOS > v11. (Monterey or Ventura)? Thanks
December 3, 20223 yr Author Would ddrescue automatically format the destination drive the same FS as the source drive? Edited December 3, 20223 yr by ra_bliss
December 3, 20223 yr Community Expert 58 minutes ago, ra_bliss said: Would ddrescue automatically format the destination drive the same FS as the source drive? No need to format, it works at a lower level than the filesystem. So the filesystem is copied.
December 3, 20223 yr Author Ok great. I am pre-clearing the new 8tb first to see if it breaks, then I will just do a basic ddrescue -f /dev/sdX_*source* /dev/sdY_*dest* /boot/ddrescue.log Wish Me Luck ALSO Are there any checksums or data recovery tools that are especially good for APFS and HFS+(Journaled)? I want to maximize the data recovered. Are there any extra tricks or steps after, like giving it a way to be able to figure out bad sectors with checksums or anything?
December 3, 20223 yr Author Still waiting on the Pre-Clear. But I remembered something that might be related, but also maybe not. I think this error window popped up the first time I plugged the failing drive back into my hackintosh and disconnecting it to work on the boot drive. Does anyone know what this means? Can anyone tell me if it's possible their related problems? Thanks " Legacy System Extension Existing software on your system loaded a system extension signed by "EDSS GLOBAL COMPANY LIMITED" which will be incompatible with a future version of macOS. Contact the developer for support. "
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.