Installer not seeing free space on disk

LinuxManiac · 2015-12-06 19:02:58

Hello,

I am trying to install #! 11 - Waldorf (Yes, I know BunsenLabs continued #! as BunsenLabs Linux, but I just wanted to see the latest version of the original, and anyway,I don't know how to download it, and the name is rubbish), and I have three partitions: The NTFS Windows partition, and an extended partition containing a SWAP (linux-SWAP) and an Ext4 parttion. Apart from that, I also have about 100GB of free space, that I would like to install #! to. However, when I make a new fat32 or ext4 partiton there, then the installer says that I have two partitions: One around 200 GB in size, and one 5GB Swap partition, and when I do NOT make any partition there, then the installer lists all the partitions available, apaert from the free space which is what I want to install it to. Where have I gone wrong?

Thanks,
Hubert

LinuxManiac · 2015-12-06 19:04:35

I use Gparted on Ubuntu for partitioning, as I am currently dual-booting Windows 7 and Ubuntu. Will #! cause any GRUB problems? It should theoretically work just fine, right?

Horizon_Brave · 2015-12-06 19:52:47

The Ubuntu is running off of the ext4 partition right? Go to your command line and do a sudo fdisk -l to print the table and paste the results here.

damo · 2015-12-06 19:59:19

In your Ubuntu, what is the output of:

sudo fdisk -l

If you install grub to mbr, then it should pick up anything else which has been installed - your windoze and ubuntu will appear in the boot list.

You download and install BL the exact same way as #! ie get the iso, write it to usb with `dd` or `cp`, and choose the Install option when you boot it. Instructions are on the website.

By all means you can say you don't like the name, but is everything you don't like also "rubbish"?

You can install Crunchbang, but the welcome script won't work, and you won't be able to `apt-get update` unless you remove the crunchbang package lines from your sources.list - the repo is no longer online.

LinuxManiac · 2015-12-06 20:04:48

Disk /dev/ram0: 64 MiB, 67108864 bytes, 131072 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 /dev/ram1: 64 MiB, 67108864 bytes, 131072 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 /dev/ram2: 64 MiB, 67108864 bytes, 131072 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 /dev/ram3: 64 MiB, 67108864 bytes, 131072 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 /dev/ram4: 64 MiB, 67108864 bytes, 131072 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 /dev/ram5: 64 MiB, 67108864 bytes, 131072 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 /dev/ram6: 64 MiB, 67108864 bytes, 131072 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 /dev/ram7: 64 MiB, 67108864 bytes, 131072 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 /dev/ram8: 64 MiB, 67108864 bytes, 131072 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 /dev/ram9: 64 MiB, 67108864 bytes, 131072 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 /dev/ram10: 64 MiB, 67108864 bytes, 131072 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 /dev/ram11: 64 MiB, 67108864 bytes, 131072 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 /dev/ram12: 64 MiB, 67108864 bytes, 131072 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 /dev/ram13: 64 MiB, 67108864 bytes, 131072 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 /dev/ram14: 64 MiB, 67108864 bytes, 131072 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 /dev/ram15: 64 MiB, 67108864 bytes, 131072 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 /dev/sda: 232.9 GiB, 250059350016 bytes, 488397168 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
Disklabel type: dos
Disk identifier: 0xefff69d4

Device     Boot     Start       End   Sectors  Size Id Type
/dev/sda1              63 188745727 188745665   90G  7 HPFS/NTFS/exFAT
/dev/sda2       392226814 488396799  96169986 45.9G  5 Extended
/dev/sda5       484284416 488396799   4112384    2G 82 Linux swap / Solaris
/dev/sda6       392226816 484284415  92057600 43.9G 83 Linux

Partition table entries are not in disk order.

LinuxManiac · 2015-12-06 22:18:56

Also, what do you mean "welcome script"?

Head_on_a_Stick · 2015-12-06 22:30:56

LinuxManiac wrote:

I don't know how to download it

From here:
https://www.bunsenlabs.org/installation.html

LinuxManiac wrote:

the name is rubbish

Panda · 2015-12-06 23:52:58

Greetings @LinuxManiac

damo wrote:

If you install grub to mbr, then it should pick up anything else which has been installed - your windoze and ubuntu will appear in the boot list.

^+1

Head_on_a_Stick wrote:

