Re: Debian installer not finding free space

[David Christensen]

On 06/16/2017 08:12 AM, David DLC wrote:

I have a backup of my files and documents, but not the C: drive. I don't
have my installation disk either, so I am trying to find a fix online.


Try this:

http://www.hp.com/ctg/Manual/c03572829.pdf

Using the HP Recovery partition to recover a minimized image
(select models only)
The HP Recovery partition (select models only) allows you to perform a 
minimized image recovery
without the need for recovery discs or a recovery USB flash drive. This 
type of recovery can only be

used if the hard drive is still working.
To start HP Recovery Manager from the HP Recovery partition:
1.
Press f11 while the computer boots.
– or –
Press and hold f11 as you press the power button.
2. Select Troubleshoot from the boot options menu.
3. Select HP Recovery Manager, and follow the on-screen instructions.


If/when you succeed, then create recovery media per "Creating recovery 
media and backups".



David

Re: Debian installer not finding free space

[David DLC]

On Fri, Jun 16, 2017 at 12:38 AM, David Christensen <
dpchr...@holgerdanske.com> wrote:

> Messing with partitions involves the risk of breaking your system.  But,
> breaking and fixing your system is part of the FOSS hobby.
>
>
> Do you have a backup of the Windows C:\ file system?
>
>
I have a backup of my files and documents, but not the C: drive. I don't
have my installation disk either, so I am trying to find a fix online.

Re: Debian installer not finding free space

[David Christensen]

On 06/15/2017 09:13 AM, David DLC wrote:

So it seems I messed something up. After using the recovery console
yesterday, my computer will not start up. When booting it, I get the
"repairing disk errors" message. It has been like this all night, and I
can't get in. I've been attempting to repair the computer, but I will let
you guys know how it goes.

I think this may have stemmed from some commands that I used in the
console. I think for this prompt:
"Warning: Not all of the space available to /dev/sda appears to be used,
you can fix the GPT to use all of the space or continue with the current
setting?"
I think I typed fix, and that's the only reason I can think of for this
error.


Messing with partitions involves the risk of breaking your system.  But, 
breaking and fixing your system is part of the FOSS hobby.



Do you have a backup of the Windows C:\ file system?


David

Re: Debian installer not finding free space

[David Christensen]

On 06/15/2017 07:15 AM, David Wright wrote:

On Wed 14 Jun 2017 at 21:43:43 (-0700), David Christensen wrote:

... by convention (de facto standard?), partitions have monotonically
increasing sector numbers -- e.g. the First and Last LBA's of partition
4 must be greater than the LBA's for partition 3 and less than the LBA's
for partition 5. ...


Never heard of this standard. Sounds like a broken tool.


More likely, PEBKAC -- it's a convention I've seen and followed for the 
past 25+ years of using PC's with MBR system drives.  Your example with 
gdisk demonstrates that new technologies (GPT) open new possibilities.




[Renumbering GPT partitions] sounds very dangerous to me. If you feel the need 
to have
the numbers in sequential order, just type "s" in a tool like gdisk:


The renumbering part is mechanical -- it's the risk of breaking things 
that depend upon partition numbers that makes it dangerous.  That's why 
I use and recommend one disk for each OS.



David

Re: Debian installer not finding free space

[David DLC]

So it seems I messed something up. After using the recovery console
yesterday, my computer will not start up. When booting it, I get the
"repairing disk errors" message. It has been like this all night, and I
can't get in. I've been attempting to repair the computer, but I will let
you guys know how it goes.

I think this may have stemmed from some commands that I used in the
console. I think for this prompt:
"Warning: Not all of the space available to /dev/sda appears to be used,
you can fix the GPT to use all of the space or continue with the current
setting?"
I think I typed fix, and that's the only reason I can think of for this
error.

On Thu, Jun 15, 2017 at 9:15 AM, David Wright 
wrote:

