failed with error 19

Status
Not open for further replies.

John M. Długosz

Contributor
Joined
Sep 22, 2013
Messages
160
000276.png


My Inaugural Boot got this far.

I have a Supermicro X10 motherboard, but has a serial number indicating it is fresh, like made in the last month, so I expect it has the newer PCH. The symptom of "can't remount the USB" sounds like what I'm seeing, and was reported as a problem with early Intel chips on USB3.
 
D

dlavigne

Guest
Did you install from CD or write the image to USB? If the image, what tool did you use to write the image and what size stick?
 

John M. Długosz

Contributor
Joined
Sep 22, 2013
Messages
160
I moved the USB stick to a USB2 port, and it booted.
Then, the web page locked up (though ping and console menu still worked), and I rebooted. It gave the same error again. I power-cycled instead of just "restart"ing, and it worked again.

I tentatively think that the xHCI issue is still present even though I have a new board. The newer thread I read indicated that it was a problem with the PCH chip and boards made after a certain date would have the newer, corrected, one.
 

Dusan

Guru
Joined
Jan 29, 2013
Messages
1,165
I don't think so. The Intel bug is about USB 3.0 devices not being recognized after the system wakes from S3 sleep. There is no S3 sleep during FreeNAS boot sequence. This is more about the FreeBSD 9.1 xHCI driver being still a bit buggy / incompatible with the chipset. Disable xHCI and your experience should be much better.
 

tac12345

Dabbler
Joined
Jun 19, 2011
Messages
22
I have this same issue, and i don't have any usb3 port, or any xHCI in the bios. it on intel ICH9 generation.
 

Alfred Melvin

Explorer
Joined
Dec 5, 2012
Messages
55
I'm setting up new system listed in signature and had same problem with "error 19"
Reset bios to defaults, disabled usb 3.0, and purchased new ( and totally unused ) 8gb stick identical to one with "error 19" problem.
Plugged new usb stick into 2.0 port and did install from CD drive to new stick location and worked fine this time.
 

panz

Guru
Joined
May 24, 2013
Messages
556
This thing is driving me crazy. I've just completed my build with ASRock Z87 Pro4 + Intel Core i3-4130: no way to force USB sticks (I tried SanDisk and other well-known brands) to work with FreeNAS v. 9.1.1.

If I disable legacy USB or USB3 or xHCI from the BIOS, the system stops detecting the keyboard after reboot...

One strange behavior is: if I connect a mouse during installation from CD-Drive, FreeNAS continuously disconnects / reconnects the device.

I _must_ use 9.1 because of Giga PHY Intel® I217V LAN controller.

8.3.2-RELEASE-x64 (r12686+70c2cb8) doesn't have this problems (but I had to use an old RealTek LAN adapter, which is crap). :mad:
 

Dusan

Guru
Joined
Jan 29, 2013
Messages
1,165
If 8.3.2 works and 9.1.1 doesn't you can try disabling the xhci driver:
  1. Quickly hit Esc on the Welcome to FreeNAS boot prompt ([Esc]ape to loader prompt)
  2. unload xhci
  3. disable-module xhci
  4. boot
If it helps, create an xhci_load=no tunable (System->Tunables).
 

Alfred Melvin

Explorer
Joined
Dec 5, 2012
Messages
55
About a month ago I spent several days trying to get ASUS P8H77pro/i5 combination to work with no positive results.
Decided to give AMD system a shot with current system because I really want to use 9.1.1
So far less trouble than before. The systems I built with older twin Xeon and Opteron setups never had any issues at all with new
version but were just way too loud for use in my home.
 

panz

Guru
Joined
May 24, 2013
Messages
556
About a month ago I spent several days trying to get ASUS P8H77pro/i5 combination to work with no positive results.
Decided to give AMD system a shot with current system because I really want to use 9.1.1
So far less trouble than before. The systems I built with older twin Xeon and Opteron setups never had any issues at all with new
version but were just way too loud for use in my home.

I think it's not an hardware problem.
 

panz

Guru
Joined
May 24, 2013
Messages
556
If 8.3.2 works and 9.1.1 doesn't you can try disabling the xhci driver:
  1. Quickly hit Esc on the Welcome to FreeNAS boot prompt ([Esc]ape to loader prompt)
  2. unload xhci
  3. disable_module xhci
  4. boot
If it helps, create an xhci_load="no" tunable (System->Tunables).

it booted with your suggestions, but tunable settings didn't work. Tried redoing all the procedure, the system unloads the xhci but prints error 19 at sequent boot :oops:

I've just ordered an SSD, hoping this is going to solve the problem... :confused:
 

Dusan

Guru
Joined
Jan 29, 2013
Messages
1,165
it booted with your suggestions, but tunable settings didn't work.
How did you add the tunable? You need to go to System->Tunables->Add Tunable, set the Variable to xhci_load and Value to no (no quotes!, the system will add the quotes automatically when creating /boot/loader.conf.local).
 

Alfred Melvin

Explorer
Joined
Dec 5, 2012
Messages
55
The SSD will not solve the problem. Tried that with a 40gb that I had and still same "error 19".
My question is what circumstances trigger the "error 19" in the software?
Something is causing this to happen and the software designers must know what situation and/or circumstance is necessary for the
"error 19" response. Is it machine code problem? I can't see it as a random problem.
 

panz

Guru
Joined
May 24, 2013
Messages
556
How did you add the tunable? You need to go to System->Tunables->Add Tunable, set the Variable to xhci_load and Value to no (no quotes!, the system will add the quotes automatically when creating /boot/loader.conf.local).

I first tried to boot as you suggested:

"hit Esc on the Welcome to FreeNAS boot prompt ([Esc]ape to loader prompt)
unload xhci
disable_module xhci
boot"
It booted OK, and I had access to the WebGUI.

Then, I setup the tunable (and I did something wrong, maybe), because then the system didn't start and now doesn't accept the first procedure anymore. So I reinstalled 9.1.1 on the USB key, tried redoing the "Esc" method to regain access to the system, but it refuses with Error 19 :(
 

panz

Guru
Joined
May 24, 2013
Messages
556
The SSD will not solve the problem. Tried that with a 40gb that I had and still same "error 19".
My question is what circumstances trigger the "error 19" in the software?
Something is causing this to happen and the software designers must know what situation and/or circumstance is necessary for the
"error 19" response. Is it machine code problem? I can't see it as a random problem.

I thought the problem was with USB, because if I install 9.1.1 on a SATA HD it works flawlessly. The SSD is SATA so... Am I wrong?
 

panz

Guru
Joined
May 24, 2013
Messages
556
How did you add the tunable? You need to go to System->Tunables->Add Tunable, set the Variable to xhci_load and Value to no (no quotes!, the system will add the quotes automatically when creating /boot/loader.conf.local).

I found the error in the procedure!!! You wrote "disable_module xhci" for the command to enter after "ESC" at boot;

my fault not to check the available command list: it was "disable-module xhci" with a minus (or dash) between the 2 words, not an underline score! :cool:

Now I added the Tunable (as you suggested) and the system boots up correctly! Thank you :) :) :)
 

Dusan

Guru
Joined
Jan 29, 2013
Messages
1,165
my fault not to check the available command list: it was "disable-module xhci" with a minus (or dash) between the 2 words, not an underline score! :cool:
Ah, I'm sorry for the mistake :oops:, I typed that from top of my head. I fixed the instructions above for future readers.
 
Status
Not open for further replies.
Top