SOLVED Mounting Failed with Error 19

[Savell Martin]

Hey Guys,

I have a new Haswell based system so had to install 9.1 Beta otherwise network card isn't found on 8.3.1.

But upon cold or first boot (or first restart) I get an error mounting:
Mounting from ufs:/dev/ufs/FreeNASs1a failed with error 19.

This is using a 16gb USB flash drive on a USB 2 port.

See this screenshot for whole screen:

 

[dlavigne]

Did you install by CD or an .img file? If an .img file, which utility did you use to burn it to the stick?

 

[Savell Martin]

Installed from a CD.

 

[reidara]

I have the same issue. Error 19. The screen shot is the same.
I have haswell too... But Im installing from USB stick.

 

[dlavigne]

I'm not sure if the Haswell support has made it into FreeBSD 9.1 yet or if it is just in FreeBSD HEAD. From what you are experiencing, I suspect it has not. It looks like patches went into HEAD in February (http://lists.freebsd.org/pipermail/freebsd-current/2013-February/039421.html). Can you google a bit to see if those have been MFCd into 9.1, and if not, create a feature request at support.freenas.org to see if they can be.

 

[reidara]

I have no problem installing 8.3 on the same computer using haswell .
Cant find anything about haswell support in FreeBSD 9.1

PS! I am thinking of using ESXi and install FreeNAS on top of that in a VM with RDM.

 

[dlavigne]

I have no problem installing 8.3 on the same computer using haswell .

Interesting... Worth creating a ticket at support.freenas.org if one does not already exist.

 

[reidara]

I have created a ticket now

 

[gpsguy]

Please read these two threads, before you attempt to virtualize FreeNAS.

please do not run freenas in production as a virtual machine

absolutely must virtualize freenas a guide to not completely losing your data

PS! I am thinking of using ESXi and install FreeNAS on top of that in a VM with RDM.

 

[jgreco]

Well, there's a lot of speculation here but few facts.

1) Make /sure/ you are plugged into a USB2 port, not a USB2 device on a USB3 port.

2) Scroll back up (use SCRL LOCK and then PAGE UP/DOWN) to see whether or not the boot device has been found. 19 is "Operation not supported by device" which is a curious fsckin' thing, and makes me think that possibly it /has/ been found. Or possibly corruption is preventing it from being found.

3) FreeBSD has historically booted on lots of stuff prior to explicit support being available for the "latest and greatest" chipset/CPU/etc., so I am skeptical that "lack of Haswell support" would let it boot into the installer, install to media, and reboot into a kernel, but then just not be able to find the rootdev.

So I suggest to try this: when it's booting, and you see the "Welcome to FreeNAS" screen, hit ESC real quick to get to the loader prompt. Type:

set debug.acpi.disabled="hostres"
boot

and see if it works. Just curious. Oh, and also, output from a question mark at the mountroot prompt might be nice.

 

[reidara]

Im sure im using usb 2.0 port.

I stopped the booting and sat this variable and continued booting:
set debug.acpi.disabled="hostres"
boot

same result...
questionmark gives these devices:
List og GEOM managed disk devices:
ada4 ada3 ada2 ada1 ada0


When I scroll up i find something...
acpi Error: [RAMB] Namespace lookup failure, AE_NOT_FOUND

 

[Savell Martin]

So I haven't tried the hostres promt.

But I want to point out in my first post that I can get into FreeNAS...
Its just first boot, or first restart that does it.

I then turn off power and back on and it boots in fine.
Just never first time, but after it works, and the box works fine.

But if I reboot again then it does the same screen.

So I know the hardware is supported.

 

[cyberjock]

So I haven't tried the hostres promt.

But I want to point out in my first post that I can get into FreeNAS...
Its just first boot, or first restart that does it.

I then turn off power and back on and it boots in fine.
Just never first time, but after it works, and the box works fine.

But if I reboot again then it does the same screen.

So I know the hardware is supported.

That sounds to me like hardware that either isn't completely compatible or broken.

 

[Savell Martin]

Its not the hardware, at least im pretty sure its not.

I ran Memtest for 3 passes and all fine.

I am currently running unRAID as a test and its fine.
Been on for the last 16 hours not issues.

I would prefer FreeNAS

 

[reidara]

I wrote the latest nightly of 9.1 beta today
I am experiencing the same problem as you describe.
ok first boot. then after soft reset bang same problem. then after power off and on reboot fine.

 

[cyberjock]

Can you both list your hardware specs?

 

[Savell Martin]

Intel Haswell i5 4670T
Sabertooth Z87
Corsair Arctic White Vengeance 16gb 1.35v
Seasonic 660w Platinum
4x 3TB WD Reds
1x 128GB Samsung 840 Pro
1x Patriot Tab 16GB USB 3.0 Flash Drive (Boot Drive)

 

[reidara]

ASUS H87I-PLUS
TX 650M
Intel Core i5-4570S

 

[jgreco]

If it reliably boots after a coldboot but not after a warmboot, it could be that the BIOS is setting something funky, or it could be that FreeBSD is seeing something that it ought to be handling but isn't (or both problems combined). You should definitely see if the problem is consistent:

1) always works when booting after power-off,

2) always works when you halt the system, get the "press any key" prompt, and hit RESET (hard reset),

3) never works when you halt the system, get the "press any key" prompt, and hit spacebar.

These cases each exercise different sets of circumstances, and the answer for each one should be consistent.

 

[cyberjock]

If it reliably boots after a coldboot but not after a warmboot, it could be that the BIOS is setting something funky, or it could be that FreeBSD is seeing something that it ought to be handling but isn't (or both problems combined). You should definitely see if the problem is consistent:

1) always works when booting after power-off,

2) always works when you halt the system, get the "press any key" prompt, and hit RESET (hard reset),

3) never works when you halt the system, get the "press any key" prompt, and hit spacebar.

These cases each exercise different sets of circumstances, and the answer for each one should be consistent.

+1. Something is still wrong and should be investigated.