Mirrored cache drive upgrade resulted in unmountable: No file system

[JunkoZane]

I don't understand next step... Yesterday I posted new diags after assigning old (256gb ssd) to be the only cache pool device. 
Or should I assign the other 256GB ssd?

[JorgeB]

The btrfs balance was still going on, I want to make sure it finished, post new diags without changing anything else.

[JunkoZane]

the-beast-diagnostics-20230404-1853.zip

[JorgeB]

Balance finished without errors, you can now add the 1TB device to this pool, post new diags if there are any issues.

[JunkoZane]

It worked out fine, not sure why I had problems the first two times. 

Anyways, thank you for your time and help! Appreciate it 

[JunkoZane]

Happy Easter to all who celebrate it 

Could you please help me out with one more case?
Recently I got a warning that my syslog is 100% full, turns out that it got spammed with BTRFS errors... 
Is it related to my previous problem, or should I change the sata cable that connects sdg to the motherboard?

 

the-beast-diagnostics-20230409-2143.zip

[JorgeB]

Apr  4 22:25:36 The-Beast kernel: ata6.00: disable device
Apr  4 22:25:36 The-Beast kernel: ata6: EH complete
Apr  4 22:25:36 The-Beast kernel: sd 6:0:0:0: [sdg] tag#21 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=DRIVER_OK cmd_age=121s
Apr  4 22:25:36 The-Beast kernel: sd 6:0:0:0: [sdg] tag#21 CDB: opcode=0x2a 2a 00 00 10 9e c8 00 0a 00 00
Apr  4 22:25:36 The-Beast kernel: I/O error, dev sdg, sector 1089224 op 0x1:(WRITE) flags 0x104000 phys_seg 20 prio class 0

 

This device dropped offline, start by replacing cables, also see here for better pool monitoring.

[JunkoZane]

Hi there,

"Docker Service failed to start." after changing cables. I'm starting to feel guilty for bothering you...

Could yo uplease help me to get my server back ? :)

the-beast-diagnostics-20230414-2112.zip

[JorgeB]

First run a scrub on the pool, if there aren't uncorrectable errors recreate the docker image.

[JunkoZane]

Does that mean I'll have to reconfigure all my docker containers? If so, could it be possible to use very first drive that I took out of the system (256gb SSD)?

Actually I already tried that, but cache pool just displayed error: UNMOUNTABLE: NO POOL UUID

Edited April 17, 2023 by JunkoZane

[JorgeB]

12 hours ago, JunkoZane said:

Does that mean I'll have to reconfigure all my docker containers?

No, see the link, but first post new diags.

[JunkoZane]

I somehow misinterpreted info in that link...

Also, it's kind'a strange that after running scrub with "repair corrupted blocks" enabled I got a bunch uncorrectable blocks. But after second time I did same thing - I have cache pool with 0 uncorrectable blocks

the-beast-diagnostics-20230418-2152.zip

[JorgeB]

11 hours ago, JunkoZane said:

But after second time I did same thing - I have cache pool with 0 uncorrectable blocks

It doesn't make much sense, but if it's not detecting errors at the moment see how it goes.

[JunkoZane]

Hi there,
unfortunately I'm getting SDE (one of cache pool drives) errors again...
If not cable, what else could it be? MB, the drive itself?

Thank you in advance

the-beast-diagnostics-20230503-2348.zip

Edited May 3, 2023 by JunkoZane

[JorgeB]

See if this helps:

https://forums.unraid.net/topic/134954-warning-crucial-mx500-ssds-world-of-pain-stay-away-from-these/?do=findComment&comment=1255816