Unable to boot TrueNAS Core

TrueNAS General
22

Intel i210 or i350 are safe bets.

23

Thank you etorix for this buying advice.

Without waiting for my network card to be replaced before relaunching TrueNAS Core, I set about installing TrueNAS Scale (on test USB sticks).

The installation went well and I finally got access to my NAS via the web interface.

The problem now is that when I try to import my old pool, I get a kernel panic and the NAS reboots:

kernel_panic
kernel_panic1920Ɨ1093 185 KB

24

Hi all

Iā€™m still with Scale 25.04 and despite some settings Iā€™ve found on the net :

sysctl
sysctl2056Ɨ644 76.6 KB

ā€¦ I canā€™t manage to import my pool.

I would like to try the operation in ā€˜read onlyā€™ mode but I donā€™t know how to do it.

Does anyone have any ideas?
Thanks in advance

25

Hi all,

Iā€™m making progressā€¦
Via the ā€˜Linux shellā€™ and the command :
zpool import -o readonly=on -R /mnt Volume Volume2
(the initial pool name is Volume)
ā€¦I managed to mount my pool without causing a kernel panic.

Now my datasets appear in TrueNAS and thatā€™s a big improvement and a great hope for my data:

Datasets
Datasets1866Ɨ1432 151 KB

I can see my files in the Linux console, but how can I make them visible in TrueNAS and directly in the Finder (Iā€™m on macOS) to make a backup on external media.

I imagine that it should be possible to do this directly from the Linux console, but I donā€™t know anything about it and I donā€™t even know how to access a USB disk.
And will the copied files be readable directly under macOS?

Thanks for your help

26

Hi all,

I just saw on the net that macOS can natively recognize the zfs format.

So I installed one of the two data disks (they are mirrored, so identical) in an external box, and imported my pool from my Mac (with the appropriate command: sudo pool import -f -o readonly=on -R /Volumes Volume Nas )

I was able to recover some of my data, but one of the Datasets (ā€˜Utilisateursā€™) is recalcitrant and is only truly visible by an ā€˜importā€™ from TrueNAS.

My question therefore remains the same: how to make a Dataset visible in TrueNAS appear in the Finder without any pool being created in TrueNAS?

Thank you for the slightest clue

(PS: the Dataset in question is indeed ā€˜importedā€™ into TrueNAS but the copies on a Fat32 external disk - so that it remains compatible with macOS - are not done correctly and a large part of the data cannot be copied)

27

Permission issues?
mecOS specific resource branches not being copied correctly?

We do not have much information to work with.

28

Hi etorix,

Thank you for your support.

  1. macOS side
    As you suggest, there may be an access permission problem to some ā€˜Datasetsā€™ under macOS because the dataset concerned is that of the ā€˜usersā€™ which is probably more protected by TrueNAS than the others!?
    But how then to make it treated like everyone else?
    On the macOS desktop it appears -as others- as a mounted disk but with a small ā€˜forbidden senseā€™ panelā€¦ (I will make a screenshot so useful)

  2. TrueNAS side
    Under TrueNAS (in Linux console) all datasets are apparently accessible after mounting the pool.
    But when I want to copy the ā€˜usersā€™ folder on an externe USB drive, the copy is very partial, stops quite quickly, and finally Scale reboot

  3. To test?
    As a final solution I could maybe add two additional disks to my NAS to create a pool, but I donā€™t know how I can transfer the data from the datasets visible under TrueNAS (the 2 initial disks of the imported initial pool) to the created pool (with the 2 disks added).

I hope I have been a little clearer, but I can of course give precisions and answer all questions (but in my little area of expertise :frowning: )

29

Read-only prevents changing ownership/permissions.
If youā€™ve reinstalled anew, have you recreated users with the same user IDs as before on the NAS?

Why, oh why FAT32??? Use HFS or APFS: No size limit. Then copy all data, and reassign ownership on the copy.
sudo cp -a /Volumes/Nas/* /Volumes/MY_BIG_USB_DRIVE/ &

30

I didnā€™t know that Linux could write to an external drive formatted in HFS or APFSā€¦
Iā€™ll try that, thanks!

31

Linux canā€™t (not without further add-ons at least), but I thought you had the pool on macOS.

32

Yes, the pool can be directly imported under macOS, but one of the important datasets (ā€˜Utilisateursā€™) is not accessible.

Hence the need for me to also work on the TrueNAS mounted pool, and try to save the data to an external USB disk.

Iā€™ve looked for a file system natively supported by Linux and macOS, and at this stage Iā€™ve only found Fat32 with the limitations we know about.

Is there a more interesting alternative?

33

Hi all,

Iā€™ve finally got most of my data back:
Under TrueNAS, in Linux console, I first imported my pool in read-only mode, as already mentioned above.
Then I copied my data in SSH using the ā€˜scpā€™ command, repeating the process several times in case of errors.

SSH proved to be the only effective way of exchanging my data between Linux and macOS.
Whatā€™s more, itā€™s faster than a conventional copy.

As I still donā€™t know what happened to the original pool, I think Iā€™m going to abandon TrueNAS, at least temporarily, and make do with backups on external removable mediaā€¦

And thanks again to everyone here who took the time to help me :+1: