Attempt of to repair a HDD causes reboot kernel panic


macrumors member
Original poster
Oct 29, 2008
Hi! I have an external HDD Seagate st1000m035 1TB that I use to backups. Carbon Copy stop making backups and I realize one of it's partitions just gone. The other one is inaccessible, but still there. So I am trying to fix this HDD in several ways, but when I tried to use Disk Utility to test and repair, the os eventually hang and reboot.

I tried to connect using the original USB-SATA interface and another one. Same problem. I didn't try anymore after second time because this kind of trouble make me nervous, I am already without a backup! This HDD will be garbage, probably. But I though you might be interested in the case. So the report is above, I am open to suggestions.

Anonymous UUID: 5D622C4B-9B9A-1324-5B1E-10A7B6CBB1AA

Mon Feb 25 10:48:45 2019

*** Panic Report ***
panic(cpu 0 caller 0xffffff7f8937a932): @/BuildRoot/Library/Caches/
Backtrace (CPU 0), Frame : Return Address
0xffffff9116423780 : 0xffffff800806e1c6
0xffffff91164237d0 : 0xffffff8008196a74
0xffffff9116423810 : 0xffffff8008188d44
0xffffff9116423880 : 0xffffff80080201e0
0xffffff91164238a0 : 0xffffff800806dc3c
0xffffff91164239d0 : 0xffffff800806d9fc
0xffffff9116423a30 : 0xffffff7f8937a932
0xffffff9116423a80 : 0xffffff7f8936f9e7
0xffffff9116423b00 : 0xffffff800869b658
0xffffff9116423b70 : 0xffffff7f88fbf7f5
0xffffff9116423bc0 : 0xffffff7f8936f068
0xffffff9116423c30 : 0xffffff7f88feac26
0xffffff9116423c90 : 0xffffff800869b658
0xffffff9116423d00 : 0xffffff7f88fea9d6
0xffffff9116423d90 : 0xffffff7f8a90eeca
0xffffff9116423df0 : 0xffffff7f8a90ec90
0xffffff9116423e50 : 0xffffff7f8884fc55
0xffffff9116423eb0 : 0xffffff7f888500a1
0xffffff9116423ee0 : 0xffffff7f892d23e1
0xffffff9116423f20 : 0xffffff7f892cd830
0xffffff9116423f80 : 0xffffff7f892cd8d7
0xffffff9116423fa0 : 0xffffff800801f557
Kernel Extensions in backtrace:[93B5E6D7-8F74-39E2-A9C6-6B25F334733D]@0xffffff7f88fb1000->0xffffff7f89029fff

BSD process name corresponding to current thread: kernel_task

Mac OS version:

Kernel version:
Darwin Kernel Version 17.7.0: Thu Dec 20 21:47:19 PST 2018; root:xnu-4570.71.22~1/RELEASE_X86_64
Kernel UUID: 4A5298BF-709E-37DF-B7F0-4298065CC266
Kernel slide: 0x0000000007e00000
Kernel text base: 0xffffff8008000000
__HIB text base: 0xffffff8007f00000
System model name: MacBookPro9,2 (Mac-6F01561E16C75D06)

System uptime in nanoseconds: 13434790147857
last loaded kext at 13251842405227: 3 (addr 0xffffff7f8b534000, size 32768)
last unloaded kext at 12226194527252: 5.0.0 (addr 0xffffff7f8b526000, size 28672)
loaded kexts:
org.dungeon.driver.SATSMARTDriver 0.8.1
org.virtualbox.kext.VBoxNetAdp 5.1.8
org.virtualbox.kext.VBoxNetFlt 5.1.8
org.virtualbox.kext.VBoxUSB 5.1.8
org.virtualbox.kext.VBoxDrv 5.1.8
com.paragon-software.filesystems.ntfs 23.0.15
com.paragon-software.kext.VDMounter 111.2
com.Cycling74.driver.Soundflower 2 404.30.2 1.4 110.23.37 1.0.0 3.0 3.13 131 1.70 3.20.14 3.20.0 3.6.5 281.52 1 1.0.1 281.52 10.3.6 1 6.0.7f12 1 7.0.0 211 3.0.4d1 3.1.1 1.0.0 4.0.0 3.1 1 10.3.6 170.12.6 1.5.5 254 254 353 407.50.6 1.0.0d1 40 1.0.0 1.0 748.51.0 1.7.6 10.3.1 1240.19.1a3 5.5.9 329.50.2 161.0.0 2.0 6.1 1.8 2.1 6.1 1.7 220.50.1 183 8 3 220.50.1 3 5.0.0 900.4.1 1.0 683.1 680.15 281.52 526 1.0 11 3.20.0 281.52 281.52 206.5 1.2.0 3.20.14 1.0.14d1 1.0.0 1.0.0 6.0.0d8 378.26 211.15 2.2.9 3.20.14 1.1.0 519.21 1.0.18d1 519.21 6.0.7f12 6.0.7f12 6.0.7f12 6.0.7f12 262 1.2 5.0.0 1.2 1.2 1 5.5.5 5.5.5 2.1.3 301.40.2 4.7.3 6.7.9 1.1.0 1200.12.2 1.0.1b8 1.0.4 4.7.2 288 1.0 900.4.1 1.2 1.2 1.2 1.2 2.1 2.1 1.2 1.1 2.0.0 300.0 1.0.0d1 480.60.2 28.30 1.0 2 439.70.3 1.0.5 140.70.2 404.30.2 404.30.2 2.1 1.0 1 1.2 1.0 1.0 1.0.1 1 31 680.15 3.4 6.1 3.1.9 2.9 1.4 1 1.0 1

