I've searched several threads with this same topic but none have helped so far. I have a Super Talent 16gb PATA SSD drive installed on my old Dell laptop. This is the only drive in the machine other than the CD.
Using sysinstall I see the following at the allocation menu after choosing to use the entire disk.
I chose to install the FreeBSD boot manager.
At the label menu, I choose auto defaults which look reasonable.
But on committing installation I get the above error message. Per other similar threads, I've used the live FSdisk and dd to write /dev/zero to the first and last 35 sectors. No luck.
I saw one post that said to use gpart list and gpart destroy, but gpart list shows no devices at all, yet fdisk in sysinstall obviously sees it.
When I rebooted from sysinstall, a FreeBSD boot menu did appear, so it must be able to write *something* to the disk.
Is it possible the hard drive is not compatible with the laptop interface? If so, why can it install the boot manager?
Thanks for any advice you may have.
Using sysinstall I see the following at the allocation menu after choosing to use the entire disk.
Code:
Disk name ad0
Disk Geometry 29582 cyls/16 heads/63 sectors (14559MB)
Offset Size(ST) End Name PType Desc Subtype Flags
0 63 62 - 12 unused 0
63 29818593 29818655 ad0s1 0 freebsd 165 =
I chose to install the FreeBSD boot manager.
At the label menu, I choose auto defaults which look reasonable.
But on committing installation I get the above error message. Per other similar threads, I've used the live FSdisk and dd to write /dev/zero to the first and last 35 sectors. No luck.
I saw one post that said to use gpart list and gpart destroy, but gpart list shows no devices at all, yet fdisk in sysinstall obviously sees it.
When I rebooted from sysinstall, a FreeBSD boot menu did appear, so it must be able to write *something* to the disk.
Is it possible the hard drive is not compatible with the laptop interface? If so, why can it install the boot manager?
Thanks for any advice you may have.