(Download) From here:
https://www.bunsenlabs.org/installation.html

^+1

LinuxManiac wrote:

Also, what do you mean "welcome script"?

It's a little helpful script that.. Welcomes you.

damo · 2015-12-07 13:14:08

LinuxManiac wrote:

Also, what do you mean "welcome script"?

When you first start #! (and BL does the same), a terminal script called "cb-welcome" runs. It gives options to install various packages, and is an admired feature of crunchbang. But it first needs to do an update/upgrade, and the crunchbang package repo has been off-line for months, so the only crunchbang-specific material is what is on the live iso.

nobody0 · 2015-12-07 18:51:37

LinuxManiac wrote:

Disk /dev/sda: 232.9 GiB,...
Device     Boot     Start       End   Sectors  Size Id Type
/dev/sda1                     63 188745727 188745665    90G  7 HPFS/NTFS/exFAT
/dev/sda2       392226814 488396799  96169986  45.9G  5 Extended
/dev/sda5       484284416 488396799   4112384       2G 82 Linux swap / Solaris
/dev/sda6       392226816 484284415  92057600 43.9G 83 Linux

You have 4 partitions, and you have about 51GB free space, which fdisk -l doesn't see. If you want more than 4 partitions, you have to have one extended partition, in which you can have practically any amount of partitions inside it. This extended partition has to be the last one. If you have gparted, check through it to see, where this free space is. If it is after your /dev/sda6, you can delete /dev/sda6 and add that space to it. Once you delete /dev/sda6 your free space would grow to about 85GB. Then, you partition it as extended. You'd officially have (the MBR way) only 4 partitions, the last being the extended one. Then, you can partition this extended partition further to few more extended partitions.

There is missing /dev/sda3 and /dev/sda4 here, which might mean that the free space is before the swap. In that case, you'd have to delete both sda5 and sda6 and start partitioning again.

Horizon_Brave · 2015-12-07 19:08:13

LinuxManiac wrote:

Disk /dev/ram0: 64 MiB, 67108864 bytes, 131072 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 /dev/ram1: 64 MiB, 67108864 bytes, 131072 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 /dev/ram2: 64 MiB, 67108864 bytes, 131072 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 /dev/ram3: 64 MiB, 67108864 bytes, 131072 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 /dev/ram4: 64 MiB, 67108864 bytes, 131072 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 /dev/ram5: 64 MiB, 67108864 bytes, 131072 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 /dev/ram6: 64 MiB, 67108864 bytes, 131072 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 /dev/ram7: 64 MiB, 67108864 bytes, 131072 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 /dev/ram8: 64 MiB, 67108864 bytes, 131072 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 /dev/ram9: 64 MiB, 67108864 bytes, 131072 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 /dev/ram10: 64 MiB, 67108864 bytes, 131072 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 /dev/ram11: 64 MiB, 67108864 bytes, 131072 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 /dev/ram12: 64 MiB, 67108864 bytes, 131072 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 /dev/ram13: 64 MiB, 67108864 bytes, 131072 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 /dev/ram14: 64 MiB, 67108864 bytes, 131072 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 /dev/ram15: 64 MiB, 67108864 bytes, 131072 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 /dev/sda: 232.9 GiB, 250059350016 bytes, 488397168 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
Disklabel type: dos
Disk identifier: 0xefff69d4

Device     Boot     Start       End   Sectors  Size Id Type
/dev/sda1              63 188745727 188745665   90G  7 HPFS/NTFS/exFAT
/dev/sda2       392226814 488396799  96169986 45.9G  5 Extended
/dev/sda5       484284416 488396799   4112384    2G 82 Linux swap / Solaris
/dev/sda6       392226816 484284415  92057600 43.9G 83 Linux

Partition table entries are not in disk order.

None of your partitions are bootable? Where do you boot to?

Also you may want to try running cfdisk as well...to me it's a bit more concise, and apparently shows free space, but not confirmed..

porkpiehat · 2015-12-07 19:08:55

^^ Look again, ostrolek. sda2 *is* an extended partition, inside which he has created logical partitions sda5 and sda6. sda3 and 4 are missing because those are reserved for primary partitions.Logical partitions always start with sda5, so once an extended partition was created with sda2, sda3 and 4 were skipped.

Nothing in your post has anything to do with the OP's problem.

