Fedora 19 install hard drives not visible
up vote
2
down vote
favorite
(Asking here as I haven't had a response to a post on Ask Fedora)
I'm trying to install Fedora 19 Gnome as a dual boot system on my HP Envy laptop (hardware specifications HP ENVY 6-1202sa, although I think the hard drive is a hybrid drive with possibly an SSD cache [unsure])
I have successfully created a USB live disc which I can boot up and run the live disc with no problems, but when I choose the option to install to hard drive none of my hard drives are available?
As per the suggestion in the linked post I've deleted the recovery partition (from the HP recovery utility in Windows) but this didn't solve the problem, the drives are still not visible to the installer.
[liveuser@localhost ~]$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 465.8G 0 disk
├─sda1 8:1 0 400M 0 part
├─sda2 8:2 0 260M 0 part
├─sda3 8:3 0 128M 0 part
└─sda4 8:4 0 465G 0 part
sdb 8:16 0 29.8G 0 disk
└─sdb1 8:17 0 8G 0 part
sdc 8:32 1 14.9G 0 disk
└─sdc1 8:33 1 14.9G 0 part /run/initramfs/live
loop0 7:0 0 12K 1 loop
loop1 7:1 0 2.2M 1 loop
└─live-osimg-min 253:1 0 8G 1 dm
loop2 7:2 0 887.4M 1 loop
loop3 7:3 0 8G 1 loop
├─live-rw 253:0 0 8G 0 dm /
└─live-osimg-min 253:1 0 8G 1 dm
loop4 7:4 0 512M 0 loop
└─live-rw 253:0 0 8G 0 dm /
and also:
[liveuser@localhost ~]$ sudo fdisk -l
Disk /dev/sda: 500.1 GB, 500107862016 bytes, 976773168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk label type: dos
Disk identifier: 0x712f758b
Device Boot Start End Blocks Id System
/dev/sda1 1 976766975 488383487+ ee GPT
Partition 1 does not start on physical sector boundary.
Disk /dev/sdb: 32.0 GB, 32017047552 bytes, 62533296 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk label type: dos
Disk identifier: 0x2f7c2cab
Device Boot Start End Blocks Id System
/dev/sdb1 1 4294967295 2147483647+ ee GPT
Disk /dev/sdc: 16.0 GB, 16008609792 bytes, 31266816 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk label type: dos
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/sdc1 * 32 31266815 15633392 c W95 FAT32 (LBA)
Disk /dev/mapper/live-rw: 8589 MB, 8589934592 bytes, 16777216 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/mapper/live-osimg-min: 8589 MB, 8589934592 bytes, 16777216 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
I've also been trying other live distributions and I get the following error when I attempt to browse to the "OS" disk on a Linux Mint live disc (I haven't checked to see whether I get the same error on the Fedora live disc):
Error mounting /dev/sda4 at /media/mint/OS: Command-line `mount -t "ntfs" -o "uhelper=udisks2,nodev,nosuid,uid=999,gid=999,dmask=0077,fmask=0177" "/dev/sda4" "/media/mint/OS"' exited with non-zero exit status 14: The disk contains an unclean file system (0, 0).
Metadata kept in Windows cache, refused to mount.
Failed to mount '/dev/sda4': Operation not permitted
The NTFS partition is in an unsafe state. Please resume and shutdown
Windows fully (no hibernation or fast restarting), or mount the volume
read-only with the 'ro' mount option.
This is how the disk manager looks in Windows 8:

Any suggestions?
This may be related.
fedora software-installation live-usb
add a comment |
up vote
2
down vote
favorite
(Asking here as I haven't had a response to a post on Ask Fedora)
I'm trying to install Fedora 19 Gnome as a dual boot system on my HP Envy laptop (hardware specifications HP ENVY 6-1202sa, although I think the hard drive is a hybrid drive with possibly an SSD cache [unsure])
I have successfully created a USB live disc which I can boot up and run the live disc with no problems, but when I choose the option to install to hard drive none of my hard drives are available?
As per the suggestion in the linked post I've deleted the recovery partition (from the HP recovery utility in Windows) but this didn't solve the problem, the drives are still not visible to the installer.
[liveuser@localhost ~]$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 465.8G 0 disk
├─sda1 8:1 0 400M 0 part
├─sda2 8:2 0 260M 0 part
├─sda3 8:3 0 128M 0 part
└─sda4 8:4 0 465G 0 part
sdb 8:16 0 29.8G 0 disk
└─sdb1 8:17 0 8G 0 part
sdc 8:32 1 14.9G 0 disk
└─sdc1 8:33 1 14.9G 0 part /run/initramfs/live
loop0 7:0 0 12K 1 loop
loop1 7:1 0 2.2M 1 loop
└─live-osimg-min 253:1 0 8G 1 dm
loop2 7:2 0 887.4M 1 loop
loop3 7:3 0 8G 1 loop
├─live-rw 253:0 0 8G 0 dm /
└─live-osimg-min 253:1 0 8G 1 dm
loop4 7:4 0 512M 0 loop
└─live-rw 253:0 0 8G 0 dm /
and also:
[liveuser@localhost ~]$ sudo fdisk -l
Disk /dev/sda: 500.1 GB, 500107862016 bytes, 976773168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk label type: dos
Disk identifier: 0x712f758b
Device Boot Start End Blocks Id System
/dev/sda1 1 976766975 488383487+ ee GPT
Partition 1 does not start on physical sector boundary.
Disk /dev/sdb: 32.0 GB, 32017047552 bytes, 62533296 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk label type: dos
Disk identifier: 0x2f7c2cab
Device Boot Start End Blocks Id System
/dev/sdb1 1 4294967295 2147483647+ ee GPT
Disk /dev/sdc: 16.0 GB, 16008609792 bytes, 31266816 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk label type: dos
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/sdc1 * 32 31266815 15633392 c W95 FAT32 (LBA)
Disk /dev/mapper/live-rw: 8589 MB, 8589934592 bytes, 16777216 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/mapper/live-osimg-min: 8589 MB, 8589934592 bytes, 16777216 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
I've also been trying other live distributions and I get the following error when I attempt to browse to the "OS" disk on a Linux Mint live disc (I haven't checked to see whether I get the same error on the Fedora live disc):
Error mounting /dev/sda4 at /media/mint/OS: Command-line `mount -t "ntfs" -o "uhelper=udisks2,nodev,nosuid,uid=999,gid=999,dmask=0077,fmask=0177" "/dev/sda4" "/media/mint/OS"' exited with non-zero exit status 14: The disk contains an unclean file system (0, 0).
Metadata kept in Windows cache, refused to mount.
Failed to mount '/dev/sda4': Operation not permitted
The NTFS partition is in an unsafe state. Please resume and shutdown
Windows fully (no hibernation or fast restarting), or mount the volume
read-only with the 'ro' mount option.
This is how the disk manager looks in Windows 8:

