UD Failure on new drive

[a12vman]

This device(Lexar SSD), sdg, has failed 32 days after purchase.  I have it installed as an unassigned device.

 

Is there any diagnostic(chkdsk) tools to examine the drive within UnRaid?

 

Here is an Excerpt from the System Log.  When I un-mount & re-mount the drive there are no files or folders present.

This drive just serves as a download location for Sonarr, then files are moved to cache and then to the array(overnight).

 

The drive is a Lexar NQ100 SSD 1.92TB 2.5” SATA III Internal Solid State Drive, Up to 550MB/s Read (LNQ100X1920-RNNNU),

did I pick the wrong SSD to serve as a scratch drive? I tried to do the "Check File System" in Unassigned Devices, but Unraid tells

me that there are I/O Errors and it can't be read.

 

15:38:51 MediaTower kernel: I/O error, dev sdg, sector 357171856 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 Sep 6 15:38:51 MediaTower kernel: sd 5:0:0:0: [sdg] tag#7 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=DRIVER_OK cmd_age=0s Sep 6 15:38:51 MediaTower kernel: sd 5:0:0:0: [sdg] tag#7 CDB: opcode=0x2a 2a 00 38 53 c4 08 00 04 68 00 Sep 6 15:38:51 MediaTower kernel: I/O error, dev sdg, sector 945013768 op 0x1:(WRITE) flags 0x100000 phys_seg 88 prio class 0 Sep 6 15:38:51 MediaTower kernel: sd 5:0:0:0: [sdg] tag#8 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=DRIVER_OK cmd_age=0s Sep 6 15:38:51 MediaTower kernel: sd 5:0:0:0: [sdg] tag#8 CDB: opcode=0x2a 2a 00 38 53 c8 70 00 07 a8 00 Sep 6 15:38:51 MediaTower kernel: I/O error, dev sdg, sector 945014896 op 0x1:(WRITE) flags 0x104000 phys_seg 168 prio class 0 Sep 6 15:38:51 MediaTower kernel: sd 5:0:0:0: [sdg] tag#9 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=DRIVER_OK cmd_age=0s Sep 6 15:38:51 MediaTower kernel: sd 5:0:0:0: [sdg] tag#9 CDB: opcode=0x2a 2a 00 38 53 d0 18 00 04 08 00 Sep 6 15:38:51 MediaTower kernel: I/O error, dev sdg, sector 945016856 op 0x1:(WRITE) flags 0x100000 phys_seg 88 prio class 0 Sep 6 15:38:51 MediaTower kernel: sd 5:0:0:0: [sdg] tag#10 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=DRIVER_OK cmd_age=0s Sep 6 15:38:51 MediaTower kernel: sd 5:0:0:0: [sdg] tag#10 CDB: opcode=0x2a 2a 00 38 53 d4 20 00 08 18 00 Sep 6 15:38:51 MediaTower kernel: I/O error, dev sdg, sector 945017888 op 0x1:(WRITE) flags 0x104000 phys_seg 168 prio class 0 Sep 6 15:38:51 MediaTower kernel: sdg1: writeback error on inode 4609739, offset 0, sector 9922400 Sep 6 15:38:51 MediaTower kernel: XFS (sdg1): log I/O error -5 Sep 6 15:38:51 MediaTower kernel: XFS (sdg1): metadata I/O error in "xfs_buf_ioend+0x113/0x386 [xfs]" at daddr 0xa7abe630 len 32 error 5 Sep 6 15:38:51 MediaTower kernel: XFS (sdg1): Filesystem has been shut down due to log error (0x2).

Edited September 6, 2023 by a12vman

[JorgeB]

You can post the diagnostics.

[a12vman]

I pulled the drive and replaced it with a spinning drive. 

All is well now.

 

Interesting though that even after the drive was unmounted from UD 

that syslog filled up with this line(over & over) until I did a re-boot.

 

SMARTCTL IS USING A DEPRECATED SCSI IOCTL, PLEASE CONVERT IT TO SG_IO

[a12vman]

Was using an SSD as a download drive(lots of write/read/delete cycles) a bad choice?

 

[JorgeB]

That's fine, though I guess it depends on the SSD used.

[nightreap3r]

That's crazy...  I found this post while looking for the MTBF of the drive.  Bought this drive two months back and mine just died today.  Was just using it for a single VM's disk.  Guess I'll stick to the better named brands than the has-beens like Lexar...

Edited September 20, 2023 by nightreap3r