Red X on 1 drive show 1 error need help

[rushgunner]

I logged on after my party check showing 1 error on one drive with red X any help?  Very new user here and any specific help would greatly be appreciated 

 

has been running fine almost 1 year

skynet-diagnostics-20240913-1422.zip

[rushgunner]

I ran file system check with these results:

 

xfs_repair status:

Phase 1 - find and verify superblock...

Phase 2 - using internal log

        - zero log...

        - scan filesystem freespace and inode maps...

        - found root inode chunk

Phase 3 - for each AG...

        - scan (but don't clear) agi unlinked lists...

        - process known inodes and perform inode discovery...

        - agno = 0

        - agno = 1

        - agno = 2

        - agno = 3

        - agno = 4

        - agno = 5

        - agno = 6

        - agno = 7

        - process newly discovered inodes...

Phase 4 - check for duplicate blocks...

        - setting up duplicate extent list...

        - check for inodes claiming duplicate blocks...

        - agno = 0

        - agno = 4

        - agno = 3

        - agno = 2

        - agno = 5

        - agno = 6

        - agno = 7

        - agno = 1

No modify flag set, skipping phase 5

Phase 6 - check inode connectivity...

        - traversing filesystem ...

        - traversal finished ...

        - moving disconnected inodes to lost+found ...

Phase 7 - verify link counts...

No modify flag set, skipping filesystem flush and exiting

 

 

not sure what to do next??

[Vr2Io]

Disk drop on 8-Sep 01:00, but don't know why it have spin-up on 13-Sep. Pls try reboot and post diagnostics again.

 

Sep  8 01:00:32 Skynet kernel: sd 1:0:4:0: task abort: SUCCESS scmd(0x000000007078cd1c)
Sep  8 01:00:32 Skynet kernel: sd 1:0:4:0: [sdf] tag#3685 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=19s
Sep  8 01:00:32 Skynet kernel: sd 1:0:4:0: [sdf] tag#3685 Sense Key : 0x2 [current] 
Sep  8 01:00:32 Skynet kernel: sd 1:0:4:0: [sdf] tag#3685 ASC=0x4 ASCQ=0x0 
Sep  8 01:00:32 Skynet kernel: sd 1:0:4:0: [sdf] tag#3685 CDB: opcode=0x8a 8a 08 00 00 00 02 00 05 91 40 00 00 00 08 00 00
Sep  8 01:00:32 Skynet kernel: I/O error, dev sdf, sector 8590299456 op 0x1:(WRITE) flags 0x20800 phys_seg 1 prio class 2
Sep  8 01:00:32 Skynet kernel: md: disk4 write error, sector=8590299392

 

Sep 13 14:06:27 Skynet emhttpd: spinning up /dev/sdf
Sep 13 14:06:42 Skynet kernel: sd 1:0:4:0: attempting task abort!scmd(0x000000005ba4e52f), outstanding for 15080 ms & timeout 15000 ms
Sep 13 14:06:42 Skynet kernel: sd 1:0:4:0: [sdf] tag#3667 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 e3 00
Sep 13 14:06:42 Skynet kernel: scsi target1:0:4: handle(0x000d), sas_address(0x4433221106000000), phy(6)
Sep 13 14:06:42 Skynet kernel: scsi target1:0:4: enclosure logical id(0x500605b00a6bd240), slot(5) 
Sep 13 14:06:46 Skynet emhttpd: sdspin /dev/sdf up: 22
Sep 13 14:06:46 Skynet emhttpd: read SMART /dev/sdf
Sep 13 14:06:46 Skynet kernel: sd 1:0:4:0: task abort: SUCCESS scmd(0x000000005ba4e52f)

 

2nd issue, you need check why the NVMe non-stop got AER error, it is Samsung 980pro, pls try clean-up contact pin and re-seat.

Edited September 14, 2024 by Vr2Io

[rushgunner]

Thanks for taking a look at it. I have the new one attached. As far as the NVMe do you mean to power it down and remove the actual module and clean it off and re-inserting it?

skynet-diagnostics-20240913-2121.zip

[Vr2Io]

Not likely disk problem, if the emulated disk content look fine, then you may rebuild on it.

 

13 minutes ago, rushgunner said:

do you mean to power it down and remove the actual module and clean it off and re-inserting it?

Yes. But the new diagnostics haven't record it ( may be due to short during ), pls keep check.

[rushgunner]

I’m confused on how I would rebuild it are you able to let me know what I need to do again

 

I appreciate your time in this

[Vr2Io]

Does emulated disk look normal ? If it doesn't normal then don't rebuild on-it.

 

https://docs.unraid.net/unraid-os/manual/storage-management/

 

Section :

 

To replace a failed disk or disks: 

 

You may skip step (2) to (4).

 

[rushgunner]

It does appear like all the stuff on the emulated drive is there though

[Vr2Io]

If that you can rebuild as usual.

[rushgunner]

Not seeing where the rebuild option is?

[Vr2Io]

As step (8) said, click "start", then it will rebuild.

 

And you may need an extra step, stop array then unassigned the emulated disk and start array, then stop.

Edited September 14, 2024 by Vr2Io

[rushgunner]

Sorry newb here, so I’ll need to replace the drive then?

 

 

 

[Vr2Io]

No need replace the drive, if it rebuild success.

[rushgunner]

I have the server stopped and  I see the box to put in maintenance mode, but where is the other box I select for sync?

[Vr2Io]

Could you capture the array screen after " unassigned disable disk ( disk 4 ? ) then start and stop array "

Edited September 14, 2024 by Vr2Io

[Gragorg]

If your disk is good and you are rebuilding on the exsisting disk

 

1. Stop the Array

2. unassign the disk with the x

3. Start the Array

4. Stop the Array

5. Re assign the same disk

6. Start the Array

 

The rebuild will start and rebuild on the disk

[rushgunner]

Thank you!!!

[itimpi]

11 hours ago, rushgunner said:

Thank you!!!

For reference the procedure is documented here in the online documentation accessible via the Manual link at the bottom of the Unraid GUI.  In addition every forum page has a DOCS link at the top and a Documentation link at the bottom.   The Unraid OS->Manual section covers most aspects of the current Unraid release.