Trouble importing pools from freenas 11.1-U7 to Truenas 13.0-U4

[russman]

Hello,

If this has been covered already, I apologize. I have done several searches and didn't find anything that helped.

I have a freenas 11.1-U7 install that is just used as a file server. It works really well and I believe when I first installed freenas, it was somewhere in the low 9s? It was early to middle 2015 and I'm sure that I installed the current release at that time.

The upgrades that I have done have gone really well and as far as I can remember, there weren't any issues.

Sometime last year, I tried to upgrade and according to the "Boot" tab under system, it was 11.3-U5. The upgrade went smoothly except it would not connect to the domain so I had no access to any mapped drives. It looks like after some troubleshooting, I then upgraded to 12.0-U8 I guess hoping that whatever was going on with Active Directory might have been corrected in a later release but I was in the same situation. I then rolled back to 11.1-U7 and stayed there until the first part of this year?

I wanted to put a new server at my house for off-site replication so I thought that it would be a good idea to be on the Truenas updated version. I bought a new SSD and installed Truenas core 13.0-U4 and then imported my pools. The problem was that I couldn't get access to the mapped drives from Windows. After trying multiple things unsuccessfully, I put the old SSD in and booted freenas. I had to go into storage>change permissions and put the correct permissions in before I had access to the mapped drives in Windows again.

I guess my question is what needs to be done to successfully import the pools from freenas to Truenas core or can this be done?

I'm not an expert by any means and quite frankly, freenas has worked so well that I haven't needed to do anything with it other than the occasional upgrade that I am not as proficient as I would like to be.

Any help or suggestions would be greatly appreciated.

Thanks,
Rusty

 

[Arwen]

Please supply the output from the following commands, in code tags;
zpool status zpool import

Further, it is always helpful to list your complete hardware. And how the disks or other storage are wired to the computer.

On rare occasions, an off brand device, like a disk controller, will have it's support dropped due to lack of testing. Or lack of support of modern features like DMA. This is probably not your case.

 

[russman]

I started to list my hardware but didn't think it would have a bearing. Next time, I will post that first.

Asus Z8NA-D6 motherboard
Dual Xeon E5520 @ 2.27GHz
48G PC3 10600 DDR3 ram
4 10TB WD Gold NAS drives - SATA to MB in 10 RAID

root@freenas:~ # zpool status
pool: Storage
state: ONLINE
scan: resilvered 69.7G in 0 days 04:06:49 with 0 errors on Wed Mar 15 17:40:27 2023
config:

NAME STATE READ WRITE CKSUM
Storage ONLINE 0 0 0
mirror-0 ONLINE 0 0 0
ada4p2 ONLINE 0 0 0
gptid/f5d622bd-2e6d-11e7-b3dd-bcaec526499c ONLINE 0 0 0
mirror-1 ONLINE 0 0 0
gptid/daef1894-28ed-11e7-8743-bcaec526499c ONLINE 0 0 0
gptid/614eed8f-2935-11e7-965b-bcaec526499c ONLINE 0 0 0

errors: No known data errors

pool: freenas-boot
state: DEGRADED
status: One or more devices could not be opened. Sufficient replicas exist for
the pool to continue functioning in a degraded state.
action: Attach the missing device and online it using 'zpool online'.
see: http://illumos.org/msg/ZFS-8000-2Q
scan: scrub repaired 0 in 0 days 00:01:21 with 0 errors on Sat Mar 25 03:46:21 2023
config:

NAME STATE READ WRITE CKSUM
freenas-boot DEGRADED 0 0 0
mirror-0 DEGRADED 0 0 0
ada0p2 ONLINE 0 0 0
11818633377269820959 UNAVAIL 0 0 0 was /dev/da0p2

The boot pool is degraded because the USB flash drive was left out when I was troubleshooting.

I don't get anything on the zpool import command. I should say that currently I'm running on the freenas OS because this is a production file server.

Everyone leaves early on Friday and because of that, I can start rebooting servers or doing upgrades, etc at 3:00 PM. If I can get some good suggestions, I can try them tomorrow at 3.

 

[c77dk]

How are the shares setup? If i remember correctly you could share the whole pool directly in earlier versions, but need a dataset now (or maybe I just need some sleep :p )

 

[Arwen]

Could you be a little clearer on your disk connections to the system board?
Are you using the 6 Intel SATA ports, without BIOS / Driver / fake RAID?

Many of that system board's options are HW RAID, which causes problems:

Z8NA-D6 | Servers & Workstations |

www.asus.com

See;

What's all the noise about HBAs, and why can't I use a RAID controller?

1) An HBA is a Host Bus Adapter. This is a controller that allows SAS and SATA devices to be attached to, and communicate directly with, a server. RAID controllers typically aggregate several disks into a Virtual Disk abstraction of some sort...

www.truenas.com

 

[russman]

Sorry for the delay in my answer. Here are the shares:

The drives are connected to the Intel SATA ports. There is no HW RAID no BIOS RAID.

 

[Arwen]

Okay, then I have no further suggestions, sorry.

 

[russman]

I appreciate your effort and time.

 

[russman]

Well, I thought that I would let everyone know what I did just in case someone was having the same issue.

I decided to try to do an "upgrade" again to 13.0-U4. My first hop was to 11.2-U8 and there was no issues. I don't know exactly what the next hops were as when freenas/truenas does the config backups, the default name changed from this: freenas-FreeNAS-11.1-U7 (b45bfcf29)-20230331145927.db to this: freenas-FreeNAS-11.1-U7 (b45bfcf29)-20230331145927.db to this: freenas-20230331153010.db. Since I didn't change the file name to include the release that it was backing up, I don't remember exactly what it was. If I look at system > boot, it shows 11.1-U7, 11.2-U8, 11.3-U5.1, 12.0-U8.1, 13.0-U4.

I don't know why it worked this time (3-31-23) and not the previous two times.

This time, I followed the "next hop" as shown by the next higher train. I don't remember if previously, I made each hop or skipped any, seems like I may have skipped , not sure.

Maybe they addressed some upgrade issues between then and now? Not sure but glad it worked.

Thanks for the help.