I have a SanDisc 500GB external drive which I'm using with Time Machine. I pulled it out without ejecting it in mistake for another external drive.
It will no longer mount.
Disc Utility recognises it as a disc. But that is all. It will not erase, and First Aid returns Operation sccessful instantly, without doing anything.
All its vital statistics look OK (size etc). The TM volume shows zero space available, owners disabled.
I get a "com.apple.DiskManagement.disenter error 0." Error from Disc Utility.
I am running OS 12.6.1 (Monterey) on a 2017 iMac.
Can anything be done to recover it, or is it now a brick? I don't care about the actual back up (I have alternatives) but I would like it back.
I have a SanDisc 500GB external drive which I'm using with Time Machine. I pulled it out without ejecting it in mistake for another external drive.
It will no longer mount.
Disc Utility recognises it as a disc. But that is all. It will not erase, and First Aid returns Operation sccessful instantly, without doing anything.
All its vital statistics look OK (size etc). The TM volume shows zero space available, owners disabled.
I get a "com.apple.DiskManagement.disenter error 0." Error from Disc Utility.
I am running OS 12.6.1 (Monterey) on a 2017 iMac.
Can anything be done to recover it, or is it now a brick?
I don't care about
the actual back up (I have alternatives) but I would like it back.
On 14/12/2022 09:11, John Hill wrote:
I have a SanDisc 500GB external drive which I'm using with Time Machine. I >> pulled it out without ejecting it in mistake for another external drive.
It will no longer mount.
Disc Utility recognises it as a disc. But that is all. It will not erase, and
First Aid returns Operation sccessful instantly, without doing anything.
All its vital statistics look OK (size etc). The TM volume shows zero space >> available, owners disabled.
I get a "com.apple.DiskManagement.disenter error 0." Error from Disc Utility.
I am running OS 12.6.1 (Monterey) on a 2017 iMac.
Can anything be done to recover it, or is it now a brick? I don't care about >> the actual back up (I have alternatives) but I would like it back.
Hello John
First - how is your wife? Has she survived the hip operation?
I asked my good friend if help was possible. You may like to consider
the answer provided here:- https://discussions.apple.com/thread/254464972
I have a SanDisc 500GB external drive which I'm using with Time Machine. I pulled it out without ejecting it in mistake for another external drive....
It will no longer mount.
Can anything be done to recover it, or is it now a brick? I don't care about the actual back up (I have alternatives) but I would like it back.
I have a SanDisc 500GB external drive which I'm using with Time Machine. I pulled it out without ejecting it in mistake for another external drive.
It will no longer mount....
Can anything be done to recover it, or is it now a brick? I don't care about
the actual back up (I have alternatives) but I would like it back.
In the worst case where you just want the drive and not the data, you could try zapping the partition table using Terminal.
Use 'diskutil list' to get its /dev/diskN number. Be very careful to get this right so you don't end up zapping something else like your main
storage. Then:
sudo dd if=/dev/zero of=/dev/rdiskN bs=1m count=1000
where N is the number from diskutil. Wait for that to complete then type 'sync', and then unplug it.
Then replug it and see if you can format it with Disc Utility.
However one thing that can happen to failing SSDs is they go read-only. If you do the above, which is supposed to make it look like a blank unformatted drive again, and it still shows with stuff on it, then it may have gone that way.
John Hill <watcombeman@yahoo.co.uk> wrote:
I have a SanDisc 500GB external drive which I'm using with Time Machine. I >> pulled it out without ejecting it in mistake for another external drive....
It will no longer mount.
Can anything be done to recover it, or is it now a brick? I don't care about >> the actual back up (I have alternatives) but I would like it back.
In the worst case where you just want the drive and not the data, you could try zapping the partition table using Terminal.
Use 'diskutil list' to get its /dev/diskN number. Be very careful to get this right so you don't end up zapping something else like your main
storage. Then:
sudo dd if=/dev/zero of=/dev/rdiskN bs=1m count=1000
where N is the number from diskutil. Wait for that to complete then type 'sync', and then unplug it.
Then replug it and see if you can format it with Disc Utility.
However one thing that can happen to failing SSDs is they go read-only. If you do the above, which is supposed to make it look like a blank unformatted drive again, and it still shows with stuff on it, then it may have gone that way.
Theo
The problem is that it would not mount. So it would not erase.
I did a restart and this time it did mount. I managed to erase and reformat it, but I do not trust it anymore - especially as a Time Machine backup!
However, this has somehow created another problem. There is a "virtual" external disc media somewhere, as reported by Disc Utility, with a
mountable volume to which I can copy files. In fact it behaves in all respects as though it really was an external drive. Except that I cannot eject it. I can mount it from Disc Utility, but obviously not by plugging
it in!
I'm not sure what to do about it. I can think of a few options:
A. Hope that some knowledgeable person in this group (perhaps with Terminal skills) can help me.
B. Ignore it in the hope that it is not using up much storage. It may go away, but I doubt it; it survived a Shutdown and power off cycle, which
cures many ills.
C. Do a Recovery with erase drive in it and restore from a CCC backup. This seems a risky thing to do for what it would be worth.
Meanwhile, I am ordering a replacement drive.
In article <tnc40o$2ovlf$1@dont-email.me>, John Hill <watcombeman@yahoo.co.uk> wrote:
I have a SanDisc 500GB external drive which I'm using with Time Machine. I >> pulled it out without ejecting it in mistake for another external drive.
It will no longer mount.
Disc Utility recognises it as a disc. But that is all. It will not erase, and
First Aid returns Operation sccessful instantly, without doing anything.
All its vital statistics look OK (size etc). The TM volume shows zero space >> available, owners disabled.
I get a "com.apple.DiskManagement.disenter error 0." Error from Disc Utility.
I am running OS 12.6.1 (Monterey) on a 2017 iMac.
Can anything be done to recover it, or is it now a brick?
alsoft disk warrior.
I don't care about
the actual back up (I have alternatives) but I would like it back.
if you don't care about the backup, then simply reformat it and create
a new backup. be sure to select the drive and not the volume.
In article <tnd89g$2rs3b$1@dont-email.me>, John Hill
<yclept@outlook.com> wrote:
The problem is that it would not mount. So it would not erase.
there should be a device listed in the sidebar in disk utility, even
though it won't mount. the info panel would say something like 'unknown format' or similar.
I did a restart and this time it did mount. I managed to erase and reformat >> it, but I do not trust it anymore - especially as a Time Machine backup!
if you reformatted it, then there's no reason not to trust it.
However, this has somehow created another problem. There is a "virtual"
external disc media somewhere, as reported by Disc Utility, with a
mountable volume to which I can copy files. In fact it behaves in all
respects as though it really was an external drive. Except that I cannot
eject it. I can mount it from Disc Utility, but obviously not by plugging
it in!
I'm not sure what to do about it. I can think of a few options:
A. Hope that some knowledgeable person in this group (perhaps with Terminal >> skills) can help me.
B. Ignore it in the hope that it is not using up much storage. It may go
away, but I doubt it; it survived a Shutdown and power off cycle, which
cures many ills.
C. Do a Recovery with erase drive in it and restore from a CCC backup. This >> seems a risky thing to do for what it would be worth.
ignore it.
Meanwhile, I am ordering a replacement drive.
it's always helpful to have more drives.
On 14 Dec 2022 at 17:50:20 GMT, "Theo" <theom+news@chiark.greenend.org.uk> wrote:
John Hill <watcombeman@yahoo.co.uk> wrote:/dev/disk0 (internal, physical):
I have a SanDisc 500GB external drive which I'm using with Time Machine. I >> pulled it out without ejecting it in mistake for another external drive. >>
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *500.3 GB disk0
2: Apple_APFS Container disk1 500.0 GB disk0s2
/dev/disk1 (synthesized):
#: TYPE NAME SIZE IDENTIFIER
0: APFS Container Scheme - +500.0 GB disk1
Physical Store disk0s2
/dev/disk2 (external, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *500.1 GB disk2
2: Apple_APFS Container disk3 499.9 GB disk2s2
/dev/disk3 (synthesized):
#: TYPE NAME SIZE IDENTIFIER
0: APFS Container Scheme - +499.9 GB disk3
Physical Store disk2s2
1: APFS Volume This is not a real d... 1.4 MB disk3s1
/dev/disk4 (external, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *1.0 TB disk4
1: EFI EFI 209.7 MB disk4s1
2: Apple_APFS Container disk5 1000.0 GB disk4s2
/dev/disk5 (synthesized):
#: TYPE NAME SIZE IDENTIFIER
0: APFS Container Scheme - +1000.0 GB disk5
Physical Store disk4s2
1: APFS Volume Time Machine SSD 81.3 GB disk5s2
<font color="#000000">The last of these WAS the offending disk. Disk Utility no longer sees it, so why is it hanging around? This is disk5s2.</font>
<font color="#000000"></font>
<font color="#000000">Also, the entry for dev/disk3, disk3s1, is the one that Disk Utility CAN see and behaves in some respects as though it was real. </font>
<font color="#000000"></font>
<font color="#000000">Both of these are synthesized. /dev/disk4 (external, physical): is almost certainly the current time machine drive; I would, I think, eject that for safety's sake. I would be certain not to touch the top three.</font>
<font color="#000000"></font>
<font color="#000000">Would it be safe to apply sudo dd if=/dev/zero of=/dev/rdiskN bs=1m count=1000 to the two synthesized drives?</font>
On 14 Dec 2022 at 21:48:14 GMT, "Theo" <theom+news@chiark.greenend.org.uk> wrote:
John Hill <watcombeman@yahoo.co.uk> wrote:
On 14 Dec 2022 at 17:50:20 GMT, "Theo" <theom+news@chiark.greenend.org.uk> >>> wrote:
John Hill <watcombeman@yahoo.co.uk> wrote:/dev/disk0 (internal, physical):
I have a SanDisc 500GB external drive which I'm using with Time Machine. I
pulled it out without ejecting it in mistake for another external drive. >>>>>
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *500.3 GB disk0 >>> 2: Apple_APFS Container disk1 500.0 GB disk0s2
/dev/disk1 (synthesized):
#: TYPE NAME SIZE IDENTIFIER
0: APFS Container Scheme - +500.0 GB disk1 >>> Physical Store disk0s2
/dev/disk2 (external, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *500.1 GB disk2 >>> 2: Apple_APFS Container disk3 499.9 GB disk2s2
/dev/disk3 (synthesized):
#: TYPE NAME SIZE IDENTIFIER
0: APFS Container Scheme - +499.9 GB disk3 >>> Physical Store disk2s2
1: APFS Volume This is not a real d... 1.4 MB disk3s1
/dev/disk4 (external, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *1.0 TB disk4 >>> 1: EFI EFI 209.7 MB disk4s1
2: Apple_APFS Container disk5 1000.0 GB disk4s2
/dev/disk5 (synthesized):
#: TYPE NAME SIZE IDENTIFIER
0: APFS Container Scheme - +1000.0 GB disk5 >>> Physical Store disk4s2
1: APFS Volume Time Machine SSD 81.3 GB disk5s2
<font color="#000000">The last of these WAS the offending disk. Disk Utility
no longer sees it, so why is it hanging around? This is disk5s2.</font>
<font color="#000000"></font>
<font color="#000000">Also, the entry for dev/disk3, disk3s1, is the one that
Disk Utility CAN see and behaves in some respects as though it was real. >>> </font>
<font color="#000000"></font>
<font color="#000000">Both of these are synthesized. /dev/disk4 (external, >>> physical): is almost certainly the current time machine drive; I would, I >>> think, eject that for safety's sake. I would be certain not to touch the top
three.</font>
<font color="#000000"></font>
<font color="#000000">Would it be safe to apply sudo dd if=/dev/zero
of=/dev/rdiskN bs=1m count=1000 to the two synthesized drives?</font>
[urgh, HTML]
I thought you said it was a 500GB Sandisk? You have two 500GB drives, one >> being disk0 and its virtual APFS container disk1, which appears to be your >> internal
storage. Then there's external disk2 and its virtual container disk3. Disk4
(virtual disk5) is 1000GB, and that one is marked 'Time Machine SSD'.
It seems like each APFS-formatted drive holds a container which then appears >> as a separate virtual (synthesised) drive. But that only works if the disc >> is detected as APFS formatted - if you zap the physical drive the
synthesised container goes too.
So it sounds like the external 500GB to zap is /dev/rdisk2 (500.1GB)
Either way, I'd unplug any other external drives so you just have the
troublesome one plugged in. And then steer clear of doing anything to disk0 >> or disk1.
Theo
Thank you, I now think the I understand the way it works.
I have a nice clean iMac, so that is nice.
John Hill <watcombeman@yahoo.co.uk> wrote:
On 14 Dec 2022 at 17:50:20 GMT, "Theo" <theom+news@chiark.greenend.org.uk> >> wrote:
John Hill <watcombeman@yahoo.co.uk> wrote:/dev/disk0 (internal, physical):
I have a SanDisc 500GB external drive which I'm using with Time Machine. I >>>> pulled it out without ejecting it in mistake for another external drive. >>>>
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *500.3 GB disk0
2: Apple_APFS Container disk1 500.0 GB disk0s2 >>
/dev/disk1 (synthesized):
#: TYPE NAME SIZE IDENTIFIER
0: APFS Container Scheme - +500.0 GB disk1
Physical Store disk0s2
/dev/disk2 (external, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *500.1 GB disk2
2: Apple_APFS Container disk3 499.9 GB disk2s2 >>
/dev/disk3 (synthesized):
#: TYPE NAME SIZE IDENTIFIER
0: APFS Container Scheme - +499.9 GB disk3
Physical Store disk2s2
1: APFS Volume This is not a real d... 1.4 MB disk3s1 >>
/dev/disk4 (external, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *1.0 TB disk4
1: EFI EFI 209.7 MB disk4s1 >> 2: Apple_APFS Container disk5 1000.0 GB disk4s2 >>
/dev/disk5 (synthesized):
#: TYPE NAME SIZE IDENTIFIER
0: APFS Container Scheme - +1000.0 GB disk5
Physical Store disk4s2
1: APFS Volume Time Machine SSD 81.3 GB disk5s2 >>
<font color="#000000">The last of these WAS the offending disk. Disk Utility >> no longer sees it, so why is it hanging around? This is disk5s2.</font>
<font color="#000000"></font>
<font color="#000000">Also, the entry for dev/disk3, disk3s1, is the one that
Disk Utility CAN see and behaves in some respects as though it was real.
</font>
<font color="#000000"></font>
<font color="#000000">Both of these are synthesized. /dev/disk4 (external, >> physical): is almost certainly the current time machine drive; I would, I
think, eject that for safety's sake. I would be certain not to touch the top >> three.</font>
<font color="#000000"></font>
<font color="#000000">Would it be safe to apply sudo dd if=/dev/zero
of=/dev/rdiskN bs=1m count=1000 to the two synthesized drives?</font>
[urgh, HTML]
I thought you said it was a 500GB Sandisk? You have two 500GB drives, one being disk0 and its virtual APFS container disk1, which appears to be your internal
storage. Then there's external disk2 and its virtual container disk3. Disk4 (virtual disk5) is 1000GB, and that one is marked 'Time Machine SSD'.
It seems like each APFS-formatted drive holds a container which then appears as a separate virtual (synthesised) drive. But that only works if the disc is detected as APFS formatted - if you zap the physical drive the
synthesised container goes too.
So it sounds like the external 500GB to zap is /dev/rdisk2 (500.1GB)
Either way, I'd unplug any other external drives so you just have the troublesome one plugged in. And then steer clear of doing anything to disk0 or disk1.
Theo
On 15/12/2022 09:16, John Hill wrote:
On 14 Dec 2022 at 21:48:14 GMT, "Theo" <theom+news@chiark.greenend.org.uk> >> wrote:
John Hill <watcombeman@yahoo.co.uk> wrote:
On 14 Dec 2022 at 17:50:20 GMT, "Theo" <theom+news@chiark.greenend.org.uk> >>>> wrote:
John Hill <watcombeman@yahoo.co.uk> wrote:/dev/disk0 (internal, physical):
I have a SanDisc 500GB external drive which I'm using with Time Machine. I
pulled it out without ejecting it in mistake for another external drive. >>>>>>
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *500.3 GB disk0 >>>> 2: Apple_APFS Container disk1 500.0 GB disk0s2
/dev/disk1 (synthesized):
#: TYPE NAME SIZE IDENTIFIER
0: APFS Container Scheme - +500.0 GB disk1 >>>> Physical Store disk0s2
/dev/disk2 (external, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *500.1 GB disk2 >>>> 2: Apple_APFS Container disk3 499.9 GB disk2s2
/dev/disk3 (synthesized):
#: TYPE NAME SIZE IDENTIFIER
0: APFS Container Scheme - +499.9 GB disk3 >>>> Physical Store disk2s2
1: APFS Volume This is not a real d... 1.4 MB disk3s1
/dev/disk4 (external, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *1.0 TB disk4 >>>> 1: EFI EFI 209.7 MB disk4s1
2: Apple_APFS Container disk5 1000.0 GB disk4s2
/dev/disk5 (synthesized):
#: TYPE NAME SIZE IDENTIFIER
0: APFS Container Scheme - +1000.0 GB disk5 >>>> Physical Store disk4s2
1: APFS Volume Time Machine SSD 81.3 GB disk5s2
<font color="#000000">The last of these WAS the offending disk. Disk Utility
no longer sees it, so why is it hanging around? This is disk5s2.</font> >>>> <font color="#000000"></font>
<font color="#000000">Also, the entry for dev/disk3, disk3s1, is the one that
Disk Utility CAN see and behaves in some respects as though it was real. >>>> </font>
<font color="#000000"></font>
<font color="#000000">Both of these are synthesized. /dev/disk4 (external, >>>> physical): is almost certainly the current time machine drive; I would, I >>>> think, eject that for safety's sake. I would be certain not to touch the top
three.</font>
<font color="#000000"></font>
<font color="#000000">Would it be safe to apply sudo dd if=/dev/zero
of=/dev/rdiskN bs=1m count=1000 to the two synthesized drives?</font>
[urgh, HTML]
I thought you said it was a 500GB Sandisk? You have two 500GB drives, one >>> being disk0 and its virtual APFS container disk1, which appears to be your >>> internal
storage. Then there's external disk2 and its virtual container disk3. Disk4
(virtual disk5) is 1000GB, and that one is marked 'Time Machine SSD'.
It seems like each APFS-formatted drive holds a container which then appears
as a separate virtual (synthesised) drive. But that only works if the disc >>> is detected as APFS formatted - if you zap the physical drive the
synthesised container goes too.
So it sounds like the external 500GB to zap is /dev/rdisk2 (500.1GB)
Either way, I'd unplug any other external drives so you just have the
troublesome one plugged in. And then steer clear of doing anything to disk0
or disk1.
Theo
Thank you, I now think the I understand the way it works.
I have a nice clean iMac, so that is nice.
That's great!
A good time to update to Ventura?!!! 🙂
On 15 Dec 2022 at 09:33:07 GMT, "David Brooks" <David.is@home.now> wrote:<snip>
That's great!
A good time to update to Ventura?!!! 🙂
No, quite definitely NOT!
On 15 Dec 2022 at 09:33:07 GMT, "David Brooks" <David.is@home.now> wrote:[....]
A good time to update to Ventura?!!! 🙂
No, quite definitely NOT!
I have a SanDisc 500GB external drive which I'm using with Time Machine. I pulled it out without ejecting it in mistake for another external drive.
It will no longer mount.
Disc Utility recognises it as a disc. But that is all. It will not erase, and First Aid returns Operation sccessful instantly, without doing anything.
All its vital statistics look OK (size etc). The TM volume shows zero space available, owners disabled.
I get a "com.apple.DiskManagement.disenter error 0." Error from Disc Utility.
I am running OS 12.6.1 (Monterey) on a 2017 iMac.
Can anything be done to recover it, or is it now a brick? I don't care about the actual back up (I have alternatives) but I would like it back.
John.
On 15/12/2022 19:27, John Hill wrote:
On 15 Dec 2022 at 09:33:07 GMT, "David Brooks" <David.is@home.now> wrote:<snip>
That's great!
A good time to update to Ventura?!!! 🙂
No, quite definitely NOT!
Ha! :-D
FWIW, it works without problem here on my iMac (which is similar to your own).
Btw, I think I forgot to say that I was pleased to learn that your
wife's hip replacement was completed satifactorily. There'll be be lots
of 'looking after' for you to do, that's for sure!
On 15 Dec 2022 at 19:35:55 GMT, "David Brooks" <David.is@home.now> wrote:
On 15/12/2022 19:27, John Hill wrote:
On 15 Dec 2022 at 09:33:07 GMT, "David Brooks" <David.is@home.now> wrote: >> <snip>
That's great!
A good time to update to Ventura?!!! 🙂
No, quite definitely NOT!
Ha! :-D
FWIW, it works without problem here on my iMac (which is similar to your
own).
Btw, I think I forgot to say that I was pleased to learn that your
wife's hip replacement was completed satifactorily. There'll be be lots
of 'looking after' for you to do, that's for sure!
I'm sure it does, David, but this is no time for me to tangle with any changes, no matter how minor.
Anne should be coming home tomorrow, or Monday at the latest; that's where my attention goes.
John.
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 546 |
| Nodes: | 16 (0 / 16) |
| Uptime: | 162:52:58 |
| Calls: | 10,385 |
| Calls today: | 2 |
| Files: | 14,057 |
| Messages: | 6,416,508 |