Skip to content

Instantly share code, notes, and snippets.

@nosmo

nosmo/WD80EZAZ.md

Created December 19, 2019 21:11
Show Gist options

  • Select an option

    Learn more about clone URLs
  • Save nosmo/3889a050a31b374a8304db0cce4de0e8 to your computer and use it in GitHub Desktop.

Select an option

Learn more about clone URLs
Save nosmo/3889a050a31b374a8304db0cce4de0e8 to your computer and use it in GitHub Desktop.
Download ZIP
Fixing issues with WD80EZAZ drives blocking boot
Raw
WD80EZAZ.md

I just added a shucked WD80EZAZ to my system after doing the pin masking fix. My system failed to boot, even the BIOS was inaccessible. However, my RAID controller recognised the drives and it seemed like all was well otherwise. It appears that a corrupted GPT is at least partially to blame as others have seen this issue. On Linux the solution is as follows:

Boot the system as normal with the drive plugged into the power supply as normal but with the SATA connector disconnected.

Once your OS has booted, log in and fix the GPT when prompted. I also deleted the existing FAT partition.

~ # parted /dev/$THE_DISK
GNU Parted 3.2
Using /dev/sdg
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) p
Error: The backup GPT table is corrupt, but the primary appears OK, so that will be used.
OK/Cancel? o
Warning: Not all of the space available to /dev/sdg appears to be used, you can fix the GPT to use all of the space (an extra 688 blocks) or continue with the current setting?
Fix/Ignore? fix
(parted) rm 1
(parted) quit
~ # shutdown -r now

The system booted without issue at this point.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment