Hi Community,

A little over a month ago i replaced a faulty disk 2. It was a shucked 2,5" 4TB drive, so I wasnt too surprised at the failure. I replaced with a reconditioned 16TB Seagate.

1st of the month and my server does its monthly parity check. Unfortunately about halfway in, we had a power cut in the house longer than the UPS could survive and the parity check was interrupted.

Server started again and parity check was restarted. It finished this time but found loads of errors. I blamed these on Immich working on making thumbnails for nearly a million photos(as it has been working on for the past week or more).

This morning, a day after the parity check finished, I woke up to Disk 2 disabled with 1071 errors.

This is the log from the drive:

Apr  5 05:21:32 Alameda kernel: sd 1:0:2:0: [sdj] tag#1883 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=4s
Apr  5 05:21:32 Alameda kernel: sd 1:0:2:0: [sdj] tag#1883 Sense Key : 0x2 [current]
Apr  5 05:21:32 Alameda kernel: sd 1:0:2:0: [sdj] tag#1883 ASC=0x4 ASCQ=0x0
Apr  5 05:21:32 Alameda kernel: sd 1:0:2:0: [sdj] tag#1883 CDB: opcode=0x88 88 00 00 00 00 01 1b dc 49 50 00 00 00 08 00 00
Apr  5 05:21:32 Alameda kernel: I/O error, dev sdj, sector 4762388816 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Apr  5 05:21:32 Alameda kernel: sd 1:0:2:0: [sdj] tag#1884 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=4s
Apr  5 05:21:32 Alameda kernel: sd 1:0:2:0: [sdj] tag#1884 Sense Key : 0x2 [current]
Apr  5 05:21:32 Alameda kernel: sd 1:0:2:0: [sdj] tag#1884 ASC=0x4 ASCQ=0x0
Apr  5 05:21:32 Alameda kernel: sd 1:0:2:0: [sdj] tag#1884 CDB: opcode=0x88 88 00 00 00 00 01 1b dc 49 40 00 00 00 08 00 00
Apr  5 05:21:32 Alameda kernel: I/O error, dev sdj, sector 4762388800 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Apr  5 05:21:32 Alameda kernel: sd 1:0:2:0: [sdj] tag#1887 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=4s
Apr  5 05:21:32 Alameda kernel: sd 1:0:2:0: [sdj] tag#1887 Sense Key : 0x2 [current]
Apr  5 05:21:32 Alameda kernel: sd 1:0:2:0: [sdj] tag#1887 ASC=0x4 ASCQ=0x0
Apr  5 05:21:32 Alameda kernel: sd 1:0:2:0: [sdj] tag#1887 CDB: opcode=0x88 88 00 00 00 00 01 1b dc 48 e8 00 00 00 08 00 00
Apr  5 05:21:32 Alameda kernel: I/O error, dev sdj, sector 4762388712 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Apr  5 05:21:32 Alameda kernel: sd 1:0:2:0: [sdj] tag#1888 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=4s
Apr  5 05:21:32 Alameda kernel: sd 1:0:2:0: [sdj] tag#1888 Sense Key : 0x2 [current]
Apr  5 05:21:32 Alameda kernel: sd 1:0:2:0: [sdj] tag#1888 ASC=0x4 ASCQ=0x0
Apr  5 05:21:32 Alameda kernel: sd 1:0:2:0: [sdj] tag#1888 CDB: opcode=0x88 88 00 00 00 00 01 1b dc 49 48 00 00 00 08 00 00
Apr  5 05:21:32 Alameda kernel: I/O error, dev sdj, sector 4762388808 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Apr  5 05:21:32 Alameda kernel: sd 1:0:2:0: [sdj] tag#1889 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=4s
Apr  5 05:21:32 Alameda kernel: sd 1:0:2:0: [sdj] tag#1889 Sense Key : 0x2 [current]
Apr  5 05:21:32 Alameda kernel: sd 1:0:2:0: [sdj] tag#1889 ASC=0x4 ASCQ=0x0
Apr  5 05:21:32 Alameda kernel: sd 1:0:2:0: [sdj] tag#1889 CDB: opcode=0x88 88 00 00 00 00 01 1b dc 48 b8 00 00 00 08 00 00
Apr  5 05:21:32 Alameda kernel: I/O error, dev sdj, sector 4762388664 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Apr  5 05:21:32 Alameda kernel: sd 1:0:2:0: [sdj] tag#1890 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=4s
Apr  5 05:21:32 Alameda kernel: sd 1:0:2:0: [sdj] tag#1890 Sense Key : 0x2 [current]
Apr  5 05:21:32 Alameda kernel: sd 1:0:2:0: [sdj] tag#1890 ASC=0x4 ASCQ=0x0
Apr  5 05:21:32 Alameda kernel: sd 1:0:2:0: [sdj] tag#1890 CDB: opcode=0x88 88 00 00 00 00 01 1b dc 48 e0 00 00 00 08 00 00
Apr  5 05:21:32 Alameda kernel: I/O error, dev sdj, sector 4762388704 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Apr  5 05:21:32 Alameda kernel: sd 1:0:2:0: [sdj] tag#1893 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=4s
Apr  5 05:21:32 Alameda kernel: sd 1:0:2:0: [sdj] tag#1893 Sense Key : 0x2 [current]
Apr  5 05:21:32 Alameda kernel: sd 1:0:2:0: [sdj] tag#1893 ASC=0x4 ASCQ=0x0
Apr  5 05:21:32 Alameda kernel: sd 1:0:2:0: [sdj] tag#1893 CDB: opcode=0x88 88 00 00 00 00 01 1b dc 49 38 00 00 00 08 00 00
Apr  5 05:21:32 Alameda kernel: I/O error, dev sdj, sector 4762388792 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Apr  5 05:21:32 Alameda kernel: sd 1:0:2:0: [sdj] tag#1895 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=4s
Apr  5 05:21:32 Alameda kernel: sd 1:0:2:0: [sdj] tag#1895 Sense Key : 0x2 [current]
Apr  5 05:21:32 Alameda kernel: sd 1:0:2:0: [sdj] tag#1895 ASC=0x4 ASCQ=0x0
Apr  5 05:21:32 Alameda kernel: sd 1:0:2:0: [sdj] tag#1895 CDB: opcode=0x88 88 00 00 00 00 01 1b dc 48 a0 00 00 00 08 00 00
Apr  5 05:21:32 Alameda kernel: I/O error, dev sdj, sector 4762388640 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Apr  5 05:21:32 Alameda kernel: sd 1:0:2:0: [sdj] tag#1896 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=4s
Apr  5 05:21:32 Alameda kernel: sd 1:0:2:0: [sdj] tag#1896 Sense Key : 0x2 [current]
Apr  5 05:21:32 Alameda kernel: sd 1:0:2:0: [sdj] tag#1896 ASC=0x4 ASCQ=0x0
Apr  5 05:21:32 Alameda kernel: sd 1:0:2:0: [sdj] tag#1896 CDB: opcode=0x88 88 00 00 00 00 01 1b dc 48 a8 00 00 00 08 00 00
Apr  5 05:21:32 Alameda kernel: I/O error, dev sdj, sector 4762388648 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Apr  5 05:21:32 Alameda kernel: sd 1:0:2:0: [sdj] tag#1900 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=4s
Apr  5 05:21:32 Alameda kernel: sd 1:0:2:0: [sdj] tag#1900 Sense Key : 0x2 [current]
Apr  5 05:21:32 Alameda kernel: sd 1:0:2:0: [sdj] tag#1900 ASC=0x4 ASCQ=0x0
Apr  5 05:21:32 Alameda kernel: sd 1:0:2:0: [sdj] tag#1900 CDB: opcode=0x88 88 00 00 00 00 01 1b dc 48 b0 00 00 00 08 00 00
Apr  5 05:21:32 Alameda kernel: I/O error, dev sdj, sector 4762388656 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0

 

