Issue #2264 has been updated by Sascha Wildner.
AHCI attached disks will give 2TB maximum it seems. AHCI itself reports the size correctly: ahci0.1: Found DISK "Hitachi HDS723030ALA640 MKAOA3B0" serial="MK0311YHG3U8MA" ahci0.1: tags=32/32 satacap=170e satafea=005e NCQ=YES capacity=2861588.46MB ahci0.1: f85=7469 f86=bc41 f87=4763 WC=enabled RA=enabled SEC=freezing ahci0.1: Set dummy xfer mode to 46 But then CAM's da then goes: da1 at ahci0 bus 1 target 0 lun 0 da1: <SATA Hitachi HDS72303 MKAO> Fixed Direct Access SCSI-4 device da1: Serial Number MK0311YHG3U8MA da1: 150.000MB/s transfers da1: 2097151MB (4294967295 512 byte sectors: 255H 63S/T 267349C) ---------------------------------------- Bug #2264: DragonFly can't be installed on bigger than 2TB volumes http://bugs.dragonflybsd.org/issues/2264 Author: Francois Tigeot Status: In Progress Priority: Normal Assignee: Sascha Wildner Category: Target version: 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 installer 4. gpt add -t swap -s 16777216 /dev/da0 This creates a 8GB swap slice 5. 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/da0s0 create a 'a' partition covering the entire slice 7. format /boot filesystem newfs /dev/da0s0a 8. format / filesystem newfs_hammer -L BIGVOLUME /dev/da0s2 9. mount and install /boot mount /dev/da0s0a /mnt cpdup -I -v /boot /mnt vi /mnt/loader.conf vfs.root.mountfrom="hammer:da0s2" umount /mnt 10. install the future / mount -t hammer /dev/da0s2 /mnt cpdup -I -v / /mnt cd /mnt rmdir etc mv etc.hdd etc vi etc/fstab 11. reboot The first stage bootloader will show an unknown F1 choice. Just use F2 (DragonFly) and it will boot The 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 -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account