> On Wed 14 Jun 2017 at 21:43:43 (-0700), David Christensen wrote:
> > On 06/14/2017 07:00 PM, David DLC wrote:
> > >http://imgur.com/a/o83Qd
> >
> > It looks like your 500GB drive uses the GPT partitioning scheme, and the
> > Windows C:\ file system corresponds to partition Number 4.  You also
> > have partition numbers 5 (867 MB) and 6 (21,705 MB), and then a little
> > free space (~4 MB).
> >
> >
> > When you shrank the C:\ file system and partition 4, it opened a hole
> > between partition numbers 4 and 5.  While this is listed as "Free Space"
> > by parted, I believe it is inaccessible to partitioning tools because,
> > by convention (de facto standard?), partitions have monotonically
> > increasing sector numbers -- e.g. the First and Last LBA's of partition
> > 4 must be greater than the LBA's for partition 3 and less than the LBA's
> > for partition 5.  Therefore, the tools won't create a partition 7 that
> > lies between partitions 4 and 5.
>
> Never heard of this standard. Sounds like a broken tool.
>
> > Theoretically, it should be possible to delete the partition table
> > entries for partitions 5 and 6, and then create new entries for
> > partitions 5, 6, and 7 using the exact sector numbers so that the new
> > partition 5 lines up with the free space, the new partition 6 lines up
> > with the old partition 5, and the new partition 7 lines up with the old
> > partition 6.  But you would need to disconnect whatever in the firmware
> > and/or Windows uses partitions 5 and 6 beforehand, and then
> > reconnect them to partitions 6 and 7 afterwards.  Then, once you install
> > Debian in new partition 5, you'll need to run the multi-boot bootloader
> > gauntlet.
>
> All sounds very dangerous to me. If you feel the need to have
> the numbers in sequential order, just type "s" in a tool like gdisk:
>
> # gdisk /dev/sdb
> GPT fdisk (gdisk) version 0.8.10
>
> Partition table scan:
>   MBR: protective
>   BSD: not present
>   APM: not present
>   GPT: present
>
> Found valid GPT with protective MBR; using GPT.
>
> Command (? for help): p
> Disk /dev/sdb: 3893247 sectors, 1.9 GiB
> Logical sector size: 512 bytes
> Disk identifier (GUID): 97E6AEEE-E528-43A1-817A-66BE750CF257
> Partition table holds up to 128 entries
> First usable sector is 34, last usable sector is 3893213
> Partitions will be aligned on 2048-sector boundaries
> Total free space is 3862460 sectors (1.8 GiB)
>
> Number  Start (sector)End (sector)  Size   Code  Name
>28192   34815   13.0 MiBAF00  Apple HFS/HFS+
>340966143   1024.0 KiB  FB00  VMWare VMFS
>520484095   1024.0 KiB  8300  Linux filesystem
>
> Command (? for help): s
> You may need to edit /etc/fstab and/or your boot loader configuration!
>
> Command (? for help): p
> Disk /dev/sdb: 3893247 sectors, 1.9 GiB
> Logical sector size: 512 bytes
> Disk identifier (GUID): 97E6AEEE-E528-43A1-817A-66BE750CF257
> Partition table holds up to 128 entries
> First usable sector is 34, last usable sector is 3893213
> Partitions will be aligned on 2048-sector boundaries
> Total free space is 3862460 sectors (1.8 GiB)
>
> Number  Start (sector)End (sector)  Size   Code  Name
>120484095   1024.0 KiB  8300  Linux filesystem
>240966143   1024.0 KiB  FB00  VMWare VMFS
>38192   34815   13.0 MiBAF00  Apple HFS/HFS+
>
> Command (? for help): w
>
> Final checks complete. About to write GPT data. THIS WILL OVERWRITE
> EXISTING
> PARTITIONS!!
>
> Do you want to proceed? (Y/N): y
> OK; writing new GUID partition table (GPT) to /dev/sdb.
> The operation has completed successfully.
> # gdisk /dev/sdb
> GPT fdisk (gdisk) version 0.8.10
>
> Partition table scan:
>   MBR: protective
>   BSD: not present
>   APM: not present
>   GPT: present
>
> Found valid GPT with protective MBR; using GPT.
>
> Command (? for help): p
> Disk /dev/sdb: 3893247 sectors, 1.9 GiB
> Logical sector size: 512 bytes
> Disk identifier (GUID): 97E6AEEE-E528-43A1-817A-66BE750CF257
> Partition table holds up to 128 entries
> First usable sector is 34, last usable sector is 3893213
> Partitions will be aligned on 2048-sector boundaries
> Total 

Re: Debian installer not finding free space

[David Wright]