Can anyone please help me interpret what is going on? Is the newly bought disk damaged already or should i just try to reassign it and run parity rebuild again?

 

Have a nice weekend fam

Daniel

Please post the diagnostics.

3 hours ago, JorgeB said:

Please post the diagnostics.

Hi Jorge.

As always, thank you for responding. I cant create a diagnostics file. It starts writing the hundreds of thousands of thumbnail creations that Immich has been doing, and then eventually crashes my computer.

I dont know if there is a way of making diagnostics without including the log from Immich?

Perhaps the SMART report for the drive is of use?

1-W8_5W_t2QUt-bf6_EPgPHLd6l4T0Wfq

What format is that file? It should be a txt file, but it looks garbled on notepad.

That was meant to be a zip file. I have recently changed to Linux Mint and don't understand why it removes file types from uploads. Now this one should be a .txt file.

1qVe-NLAwbQcgqozwEjZcjvR13ggGRIZO

Just realized that it is only when i upload from my google drive. Here is the .txt file.

ST16000NM001G-2KK103_WL203RF2-20240406-1628.txt

SMART looks perfect, nothing suggesting it's a disk problem, so power/connection would be the main suspects, the log snippet you posted also doesn't point to a disk problem.

Thanks Jorge,

That is comforting. I am abroad at the moment. Will try to check that when I am home next.