Motherboard: ASUS E35M1-I
CPU: Fusion AMD E-350 (onboard)
Memory: 8GB
Boot Drive: 32GB USB Flash Drive. Silicon Power
Hard Drives: 6 Drives. Each model is a WD30EZRX
RAID: ZFS2
Hard Disk Control: Motherboard onboard.
Network Card: Motherboard onboard.
FreeNas 11.0-U2
I have been using this system for several years. Today I was browsing my files via the network, and the share stopped. I went to look at my server. I turned on the KVM and Monitor. I saw a db> prompt. I had never seen such a prompt before.
After doing some basic web searching, I decided to replace the USB flash drive with a fresh install of 11.0-U2. The installation went fine. I was able to access the web gui. When I imported the pool, the wizard found the pool name. I clicked next, and waited. Eventually an error was claimed at the web gui. I went to look at my server's screen, and it was in the middle of a reboot.
More searching of this forum suggested to try importing the pool as read only. This would allow me to backup data via ssh, ftp, etc. I edited GRUB to use "set kFreeBSD.vfs.zfs.recover=1" and "set kFreeBSD.vfs.zfs.debug=1", to prevent the pool from being mounted (to prevent a reboot). Using the basic /bin/sh I was able to attempt importing the pool as read only. Again, I landed at a db> prompt.
In both cases, I see similar errors. The blkptr messages with addresses look potentially helpful. Just a guess.
Some further thread wandering proposed faulty hardware. I happen to have an extra identical motherboard. I swapped it before posting this, but I get the same results.
Can anyone please advise what I should try next? I do have some of this pool backed up but... it's not extensive. So much of my past would be lost :(
I also saw today stones being thrown for using desktop motherboards and non-ECC memory. Is this a fatal decision? If so, I've never seen any warnings appear that no ECC memory was detected when using my system. I've never known this to be concern. I would find it odd that you can even run FreeNAS on non-ECC if that's the case...
If anyone can please help, I would be greatly in debt to you. At the least, it would bring peace to know without any doubt that the pool truly is corrupt beyond any data recovery. I am comfortable in command lines and working with various tools, but that's mostly my linux side. I do not use FreeBSD beyond FreeNAS.
Thank you
CPU: Fusion AMD E-350 (onboard)
Memory: 8GB
Boot Drive: 32GB USB Flash Drive. Silicon Power
Hard Drives: 6 Drives. Each model is a WD30EZRX
RAID: ZFS2
Hard Disk Control: Motherboard onboard.
Network Card: Motherboard onboard.
FreeNas 11.0-U2
I have been using this system for several years. Today I was browsing my files via the network, and the share stopped. I went to look at my server. I turned on the KVM and Monitor. I saw a db> prompt. I had never seen such a prompt before.

After doing some basic web searching, I decided to replace the USB flash drive with a fresh install of 11.0-U2. The installation went fine. I was able to access the web gui. When I imported the pool, the wizard found the pool name. I clicked next, and waited. Eventually an error was claimed at the web gui. I went to look at my server's screen, and it was in the middle of a reboot.
More searching of this forum suggested to try importing the pool as read only. This would allow me to backup data via ssh, ftp, etc. I edited GRUB to use "set kFreeBSD.vfs.zfs.recover=1" and "set kFreeBSD.vfs.zfs.debug=1", to prevent the pool from being mounted (to prevent a reboot). Using the basic /bin/sh I was able to attempt importing the pool as read only. Again, I landed at a db> prompt.

In both cases, I see similar errors. The blkptr messages with addresses look potentially helpful. Just a guess.
Some further thread wandering proposed faulty hardware. I happen to have an extra identical motherboard. I swapped it before posting this, but I get the same results.
Can anyone please advise what I should try next? I do have some of this pool backed up but... it's not extensive. So much of my past would be lost :(
I also saw today stones being thrown for using desktop motherboards and non-ECC memory. Is this a fatal decision? If so, I've never seen any warnings appear that no ECC memory was detected when using my system. I've never known this to be concern. I would find it odd that you can even run FreeNAS on non-ECC if that's the case...
If anyone can please help, I would be greatly in debt to you. At the least, it would bring peace to know without any doubt that the pool truly is corrupt beyond any data recovery. I am comfortable in command lines and working with various tools, but that's mostly my linux side. I do not use FreeBSD beyond FreeNAS.
Thank you