Last edited by porkpiehat (2015-12-07 19:12:30)

nobody0 · 2015-12-07 19:40:23

^ Its up to the OP to come back with what he had done. The command fdisk -l doesn't show free space, only show the partitions. Gparted would show all unallocated space, even small ones between partitions, so if the OP can post a scrot of gparted, we'd be able to tell exactly what's wrong. I think he had incorrectly partitioned his disk. It is usually sda1, sda2, sda3 and sda4 as the extended, which opens to all other extended partitions.

porkpiehat · 2015-12-07 19:47:00

ostrolek wrote:

It is usually sda1, sda2, sda3 and sda4 as the extended, which opens to all other extended partitions.

Once sda2 was made an extended partition, sda3 and 4 were skipped. There is no "usually" here.Again, this has nothing to do with the OPs problem, so this will be my last post on this.

The OP can create a logical partition in the free space, but the installer does not see it.I'd recommend trying BL (or any other recent distro that the OP doesn't think has a "rubbish" name) instead of Waldorf.

Head_on_a_Stick · 2015-12-07 20:26:53

porkpiehat wrote:

I'd recommend trying BL (or any other recent distro that the OP doesn't think has a "rubbish" name) instead of Waldorf.

+1

Hi porkpiehat, welcome to the forums.

It's good to see you here :)

nobody0 · 2015-12-07 22:05:24

porkpiehat wrote:

Once sda2 was made an extended partition, sda3 and 4 were skipped. There is no "usually" here.
The OP can create a logical partition in the free space, but the installer does not see it.

You cannot create a logical partition on top of the four partitions, other than by adding the free space to the extended partition. Right now, the OP has 181G usable space, while his disk is 232G. If there is a partition, the installer would see it. It'd also see the free space, but won't be able to partition it to be used. The four partition problem is here.

About the "usually" stuff; create a fat/ntfs sda1, extended partition in sda2 and add extended partitions inside it, and then try to create fat/ntfs sda3 and sda4. Would that happen?

BLizgreat! · 2015-12-15 21:37:16

Heya Porkpiehat, hope all is well with you fellow nixer. Agree with what Damo already posted ( pretty much as usual.) Don't really see any point in installing #! Waldorf. Much time and many butt pains will no doubt be sunk into messing with it and attempting to fix resulting breakage.

Better imo to just follow the documentation the fine folks here @ BL's Linux have gone to the trouble of providing. However it's your system, time and butt, so any pains ye wish to subject yourself to is a-ok with me.

Pointless babble edit:
As to your problem, you're in good hands with the nixers here. Though extending that extended partition to incorporate the freespace would be my first thought. Provided partition placement is right. Then setting up as many logical partitions as desired ?
Not seeing why doing so would be over complicated. Though thanks to the wonders of GPT, don't have to worry about mbr's partitioning limitations. Good luck, keep at it and ye shall prevail !

Last edited by BLizgreat! (2015-12-15 21:52:39)

#1 2015-12-06 19:02:58

Installer not seeing free space on disk

#2 2015-12-06 19:04:35

Re: Installer not seeing free space on disk

#3 2015-12-06 19:52:47

Re: Installer not seeing free space on disk

#4 2015-12-06 19:59:19

Re: Installer not seeing free space on disk

#5 2015-12-06 20:04:48

Re: Installer not seeing free space on disk

#6 2015-12-06 22:18:56

Re: Installer not seeing free space on disk

#7 2015-12-06 22:30:56

Re: Installer not seeing free space on disk

#8 2015-12-06 23:52:58

Re: Installer not seeing free space on disk

#9 2015-12-07 13:14:08

Re: Installer not seeing free space on disk

#10 2015-12-07 18:51:37

Re: Installer not seeing free space on disk

#11 2015-12-07 19:08:13

Re: Installer not seeing free space on disk

#12 2015-12-07 19:08:55

Re: Installer not seeing free space on disk

#13 2015-12-07 19:40:23

Re: Installer not seeing free space on disk

#14 2015-12-07 19:47:00

Re: Installer not seeing free space on disk

#15 2015-12-07 20:26:53

Re: Installer not seeing free space on disk

#16 2015-12-07 22:05:24

Re: Installer not seeing free space on disk

#17 2015-12-15 21:37:16

Re: Installer not seeing free space on disk

Board footer