I had this same problem too, I solved by this step
/dev/disk0 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *121.3 GB disk0
1: EFI EFI 314.6 MB disk0s1
You should probably upgrade to High Sierra first, then upgrade to Catalina. Installing High Sierra will upgrade the firmware. Also, High Sierra can boot from both JHFS+ and APFS partitions. Catalina can only boot from APFS which requires the Mac to have the firmware update. If you have a SSD, then the upgrade to High Sierra should also convert the boot ...
Below are three examples of how to erase the drive and create a APFS volume named MyVolume. You only need to follow one of the examples.
The commands given below create a Mac OS Extended (Journaled) partition, then reformat to APFS.
diskutil eraseDisk JHFS+ dummy GPT disk0
diskutil apfs create disk0s2 MyVolume
The commands given below create a Mac OS ...
I ran into the mysterious number 1.6 TB many times recently when trying to use a WD Blue 6 TB drive in various old FireWire enclosures I was hoping to re-use.
I tried about four enclosures, and Disk Utility reported a Volume capacity of 1.6 TB (actually 1,603,128,614,912 bytes, for one where I made detailed notes) in all except one enclosure, which ...
Is there any way to force-delete the snapshot?
Yes, and you may as well make a script of it because it's a frequent problem. 99% of the time is the oldest snapshot.
listlocalsnapshots / ... Output of that command looks like this:
Snapshots for volume group containing disk /:
It would appear you have two files named EFI. I am not sure how there can be two, but neither appears to be a directory (folder). This may prevent the creation of a EFI folder which could prevent the installation of any UEFI booting operation systems which use the EFI partition to boot.
I suppose since the volume seems to be corrupted, I would just reformat ...
Is this a serious issue? Maybe...
It is an issue with your disk that needs to be run in an environment where the normal boot volume is not the active startup volume. Fortunately that is built into all recent Macs.
FIRST, you have a recent backup, right? If not and you can make a backup, do so now.
Now boot into recovery mode by holding the ⌘ Command R ...
My (maybe educated) guess:
Your docking station (StarTech SATADOCK22UE) has a useless/faulty/old USB Bridge chipset firmware and you are hit by some double 2.2 TB barrier (=32bit block addressing error).
Depending on the firmware of the WD60EFRX it has a size of 6000527425536 B - 6001424400384 B (ref).
The 2 x 2.2 TB gpt barrier is 4398046511104 B. Disk ...
Ok. Nothing on disk3 needs changing yet, so all the CS commands are dangerous or ineffective
What happens when you issue:
diskutil eraseVolume free free disk0s4
diskutil eraseVolume free free disk0s3
Also, please use care, if you delete the wrong 0s4 you will lose everything. Do you have a backup and internet to reinstall if you or I make a mistake?
Disc Utility isn't always the best tool for something like this.
I would probably throw something like this at TechTool Pro, Paragon Hard Disk Manager or DiskWarrior* for a good 'second opinion'.
I would also be careful & make sure I had a good clone of it first - Carbon Copy Cloner
*DiskWarrior is extremely good with Time Machine drives, as they're ...
I was able to fix this by changing the Micro SD adapter into another one and then unlocking the security switch in the sd adapter. That error occurs whenthere is a physical write protect switch on the drive, and it's locked in that position.
You can do this from Terminal with the system_profiler command:
$ system_profiler SPSerialATADataType
It will generate a list of all SATA drives attached to your Mac. You will get an output similar to the following (yours will be longer as you have more drives):
Intel 7 Series Chipset:
Product: 7 Series Chipset
Link Speed: 6 Gigabit
The method I use is to grab the serial number from the drive. This information is usually printed by the factory on a label on the physical disk so that it is easy to identify.
Start by ensuring you have HomeBrew installed. Then run the following command to install smartmontools:
brew install smartmontools
Then grab the serial number from the failing ...
The safest way would be to use macOS Recovery. Reboot and hold down ⌘+R key combination until the Mac boots to macOS Recovery. Open a Terminal application window and enter the following commands.
gpt -f remove -i 3 disk0
diskutil apfs resizecontainer disk0s2 0
An alternative quicker method would be to open a Terminal application window in macOS and enter ...
I just faced the same issue on OSX Mojave with a Western Digital 2TB USB external drive. It started happening after I was trying to create multiple partitions using Disk Utility.. it kept hanging and becoming unresponsive. Even after rebooting the problem would continue. I then tried using the command line and ran into the error above.
What worked for me is ...
The equivalent commands are given below.
diskutil eraseDisk MS-DOS GPT diskX
diskutil eraseDisk MS-DOS MBR diskX
Where diskX is the identifier for the drive. The value of X needs to be replaced with a integer of 0 or higher. The command diskutil list will list all the current disk identifiers. The command diskutil listfilesystems will list the available ...
There are multiple challenges with the process you have gone through.
First of the entire premise of converting the drive seems to be a bad idea. You're using Time Machine for backups and want to convert the drive to APFS. But Time Machine doesn't support APFS at all - so even if you get the drive converted fully and correctly, then it won't work with Time ...
This will erase all data that currently exists on the USB drive:
Remove your USB drive.
Open Disk Utility.
In the menu bar, click [View] > [Show All Devices].
Insert your USB drive. You should see the drive appear in the sidebar in Disk Utility as an item whose name is the manufacturer name and model name/number of the drive.
Click [Erase] in the top bar.
The same issue with the latest Cataline 10.15.3 and two SSD Fusion Drive (internal 24Gb + 512Gb WD placed instead of HDD), made with command "diskutil resetFusion" which is related to Catalina or later OS.
Partition Map Type: MBR (Master Boot Record)
You need to format the entire drive, not just the partition.
APFS requires the underlying structure to be GUID, not MBR.
As only Volumes are shown by default, you need to change to Show All Devices from the View menu…