On Wed 14 Jun 2017 at 21:43:43 (-0700), David Christensen wrote:
> On 06/14/2017 07:00 PM, David DLC wrote:
> >http://imgur.com/a/o83Qd
> 
> It looks like your 500GB drive uses the GPT partitioning scheme, and the
> Windows C:\ file system corresponds to partition Number 4.  You also
> have partition numbers 5 (867 MB) and 6 (21,705 MB), and then a little
> free space (~4 MB).
> 
> 
> When you shrank the C:\ file system and partition 4, it opened a hole
> between partition numbers 4 and 5.  While this is listed as "Free Space"
> by parted, I believe it is inaccessible to partitioning tools because,
> by convention (de facto standard?), partitions have monotonically
> increasing sector numbers -- e.g. the First and Last LBA's of partition
> 4 must be greater than the LBA's for partition 3 and less than the LBA's
> for partition 5.  Therefore, the tools won't create a partition 7 that
> lies between partitions 4 and 5.

Never heard of this standard. Sounds like a broken tool.

> Theoretically, it should be possible to delete the partition table
> entries for partitions 5 and 6, and then create new entries for
> partitions 5, 6, and 7 using the exact sector numbers so that the new
> partition 5 lines up with the free space, the new partition 6 lines up
> with the old partition 5, and the new partition 7 lines up with the old
> partition 6.  But you would need to disconnect whatever in the firmware
> and/or Windows uses partitions 5 and 6 beforehand, and then
> reconnect them to partitions 6 and 7 afterwards.  Then, once you install
> Debian in new partition 5, you'll need to run the multi-boot bootloader
> gauntlet.

All sounds very dangerous to me. If you feel the need to have
the numbers in sequential order, just type "s" in a tool like gdisk:

# gdisk /dev/sdb
GPT fdisk (gdisk) version 0.8.10

Partition table scan:
  MBR: protective
  BSD: not present
  APM: not present
  GPT: present

Found valid GPT with protective MBR; using GPT.

Command (? for help): p
Disk /dev/sdb: 3893247 sectors, 1.9 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): 97E6AEEE-E528-43A1-817A-66BE750CF257
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 3893213
Partitions will be aligned on 2048-sector boundaries
Total free space is 3862460 sectors (1.8 GiB)

Number  Start (sector)End (sector)  Size   Code  Name
   28192   34815   13.0 MiBAF00  Apple HFS/HFS+
   340966143   1024.0 KiB  FB00  VMWare VMFS
   520484095   1024.0 KiB  8300  Linux filesystem

Command (? for help): s
You may need to edit /etc/fstab and/or your boot loader configuration!

Command (? for help): p
Disk /dev/sdb: 3893247 sectors, 1.9 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): 97E6AEEE-E528-43A1-817A-66BE750CF257
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 3893213
Partitions will be aligned on 2048-sector boundaries
Total free space is 3862460 sectors (1.8 GiB)

Number  Start (sector)End (sector)  Size   Code  Name
   120484095   1024.0 KiB  8300  Linux filesystem
   240966143   1024.0 KiB  FB00  VMWare VMFS
   38192   34815   13.0 MiBAF00  Apple HFS/HFS+

Command (? for help): w

Final checks complete. About to write GPT data. THIS WILL OVERWRITE EXISTING
PARTITIONS!!

Do you want to proceed? (Y/N): y
OK; writing new GUID partition table (GPT) to /dev/sdb.
The operation has completed successfully.
# gdisk /dev/sdb
GPT fdisk (gdisk) version 0.8.10

Partition table scan:
  MBR: protective
  BSD: not present
  APM: not present
  GPT: present

Found valid GPT with protective MBR; using GPT.

Command (? for help): p
Disk /dev/sdb: 3893247 sectors, 1.9 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): 97E6AEEE-E528-43A1-817A-66BE750CF257
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 3893213
Partitions will be aligned on 2048-sector boundaries
Total free space is 3862460 sectors (1.8 GiB)

Number  Start (sector)End (sector)  Size   Code  Name
   120484095   1024.0 KiB  8300  Linux filesystem
   240966143   1024.0 KiB  FB00  VMWare VMFS
   38192   34815   13.0 MiBAF00  Apple HFS/HFS+

Command (? for help): n
Partition number (4-128, default 4): 57
First sector (34-3893213, default = 34816) or {+-}size{KMGTP}: 6144
Last sector (6144-8191, default = 8191) or {+-}size{KMGTP}: 8191
Current type is 'Linux filesystem'
Hex code or GUID (L to show codes, Enter = 8300): bf00
Changed type of partition to 'Solaris root'