Any suggestions?
This may be related.
fedora software-installation live-usb
What aboutsudo sfdisk -l?
– slm♦
Sep 17 '13 at 15:19
Or try this one:sudo parted -l.
– slm♦
Sep 17 '13 at 15:37
I'm thinking it might be something with UEFI, depending on how new the system is. We got one of those HP systems for work from bestbuy and it wasn't accessible with any of the live CDs I had up to that point. Came with Win8
– slm♦
Sep 17 '13 at 15:41
Might be worth a look to see if this is your underlying issue: h30434.www3.hp.com/t5/Other-Notebook-PC-Questions/…. Scroll towards the bottom where they discuss dynamic partitions on HP systems.
– slm♦
Sep 17 '13 at 15:45
add a comment |
up vote
2
down vote
favorite
up vote
2
down vote
favorite
(Asking here as I haven't had a response to a post on Ask Fedora)
I'm trying to install Fedora 19 Gnome as a dual boot system on my HP Envy laptop (hardware specifications HP ENVY 6-1202sa, although I think the hard drive is a hybrid drive with possibly an SSD cache [unsure])
I have successfully created a USB live disc which I can boot up and run the live disc with no problems, but when I choose the option to install to hard drive none of my hard drives are available?
As per the suggestion in the linked post I've deleted the recovery partition (from the HP recovery utility in Windows) but this didn't solve the problem, the drives are still not visible to the installer.
[liveuser@localhost ~]$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 465.8G 0 disk
├─sda1 8:1 0 400M 0 part
├─sda2 8:2 0 260M 0 part
├─sda3 8:3 0 128M 0 part
└─sda4 8:4 0 465G 0 part
sdb 8:16 0 29.8G 0 disk
└─sdb1 8:17 0 8G 0 part
sdc 8:32 1 14.9G 0 disk
└─sdc1 8:33 1 14.9G 0 part /run/initramfs/live
loop0 7:0 0 12K 1 loop
loop1 7:1 0 2.2M 1 loop
└─live-osimg-min 253:1 0 8G 1 dm
loop2 7:2 0 887.4M 1 loop
loop3 7:3 0 8G 1 loop
├─live-rw 253:0 0 8G 0 dm /
└─live-osimg-min 253:1 0 8G 1 dm
loop4 7:4 0 512M 0 loop
└─live-rw 253:0 0 8G 0 dm /
and also:
[liveuser@localhost ~]$ sudo fdisk -l
Disk /dev/sda: 500.1 GB, 500107862016 bytes, 976773168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk label type: dos
Disk identifier: 0x712f758b
Device Boot Start End Blocks Id System
/dev/sda1 1 976766975 488383487+ ee GPT
Partition 1 does not start on physical sector boundary.
Disk /dev/sdb: 32.0 GB, 32017047552 bytes, 62533296 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk label type: dos
Disk identifier: 0x2f7c2cab
Device Boot Start End Blocks Id System
/dev/sdb1 1 4294967295 2147483647+ ee GPT
Disk /dev/sdc: 16.0 GB, 16008609792 bytes, 31266816 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk label type: dos
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/sdc1 * 32 31266815 15633392 c W95 FAT32 (LBA)
Disk /dev/mapper/live-rw: 8589 MB, 8589934592 bytes, 16777216 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/mapper/live-osimg-min: 8589 MB, 8589934592 bytes, 16777216 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
I've also been trying other live distributions and I get the following error when I attempt to browse to the "OS" disk on a Linux Mint live disc (I haven't checked to see whether I get the same error on the Fedora live disc):
Error mounting /dev/sda4 at /media/mint/OS: Command-line `mount -t "ntfs" -o "uhelper=udisks2,nodev,nosuid,uid=999,gid=999,dmask=0077,fmask=0177" "/dev/sda4" "/media/mint/OS"' exited with non-zero exit status 14: The disk contains an unclean file system (0, 0).
Metadata kept in Windows cache, refused to mount.
Failed to mount '/dev/sda4': Operation not permitted
The NTFS partition is in an unsafe state. Please resume and shutdown
Windows fully (no hibernation or fast restarting), or mount the volume
read-only with the 'ro' mount option.
This is how the disk manager looks in Windows 8:

Any suggestions?
This may be related.
fedora software-installation live-usb
(Asking here as I haven't had a response to a post on Ask Fedora)
I'm trying to install Fedora 19 Gnome as a dual boot system on my HP Envy laptop (hardware specifications HP ENVY 6-1202sa, although I think the hard drive is a hybrid drive with possibly an SSD cache [unsure])
I have successfully created a USB live disc which I can boot up and run the live disc with no problems, but when I choose the option to install to hard drive none of my hard drives are available?
As per the suggestion in the linked post I've deleted the recovery partition (from the HP recovery utility in Windows) but this didn't solve the problem, the drives are still not visible to the installer.
[liveuser@localhost ~]$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 465.8G 0 disk
├─sda1 8:1 0 400M 0 part
├─sda2 8:2 0 260M 0 part
├─sda3 8:3 0 128M 0 part
└─sda4 8:4 0 465G 0 part
sdb 8:16 0 29.8G 0 disk
└─sdb1 8:17 0 8G 0 part
sdc 8:32 1 14.9G 0 disk
└─sdc1 8:33 1 14.9G 0 part /run/initramfs/live
loop0 7:0 0 12K 1 loop
loop1 7:1 0 2.2M 1 loop
└─live-osimg-min 253:1 0 8G 1 dm
loop2 7:2 0 887.4M 1 loop
loop3 7:3 0 8G 1 loop
├─live-rw 253:0 0 8G 0 dm /
└─live-osimg-min 253:1 0 8G 1 dm
loop4 7:4 0 512M 0 loop
└─live-rw 253:0 0 8G 0 dm /
and also:
[liveuser@localhost ~]$ sudo fdisk -l
Disk /dev/sda: 500.1 GB, 500107862016 bytes, 976773168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk label type: dos
Disk identifier: 0x712f758b
Device Boot Start End Blocks Id System
/dev/sda1 1 976766975 488383487+ ee GPT
Partition 1 does not start on physical sector boundary.
Disk /dev/sdb: 32.0 GB, 32017047552 bytes, 62533296 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk label type: dos
Disk identifier: 0x2f7c2cab
Device Boot Start End Blocks Id System
/dev/sdb1 1 4294967295 2147483647+ ee GPT
Disk /dev/sdc: 16.0 GB, 16008609792 bytes, 31266816 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk label type: dos
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/sdc1 * 32 31266815 15633392 c W95 FAT32 (LBA)
Disk /dev/mapper/live-rw: 8589 MB, 8589934592 bytes, 16777216 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/mapper/live-osimg-min: 8589 MB, 8589934592 bytes, 16777216 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
I've also been trying other live distributions and I get the following error when I attempt to browse to the "OS" disk on a Linux Mint live disc (I haven't checked to see whether I get the same error on the Fedora live disc):
Error mounting /dev/sda4 at /media/mint/OS: Command-line `mount -t "ntfs" -o "uhelper=udisks2,nodev,nosuid,uid=999,gid=999,dmask=0077,fmask=0177" "/dev/sda4" "/media/mint/OS"' exited with non-zero exit status 14: The disk contains an unclean file system (0, 0).
Metadata kept in Windows cache, refused to mount.
Failed to mount '/dev/sda4': Operation not permitted
The NTFS partition is in an unsafe state. Please resume and shutdown
Windows fully (no hibernation or fast restarting), or mount the volume
read-only with the 'ro' mount option.
This is how the disk manager looks in Windows 8:

