Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #182188 > unrolled thread
| Started by | David DLC <drvrddc@gmail.com> |
|---|---|
| First post | 2017-06-15 04:10 +0200 |
| Last post | 2017-06-16 07:30 +0200 |
| Articles | 6 — 3 participants |
Back to article view | Back to linux.debian.user
Re: Debian installer not finding free space David DLC <drvrddc@gmail.com> - 2017-06-15 04:10 +0200
Re: Debian installer not finding free space David Christensen <dpchrist@holgerdanske.com> - 2017-06-15 06:50 +0200
Re: Debian installer not finding free space David Wright <deblis@lionunicorn.co.uk> - 2017-06-15 16:20 +0200
Re: Debian installer not finding free space David DLC <drvrddc@gmail.com> - 2017-06-15 18:20 +0200
Re: Debian installer not finding free space David Christensen <dpchrist@holgerdanske.com> - 2017-06-16 07:40 +0200
Re: Debian installer not finding free space David Christensen <dpchrist@holgerdanske.com> - 2017-06-16 07:30 +0200
| From | David DLC <drvrddc@gmail.com> |
|---|---|
| Date | 2017-06-15 04:10 +0200 |
| Subject | Re: Debian installer not finding free space |
| Message-ID | <tSsoq-4ML-11@gated-at.bofh.it> |
[Multipart message — attachments visible in raw view] — view raw
> > 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
[toc] | [next] | [standalone]
| From | David Christensen <dpchrist@holgerdanske.com> |
|---|---|
| Date | 2017-06-15 06:50 +0200 |
| Message-ID | <tSuTf-6j6-3@gated-at.bofh.it> |
| In reply to | #182188 |
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/
[toc] | [prev] | [next] | [standalone]
| From | David Wright <deblis@lionunicorn.co.uk> |
|---|---|
| Date | 2017-06-15 16:20 +0200 |
| Message-ID | <tSDMR-3vs-3@gated-at.bofh.it> |
| In reply to | #182191 |
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
2 8192 34815 13.0 MiB AF00 Apple HFS/HFS+
3 4096 6143 1024.0 KiB FB00 VMWare VMFS
5 2048 4095 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
1 2048 4095 1024.0 KiB 8300 Linux filesystem
2 4096 6143 1024.0 KiB FB00 VMWare VMFS
3 8192 34815 13.0 MiB AF00 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
1 2048 4095 1024.0 KiB 8300 Linux filesystem
2 4096 6143 1024.0 KiB FB00 VMWare VMFS
3 8192 34815 13.0 MiB AF00 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 be aligned on 2048-sector boundaries
Total free space is 3860412 sectors (1.8 GiB)
Number Start (sector) End (sector) Size Code Name
1 2048 4095 1024.0 KiB 8300 Linux filesystem
2 4096 6143 1024.0 KiB FB00 VMWare VMFS
3 8192 34815 13.0 MiB AF00 Apple HFS/HFS+
57 6144 8191 1024.0 KiB BF00 Solaris root
Command (? for help): s
You may need to edit /etc/fstab and/or your boot loader configuration!
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 3860412 sectors (1.8 GiB)
Number Start (sector) End (sector) Size Code Name
1 2048 4095 1024.0 KiB 8300 Linux filesystem
2 4096 6143 1024.0 KiB FB00 VMWare VMFS
3 6144 8191 1024.0 KiB BF00 Solaris root
4 8192 34815 13.0 MiB AF00 Apple HFS/HFS+
Command (? for help):
Cheers,
David.
[toc] | [prev] | [next] | [standalone]
| From | David DLC <drvrddc@gmail.com> |
|---|---|
| Date | 2017-06-15 18:20 +0200 |
| Message-ID | <tSFF0-4Gu-25@gated-at.bofh.it> |
| In reply to | #182196 |
[Multipart message — attachments visible in raw view] — view raw
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 <deblis@lionunicorn.co.uk>
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
> 2 8192 34815 13.0 MiB AF00 Apple HFS/HFS+
> 3 4096 6143 1024.0 KiB FB00 VMWare VMFS
> 5 2048 4095 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
> 1 2048 4095 1024.0 KiB 8300 Linux filesystem
> 2 4096 6143 1024.0 KiB FB00 VMWare VMFS
> 3 8192 34815 13.0 MiB AF00 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
> 1 2048 4095 1024.0 KiB 8300 Linux filesystem
> 2 4096 6143 1024.0 KiB FB00 VMWare VMFS
> 3 8192 34815 13.0 MiB AF00 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 be aligned on 2048-sector boundaries
> Total free space is 3860412 sectors (1.8 GiB)
>
> Number Start (sector) End (sector) Size Code Name
> 1 2048 4095 1024.0 KiB 8300 Linux filesystem
> 2 4096 6143 1024.0 KiB FB00 VMWare VMFS
> 3 8192 34815 13.0 MiB AF00 Apple HFS/HFS+
> 57 6144 8191 1024.0 KiB BF00 Solaris root
>
> Command (? for help): s
> You may need to edit /etc/fstab and/or your boot loader configuration!
>
> 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 3860412 sectors (1.8 GiB)
>
> Number Start (sector) End (sector) Size Code Name
> 1 2048 4095 1024.0 KiB 8300 Linux filesystem
> 2 4096 6143 1024.0 KiB FB00 VMWare VMFS
> 3 6144 8191 1024.0 KiB BF00 Solaris root
> 4 8192 34815 13.0 MiB AF00 Apple HFS/HFS+
>
> Command (? for help):
>
> Cheers,
> David.
>
>
[toc] | [prev] | [next] | [standalone]
| From | David Christensen <dpchrist@holgerdanske.com> |
|---|---|
| Date | 2017-06-16 07:40 +0200 |
| Message-ID | <tSS9c-4gj-9@gated-at.bofh.it> |
| In reply to | #182205 |
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
[toc] | [prev] | [next] | [standalone]
| From | David Christensen <dpchrist@holgerdanske.com> |
|---|---|
| Date | 2017-06-16 07:30 +0200 |
| Message-ID | <tSRZv-4da-3@gated-at.bofh.it> |
| In reply to | #182196 |
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
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.user
csiph-web