Disk error, cannot access data but should be RAID1

[mattie112]

Hi,

 

I have 2 disks added to a 2nd pool (Unraid 6.9.0-rc1) and I have some issues with it. Last night my server crashed, did not see anything when I connected a monitor so I just hard-rebooted it.

 

Now the thing is, I have a pool for my VirtualMachines and one of that disks looks to be dead, well OK

 

But this is a RAID 1 pool so the data should be ok right?

 

But when I try to access the files (or start a VM):

root@Tower:/mnt/vmpool/domains# ls -alh
/bin/ls: cannot access 'server': Input/output error
/bin/ls: cannot access 'Xpenology': Input/output error
total 16K
drwxrwxrwx 1 nobody users 48 Aug 14 09:47 ./
drwxrwxrwx 1 nobody users 14 Jan  2 04:40 ../
d????????? ? ?      ?      ?            ? Xpenology/
drwxrwxrwx 1 root   root  42 Aug  8 14:00 debiandns/
d????????? ? ?      ?      ?            ? server/
root@Tower:/mnt/vmpool/domains#

 

Did I configure this incorrectly? Shouldn't my data be here? Any ideas? Diagnostics added.

 

edit:

I have not tried to reconnect the disk at this point, also I know this is not the latest Unraid version but I won't execute an upgrade in a problem state

tower-diagnostics-20210102-1016.zip

Edited January 2, 2021 by mattie112

[JorgeB]

Constant ATA errors on ATA1 and ATA2:

 

Jan  2 09:53:28 Tower kernel: ata1.00: link online but device misclassified
Jan  2 09:53:28 Tower kernel: ata1: link online but 1 devices misclassified, device detection might fail
Jan  2 09:53:29 Tower kernel: ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Jan  2 09:53:29 Tower kernel: ata2.00: link online but device misclassified
Jan  2 09:53:29 Tower kernel: ata2: link online but 1 devices misclassified, retrying
Jan  2 09:53:29 Tower kernel: ata2: reset failed (errno=-11), retrying in 10 secs
Jan  2 09:53:39 Tower kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Jan  2 09:53:39 Tower kernel: ata1.00: link online but device misclassified
Jan  2 09:53:39 Tower kernel: ata1: link online but 1 devices misclassified, retrying
Jan  2 09:53:39 Tower kernel: ata1: reset failed (errno=-11), retrying in 10 secs
Jan  2 09:53:39 Tower kernel: ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Jan  2 09:53:39 Tower kernel: ata2.00: link online but device misclassified
Jan  2 09:53:39 Tower kernel: ata2: link online but 1 devices misclassified, retrying
Jan  2 09:53:39 Tower kernel: ata2: reset failed (errno=-11), retrying in 35 secs
Jan  2 09:53:49 Tower kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Jan  2 09:53:49 Tower kernel: ata1.00: link online but device misclassified

 

Probably the SSDs, try connecting them in the other controller.

[mattie112]

Oh that's interesting, I didn't notices that it had issues with 2 disks. I thought it was only 1 because in the UI only 1 disks is "not installed". But yes if both disks have issues (perhaps the same controller need to check) then I can assume it has trouble accessing my data.

 

I will try to fiddle a bit and report back here.

[mattie112]

Well... that was strange:

When I stopped the array only 1 disk was missing the other one was "unassigned".

(They both where not listed in the "choose device" select)

 

But then after replugging them:

Not really sure what happend. They where on the same controller yes, but also other disks where on that controller.

 

So the questions I have left (perhaps for some Unraid employee):

- Why was it listed as 1 disk OK?

- Why was the pool still accessable? But then not everything could be accessed?

 

edit:

Oh and another question: I now notice my pool was converted to non-raid? So why?

 

Edited January 2, 2021 by mattie112

[JorgeB]

Both devices having issues suggest there's some connection/power problem or they could have a compatibility problem with the controller, hence why I suggested trying the other one.

[mattie112]

Yeah could be but (yes that is no guarantee) it worked perfectly for the last year, other disks also work fine and now it works again so for now I won't change anything. Mostly I am just confused on what the UI was reporting.

[JorgeB]

GUI is not great for monitoring pools, see here for more info.

[mattie112]

Ah great! I did not know that that was not fully integrated yet. I have now added the script (and yes this pool had errors, reset them now so i know if it still is a problem). Thanks for the tips!