On 1/26/2011 9:58 AM, Mike Tancsa wrote:
> On 1/25/2011 4:58 PM, Jed Clear wrote:
>
>> At least in 8.1 you can add the line "FlashDevice sandisk 4G" to your
>> nanobsd.conf file and omit the NANO_MEDIASIZE value. You might want to try
>> that first.
>
> Same issues :(
Some more details.
If I boot the box, and then do something like this
0[old261]# dd if=/dev/ad0 of=/dev/null bs=64k
It actually completes without error.
The errors seem to happen when I write to the box. e.g. mount -u / ;do
something;mount -u -oro /
on the mount -u -oro /
I will get the odd error.
What exactly does NID_NOT_FOUND mean ?
Also, on the machine that burns the flash, I can read and write to the
CF without error. However, there are these warning messages
Jan 26 10:56:54 ich10 kernel: GEOM: da0: partition 4 does not start on a
track boundary.
Jan 26 10:56:54 ich10 kernel: GEOM: da0: partition 4 does not end on a
track boundary.
Jan 26 10:56:54 ich10 kernel: GEOM: da0: partition 3 does not start on a
track boundary.
Jan 26 10:56:54 ich10 kernel: GEOM: da0: partition 3 does not end on a
track boundary.
Jan 26 10:56:54 ich10 kernel: GEOM: da0: partition 2 does not start on a
track boundary.
Jan 26 10:56:54 ich10 kernel: GEOM: da0: partition 2 does not end on a
track boundary.
Jan 26 10:56:54 ich10 kernel: GEOM: da0: partition 1 does not start on a
track boundary.
Jan 26 10:56:54 ich10 kernel: GEOM: da0: partition 1 does not end on a
track boundary.
Jan 26 10:56:54 ich10 kernel: GEOM: da0s1: geometry does not match label
(16h,32s != 255h,63s).
Jan 26 10:56:54 ich10 kernel: GEOM: da0s2: geometry does not match label
(16h,32s != 255h,63s).
Jan 26 10:59:59 ich10 kernel: GEOM: da0s1: geometry does not match label
(16h,63s != 255h,63s).
Jan 26 10:59:59 ich10 kernel: GEOM: da0s2: geometry does not match label
(16h,63s != 255h,63s).
---Mike
_______________________________________________
Soekris-tech mailing list
[email protected]
http://lists.soekris.com/mailman/listinfo/soekris-tech
