AM07 SSD Failure

[pausenklaus]

After 2 months of working great i tried switching my operating system from Ubuntu back to the stock Windows image.
Unfortunately i encountered an error where it was unable to discover the SSD.

I tried using an external mounting case and test the drive on another computer but i cannot get it to work. It is however being recognized in the windows disk management. But i cannot initialize it or do anything else than look at the error message

Any ideas on how to fix that?


I've attached a screenshot of the error message when using the full image backup from barrys post.
To ensure that there is no other failure i inserted another ssd into the pc and will test it now

[dragonpoo]

Back up a little bit and explain what you did before these errors, please? You said you had Ubuntu running on this system, so was it on the internal m.2 drive, or on a different one? When you boot from a Windows installer disk, it's unable to find the internal drive?

I'm not sure about the whole situation, but I'd suggest some generic troubleshooting:
Verify the internal drive is mounted correctly.
Reset the BIOS to defaults. Reboot.
Verify the internal drive appears in the BIOS.
Boot from your Windows installer USB drive and see if it appears there.
There are some troubleshooting tools you can use from Windows, like a command prompt, diskpart to verify Windows can see it, etc.

[pausenklaus]

Back up a little bit and explain what you did before these errors, please? You said you had Ubuntu running on this system, so was it on the internal m.2 drive, or on a different one? When you boot from a Windows installer disk, it's unable to find the internal drive?

I'm not sure about the whole situation, but I'd suggest some generic troubleshooting:
Verify the internal drive is mounted correctly.
Reset the BIOS to defaults. Reboot.
Verify the internal drive appears in the BIOS.
Boot from your Windows installer USB drive and see if it appears there.
There are some troubleshooting tools you can use from Windows, like a command prompt, diskpart to verify Windows can see it, etc.

Haha srry eah i was kinda frustrated and blurted out everything.

I was running everything from the internal drive.
I ran ubuntu server for a while and everything worked great. I was interested in Unraid too and booted it once but only from my usb drive and tried to add the internal drive to the array. The first reboot afterwards did put me into the ubuntu shell. That was the last time i was able to boot internally.

I then tried to install different operating systems but was not able to find my internal drive either in bios or any installer.

I feared that i messed up my drive with unraid and tried different troubleshooting steps to get it back to work but was not able to do so.

Every troubleshooting from within windowspe or other distros booted from usb did not work and did not see the drive.

My fear is that i somehow messed up my drive because i made it part of a zfs array but for now i could not find any way to restore it.

I did attach the drive to other computers using a usb case and was not able to mount it or format it.

Every other aspect of the pc is working fine. I replaced the drive with a spare one and it works just as expected. I kinda wonder now if this is completely my fault or if there is either a way to fix it or if i completely borked it some kind of leftover warranty in this case.

[dragonpoo]

Changing it from the default partitions to ZFS definitely broke something, but you should still be able to recover it. I would personally put the drive back into the computer and boot from a Linux Live USB or Windows installer USB. USB enclosures aren't always effective on recovering a bad drive.

As I asked before, if booting internally, does it show up in the BIOS? If it doesn't, don't expect an OS to recognize it. However, if it does, you should be able to recover it.

There are a lot of websites with steps to recover the drive. Assume that adding it to your ZFS array completely altered the boot record, possibly changing it from UEFI (default for current Windows versions) to MBR. From Windows, you'll use diskpart. You can get a lot of information from it and run some commands to clean the existing configuration and start from scratch.

[pausenklaus]

Changing it from the default partitions to ZFS definitely broke something, but you should still be able to recover it. I would personally put the drive back into the computer and boot from a Linux Live USB or Windows installer USB. USB enclosures aren't always effective on recovering a bad drive.

As I asked before, if booting internally, does it show up in the BIOS? If it doesn't, don't expect an OS to recognize it. However, if it does, you should be able to recover it.

There are a lot of websites with steps to recover the drive. Assume that adding it to your ZFS array completely altered the boot record, possibly changing it from UEFI (default for current Windows versions) to MBR. From Windows, you'll use diskpart. You can get a lot of information from it and run some commands to clean the existing configuration and start from scratch.

