This system has two 1GB (Samsung F3) HDD setup in ICH10R RAID-0.
The RAID-0 has two volumes:
- volume 1 has 524GB with 64k stripe (small files) - ar0
- volume 2 has the remaining space with 128k stripe (large multimedia files) - ar1
Volume 1 has three primary partitions: WinSystem NTFS, Win7 NTFS and other NTFS. - ar0s{1,2,3}
Volume 2 has one primary partition: 1GB NTFS - ar1s1
FreeBSD was installed in the remaining free space, creating second slice (primary partition) - ar1s2
Install run fine, except error messages:
- In dmesg: GEOM warning, something like «ar{0,1} track out of bounds»
- During sysinstall: fdisk «chunk 'ar1s2' [(...)] does not start on a track boundary»
Install option for boot code was none. Sysinstall should have it installed in slice ar1s2, marked active.
Setting volume 2 the first boot device in bios, boots ar1s2 - as expected - but the screen reads:
Is there anything I can do to make it boot?
Please let me know how to fix it ( hardware RAID-0 and volumes should be kept as it is)
::atomic
The RAID-0 has two volumes:
- volume 1 has 524GB with 64k stripe (small files) - ar0
- volume 2 has the remaining space with 128k stripe (large multimedia files) - ar1
Volume 1 has three primary partitions: WinSystem NTFS, Win7 NTFS and other NTFS. - ar0s{1,2,3}
Volume 2 has one primary partition: 1GB NTFS - ar1s1
FreeBSD was installed in the remaining free space, creating second slice (primary partition) - ar1s2
Install run fine, except error messages:
- In dmesg: GEOM warning, something like «ar{0,1} track out of bounds»
- During sysinstall: fdisk «chunk 'ar1s2' [(...)] does not start on a track boundary»
Install option for boot code was none. Sysinstall should have it installed in slice ar1s2, marked active.
Setting volume 2 the first boot device in bios, boots ar1s2 - as expected - but the screen reads:
Code:
BTX Loader 1.0
(...)
FreeBSD/x86 bootstrap loader, Rev 1.1
(...)
can't load 'kernel'
Type '?' for a list of commands
OK _
Is there anything I can do to make it boot?
Please let me know how to fix it ( hardware RAID-0 and volumes should be kept as it is)
::atomic