Command (? for help): p
Disk /dev/sdb: 3893247 sectors, 1.9 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): 97E6AEEE-E528-43A1-817A-66BE750CF257
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 3893213
Partitions will 

Re: Debian installer not finding free space

[David Christensen]

On 06/14/2017 07:00 PM, David DLC wrote:

http://imgur.com/a/o83Qd


It looks like your 500GB drive uses the GPT partitioning scheme, and the
Windows C:\ file system corresponds to partition Number 4.  You also
have partition numbers 5 (867 MB) and 6 (21,705 MB), and then a little
free space (~4 MB).


When you shrank the C:\ file system and partition 4, it opened a hole
between partition numbers 4 and 5.  While this is listed as "Free Space"
by parted, I believe it is inaccessible to partitioning tools because,
by convention (de facto standard?), partitions have monotonically
increasing sector numbers -- e.g. the First and Last LBA's of partition
4 must be greater than the LBA's for partition 3 and less than the LBA's
for partition 5.  Therefore, the tools won't create a partition 7 that
lies between partitions 4 and 5.


Theoretically, it should be possible to delete the partition table
entries for partitions 5 and 6, and then create new entries for
partitions 5, 6, and 7 using the exact sector numbers so that the new
partition 5 lines up with the free space, the new partition 6 lines up
with the old partition 5, and the new partition 7 lines up with the old
partition 6.  But you would need to disconnect whatever in the firmware
and/or Windows uses partitions 5 and 6 beforehand, and then
reconnect them to partitions 6 and 7 afterwards.  Then, once you install
Debian in new partition 5, you'll need to run the multi-boot bootloader
gauntlet.


I prefer KISS.  That's why I said:

On 06/08/2017 07:10 PM, David Christensen wrote:

I would suggest using a 2.5" HDD/SSD for Windows and using an mSATA
SSD for Debian.  If your computer has both and the mSATA device is
configured as a cache, you will want to reconfigure the firmware
and/or Windows to stop using the cache before you install Debian.



It looks like you also have a 32 GB Intel Fast Flash drive, with ~8 GB
partitioned and ~24 GB free space (for over-provisioning, see [1]). 
This surely looks like a Windows cache device.



Unfortunately, such devices usually are not bootable.  If you configure
Windows to stop using it, you could replace it with an mSATA SSD that is
bootable, put Debian on that, and then configure your CMOS setup and/or
use your POST hotkeys to select which drive to boot.


If you get a large mSATA SSD, you could include partitions for:

1.  A cache for Windows.

2.  A lowest-common-denominator file system (such as FAT32 or NTFS) that
can be shared between Windows, Debian, etc..

3.  Debian.

4.  Other operating systems.


Be sure to leave a good chunk of free space at the end for
over-provisioning.


David


[1]
http://www.seagate.com/tech-insights/ssd-over-provisioning-benefits-master-ti/

Re: Debian installer not finding free space

[David DLC]

>
> Using debian-8.7.1-amd64-xfce-CD-1.iso burned to a USB flash drive:
>>
>
> 1.  Power down computer.  Insert USB flash drive.  Power up computer. Boot
> the USB flash drive with the Debian installer (you stated you already know
> how to do this).
>
> 2.  "Debian GNU/Linux installer boot menu" -- choose "Advanced options".
>
> 3.  "Advanced options" -- choose "Rescue mode".
>
> 4.  "Language" -- choose your preferred language.
>
> 5.  "Country, territory or area" -- choose your preferred country,
> territory, or area.
>
> 6.  "Keymap to use" -- pick your preferred keymap.
>
> 7.  On my laptop that I am using for testing, I am prompted to load
> missing firmware.  I chose "No".
>
> 8.  I am also prompted to choose the primary network interface.  I chose
> "eth0".
>
> 9.  "Hostname" -- accept default (debian).
>
> 10. "Domain name" -- leave blank
>
> 11. "Select your time zone" -- choose your time zone.
>
> 12. "Device to use as root file system" -- choose "Do not use a root file
> system".
>
> 13. "Rescue operations" -- choose "Execute a shell in the installer
> environment".
>
> 14. "Executing a shell" -- choose "Continue".
>
>
> You should now be presented with a root prompt.  Do your work.  Enter
> "exit" when you're done.
>
>

