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 <deb...@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.
>
>

Reply via email to