Watchguard questions

[deanot]

This is getting worse, now it will not get past the bios.  It gets stuck on this screen and I am stumped, I thought it was the 2.2.1 image so I downloaded and pushed 2.2 to the CF.

Anyone have a clue?

[stephenw10]

If you are using a new CF card and you're still running BIOS V1.7 (as you are) then you will need to reset the primary master channel to auto so that it detects the card geometry and then change back to CHS H=2.
Alternatively the image may not be on the card correctly, did you extract the image first?

Steve

[deanot]

Yeah, I have done this 12 times now with the settings for the drive.

I press enter to auto detect the drive, which shows capacity of 8019 MB

I change the IDE channel 0 master mode to manual, access mode to CHS, change heads to 2.

Save and exit yes, reboots and does the mem check…...  starts the PCI device listing and gets stuck, now on En?decryption.....

I did extract the image, used Win32diskimager to put the image on the CF.

[deanot]

Frustrated…

[deanot]

I made some progress…....

Now all I am seeing is this repeatedly.

Timecounter "TSC" frequency 1300076613 Hz quality 800
uhub0: 2 ports with 2 removable, self powered
uhub1: 2 ports with 2 removable, self powered
uhub2: 2 ports with 2 removable, self powered
uhub3: 2 ports with 2 removable, self powered
uhub4: 8 ports with 8 removable, self powered
(ada0:ata0:0:0:0): READ_DMA. ACB: c8 00 de fc ee 40 00 00 00 00 01 00
(ada0:ata0:0:0:0): CAM status: Command timeout
(ada0:ata0:0:0:0): Retrying command
ata0: DMA limited to UDMA33, controller found non-ATA66 cable
(ada0:ata0:0:0:0): READ_DMA. ACB: c8 00 de fc ee 40 00 00 00 00 01 00
(ada0:ata0:0:0:0): CAM status: Command timeout
(ada0:ata0:0:0:0): Retrying command
ata0: DMA limited to UDMA33, controller found non-ATA66 cable
(ada0:ata0:0:0:0): READ_DMA. ACB: c8 00 de fc ee 40 00 00 00 00 01 00
(ada0:ata0:0:0:0): CAM status: Command timeout
(ada0:ata0:0:0:0): Retrying command
ata0: DMA limited to UDMA33, controller found non-ATA66 cable

[deanot]

Figured it out….

set hint.ata.0.mode=PIO4
boot

Set up my Wan and Lan and off to the interface to set the rest up!

The issue with the card or getting stuck at the boot, that was due to my installing the bigger CF and running auto detect on that CF.  The instructions I was following was not very good, found more and I left the original card in and set manual and 2 hd from that.  Booted right away, well until I got the error above.

I really appreciate your help.

[stephenw10]

Ah, interesting. I admit I've not tried an 8GB myself. I guess the presented card geometry is sufficiently different to cause a problem.
Glad you got it sorted.

Steve

[deanot]

It certainly would seem so, I did not think about it at first, the instructions I was following was not the original and could not remember all of the details to get it working again.

An 8 gig card is really over kill, the 4G does what it says, it Partitions the drive and leaves around 3.7GB unpartitioned on the CF, maybe use that later as a swap drive or something.

So glad it is up and running, I still have not looked to make sure the correct directories are on the CF…..  Best look into that before getting too excited huh.  lol.

[deanot]

Look what I have :)

$ df -hi
Filesystem          Size    Used  Avail Capacity iused ifree %iused  Mounted on
/dev/ufs/pfsense0    1.8G    190M    1.5G    11%    5.8k  237k    2%  /
devfs                1.0K    1.0K      0B  100%      0    0  100%  /dev
/dev/ufs/cf          49M    89K    45M    0%      23  6.5k    0%  /cf
/dev/md0              38M    584K    35M    2%    100  5.5k    2%  /tmp
/dev/md1              58M    19M    34M    36%    148  8.0k    2%  /var
devfs                1.0K    1.0K      0B  100%      0    0  100%  /var/dhcpd/dev