I did what you asked! I had a friend also help me with some of the
commands, because one of them wasn't working. I'm not sure what he did with
it though. I uploaded the pictures here:
http://imgur.com/a/o83Qd

Re: Debian installer not finding free space

[David Christensen]

On 06/14/2017 02:37 PM, David DLC wrote:

On Tue, Jun 13, 2017 at 5:18 PM, David Christensen wrote:


Boot the Debian installer and get to a recovery console prompt.

Run lsblk (8) and determine the device node for your ~500 GB drive (it
should be /dev/sda, but you should confirm this):

https://manpages.debian.org/jessie/util-linux/lsblk.8.en.html

# lsblk

Then run parted (8) to see how the disk is partitioned:

https://manpages.debian.org/jessie/parted/parted.8.en.html

# parted /dev/sda u s p free

Take a photograph of the screen with the two commands and their output,
upload, and reply with the URL.


Sorry about that, I am usually busy during the day with either work or
school. I am unsure how to enter this recovery console mode you are talking
about. I have the Debian installer pulled up, but am not sure where to go
from there.


Using debian-8.7.1-amd64-xfce-CD-1.iso burned to a USB flash drive:

1.  Power down computer.  Insert USB flash drive.  Power up computer. 
Boot the USB flash drive with the Debian installer (you stated you 
already know how to do this).


2.  "Debian GNU/Linux installer boot menu" -- choose "Advanced options".

3.  "Advanced options" -- choose "Rescue mode".

4.  "Language" -- choose your preferred language.

5.  "Country, territory or area" -- choose your preferred country, 
territory, or area.


6.  "Keymap to use" -- pick your preferred keymap.

7.  On my laptop that I am using for testing, I am prompted to load 
missing firmware.  I chose "No".


8.  I am also prompted to choose the primary network interface.  I chose 
"eth0".


9.  "Hostname" -- accept default (debian).

10. "Domain name" -- leave blank

11. "Select your time zone" -- choose your time zone.

12. "Device to use as root file system" -- choose "Do not use a root 
file system".


13. "Rescue operations" -- choose "Execute a shell in the installer 
environment".


14. "Executing a shell" -- choose "Continue".


You should now be presented with a root prompt.  Do your work.  Enter 
"exit" when you're done.



David

Re: Debian installer not finding free space

[David DLC]

On Tue, Jun 13, 2017 at 5:18 PM, David Christensen <
dpchr...@holgerdanske.com> wrote:
>
> Boot the Debian installer and get to a recovery console prompt.
>
>
> Run lsblk (8) and determine the device node for your ~500 GB drive (it
> should be /dev/sda, but you should confirm this):
>
> https://manpages.debian.org/jessie/util-linux/lsblk.8.en.html
>
> # lsblk
>
>
> Then run parted (8) to see how the disk is partitioned:
>
> https://manpages.debian.org/jessie/parted/parted.8.en.html
>
> # parted /dev/sda u s p free
>
>
> Take a photograph of the screen with the two commands and their output,
> upload, and reply with the URL.
>
>
>
Sorry about that, I am usually busy during the day with either work or
school. I am unsure how to enter this recovery console mode you are talking
about. I have the Debian installer pulled up, but am not sure where to go
from there.

Re: Debian installer not finding free space

[David Christensen]

On 06/12/2017 10:16 PM, David DLC wrote:

I wanted to thank everyone for the help on the "Debian Installation Issues"
thread. I got the installer to start up through some fiddling around with
settings that were discussed. I am actually not 100% sure which solution
solved the problem, but I am glad it worked out!


So, you can boot Windows and you can boot the Debian installer on USB a 
flash drive -- good.  I would write down the CMOS settings as they are 
right now.




I have encountered a new problem, and decided to start a new thread due to
the large amount of messages already present on the previous thread.

I have 40 gb unallocated on my C drive currently. When I start up the
installer and get to the disk partitioning section, it cannot find the free
space in the "guided" section. Am I doing something wrong with the disk
management?

I took a screenshot of my disk management program to show you guys:
http://imgur.com/a/qUoE0


Boot the Debian installer and get to a recovery console prompt.


Run lsblk (8) and determine the device node for your ~500 GB drive (it 
should be /dev/sda, but you should confirm this):


https://manpages.debian.org/jessie/util-linux/lsblk.8.en.html

# lsblk


Then run parted (8) to see how the disk is partitioned:

