Hp prodesk 600 NVME Adata sx6000 randomaly failed deploy image
-
Hi, I have problem with hp prodesk 600 and adata m2 nvme sx6000 , fog version 1.5.5.2, kernel 4.19.1…
Then I try deploy image I get error nvme0 abort status 0:0, nvme I/O timeout… some time deploy hang , some time continue deploy… -
Can you take a clear picture of the error with a mobile phone? Please post it here. Having the context of the error is almost as important as the error itself.
Also ensure the firmware (BIOS) has been updated on these Prodesk 600 systems. It never hurts to ensure they are on the latest release especially when you see random responses.
-
I have problem upload image… This is only my problem or problem in forum ?
-
@sgennadi This is specific to your hardware I suppose. Have you tried on a different PC (a bit older model)?
As George said, please take a picture of the error and post here.
-
@george1421
Something strange, I can’t upload pictures not from my iPhone , not from two different computers, then I try to upload pictures nothing happen… Can I upload pictures to you email and you post it here ? -
@sgennadi FWIW, I’ve had to email pictures from my phone to my gmail account and then upload them using a personal computer from gmail to the fog forum. I know its a bit of a pain, but that way works the best.
-
@george1421
I am not new on this forum and upload pictures many times but now upload not work neither phone nor computers… I click upload picture chose picture then noting happen -
@sgennadi Hmm…
I agree @Developers the forum sites are not allowing picture upload. The drag and drop upload actually freezes my browser session using FF under Linux Mint. I have also noticed that really old posts are showing up when browsing forum topics. Not sure if that is related to a recent update or not.
@sgennadi As a workaround, can you upload the image to a google drive and publicly share it or some other photobucket site?
-
Uploaded Images to Google Drive
Sometimes image deployed successful and nvme error not appear , sometimes hang after this error message , sometimes hang at the and after restore image and trying resize partition… , sometimes deploy image successful after error appear -
@sgennadi Excellent pictures. They all tell use that sgdisk utility is having an issue with these nvme drives. While that doesn’t drive us to an immediate answer, it gets us closer.
I realize you are using HP computers, on the Dell computers they have a disk controller option called Raid-on. This is a specific mode related to intel rapid store controllers. Does HP have a similar setting. This might be on the page/setting that allows you to set ATA/AHCI/Raid-On mode.
Also again, do these prodesk 600’s have the latest firmware installed?
-
@george1421
Latest firmware HP Prodesk 600 G4 pci mt
Latest Adata firmware
AHCI/Raid-On mode I can check at Sunday … -
@sgennadi said in Hp prodesk 600 NVME Adata sx6000 randomaly failed deploy image:
AHCI/Raid-On mode I can check at Sunday …
If there is such a setting set it to ahci mode and see if you have the same results. It may not have an impact since we are talking about NVMe here and not SATA attached storage.
-
@george1421
No option ATA/AHCI
Only Intel Optane enable/disable ( Enable fog don’t detect disk) -
I tried replace adata ssd with intel 6 series m2 ssd and image deployed without any issues…
Seems to be compatibility problem with Realtek RTS5760 SSD controller … -
@sgennadi How does that disk interface with the system, is it via sata or a M.2 slot? I’m a bit curious about how the realtek controller fits into the solution.
-
@george1421
Intel m2 ssd
I have 600 HP with Adata sx6000 m2 all of them have some problem, then I change ssd to Intel m2 all work fine ( SX6000 use new realtek controller , may be firmware compatibility problem) -
@sgennadi ok the SX6000 IS the the PCIE/NVMe M.2 storage card, gotcha.
I did a quick google search and only found one post where they were talking about getting crc errors in their drive. There is also an ssd toolbox created by adata that can inspect the drive. I’m wondering if there is a firmware update for the drive that might address this error. Lastly since this drive is so new, there may not be a linux driver available yet to properly manage this drive so its using the generic nvme controller driver that is giving you that error.
