APU wont boot - even with "set kern.cam.boot_delay=10000"
-
Hello!
I wanted to install my second APU-based pfsense system and run into bad problem. My second APU board won't boot with pfsense 2.1.5 amd64 from the 4GB SDCard.
I read the thread about getting into the boot loader and setting up kern.cam.boot_delay=10000 but it still jumps into
Consoles: serial port BIOS drive C: is disk0 BIOS 639kB/2064688kB available memory FreeBSD/x86 bootstrap loader, Revision 1.1 (root@pf2_1_1_amd64.pfsense.org, Mon Aug 25 08:18:48 EDT 2014) Loading /boot/defaults/loader.conf /boot/kernel/kernel data=0xbc1792 data=0x596478+0xe0ed0 syms=[0x8+0x125f70+0x8+0x113bc5] / Hit [Enter] to boot immediately, or any other key for command prompt. Booting [/boot/kernel/kernel] in 3 seconds... Type '?' for a list of commands, 'help' for more detailed help. OK set kern.cam.boot_delay=10000 OK bootand when it stops:
ugen6.2: <generic> at usbus6 umass0: <generic 0="" 2="" flash="" card="" readerwriter,="" class="" 0,="" rev="" 2.01="" 1.00,="" addr=""> on usbus6 umass0: SCSI over Bulk-Only; quirks = 0x4001 umass0:0:0:-1: Attached to scbus0 SMP: AP CPU #1 Launched! da0 at umass-sim0 bus 0 scbus0 target 0 lun 0 da0: <multiple card ="" reader="" 1.00=""> Removable Direct Access SCSI-4 device da0: 40.000MB/s transfers da0: 3781MB (7744512 512 byte sectors: 255H 63S/T 482C) GEOM: da0: the primary GPT table is corrupt or invalid. GEOM: da0: using the secondary instead -- recovery strongly advised. Trying to mount root from ufs:/dev/ufs/pfsense0 ROOT MOUNT ERROR: If you have invalid mount options, reboot, and first try the following from the loader prompt: set vfs.root.mountfrom.options=rw and then remove invalid mount options from /etc/fstab. Loader variables: vfs.root.mountfrom=ufs:/dev/ufs/pfsense0 vfs.root.mountfrom.options=ro,sync,noatime Manual root filesystem specification: <fstype>:<device> Mount <device> using filesystem <fstype> eg. ufs:/dev/da0s1a eg. cd9660:/dev/acd0 This is equivalent to: mount -t cd9660 /dev/acd0 / ? List valid disk boot devices <empty line=""> Abort manual input mountroot></empty></fstype></device></device></fstype></multiple></generic></generic>Every hint is welcome ;)
-
Enter '?' at that prompt to see if anything is available mount.
What image did you write to the card? How?Steve
-
Hello Steve!
This is how I wrote the image to the SDCard:
gzcat pfSense-2.1.5-RELEASE-2g-amd64-nanobsd.img.gz | dd of=/dev/disk5 bs=16kWhat makes we wonder is that I have a another APU board running with no issues after I setup the boot delay as mentioned above. But this one shows the boot trouble.
In the meantime I have written random data at the SDCard for about 200-300 MB and after that I filled the SDCard completely with zeros and at the moment I am writing the pfsense image a third or fourth time to this SDCard.SDCard is a 4GB SanDisk.
I stumble about the following:
GEOM: da0: the primary GPT table is corrupt or invalid. GEOM: da0: using the secondary instead -- recovery strongly advised.This should not be there, right?
Bye,
eweri -
just tried after writing the image once again - still the same problem ???
-
You wrote the image to the other box/card in exactly the same way?
Are the cards the same? Flash media can sometimes report incorrect disk geometry which can give FreeBSD a hard time.
Same bios version on each APU?Steve
-
Hello Steve!
You wrote the image to the other box/card in exactly the same way?
If I remember right I did it in exactly the same way
Are the cards the same? Flash media can sometimes report incorrect disk geometry which can give FreeBSD a hard time.
Yes the cards are of same typ and capacity but I learned the hard way that 4GB (4x2^30) is not 4GB for SDCard manufacturers, that is why I use the 2g images with 4GB SDcards. I thought of a defective media, that's why I wrote random data and zero data to the card but that worked as expected.
Same bios version on each APU?
Yes, they have exactly the same bios, because I updated to a newer version with TinyCore linux installer from pcengines - this image boots without any problem, but I can not tell if I have exactly the same bios-setup. I did not change anything.
I have downloaded the image again but same problem - now I do not know where to go.
Next week I try a different board and a different SDcard - maybe somethings wrong with the board or the card but I don think its a hardware problem, i am still thinking it is a software problem.
Thanks,
eweri -
Have you used that card for anything else? Some quick googling seems to suggest that it may still have a Secondary GPT Header somewhere at the end of the drive space that the 2GB image isn't overwriting and is somehow being discovered. See:
https://forums.freenas.org/index.php?threads/freenas-8-3-0-root-mount-error.10270/#post-46115However you say you've already zero'd the card. :-\
Steve
-
Okay next try:
1. changed the APU board - same problem :(
2. changed the SDCard to a 32GB one and wrote the same 2GB image to it - it boots! ;)Now I do not know what is going on here? :o
Is it possible that a SDcard could be written without error but fails when read?
Now I going to stress test the 4GB SDcard
Bye,
eweri -
Okay - everything is working again ;)
This is what i did with the SDcard:
root# dd if=/dev/random of=/dev/disk4 bs=16k dd: /dev/disk4: end of device 242017+0 records in 242016+1 records out 3965194240 bytes transferred in 1900.317391 secs (2086596 bytes/sec) root# dd if=/dev/null of=/dev/disk4 bs=16k 0+0 records in 0+0 records out 0 bytes transferred in 0.000020 secs (0 bytes/sec) root# dd if=/dev/zero of=/dev/disk4 bs=16k dd: /dev/disk4: end of device 242017+0 records in 242016+1 records out 3965194240 bytes transferred in 1885.583163 secs (2102901 bytes/sec) root# gzcat pfSense-2.1.5-RELEASE-2g-amd64-nanobsd.img.gz |dd of=/dev/disk4 bs=16k 121458+1 records in 121458+1 records out 1989969408 bytes transferred in 944.297691 secs (2107354 bytes/sec)And after that it works as expected.
Bye, thanks for every hint
eweri