Actions
Bug #2264
closed
DragonFly can't be installed on bigger than 2TB volumes
Start date:
12/18/2011
Due date:
% Done:
0%
Estimated time:
Description
The DragonFly installer tries to run fdisk unconditionally on target devices
and thus fails with > 2TB volumes.
This is what I've done to get DragonFly installed on a 8TB RAID volume:
1. Don't try to use the installer, log in as root on the live cd
2. gpt create /dev/da0
3. gpt boot /dev/da0
This stage adds a 256MB gpt boot slice with a disklabel32 filesystem type
FIXME: Size should be updated to 768MB, like the /boot partitions created by the installer4. gpt add -t swap -s 16777216 /dev/da0
This creates a 8GB swap slice5. gpt add -t dfly /dev/da0
This creates a slice covering the rest of the da0 volume with a DragonFly filesystem type.
FIXME: I'm not sure what is meant by DragonFly filesystem. maybe Hammer should be presented as
a choice instead.6. disklabel the /dev/da0s0 boot slice, install bootstrap code
disklabel32 -B -r -w /dev/da0s0 auto
disklabel32 -r -e /dev/da0s0create a 'a' partition covering the entire slice7. format /boot filesystem
newfs /dev/da0s0a8. format / filesystem
newfs_hammer -L BIGVOLUME /dev/da0s29. mount and install /boot
mount /dev/da0s0a /mnt
cpdup -I -v /boot /mntvi /mnt/loader.conf
vfs.root.mountfrom="hammer:da0s2"umount /mnt10. install the future /
mount -t hammer /dev/da0s2 /mnt
cpdup -I -v / /mnt
cd /mnt
rmdir etc
mv etc.hdd etcvi etc/fstab11. reboot
The first stage bootloader will show an unknown F1 choice.
Just use F2 (DragonFly) and it will bootThe new system is able to run single-user, some /var directories
which were not present on the livecd need to be created by hand
to go multi-user
The system is otherwise fully functional
Updated by 
Updated by 
Updated by Anonymous
Actions