[DragonFlyBSD - Bug #2264] DragonFly can't be installed on bigger than 2TB volumes

[Sascha Wildner via Redmine <bugtracker-admin@xxxxxxxxxxxxxxxxxxxxx>]

Issue #2264 has been updated by Sascha Wildner.


On Mon, 13 Aug 2012 21:21:03 +0200, Tim Darby via Redmine  
<bugtracker-admin@leaf.dragonflybsd.org> wrote:

>
> Issue #2264 has been updated by Tim Darby.
>
>
> Out of curiosity, would the BIOS have any affect on this? I tried  
> installing a 3TB drive recently and DF only saw 2TB of it. After a bit  
> of digging, I found that my BIOS didn't support >2TB and no firmware  
> patch was planned, so I returned the drive.  Is there a possibility that  
> this patch would have gotten around the BIOS problem?

Assuming this was a disk attaching via ahci(4), I think you were suffering  
 from the issue that was fixed with 0d92877a ("ahci(4)/sili(4): Fix for  
drives >2TB."), which corrected ahci's reporting of the capacity to CAM  
that was limiting it to 2TB.

My 3TB drive shows up here as 800something GB in the BIOS' messages on  
boot, but in DragonFly it now all works as expected.

The installer fix was just to make the installer play nice with all that  
too.

Sascha
----------------------------------------
Bug #2264: DragonFly can't be installed on bigger than 2TB volumes
http://bugs.dragonflybsd.org/issues/2264

Author: Francois Tigeot
Status: Closed
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