Bug #2264

DragonFly can't be installed on bigger than 2TB volumes

Added by ftigeot almost 3 years ago. Updated over 2 years ago.

Status:ClosedStart date:12/18/2011
Priority:NormalDue date:
Assignee:swildner% Done:

0%

Category:-
Target version:-

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 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


Related issues

Related to Bug #2674: GPT Support New 05/28/2014

History

#1 Updated by ftigeot almost 3 years ago

  • Status changed from New to In Progress

Size of boot slice created by gpt(8) has been bumped to 768MB.

#2 Updated by swildner almost 3 years ago

  • Assignee set to swildner

grab

#3 Updated by swildner over 2 years ago

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)

#4 Updated by swildner over 2 years ago

The ahci(4) (and sili(4)) bug has been fixed in 09e5fa07c78a9f63a62b8070731e3cbe5371ad39 and it is detected correctly now:

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: 2861588MB (5860533168 512 byte sectors: 255H 63S/T 364801C)

I'll look at the installer next.

#5 Updated by swildner over 2 years ago

  • Status changed from In Progress to Closed

I've pushed a fix that fixes installing to >2TB drives (a096577d7d6db4aaa199cf083e70a11e7c496267).

#6 Updated by t_dfbsd over 2 years ago

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?

#7 Updated by swildner over 2 years ago

On Mon, 13 Aug 2012 21:21:03 +0200, Tim Darby via Redmine
<> 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

#8 Updated by ftigeot 6 months ago

Also available in: Atom PDF