(SOLVED) Multiple errors after new hardware change

[petchav]

Hello, 

I changed my configuration, new cpu and new motherboard. Since I have many problems with Unraid. 

 

I have a feeling that it is not working properly.

- The shutdown or restart time is extremely long, or doesn't even work at all.

- The dashboard page loads very very slowly

- When I try to transfer files via ftp or sbm there are many failures

 

On my previous computer, everything worked like a charm. I really don't know where to look for the solution. 

I am attaching the Unraid diagnostic to this post, probably there is a glaring error in it. 

I really hope you can help me. 

unraid-diagnostics-20210822-1855.zip

[Squid]

Aug 22 18:52:40 Unraid kernel: BTRFS info (device nvme0n1p1): forced readonly

 

Personally, I am not a fan of using BTRFS on single device cache pools (Only use it on multi-device pools) and would much rather use XFS.  I'm going to leave it up to @JorgeB to help as he is without question the resident guru.

[petchav]

Ah great thank you for this information I will quickly try with xfs

 

Edit : 

This does not change anything

Edited August 22, 2021 by petchav

[JorgeB]

13 hours ago, petchav said:

This does not change anything

Please post new diags.

[petchav]

A new diagnosis here.

 

After some research, I installed the "Fix Common Problems" plugin and there was an error saying that my cache was in read-only. So I ran a "Check Filesystem" with the -Lv options to fix any errors. The check got stuck on the following lines

 

Format log to cycle 4.
xfs_repair: pwrite failed: Input/output error
libxfs_bwrite: write failed on (unknown) bno 0x3a383710/0x40000, err=5
xfs_repair: Releasing dirty buffer to free list!
found dirty buffer (bulk) on free list!
xfs_repair: pwrite failed: Input/output error
libxfs_bwrite: write failed on (unknown) bno 0x3a383b10/0x40000, err=5
xfs_repair: Releasing dirty buffer to free list!
found dirty buffer (bulk) on free list!

 

I don't know if this can be useful, but it seems that it didn't work properly

ps: I don't have any important data on my server, if it is necessary to format the disks it is not a problem.

unraid-diagnostics-20210823-1037.zip

[JorgeB]

Problems with the NVMe device, this is not a software issue:

 

Aug 23 10:27:54 Unraid kernel: nvme nvme0: I/O 199 QID 14 timeout, aborting
Aug 23 10:28:03 Unraid kernel: nvme nvme0: I/O 25 QID 0 timeout, reset controller
Aug 23 10:28:24 Unraid kernel: nvme nvme0: I/O 199 QID 14 timeout, reset controller
Aug 23 10:29:07 Unraid kernel: nvme nvme0: Abort status: 0x371
Aug 23 10:29:07 Unraid kernel: nvme nvme0: 15/0/0 default/read/poll queues
Aug 23 10:30:07 Unraid kernel: nvme nvme0: I/O 200 QID 14 timeout, aborting
Aug 23 10:30:08 Unraid kernel: nvme nvme0: I/O 3 QID 0 timeout, reset controller
Aug 23 10:30:37 Unraid kernel: nvme nvme0: I/O 200 QID 14 timeout, reset controller
Aug 23 10:31:10 Unraid kernel: nvme nvme0: Abort status: 0x371
Aug 23 10:31:10 Unraid kernel: nvme nvme0: 15/0/0 default/read/poll queues
Aug 23 10:32:11 Unraid kernel: nvme nvme0: I/O 27 QID 0 timeout, reset controller
Aug 23 10:33:13 Unraid kernel: nvme nvme0: 15/0/0 default/read/poll queues

 

[petchav]

Thanks a lot ✌️, problem solved! 
 

I removed the SSD that was causing the problem and everything works great now