Can't Access Pool?

[jonathanb4fitch]

I/O error. Weird. Is there actually an I/O error reported by the kernel when you do that?

Type "dmesg" and look at the end of it (or watch the console).

Code:

[root@freenas] ~# dmesg
arp: 172.16.32.120 moved from 54:26:96:d2:83:89 to 7c:d1:c3:c7:5b:87 on re0
arp: 172.16.32.120 moved from 7c:d1:c3:c7:5b:87 to 54:26:96:d2:83:89 on re0
arp: 172.16.32.120 moved from 54:26:96:d2:83:89 to 7c:d1:c3:c7:5b:87 on re0
arp: 172.16.32.120 moved from 7c:d1:c3:c7:5b:87 to 54:26:96:d2:83:89 on re0
arp: 172.16.32.120 moved from 54:26:96:d2:83:89 to 7c:d1:c3:c7:5b:87 on re0
arp: 172.16.32.120 moved from 7c:d1:c3:c7:5b:87 to 54:26:96:d2:83:89 on re0
arp: 172.16.32.120 moved from 54:26:96:d2:83:89 to 7c:d1:c3:c7:5b:87 on re0

I have no idea what this means haha. Device IDs?

 

[DrKK]

Code:

[root@freenas] ~# dmesg
arp: 172.16.32.120 moved from 54:26:96:d2:83:89 to 7c:d1:c3:c7:5b:87 on re0
arp: 172.16.32.120 moved from 7c:d1:c3:c7:5b:87 to 54:26:96:d2:83:89 on re0
arp: 172.16.32.120 moved from 54:26:96:d2:83:89 to 7c:d1:c3:c7:5b:87 on re0
arp: 172.16.32.120 moved from 7c:d1:c3:c7:5b:87 to 54:26:96:d2:83:89 on re0
arp: 172.16.32.120 moved from 54:26:96:d2:83:89 to 7c:d1:c3:c7:5b:87 on re0
arp: 172.16.32.120 moved from 7c:d1:c3:c7:5b:87 to 54:26:96:d2:83:89 on re0
arp: 172.16.32.120 moved from 54:26:96:d2:83:89 to 7c:d1:c3:c7:5b:87 on re0

I have no idea what this means haha. Device IDs?

No sir, that's some mobile device, like a phone, moving from on wireless access point, to another. Nothing to do with drives.

 

[jonathanb4fitch]

I/O error. Weird. Is there actually an I/O error reported by the kernel when you do that?

Type "dmesg" and look at the end of it (or watch the console).

Any further advice?

 

[SweetAndLow]

Fix your IP conflict on your network. The computers with those Mac address are using the same ip.

 

[cyberjock]

Yeah, I've been very busy (at iXHQ this week). Unfortunately there's not much to say. The hardware doesn't meet the minimum requirements and the zpool shows as faulted. Nothing obvious to fix here.

 

[jgreco]

Any further advice?

Check the partition tables on each disk to see if there's anything else obviously wrong. At this point, it kinda sounds like a software-generated fault, which probably means pool corruption, which probably means pool loss. Depending on how valuable your data is to you, you can weigh the risks of trying a forced pool import.

 

[danb35]

There's always the 'zpool import -Fn' option--it should tell you if it thinks the forced import will work, without actually changing anything on the disks.

 

[jgreco]

Excellent point. Try that. I'm obviously not thinking as clearly as @danb35 today.