Any suggestions?
This may be related.
fedora software-installation live-usb
fedora software-installation live-usb
edited Nov 26 at 0:54
Rui F Ribeiro
38.3k1475127
38.3k1475127
asked Sep 17 '13 at 14:52
Richard Lucas
1133
1133
What aboutsudo sfdisk -l?
– slm♦
Sep 17 '13 at 15:19
Or try this one:sudo parted -l.
– slm♦
Sep 17 '13 at 15:37
I'm thinking it might be something with UEFI, depending on how new the system is. We got one of those HP systems for work from bestbuy and it wasn't accessible with any of the live CDs I had up to that point. Came with Win8
– slm♦
Sep 17 '13 at 15:41
Might be worth a look to see if this is your underlying issue: h30434.www3.hp.com/t5/Other-Notebook-PC-Questions/…. Scroll towards the bottom where they discuss dynamic partitions on HP systems.
– slm♦
Sep 17 '13 at 15:45
add a comment |
What aboutsudo sfdisk -l?
– slm♦
Sep 17 '13 at 15:19
Or try this one:sudo parted -l.
– slm♦
Sep 17 '13 at 15:37
I'm thinking it might be something with UEFI, depending on how new the system is. We got one of those HP systems for work from bestbuy and it wasn't accessible with any of the live CDs I had up to that point. Came with Win8
– slm♦
Sep 17 '13 at 15:41
Might be worth a look to see if this is your underlying issue: h30434.www3.hp.com/t5/Other-Notebook-PC-Questions/…. Scroll towards the bottom where they discuss dynamic partitions on HP systems.
– slm♦
Sep 17 '13 at 15:45
What about
sudo sfdisk -l?– slm♦
Sep 17 '13 at 15:19
What about
sudo sfdisk -l?– slm♦
Sep 17 '13 at 15:19
Or try this one:
sudo parted -l.– slm♦
Sep 17 '13 at 15:37
Or try this one:
sudo parted -l.– slm♦
Sep 17 '13 at 15:37
I'm thinking it might be something with UEFI, depending on how new the system is. We got one of those HP systems for work from bestbuy and it wasn't accessible with any of the live CDs I had up to that point. Came with Win8
– slm♦
Sep 17 '13 at 15:41
I'm thinking it might be something with UEFI, depending on how new the system is. We got one of those HP systems for work from bestbuy and it wasn't accessible with any of the live CDs I had up to that point. Came with Win8
– slm♦
Sep 17 '13 at 15:41
Might be worth a look to see if this is your underlying issue: h30434.www3.hp.com/t5/Other-Notebook-PC-Questions/…. Scroll towards the bottom where they discuss dynamic partitions on HP systems.
– slm♦
Sep 17 '13 at 15:45
Might be worth a look to see if this is your underlying issue: h30434.www3.hp.com/t5/Other-Notebook-PC-Questions/…. Scroll towards the bottom where they discuss dynamic partitions on HP systems.
– slm♦
Sep 17 '13 at 15:45
add a comment |
1 Answer
1
active
oldest
votes
up vote
2
down vote
accepted
I don't have a GPT disk so this is just a guess, but that may be why fdisk has a problem -- it did not support GPT until last year. However, I notice that is dated several months after the last stable util-linux (the source package which includes fdisk), 2.21, which is the fdisk here on my fedora 17 system. You can check this with fdisk -v.
That post seems to refer to a version 2.3.1 which is not available? The last branch on git looks like 2.23.
So most likely your fdisk does not support GPT, and the version which does is apparently not ready for public consumption. However, gdisk, "an fdisk like partitioning tool for GPT disks" is available in the fedora repos (in fact, it is already on my system, so perhaps it is part of a base install). If you can use that from a live CD, you can set up the partitions yourself and tell the installer to skip that step.
Googling around, it seems that F19 should support a GPT install, but some people have had problems...
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
2
down vote
accepted
I don't have a GPT disk so this is just a guess, but that may be why fdisk has a problem -- it did not support GPT until last year. However, I notice that is dated several months after the last stable util-linux (the source package which includes fdisk), 2.21, which is the fdisk here on my fedora 17 system. You can check this with fdisk -v.
That post seems to refer to a version 2.3.1 which is not available? The last branch on git looks like 2.23.
So most likely your fdisk does not support GPT, and the version which does is apparently not ready for public consumption. However, gdisk, "an fdisk like partitioning tool for GPT disks" is available in the fedora repos (in fact, it is already on my system, so perhaps it is part of a base install). If you can use that from a live CD, you can set up the partitions yourself and tell the installer to skip that step.
Googling around, it seems that F19 should support a GPT install, but some people have had problems...
add a comment |
up vote
2
down vote
accepted
I don't have a GPT disk so this is just a guess, but that may be why fdisk has a problem -- it did not support GPT until last year. However, I notice that is dated several months after the last stable util-linux (the source package which includes fdisk), 2.21, which is the fdisk here on my fedora 17 system. You can check this with fdisk -v.
That post seems to refer to a version 2.3.1 which is not available? The last branch on git looks like 2.23.
So most likely your fdisk does not support GPT, and the version which does is apparently not ready for public consumption. However, gdisk, "an fdisk like partitioning tool for GPT disks" is available in the fedora repos (in fact, it is already on my system, so perhaps it is part of a base install). If you can use that from a live CD, you can set up the partitions yourself and tell the installer to skip that step.
Googling around, it seems that F19 should support a GPT install, but some people have had problems...
add a comment |
up vote
2
down vote
accepted
up vote
2
down vote
accepted
I don't have a GPT disk so this is just a guess, but that may be why fdisk has a problem -- it did not support GPT until last year. However, I notice that is dated several months after the last stable util-linux (the source package which includes fdisk), 2.21, which is the fdisk here on my fedora 17 system. You can check this with fdisk -v.
That post seems to refer to a version 2.3.1 which is not available? The last branch on git looks like 2.23.
So most likely your fdisk does not support GPT, and the version which does is apparently not ready for public consumption. However, gdisk, "an fdisk like partitioning tool for GPT disks" is available in the fedora repos (in fact, it is already on my system, so perhaps it is part of a base install). If you can use that from a live CD, you can set up the partitions yourself and tell the installer to skip that step.
Googling around, it seems that F19 should support a GPT install, but some people have had problems...
I don't have a GPT disk so this is just a guess, but that may be why fdisk has a problem -- it did not support GPT until last year. However, I notice that is dated several months after the last stable util-linux (the source package which includes fdisk), 2.21, which is the fdisk here on my fedora 17 system. You can check this with fdisk -v.
That post seems to refer to a version 2.3.1 which is not available? The last branch on git looks like 2.23.
So most likely your fdisk does not support GPT, and the version which does is apparently not ready for public consumption. However, gdisk, "an fdisk like partitioning tool for GPT disks" is available in the fedora repos (in fact, it is already on my system, so perhaps it is part of a base install). If you can use that from a live CD, you can set up the partitions yourself and tell the installer to skip that step.
Googling around, it seems that F19 should support a GPT install, but some people have had problems...
answered Sep 17 '13 at 15:55
goldilocks
61.1k13150204
61.1k13150204
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f91067%2ffedora-19-install-hard-drives-not-visible%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
What about
sudo sfdisk -l?– slm♦
Sep 17 '13 at 15:19
Or try this one:
sudo parted -l.– slm♦
Sep 17 '13 at 15:37
I'm thinking it might be something with UEFI, depending on how new the system is. We got one of those HP systems for work from bestbuy and it wasn't accessible with any of the live CDs I had up to that point. Came with Win8
– slm♦
Sep 17 '13 at 15:41
Might be worth a look to see if this is your underlying issue: h30434.www3.hp.com/t5/Other-Notebook-PC-Questions/…. Scroll towards the bottom where they discuss dynamic partitions on HP systems.
– slm♦
Sep 17 '13 at 15:45