FreeNAS Installation and Systemboot stops

Maxicko

Cadet
Joined
Dec 29, 2019
Messages
7
Hi Community,

i want to setup a FreeNAS-System and got a big problem with booting the installation (and FreeNAS itself).

Installation always freezes just before the console should come up.
It's not exactly the same line every time, but always some line with "uhub1: .."
At this point i can't do anything but restart the system.

I already tried nearly anything i could find from different posts (Bios settings, bootloader settings).

FreeNAS-Version is 11.2 Stable (also tried 11.3-RC1).
It is not a FreeBSD-Problem. With Version 11.2,11.3 and latest 12.3 i always get to the setup console.

Meanwhile i've installed FreeNAS 11.2 on a SSD in another system. But when i boot the SSD on the final system -> same problem.

Hardware is :

Mainboard: Fujitsu D3641-S with Intel C246 Chipset (latest BIOS 1.7.0)
CPU : Intel i3-8100
RAM: Kingston DIMM 16 GB DDR4-2400 ECC

I hope that someone here can give me a hint what else i could try.

Thanks very much and happy new year in advance.

KR,
Max
 

sretalla

Powered by Neutrality
Moderator
Joined
Jan 1, 2016
Messages
9,703
You haven't given details of the hardware you're trying to run on... that may be an important factor as FreeNAS switched to use the FreeBSD bootloader just after 11.0.

Often older systems/BIOS has trouble supporting that bootloader (newer systems should be fine).

But you can still install FreeBSD using GRUB, (just like FreeNAS used to), so maybe that explains how you are doing it in those cases...?

It's all guesswork for now until you share a but more about the age of the hardware.

EDIT: I see you added system information (or I became less blind somehow).

An interesting point in the board documentation: (http://www.braemac.co.uk/images/fujitsu/Fujitsu update 2019/DS-D3641-S.pdf)
1577639426034.png



Linux not officially supported yet and no mention of FreeBSD

Maybe you can look at disabling onboard components in the BIOS to see if you can get it to boot further.
 
Last edited:

Maxicko

Cadet
Joined
Dec 29, 2019
Messages
7
Hi,

as you noticed, the board is relatively new. BIOS Date was Dec 18 and i updated it to the latest from Jun 19.
I saw the table you've posted in your edit, but it seems to be no problem for another Fujitsu Board which is used in this (german) tutorial:
As far as i see, the only difference is, that this board is more for industrial use (Serial Ports, GPIO, 2nd LAN Ports).

It must be something special what's implemented in the FreeNAS Bootprocedure.
I've tested the same (and other) FreeBSD-Versions and i always get to the setup console without any problem.

KR,
Max
 

Maxicko

Cadet
Joined
Dec 29, 2019
Messages
7
I don't know if it's right direction to dive deeper, but usb-settings seem to make a difference:

Boot from USB-Stick with all ports enabled:
Code:
Trying to mount root from cd9660: iso9660/FREENAS []...
Root mount waiting for: usbus0
Root mount waiting for: usbus0
uhub0: 26 ports with 26 removable, self powered
random: harvesting attach, 8 bytes (4 bits) from uhub0
Root mount waiting for: usbus0


With setting "used ports enabled" (in this case USB-Stick and Keyboard):
Code:
Root mount waiting for: usbus0
uhub0: 26 ports with 26 removable, self powered
ugen0.2: <SanDisk Extreme> at usbus
umass0 on uhub0
umass0: ...
umass0: ...
umass0: ...
random: harvesting attach, 8 bytes (4 bits) from uhub0
pass0 at umass-sim0 bus 0 scbus7 target 0 lun 0
pass0: ...
pass0: ...
pass0: ...
GEOM: new disk da0
da0 at umass-sim0 ...
da0: ...
da0: ...
da0: ...
da0: ...
da0: ...
da0: ...
GEOM: da0: the secondary GPT header is not in the last LBA
GEIM: iso9660/FREENAS: the secondary GPT header is not in the last LBA
Root mount waiting for: usbus0


When i boot from the installation i made on ssd and another computer and there is no usb-device attached:
Code:
uhub0: 26 ports with 26 removable, self powered
ugen0.2: <vendor 0x83eb Standard USB Hub> at usbus0
uhub1 on uhub0
uhub1: <Standard USB Hub> on usbus0



In another thread someone described a problem with watchdog, but i think that'S something different.

At least in my BIOS-settings watchdog stands on disabled and i see this a few lines above before it stops:
Code:
wbwd0: <Nuvoton NCT6102 (0xc4/0x53) Watchdog Timer> at port 0x2e-0x2f on isa0
wbwd0: Before watchdog attach: Watchdog enabled. Scaling by 1s, timer at 4 (<=4sF7 0x00
 

Maxicko

Cadet
Joined
Dec 29, 2019
Messages
7
FreeBSD 11.2-Boot:

Same as FreeNAS (with just used ports enabled) and then:
Code:
mountroot: waiting for device /dev/iso9660/11_2_RELEASE_AMD64_CD...
cd9660: RockRidge Extension
...
...


With FreeBSD-Boot i can't find any lines about watchdog....

What i don't see with FreeNAS boot are lines about ugen0.3 and ugen0.4.
But i don't know if that's relevant.
 

sretalla

Powered by Neutrality
Moderator
Joined
Jan 1, 2016
Messages
9,703
ugen 0.3 and 0.4 are devices 3 and 4 on the USB bus 0... the one that seems to be the showstopper.

watchdog is related to IPMI (iirc) and may not be loaded by default in stock FreeBSD.
 

Maxicko

Cadet
Joined
Dec 29, 2019
Messages
7
It seems that the hub itself is ugen0.2. Keyboard and Bootstick are on 0.3 and 0.4.
But even when i start the system without any usb-device attached, it stops at the same point.

Is there any way to disable watchdog in FreeNAS?
Already tried "set wbwd_load="NO"" and "set kFreeBSD.hint.wbwd.0.disabled="1"".
But both don't change anything.
 

Maxicko

Cadet
Joined
Dec 29, 2019
Messages
7
So now i'm pretty sure that it is watchdog.
I've installed FreeBSD 11.3 and added to the loader.conf this line : "wbwd_load="YES""
Now i have the same behaviour with this installation.

Is there any way to edit the loader.conf in the loader prompt before boot?
I tried "set wbwd_load="NO", but that didn't change anything.
Maybe that's because it's not a variable of the list there.

If there is no simple way to deactivate it meanwhile boot, i would have to install it on another system and change the loader.conf there.
But then i would still have to clone the installation from ssd to nvme...
So i would prefer a solution where i can install it directly on my system. ;)

KR,
Max
 

Maxicko

Cadet
Joined
Dec 29, 2019
Messages
7
wbwd_load="NO" isn't enough
I had to disable it in /boot/device.hints with hint.wbwd.0.disabled="1"

Seems to be the same problem as here, but without the reboot:

Now i'm trying to get the installation from ssd to nvme...
 
Top