Model: MacBookPro9,2, BootROM, 2 processors, Intel Core i5, 2,5 GHz, 8 GB, SMC 2.2f44
Graphics: Intel HD Graphics 4000, Intel HD Graphics 4000, Built-In
Memory Module: BANK 1/DIMM0, 8 GB, DDR3, 1600 MHz, 0x029E, 0x434D5358384758334D314131363030433130
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0xF5), Broadcom BCM43xx 1.0 (
Bluetooth: Version 6.0.7f12, 3 services, 27 devices, 1 incoming serial ports
Network Service: Ethernet, Ethernet, en0
Network Service: Wi-Fi, AirPort, en1
Serial ATA Device: KINGSTON SV300S37A240G, 240,06 GB
Serial ATA Device: APPLE HDD HTS547550A9E384, 500,11 GB
USB Device: USB 2.0 Bus
USB Device: Hub
USB Device: USB 2.0 Hub
USB Device: USB Receiver
USB Device: FaceTime HD Camera (Built-in)
USB Device: USB 2.0 Bus
USB Device: Hub
USB Device: Hub
USB Device: Apple Internal Keyboard / Trackpad
USB Device: IR Receiver
USB Device: BRCM20702 Hub
USB Device: Bluetooth USB Host Controller
USB Device: USB 3.0 Bus
Thunderbolt Bus: MacBook Pro, Apple Inc., 25.1​


macrumors P6
Feb 20, 2009
Is this drive used ONLY for CCC backups?
If so, are all the "source drives" (the ones you make the backups from) still running OK?

In that case, what I'd try:
1. Take the backup drive and ERASE it. Yes, erase it, wipe it out.
2. Then run Disk Utility's "repair disk" function on it.
3. Do you get a "good report"?
5. If so, REPEAT the Repair Disk function FIVE TIMES
6. Do you get a good report EVERY time?
7. If so, then partition the drive again (if you were previously using partitions to "separate" the backups)
8. Then, use CCC to create completely new cloned backups for each partition.

It will take a little time to create completely new backups, but this way you erase and test the drive first, to find out if it's still worth using.

You didn't tell us HOW OLD the backup drive is, but if it's more than 5-6 years, might be time to replace it with a new drive.
If the old one still works, use it for "non-critical" stuff that you wouldn't care about if the drive fails.


macrumors member
Original poster
Oct 29, 2008
I use it only for backups, and the sources are ok, though, I will have a look on this...

You didn't tell us HOW OLD the backup drive is, but if it's more than 5-6 years, might be time to replace it with a new drive.
If the old one still works, use it for "non-critical" stuff that you wouldn't care about if the drive fails.
The HDD got one year and two months. I did verify in Seagate website and it is not eligible for a refund, warranty is only one year - what a bad luck! I am thinking about trying in Windows to avoid kernel panic, though Windows won't read inside, so after erase it I can try again by macOS.

I'm wondering what can be inside this HDD that got kernel in panic...


macrumors 68000
Nov 9, 2015
Honolulu HI
Are you still having this kernel panic now that the drive is no longer connected via USB? The kernel panic seems to related to a USB connection and it may have been this problem that caused the HDD corruption. In which case, the drive may not have a defect, it was the USB connection. Did you install the SAT SMART Driver (org.dungeon.driver.SATSMARTDriver) before you were having these problems or did you install it to help fix your problem? If it was installed before the drive went bad, there may be some problem with the driver.


macrumors member
Original poster
Oct 29, 2008
Ok, I finally got some time to work on this once again. My HDD was already labeled as "Garbage" but I have recovery it and it is fully funcional so far.

So I reboot to use my Windows 10 for testing it. As Windows started in my user, the HDD was detected and a problem too, Windows asked to fix it - and I allowed, why not? Now I have the exFAT partition working with all files inside (I did some tests later, no problems). The other two mac partitions were hidden, got no HFS access anyway, so I don't know the exactly state of those partitions. I worked for some time in other task, unrelated to this, to monitor this volume, waiting to see if will unmount or so. Nothing happened, so let's work on it!

I consider the Windows native tool for hard disk manager a bit confuse, so I'd pick Minitool Partition Wizard. I tried just to erase the HFS partitions and boot from macOS to recreate them. But once in macOS, the unused space became unavailable space. I don't have a third part software to use now, maybe with Paragon HDM I could fix it, but without any options, I saved the important data from the exFAT and erased all the HDD. I did rebuild my two HFS+ backup partitions and the exFAT partitions, and all of them are 100% now, I am using Carbon Copy Cloner again with no problems.

I will upgrade my CCC from 4 to 5 because this version is not optimized to High Sierra, this can be one cause (if not the cause) of kernel panic. Either way, I still consider a big weakness of this macOS version because it was obviously only logical problems that the system should be able to escape at list from a critical failure.

Also I hope this testimony will be useful so other people won't trow the HDD to garbage so fast!