https://manpages.debian.org/jessie/parted/parted.8.en.html

# parted /dev/sda u s p free


Take a photograph of the screen with the two commands and their output, 
upload, and reply with the URL.



David

Re: Debian installer not finding free space

[David Wright]

On Tue 13 Jun 2017 at 11:01:10 (-0500), David DLC wrote:

> I have Windows 10 running on my computer currently.

Have you reconciled "I have shrunk the main C drive by 25 gbs"
and the 40GB of unallocated space?

> I will attempt to combine 2 of the existing partitions.

Not a very useful statement unless you reveal which two partitions
you're talking about. I can't see any obvious candidates.

> I am not familiar
> with any steps for this, so if anyone has tips on deleting and recreating
> partitions, that would be great.

Not in a windows context. Why not use windows to create a partition in
the 40G space and, say, FAT format it. Then see if the Debian installer
can see it, now that you know what you're looking for. (If you put
files into it, the d-i should be able to mount it and see the files.)

> Also, I am unsure what the "disk 1" drive
> is. It seems to be 8 gb of free space, not doing anything. Should I just
> delete that?

Acting hastily is a recipe for disaster. When you're using
partitioning tools, you should never act without knowing exactly
what your actions are acting on.

One has to ask, do you have an 8GB stick plugged in? An SD card?
And this "Disk Management" program; can it not give you more
information? What's the significance of the diagonal stripes?

Cheers,
David.

Re: Debian installer not finding free space

[Fungi4All]

From: drvr...@gmail.com
To: debian-user 

On Tue, Jun 13, 2017 at 4:20 AM, Dan Purgert  wrote:
If it's MBR partitioned, you're already using up your four (4)
partitions (OS (C:\) ; Recovery(400MB); RECOVERY (D:\); Recovery
(800MB); and I'm not 100% sure if the EFI partition counts against you
too).

You would need to remove some of those partitions, and set up an extended
partition container in order to create logical partitions which you can
then install Debian to.

Though, since you already have four (five if we count the EFI
partition), perhaps the drive is already GPT partitioned ...

My computer is actually already GPT partitioned, I already made sure of that.

On Tue, Jun 13, 2017 at 5:42 AM, Fungi4All  wrote:

May I ask what version of windows is it that has terrorized your disk?
In a different discussion I brought up the subject (in reference to win10
being intentinally hostile to other cohabitating systems with uefi/boot protect)
and this is why I am asking.

I have Windows 10 running on my computer currently.

I will attempt to combine 2 of the existing partitions. I am not familiar with 
any steps for this, so if anyone has tips on deleting and recreating 
partitions, that would be great. Also, I am unsure what the "disk 1" drive is. 
It seems to be 8 gb of free space, not doing anything. Should I just delete 
that?

Hold on, if you have a gpt partition why would you be limited in creating 123 
more partitions?
But you need a gpt capable partitioning tool, like someone else mentioned the 
gdisk
Would the win10 disk management tool be limiting what is otherwise nearly 
unlimited?

Re: Debian installer not finding free space

[David DLC]

On Tue, Jun 13, 2017 at 4:20 AM, Dan Purgert  wrote:
>
> If it's MBR partitioned, you're already using up your four (4)
> partitions (OS (C:\) ; Recovery(400MB); RECOVERY (D:\); Recovery
> (800MB); and I'm not 100% sure if the EFI partition counts against you
> too).
>
> You would need to remove some of those partitions, and set up an extended
> partition container in order to create logical partitions which you can
> then install Debian to.
>
> Though, since you already have four (five if we count the EFI
> partition), perhaps the drive is already GPT partitioned ...
>
>
My computer is actually already GPT partitioned, I already made sure of
that.


On Tue, Jun 13, 2017 at 5:42 AM, Fungi4All  wrote:

>
>
> May I ask what version of windows is it that has terrorized your disk?
> In a different discussion I brought up the subject (in reference to win10
> being intentinally hostile to other cohabitating systems with uefi/boot
> protect)
> and this is why I am asking.
>

>

I have Windows 10 running on my computer currently.

I will attempt to combine 2 of the existing partitions. I am not familiar
with any steps for this, so if anyone has tips on deleting and recreating
partitions, that would be great. Also, I am unsure what the "disk 1" drive
is. It seems to be 8 gb of free space, not doing anything. Should I just
delete that?

Re: Debian installer not finding free space

[Fungi4All]