I did mention it but my last post was again very cluttered.
The disk does not show up in the BIOS. Booting from a live USB did not allow me to see it in any way. (I tried gparted on Ubuntu and diskpart from the windows shell)

When connecting the disk to a Windows PC using an external case the Disk Management takes quite long to initialize the virtual disk service prompts me to initialize the disk. No matter what i try to initalize it to i get the error

Code: Select all

The request failed due to a fatal device hardware error.

accompanied by Eventlog entries with the ID 154 stating:

Code: Select all

The IO operation at logical block address 0x3f00c000 for Disk 4 (PDO name: \Device\00000151) failed due to a hardware error.

and

Code: Select all

The IO operation at logical block address 0x0 for Disk 4 (PDO name: \Device\00000151) failed due to a hardware error.

*UPDATE*
I played around a bit more. The DCOM Server Service crashes from time to time but i do actually see the disk with diskpart.

Code: Select all

DISKPART> lis dis

  Disk ###  Status         Size     Free     Dyn  Gpt
  --------  -------------  -------  -------  ---  ---
  Disk 0    Online          931 GB  1024 KB        *
  Disk 1    Offline         223 GB      0 B
  Disk 2    Online          465 GB  2048 KB        *
* Disk 4    Online             0 B      0 B

And i'm also able to select it.

Initial attempts to create a partition or do anything to recover it have been unsuccessful throwing the following error:

Code: Select all

DISKPART> create partition primary

DiskPart has encountered an error: The request failed due to a fatal device hardware error.
See the System Event Log for more information.

I moved back to try other ways. I can see the Disk in the device manager too so my hopes are up again!
It's called Jmicron Tech SCSI Disk Device in there.

[dragonpoo]

I'm glad some options work. So to confirm, when the drive is internal, and the system is freshly booted, BIOS does not report it? That really sounds like it's a hardware issue. Combined with all those "hardware errors" you keep mentioning, it really sounds like the drive is experiencing hardware issues.

If that was the internal one that came with the computer, it might still be covered by the original warranty, so try contacting tech support and see if they'll help. Or message admin or Barry for help, that could work as well.

[pausenklaus]

I'm glad some options work. So to confirm, when the drive is internal, and the system is freshly booted, BIOS does not report it? That really sounds like it's a hardware issue. Combined with all those "hardware errors" you keep mentioning, it really sounds like the drive is experiencing hardware issues.

If that was the internal one that came with the computer, it might still be covered by the original warranty, so try contacting tech support and see if they'll help. Or message admin or Barry for help, that could work as well.

That's correct. Internal: no signs of life either in BIOS nor in diskpart or gparted. When external i see a few signs of life.

I'll try a few more things within diskpart for now.

On another note: I already tried booting UNRAID once more with the disk being internal but even there it is no longer visible :/

[dragonpoo]

I suspect the few signs of life, when externally mounted in a adapter, is because the adapter works. It's just when it tries to get information from the drive, that's failing.

Good luck! Maybe it's just some corrupted MBR information that diskpart can help with.

[pausenklaus]

I suspect the few signs of life, when externally mounted in a adapter, is because the adapter works. It's just when it tries to get information from the drive, that's failing.

Good luck! Maybe it's just some corrupted MBR information that diskpart can help with.

I did not think of this before but that makes a lot of sense! All device identifiers are zero so i guess it really died
Sadly i was not able to make any progress.

[barry777]

1. It is recommended to try downloading [DiskGenius] to format the SSD.
It is recommended to refer to the following video for formatting operations:




2. Format the U disk into NTFS, then name it [WINPE], and then copy all the system files.

AM07 system 20230809



AM07 system reinstallation tutorial (20230816)





3. If the above steps are invalid, it is recommended to try another SSD (if the other SSD works normally, then the SSD of the original machine is faulty);
Please contact the Amazon store service specialist; or provide the Amazon order number and send it to me.