Booting from CF stuck halfway
Hi all gurus, PF newbie entering…
After having to use a consumer router/fw for a couple of years I'm now setting up a new PF box.
I used to use m0n0wall for several years, so PF seemed as a natural and more feature-rich successor, and I allready like it :)
I bought the GA-J1900N-D3V mini ITX board (which I've read afterwards some people had problems with) and set it up with 8GB of RAM and a CF cardreader with SATA.
Wrote (Win32diskimager) the nanoBSD image (64bit) to the card and tried to boot of it.
At start it seemed all fine, until it reached the "Mounting filesystem...", where it gets stuck and writes "WRITE_MUL. ACB: c5,..." etc, see picture
So, I tried doing a new install from USB thumb drive to the CF card instead , but same result.
I then wrote the image to the USB thumb drive and tried booting that, instead of the CF, and everything works just fine :) ???
However, it would be nice to be able to use CF since I have a couple of industrial grade ones laying around for no other use, so does someone know why it can't finish boot from CF?
I'v used as much standard bios settings as possible, and also tried changing settings for IDE/USB/legacy etc as many suggests for this MB. Bios version F4.
![pfSense boot error.jpg](/public/imported_attachments/1/pfSense boot error.jpg)
![pfSense boot error.jpg_thumb](/public/imported_attachments/1/pfSense boot error.jpg_thumb)
That's a 256 MB CF card from the looks of it? None of our images will fit on a 256 MB CF, guessing you ended up with a fraction of the image.
Hmm, strange, because it's definitely a 1G CF card used, and win32diskimager didn't complain either when i wrote the image. Neither did I seem to get any errors when doing the install from USB to CF, but both behaves in the same manor.
Isn't it so that the image contains several partitions, and that is what can be seen in the picture (i.e. one partition being 240M)?
Could there be some issue with the CF–>SATA adapter that make the CF to appear with wrong size?
Possible the 1G image is just a little too big for your "1G" card.
That seems to be an ongoing fight with CF manufacturers labelling a card as 1G and delivering "slightly" less.
You could try a larger card.
Did you download the 1G nanobsd img file?
Yes, I used the 1G nano image.
The size mismatch actully occured when i tried to write a 2G image to a 2G USB drive, and Win32diskimager complained so had to use the 1G image instead. No such error with the CF card though, but the size check seems to work so less probable it's a size mismatch. But of course, I can do a test next time I open the case.