UTC Time: June 13, 2017 5:16 AM
From: drvr...@gmail.com

I have 40 gb unallocated on my C drive currently. When I start up the installer 
and get to the disk partitioning section, it cannot find the free space in the 
"guided" section. Am I doing something wrong with the disk management?

I took a screenshot of my disk management program to show you guys:
http://imgur.com/a/qUoE0

May I ask what version of windows is it that has terrorized your disk?
In a different discussion I brought up the subject (in reference to win10
being intentinally hostile to other cohabitating systems with uefi/boot protect)
and this is why I am asking.

If you are careful enough, using a live linux USBstick, take the last large 
partition
and use it to store images (zipped) of the small partitions. Then delete the 
ones
you have made images of. Then in the left over space create an extended
partition and recreate those that were deleted. Then restore the images in them.
Then create as many partitions you need for linux in the left over.
I have no experience with any windows past 7 and how it recognizes extended
partitions or identifies them. Utilizing dd if=/dev/sd** bzip2 >part** you can 
safely
recreate any partition. The larger the longer it takes. I am not even sure 
whether
or not all those recovery partitions are wanted or necessary since you can 
create
recovery disks in external mediums whenever you like. Recovery is only for 
fixing
your system returning it to a previous state, none of your data will be 
recovered
if lost (win).

It is a timely lengthy process but it is the only option you have to a second 
hd.
If you go the second way then move and expand your last partitions to utilize
the free space in your work area partition.

What a mesh! If this setup is OEM (which is weird for not taking up the whole
disk) it is a definite move to prevent a seconf operating system within the
same disk, which further undermines the intelligence of the customer (sw & hw).

Re: Debian installer not finding free space

[Michael Fothergill]

On 13 June 2017 at 10:20, Dan Purgert  wrote:

> David DLC wrote:
> > [...]
> > I have 40 gb unallocated on my C drive currently. When I start up the
> > installer and get to the disk partitioning section, it cannot find the
> > free space in the "guided" section. Am I doing something wrong with
> > the disk management?
>
> If it's MBR partitioned, you're already using up your four (4)
> partitions (OS (C:\) ; Recovery(400MB); RECOVERY (D:\); Recovery
> (800MB); and I'm not 100% sure if the EFI partition counts against you
> too).
>
>
> You would need to remove some of those partitions, and set up an extended
> partition container in order to create logical partitions which you can
> then install Debian to.
>

​Unlike Ubuntu which I think can find a way to make space within the
windows partitions to install itself, I don't think Debian has that option.

I am not sure if you would need to reinstall Windows and reduce the
partition sizes to create free disk space that the installer will see and
make use of.

Perhaps if you nobble the two recovery partitions that won't make Windows
unusable.  If you could then install debian in the space freed up when you
reboot into Windows it will discover that the recovery partitions are gone
but there is no space in which to recreate them.   I think that Windows
might then reorganise things to reduce the C drive partition size and allow
new recovery partitions to be created. I am not 100% sure on this but you
could google it and check.

Regards

MF
​


>
> Though, since you already have four (five if we count the EFI
> partition), perhaps the drive is already GPT partitioned ...
>
>
> --
> |_|O|_| Registered Linux user #585947
> |_|_|O| Github: https://github.com/dpurgert
> |O|O|O| PGP: 05CA 9A50 3F2E 1335 4DC5  4AEE 8E11 DDF3 1279 A281
>
>

Re: Debian installer not finding free space

[Dan Purgert]

David DLC wrote:
> [...]
> I have 40 gb unallocated on my C drive currently. When I start up the
> installer and get to the disk partitioning section, it cannot find the
> free space in the "guided" section. Am I doing something wrong with
> the disk management?

If it's MBR partitioned, you're already using up your four (4)
partitions (OS (C:\) ; Recovery(400MB); RECOVERY (D:\); Recovery
(800MB); and I'm not 100% sure if the EFI partition counts against you
too).


You would need to remove some of those partitions, and set up an extended
partition container in order to create logical partitions which you can
then install Debian to.

Though, since you already have four (five if we count the EFI
partition), perhaps the drive is already GPT partitioned ... 


-- 
|_|O|_| Registered Linux user #585947
|_|_|O| Github: https://github.com/dpurgert
|O|O|O| PGP: 05CA 9A50 3F2E 1335 4DC5  4AEE 8E11 DDF3 1279 A281