The new SU800 is error-free (so far) and RAID controller errors are back to 0. My Intel RAID controller did eventually mark this failing SSD as "Failed" (after less than 30 days of ownership) before I replaced it. I replaced the SU800 that was reporting an increasing number of "Reallocated Sectors Count" and "Reallocation Event Count" SMART errors. Knowing what I know now, I would not purchase ADATA SU800-256 SSDs for a RAID array (too many firmware versions for the same part number). Summary: My RAID10 array is running fine after replacing the failed SU800-256. But, before I do anything either RMA or return it, i'm going to try with a USB M.2 NVME enclosure and see if it will be recognized that way.Update after replacing the failing SU800-256 in my RAID10 Array I really love the speed of this drive, but if it's not able to work under Linux, then I think i'm just going to return it. The support person basically punted and said to open a RMA to get the drive replaced. If there wasn't any update available, I would not have been able to download the FW that appears in Adata SSD Toolbox. The other reason is that there is no newer update available for the drive." I had already ran the extended Drive Diagnostics (physical scan) in the Adata SSD Toolbox and it didn't report any errors. The first would be physical errors being reported by the drive, and it was suggested to run 'chkdisk'. The Adata support is horrible and unhelpful, they said "There can only be 2 reasons that wouldn't allow the drive to be updated with newer firmware. Next update: I used Window 10 PE and attempted to update the FW, but again the drive is only detected in Adata SSD Toolbox, and not with the Adata Firmware Flash Updater. Update: I think what I will try next is to boot with a Windows 10 PE or Gandalf's Win 10 ISO and try to update the firmware from there. Workqueue: nvme-wq nvme_remove_dead_ctrl_work Modules linked in: crc32_pclmul crc32c_intel aesni_intel nvme realtek crypto_simd mdio_devres cryptd xhci_pci nvme_core libphy xhci_pci_renesas wmi vmw_vsock_vmci_transport vsock vmxnet3 vmwgfx drm_ttm_helper ttm vmw_pvscsi vmw_vmci virtio_net net_failover failover virtio_pci virtio_pci_legacy_dev virtio_pci_modern_dev virtio_blk workqueue: WQ_MEM_RECLAIM nvme-wq:nvme_remove_dead_ctrl_work is flushing !WQ_MEM_RECLAIM events:flush_cpu_slab nvme nvme0: Removing after probe failure status: -22 Unknown kernel command line parameters "BOOT_IMAGE=/arch/boot/x86_64/vmlinuz-linux archisobasedir=arch archisolabel=ROSL_202207 nvme_load=yes cow_spacesize=16G", will be passed to user space. Kernel command line: BOOT_IMAGE=/arch/boot/x86_64/vmlinuz-linux archisobasedir=arch archisolabel=ROSL_202207 nvme_load=yes cow_spacesize=16G i915.modeset=1 radeon.modeset=1 nouveau.modeset=0 nvidia-drm.modeset=1 module_blacklist=nouveau initrd=/arch/boot/intel-ucode.img,/arch/boot/amd-ucode.img,/arch/boot/x86_64/initramfs-linux.img Command line: BOOT_IMAGE=/arch/boot/x86_64/vmlinuz-linux archisobasedir=arch archisolabel=ROSL_202207 nvme_load=yes cow_spacesize=16G i915.modeset=1 radeon.modeset=1 nouveau.modeset=0 nvidia-drm.modeset=1 module_blacklist=nouveau initrd=/arch/boot/intel-ucode.img,/arch/boot/amd-ucode.img,/arch/boot/x86_64/initramfs-linux.img
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |