Scoopsy13

@JorgeB That worked perfectly, thank you for taking the time to answer my post.

Hi, Thanks for the quick reply. I tried running the commands you mentioned but it came back as unrecognised. root@Monterrey:/mnt/user/backups# zpool mount -a unrecognized command 'mount'

Hi, I am hoping someone could help me with the issues I am having. It seems after a certain period oftime unraid loses the ability to write to some of the shares in my array. Trying mkdir (mkdir: cannot create directory ‘test1’: Invalid argument) or uploading files results in errors. However after rebooting everything returns to normal for a short while (maybe a hour or 2) before reverting to a state of not being able to write to the disk. For reference I cant write data to these shares below but not any other shares on the system. appdata domains isos system I have upload diagnostics below, could anyone help me to try and figure out whats happening on the server. Thanks monterrey-diagnostics-20251103-1042.zip

All my hard drives are powered by a backplane using two molex connections for power.

Hi, Hoping someone can help. Over the holiday period my parity disk dropped out into an error state. Each time I try to rebuild the disk the drive eventually drops back into an error state and shows errors against the disk. I have tried moving the drive to another bay in my server, replaced the sata cable to utilise the onboard storage controller instead of the LSI card my other drives are using and used an entirely different disk but the errors are occurring just the same. I have attached the diagnostics if anyone could help me shed some light on what it going on here. Thanks monterrey-diagnostics-20250102-2304.zip

I switched the drive to 3 different bays and on the 3rd try it seems to be rebuilding the parity now. Will most likely order replacement mini sas to sata cables. Will keep an eye on both the drive and the cables moving forward. Thanks for the help

Hi, I am looking for some assistance to identify whats going on with my new parity disk. Its hitting errors and being disbaled in unraid, I have already powered down the server and reseated the drive in a different bay just in case it was the ports that were causing the issue but I ran into the same issue when trying to rebuild the disk as parity again. Some of the errors can be seen below, I have also attached both the server diagnostics and I will attached the SMART extended self-test once it finishes. Can anyone help out at all? Thanks ```Jan 31 21:24:21 Monterrey kernel: I/O error, dev sdf, sector 6716624 op 0x1:(WRITE) flags 0x4000 phys_seg 128 prio class 2 Jan 31 21:24:21 Monterrey kernel: sd 2:0:4:0: [sdf] tag#2106 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Jan 31 21:24:21 Monterrey kernel: sd 2:0:4:0: [sdf] tag#2106 Sense Key : 0x2 [current] Jan 31 21:24:21 Monterrey kernel: sd 2:0:4:0: [sdf] tag#2106 ASC=0x4 ASCQ=0x0 Jan 31 21:24:21 Monterrey kernel: sd 2:0:4:0: [sdf] tag#2106 CDB: opcode=0x8a 8a 00 00 00 00 00 00 66 80 d0 00 00 04 00 00 00 Jan 31 21:24:21 Monterrey kernel: I/O error, dev sdf, sector 6717648 op 0x1:(WRITE) flags 0x4000 phys_seg 128 prio class 2 Jan 31 21:24:21 Monterrey kernel: sd 2:0:4:0: [sdf] tag#2107 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Jan 31 21:24:21 Monterrey kernel: sd 2:0:4:0: [sdf] tag#2107 Sense Key : 0x2 [current] Jan 31 21:24:21 Monterrey kernel: sd 2:0:4:0: [sdf] tag#2107 ASC=0x4 ASCQ=0x0 Jan 31 21:24:21 Monterrey kernel: sd 2:0:4:0: [sdf] tag#2107 CDB: opcode=0x8a 8a 00 00 00 00 00 00 66 84 d0 00 00 04 00 00 00 Jan 31 21:24:21 Monterrey kernel: I/O error, dev sdf, sector 6718672 op 0x1:(WRITE) flags 0x4000 phys_seg 128 prio class 2 Jan 31 21:24:21 Monterrey kernel: sd 2:0:4:0: [sdf] tag#2109 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Jan 31 21:24:21 Monterrey kernel: sd 2:0:4:0: [sdf] tag#2109 Sense Key : 0x2 [current] Jan 31 21:24:21 Monterrey kernel: sd 2:0:4:0: [sdf] tag#2109 ASC=0x4 ASCQ=0x0 Jan 31 21:24:21 Monterrey kernel: sd 2:0:4:0: [sdf] tag#2109 CDB: opcode=0x8a 8a 00 00 00 00 00 00 66 88 d0 00 00 04 00 00 00 Jan 31 21:24:21 Monterrey kernel: I/O error, dev sdf, sector 6719696 op 0x1:(WRITE) flags 0x0 phys_seg 128 prio class 2``` monterrey-diagnostics-20240131-2126.zip

Thanks very much @whitedwarf This fixed my issue as well.