On FreeNAS 9.10 the configuration is in /data/freenas-v1.db. I'm not certain if that's the same location as 9.3. If you are able to recover your config database file, what I would do is a fresh 9.3 install, restore the configuration, and then upgrade to 9.10.
- Apr 13, 2014 Installing The Plex Plugin. The Plex Media Server plugin can be installed through the plugins interface in the FreeNAS web GUI. After clicking on the plugins button, select the available tab to see the list of all the available plugins for FreeNAS. Click on plexmediaserver to begin the installation process. FreeNAS will automatically download.
- In this article, you are going to learn how to install FreeNAS 11.1. The newest FreeNAS release as of now. On the weekend I decided to backup all my data and do a complete re-install of my FreeNAS box. I was running FreeNAS 9.10-U2 and had a couple of errors I wanted to get rid of a long time.
Bug #35032
Closed
No priority
Alexander Motin
Hardware
Low Medium
Third Party to Resolve
Yes
Yes
Yes
No
n/a
No
Description
Hi all,
I've installed FreeNAS from VirtualBox on USB which is Sandisk Ultra Fit 32Gb
I've installed FreeNAS from VirtualBox on USB which is Sandisk Ultra Fit 32Gb
During installation process, I've chossen 'Boot via UEFI'
Reading output, I see that new partition ms_dos is added formated as FAT16, then second partition is added and it should be ZFS.
But when I read partition table in Ubuntu using cfdisk, it shows only ZFS one partition.
To boot on modern UEFI bioses we need to have FAT32 partition with grubx64.efi (coppied as: /boot/efi/shellx64.efi on FAT32 partition).
I have ASRock J5005-ITX and successfully run grub pushed on FAT partition where grubx64.efi was placed as /boot/efi/shellx64.efi. I need next step as
add menu entry for FreeNas, install it on d0p2 on ZFS formatted and boot. Small step.
add menu entry for FreeNas, install it on d0p2 on ZFS formatted and boot. Small step.
bug_freenas installer.png(39.8 KB)bug_freenas installer.png | After installation - failed |
mounted_devices.png(18.6 KB)mounted_devices.png | mounted devices after failed installation |
grub-install error.png(35.3 KB)grub-install error.png | grub-install error |
after_reboot_of_install.png(45.6 KB)after_reboot_of_install.png | After rebooting installation machine and reading previously creaded usb disk. |
History
#1 Updated by Dru Lavigne about 3 years ago
- Category changed from Hardware to OS
- Assignee changed from Release Council to Alexander Motin
#2 Updated by Alexander Motin about 3 years ago
- Status changed from Unscreened to Blocked
- Severity changed from New to Low Medium
- Reason for Blocked set to Need additional information from Author
I have vague memories that FreeBSD newfs_msdos tool has some issues with FAT32 for UEFI boot partition, that is why we are still using FAT16 now. While UEFI specification indeed mentions FAT32, most of implementations boot just fine from FAT16 and even FAT12.
I don't know why cfdisk does not show you the boot partition, since partition table, especially GPT, operation does not depend on file system type. Just a guess, can't it be that you are looking on MBR protective partition covering whole disk, used as part of GPT to make legacy BIOS/OS to see that disk is busy?
In the title you are saying that U5 breaks UEFI booting, does that mean that some previous version was booting fine on the same system being installed same way?
If you believe that problem is indeed in FAT16, can you just copy the partition content out, reformat it to FAT32 and copy the content back? Also, you mention shellx64.efi file name, which IMHO is not a correct name for OS to use. FreeNAS 11.1 installs GURB as BOOTx64.efi. Also in 11.2 we are moving from GRUB to bsdloader, and while we still remain with FAT16 so far, it would be good to test how that work before we start any other activities on this.
#3 Updated by Grzegorz Szostak about 3 years ago
Alexander Motin wrote:
I have vague memories that FreeBSD newfs_msdos tool has some issues with FAT32 for UEFI boot partition, that is why we are still using FAT16 now. While UEFI specification indeed mentions FAT32, most of implementations boot just fine from FAT16 and even FAT12.
I don't know why cfdisk does not show you the boot partition, since partition table, especially GPT, operation does not depend on file system type. Just a guess, can't it be that you are looking on MBR protective partition covering whole disk, used as part of GPT to make legacy BIOS/OS to see that disk is busy?
No - disk is not busy. When I booted again and read USB in freenas installation it reports same: broken GPT. That's first issue.
I'm kida linux expert but new to freebsd.
I'm kida linux expert but new to freebsd.
Install Freenas 11
In the title you are saying that U5 breaks UEFI booting, does that mean that some previous version was booting fine on the same system being installed same way?
Don't know - I haven't installed previous versions.
If you believe that problem is indeed in FAT16, can you just copy the partition content out, reformat it to FAT32 and copy the content back? Also, you mention shellx64.efi file name, which IMHO is not a correct name for OS to use. FreeNAS 11.1 installs GURB as BOOTx64.efi. Also in 11.2 we are moving from GRUB to bsdloader, and while we still remain with FAT16 so far, it would be good to test how that work before we start any other activities on this.
No - Problem with GPT table broken. Reported also by FreeBSD.
Alexander Motin wrote:
I have vague memories that FreeBSD newfs_msdos tool has some issues with FAT32 for UEFI boot partition, that is why we are still using FAT16 now. While UEFI specification indeed mentions FAT32, most of implementations boot just fine from FAT16 and even FAT12.
I don't know why cfdisk does not show you the boot partition, since partition table, especially GPT, operation does not depend on file system type. Just a guess, can't it be that you are looking on MBR protective partition covering whole disk, used as part of GPT to make legacy BIOS/OS to see that disk is busy?
In the title you are saying that U5 breaks UEFI booting, does that mean that some previous version was booting fine on the same system being installed same way?
If you believe that problem is indeed in FAT16, can you just copy the partition content out, reformat it to FAT32 and copy the content back? Also, you mention shellx64.efi file name, which IMHO is not a correct name for OS to use. FreeNAS 11.1 installs GURB as BOOTx64.efi. Also in 11.2 we are moving from GRUB to bsdloader, and while we still remain with FAT16 so far, it would be good to test how that work before we start any other activities on this.
#4 Updated by Grzegorz Szostak about 3 years ago
- Filebug_freenas installer.pngbug_freenas installer.png added
- Category changed from OS to Hardware
- Severity changed from Low Medium to New
- Reason for Blocked deleted (
Need additional information from Author)
Look at attached image - Looks like partition is broken since FreeNAS installer can't recognize file system while installing grub.
#5 Updated by Grzegorz Szostak about 3 years ago
- Filemounted_devices.pngmounted_devices.png added
mnounted devices after installation failed.
#6 Updated by Grzegorz Szostak about 3 years ago
- Filegrub-install error.pnggrub-install error.png added
I've run command manually that was run by installer. Grub-install failed:
See attached screenshot
See attached screenshot
#7 Updated by Grzegorz Szostak about 3 years ago
- Fileafter_reboot_of_install.pngafter_reboot_of_install.png added
#8 Updated by Dru Lavigne about 3 years ago
- Status changed from Blocked to Unscreened
#9 Updated by Alexander Motin about 3 years ago
- Status changed from Unscreened to Blocked
- Severity changed from New to Low Medium
- Reason for Blocked set to Need additional information from Author
I don't think I previously saw such reports about GPT corruption during install. So my first guess is that virtualbox device pass-through may do something wrong, though I am not sure what exactly and may be wrong.
Could you collect some more data after failed installation:
- `geom disk list da0` -- to get disk geometry;
- `geom part list da0` -- to see partitions as OS sees them after install;
- `umount /tmp/data/boot/efi ; false > /dev/da0` -- to make OS retaste the partition table back from disk;
- check messages for any errors during retaste;
- `geom part list da0` -- if OS was able to retaste the partition table, look for any differences. Considering reported corruption after reboot I'd guess it fail.
- `geom disk list da0` -- to get disk geometry;
- `geom part list da0` -- to see partitions as OS sees them after install;
- `umount /tmp/data/boot/efi ; false > /dev/da0` -- to make OS retaste the partition table back from disk;
- check messages for any errors during retaste;
- `geom part list da0` -- if OS was able to retaste the partition table, look for any differences. Considering reported corruption after reboot I'd guess it fail.
PS: As I have told before, in FreeNAS 11.2 we are completely moving away of GRUB, so a lot of this code was already changed, and I am not sure deep debugging of this issue on 11.1-U5 is productive. If you could test 11.2 nightly build (http://download.freenas.org/11.2/MASTER/latest/x64/) in the same environment, it would be more interesting.
#10 Updated by Grzegorz Szostak about 3 years ago
Partial success.
Story:
After installing on usb wich ends with grub-install error I went to shell.
Then run gpart backup
Story:
After installing on usb wich ends with grub-install error I went to shell.
Then run gpart backup
Taken screenshot of data. Then reboot. And now went to Shell. Then saw error from FreeBSD that GPT for da0 is corrupted. So I created /tmp/backup file using vi and added what gpart backup printed. Then run gpart restore -F da0 < /tmp/backup.
Now went to linux virtual box, mounted /dev/sdb1 on /mnt - and it is visible and shows EFI/BOOT directory (empty). So I issued grub-install --target=x86_64-efi --efi-directory=/mnt/ --removable /dev/sdb1 and it worked.
Now went to linux virtual box, mounted /dev/sdb1 on /mnt - and it is visible and shows EFI/BOOT directory (empty). So I issued grub-install --target=x86_64-efi --efi-directory=/mnt/ --removable /dev/sdb1 and it worked.
Now I went to box with UEFI bios (ASRock J5005-ITX) and booted from usb. Worked up to grub rescue. Grub wasn't able to find disk <UUID>. Grub sees only (hd0) - no ZFS partition on it. I need to figure out how install grub from FreeNAS.. Can you help me with mounting ZFS from usb, mounting fat16 and running grub-install command egain?
#11 Updated by Alexander Motin about 3 years ago
Grzegorz Szostak wrote:
Can you help me with mounting ZFS from usb,
It would sound like `zpool import -R /tmp/data freenas-boot`.
mounting fat16
Something like `mount_msdosfs /dev/da0p1 /tmp/data/boot/efi`
and running grub-install command egain?
Something like `/usr/local/sbin/grub-install --efi-directory=/tmp/data/boot/efi --removable --target=x86_64-efi /dev/da0`.
But I'd say you are already beyond the point where usually 'no serviceable parts inside' stickers appear. I would not do that, but rather evacuated config (or taken one from backup) and reinstall.
#12 Updated by Grzegorz Szostak about 3 years ago
Switched to MASTER for 11.2.
Dowloaded FreeNAS-11.2-MASTER-201806220453-0bb3c44.iso
Cleaned usb drive under windows, added one primary partition and formatted using NTFS. Drive is recognizable by windows and diskpart shows one partition and offset 1024 KB.
Dowloaded FreeNAS-11.2-MASTER-201806220453-0bb3c44.iso
Cleaned usb drive under windows, added one primary partition and formatted using NTFS. Drive is recognizable by windows and diskpart shows one partition and offset 1024 KB.
Starting installation from Master iso image. Selecting UEFI. Message: installation succeeded. Went to box, inserting usb and no luck - bios shows meaning it wasn't able to find UEFI boot code on any of partitions on thumb.
So I inserted thumb into windows and running diskpart. Now sees only one partition with offset 512 B.
Inserting to ubuntu and running gparted.
Linux doesn't see partitions:
[ 5785.109716] sd 4:0:0:0: Attached scsi generic sg2 type 0
[ 5785.112430] sd 4:0:0:0: [sdb] 60063744 512-byte logical blocks: (30.8 GB/28.6 GiB)
[ 5785.116710] sd 4:0:0:0: [sdb] Write Protect is off
[ 5785.116721] sd 4:0:0:0: [sdb] Mode Sense: 43 00 00 00
[ 5785.121284] sd 4:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[ 5785.135776] sd 4:0:0:0: [sdb] Attached SCSI removable disk
[ 5785.109716] sd 4:0:0:0: Attached scsi generic sg2 type 0
[ 5785.112430] sd 4:0:0:0: [sdb] 60063744 512-byte logical blocks: (30.8 GB/28.6 GiB)
[ 5785.116710] sd 4:0:0:0: [sdb] Write Protect is off
[ 5785.116721] sd 4:0:0:0: [sdb] Mode Sense: 43 00 00 00
[ 5785.121284] sd 4:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[ 5785.135776] sd 4:0:0:0: [sdb] Attached SCSI removable disk
running gparted which reports:
Both the primary and backup GPT tables are corrupt. Try making a fresh table, and using Parted's rescue feature to recover partitions.
Both the primary and backup GPT tables are corrupt. Try making a fresh table, and using Parted's rescue feature to recover partitions.
Going to boot 11.2
dmesg for freebsd reports that:
GEOM: da0: corrupt or invalid GPT detected.
GEOM: da0: GPT rejected -- may not be recoverable.
GEOM: da0: corrupt or invalid GPT detected.
GEOM: da0: GPT rejected -- may not be recoverable.
Running geom on that this to show what is wrong:
- geom list disk da0
Providers:
1. Name: da0
Mediasize: 30752636928 (29G)
Sectoresize: 512
Mode: r0w0e0
fwsectors: 63
fwheads: 255
[..]
- geom part list da0
geom: No such geom da0.
No partitions.
Now I will partition it on virtualbox's linux machine but first clean on windows and format as NTFS. Succeeded.
Now I will partition it on virtualbox's linux machine but first clean on windows and format as NTFS. Succeeded.
Adding GPT, adding first partition as FAT32 with size 260MB, adding second partition to occupy rest of the drive.
Went to freenas installer - geom disk list ra0 - works
geom part list da0 - shows two partitions as expected
geom part list da0 - shows two partitions as expected
First partition is at offset 1024 KB
This layout of disk preserves all data. When first partition is at 512 B as after partitioning in FreeNAS installer - drive is unreadable and there's only one partition.
So please give me instructions to:
1. format second partition as zfs
2. install on firtst partition formatted as FAT32 outside EFI code or format it as FAT16 and install efi code
3. install system on ZFS partition
1. format second partition as zfs
2. install on firtst partition formatted as FAT32 outside EFI code or format it as FAT16 and install efi code
3. install system on ZFS partition
#13 Updated by Alexander Motin about 3 years ago
Do I understand right that you are still installing under VirtualBox to passed-through USB stick? What makes you do that? Is there some problem to install on some physical system? I just want to avoid chance that VirtualBox pass-through does something wrong somehow. If you install FreeNAS under the VirtualBox, does it boot there after the install?
#14 Updated by Grzegorz Szostak about 3 years ago
Alexander Motin wrote:
Do I understand right that you are still installing under VirtualBox to passed-through USB stick? What makes you do that? Is there some problem to install on some physical system? I just want to avoid chance that VirtualBox pass-through does something wrong somehow. If you install FreeNAS under the VirtualBox, does it boot there after the install?
Yes - good finding.Probably Windows is breaking GTP table once VirtualBox is releasing it. Thans for 512 B offset.
When I installed on VB and not releasing it to Windows - it was partialy worked. For that stage, that grub had problem idenfing file system. For Master release - not working at all.
MASTER:
- reports no problem during installation
- when I insert it to box - bios doesn't find any partition to boot. Uefi not run.
- reports problem by grub during installation with identifing filesystem
- when thumb insterted to box - it is trying to boot. But nothing found (bootx64.efi not putted on partition due to error).
Install Freenas On Old Computer
I'll try to install debian from debian VM - partiar success so far - got grub rescue but unable to boot since deboostrab doesn't put initrd file on root. Will work on that.
#15 Updated by Alexander Motin about 3 years ago
Freenas Install Corrupt Excel
- Status changed from Blocked to Closed
- Reason for Closing set to Third Party to Resolve
- Reason for Blocked deleted (
Need additional information from Author)
Let us know if you find issue that we can do something about.
#16 Updated by Dru Lavigne about 3 years ago
- Target version changed from Backlog to N/A
Also available in: AtomPDF