Hi all,
I have been running FC for a long time now. While switching from FC6 to FC7 I came across the following weird problem.
I have two 250G disks on SATA. Using QTParted I discovered the second disk has a lot of free space (like 120G). But QTParted refuses to do anything other than show its properties.
I can not use it to allocate a new partition, be it primary or extended. All commands are greyed out.
So I thought, hey, I have still got fdisk. But fdisk doesn't recofnize the space at all. Neither as a partition, nor as free space.
Okee, so I started installing F7. As long as I leave that particular piece of "free space" alone all is well. But, if I want to define a new partition (primary, extended or logical) the install utility anaconda crashes! And forces a reboot. And I have no idea how to save the debug output it serves.
Who has any idea what I can look for? I was thinking along the following lines:
1. Is it a hardware problem? How can I determin that? Or rather eliminate that?
2. If it is not hardware, what could it be?
===== start fdisk output ==============
[root@athene]~# fdisk /dev/sdb
The number of cylinders for this disk is set to 30401. There is nothing wrong with that, but this is larger than 1024, and could in certain setups cause problems with: 1) software that runs at boot time (e.g., old versions of LILO) 2) booting and partitioning software from other OSs (e.g., DOS FDISK, OS/2 FDISK)
Command (m for help): p
Disk /dev/sdb: 250.0 GB, 250059350016 bytes 255 heads, 63 sectors/track, 30401 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System /dev/sdb1 * 1 131 1052226 83 Linux /dev/sdb2 132 11227 89128620 5 Extended /dev/sdb3 11228 11358 1052257+ 83 Linux /dev/sdb4 11359 14622 26218080 83 Linux /dev/sdb5 132 7964 62918541 83 Linux /dev/sdb6 7965 11227 26210016 83 Linux
Command (m for help): n No free sectors available
Command (m for help): ====== end fdisk output ===============
Guus.
A.J. Bonnema wrote: <snip>
===== start fdisk output ==============
<snip>
Device Boot Start End Blocks Id System /dev/sdb1 * 1 131 1052226 83 Linux /dev/sdb2 132 11227 89128620 5 Extended /dev/sdb3 11228 11358 1052257+ 83 Linux /dev/sdb4 11359 14622 26218080 83 Linux /dev/sdb5 132 7964 62918541 83 Linux /dev/sdb6 7965 11227 26210016 83 Linux
During install of FC7 I realised what was wrong: I have 3 primary partitions and one extended. The rest of the space is the (by definition, I guess) unreachable.
Still funny that anaconda didn't make a remark, but had the install crash. Should I insert this as a bug in a bugzilla?
Guus.
A.J. Bonnema wrote:
A.J. Bonnema wrote:
<snip> > ===== start fdisk output ============== > <snip> > Device Boot Start End Blocks Id System > /dev/sdb1 * 1 131 1052226 83 Linux > /dev/sdb2 132 11227 89128620 5 Extended > /dev/sdb3 11228 11358 1052257+ 83 Linux > /dev/sdb4 11359 14622 26218080 83 Linux > /dev/sdb5 132 7964 62918541 83 Linux > /dev/sdb6 7965 11227 26210016 83 Linux >
During install of FC7 I realised what was wrong: I have 3 primary partitions and one extended. The rest of the space is the (by definition, I guess) unreachable.
Still funny that anaconda didn't make a remark, but had the install crash. Should I insert this as a bug in a bugzilla?
Definitely.
Rahul
Rahul Sundaram wrote:
A.J. Bonnema wrote:
Still funny that anaconda didn't make a remark, but had the install crash. Should I insert this as a bug in a bugzilla?
Definitely.
Rahul
Bugzilla Bug 242050: Anaconda fails to recognize 4 partitions plus unreachable space
Guus.
On 6/1/07, A.J. Bonnema abonnema@xs4all.nl wrote:
A.J. Bonnema wrote:
<snip> > ===== start fdisk output ============== > <snip> > Device Boot Start End Blocks Id System > /dev/sdb1 * 1 131 1052226 83 Linux > /dev/sdb2 132 11227 89128620 5 Extended > /dev/sdb3 11228 11358 1052257+ 83 Linux > /dev/sdb4 11359 14622 26218080 83 Linux > /dev/sdb5 132 7964 62918541 83 Linux > /dev/sdb6 7965 11227 26210016 83 Linux >
During install of FC7 I realised what was wrong: I have 3 primary partitions and one extended. The rest of the space is the (by definition, I guess) unreachable.
Where is the unreachable space? After 14622? If yes, then U have to reformat the whole drive I guess. Else you need to delete sdb5 & sdb6 and create more partitions in there...
HTH ne...
At 2:52 PM +0200 6/1/07, A.J. Bonnema wrote:
A.J. Bonnema wrote:
<snip> > ===== start fdisk output ============== > <snip> > Device Boot Start End Blocks Id System > /dev/sdb1 * 1 131 1052226 83 Linux > /dev/sdb2 132 11227 89128620 5 Extended > /dev/sdb3 11228 11358 1052257+ 83 Linux > /dev/sdb4 11359 14622 26218080 83 Linux > /dev/sdb5 132 7964 62918541 83 Linux > /dev/sdb6 7965 11227 26210016 83 Linux >
During install of FC7 I realised what was wrong: I have 3 primary partitions and one extended. The rest of the space is the (by definition, I guess) unreachable.
...
Why not extend the last Basic partition (/dev/sdb4) to fill the rest of the disk? Or you could instead back it up and make it LVM, and add partitions to your heart's content (up to 15 total). This will have no effect on the existing Extended partitions.
-
A.J. Bonnema -
ne... -
Rahul Sundaram -
Tony Nelson