Hi All,

 

so I had a faulty drive show up so I followed the "Remove Drives Then Rebuild Parity" option which all seems to be working fine (rebuilding currently)

but since the restart my Cache Pool no longer exists and shows as blue square new devices?

 

have I lost my cache? all of my appdata for my dockers etc?

 

there was no mention of copying cache files before following this procedure, have been happily using Unraid for many years and have not seen this before

 

thanks in advance

1 hour ago, Markyb0y said:

restart my Cache Pool no longer exists and shows as blue square new devices?

This is normal after a new config, as long as all the original pool members are assigned the original pool will be imported (there can't be a "all data on this device will be deleted after array start" or similar warning for any of the devices.

Hi Johnnie.black, thanks for the response, so when my parity rebuild is complete my pool will be back also?

 

as I said since starting the array the pool has shown the 2 drives as new?

Edited July 15, 20205 yr by Markyb0y

Pool should show as new before array start, not after, now it's showing as unmountable, also those very high write numbers suggest a problem, please post the diagnostics: Tools -> Diagnostics

here is my diagnostics, reads are high as I have used these drives for several years without a single issue as cache (until now), also please let me know what you are looking at so I can learn more about what I should be looking for

Edited July 16, 20205 yr by Markyb0y

25 minutes ago, Markyb0y said:

reads are high as I have used these drives for several years

Stats are reset with all reboots, so it's not that for sure, and there are problems with various devices, including both cache devices, e.g.:

 

Jul 15 12:50:51 UNRAID kernel: sd 8:0:5:0: [sdi] 40961 512-byte logical blocks: (21.0 MB/20.0 MiB)
Jul 15 12:50:51 UNRAID kernel: sd 8:0:5:0: [sdi] Write Protect is off
Jul 15 12:50:51 UNRAID kernel: sd 8:0:5:0: [sdi] Mode Sense: 7f 00 00 08
Jul 15 12:50:51 UNRAID kernel: sd 8:0:5:0: [sdi] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
Jul 15 12:50:51 UNRAID kernel: sd 8:0:5:0: [sdi] tag#1374 UNKNOWN(0x2003) Result: hostbyte=0x0b driverbyte=0x00
Jul 15 12:50:51 UNRAID kernel: sd 8:0:5:0: [sdi] tag#1374 CDB: opcode=0x28 28 00 00 00 00 00 00 00 01 00
Jul 15 12:50:51 UNRAID kernel: print_req_error: I/O error, dev sdi, sector 0
Jul 15 12:50:51 UNRAID kernel: Buffer I/O error on dev sdi, logical block 0, async page read
Jul 15 12:50:51 UNRAID kernel: sd 8:0:5:0: [sdi] tag#1375 UNKNOWN(0x2003) Result: hostbyte=0x0b driverbyte=0x00
Jul 15 12:50:51 UNRAID kernel: sd 8:0:5:0: [sdi] tag#1375 CDB: opcode=0x28 28 00 00 00 00 01 00 00 01 00
Jul 15 12:50:51 UNRAID kernel: print_req_error: I/O error, dev sdi, sector 1
Jul 15 12:50:51 UNRAID kernel: Buffer I/O error on dev sdi, logical block 1, async page read
Jul 15 12:50:51 UNRAID kernel: sd 8:0:5:0: [sdi] tag#1376 UNKNOWN(0x2003) Result: hostbyte=0x0b driverbyte=0x00
Jul 15 12:50:51 UNRAID kernel: sd 8:0:5:0: [sdi] tag#1376 CDB: opcode=0x28 28 00 00 00 00 02 00 00 01 00
Jul 15 12:50:51 UNRAID kernel: print_req_error: I/O error, dev sdi, sector 2

 

SSDs are best not connected to a SAS2 LSI since trim might not work, it's also on a very old firmware, could also be a power/connection problem.

 

 

thansk for the info Johnnie