On Wed, 21 Feb 2018 23:19:04 +0100
Pascal Hambourg wrote:
> Le 21/02/2018 à 03:53, Dan Norton a écrit :
> >
> > In contrast, with GPT and LVM, for the second and subsequent
> > installations, the partitioning and defining of PVs, VGs, and LVs
> > needs to be done before installation using gdisk
Le 21/02/2018 à 03:53, Dan Norton a écrit :
In contrast, with GPT and LVM, for the second and subsequent
installations, the partitioning and defining of PVs, VGs, and LVs needs
to be done before installation using gdisk and the LVM tools in /sbin.
Then, the installer with manual partitioning can
As the OP, I want to try to clear up some of the confusion. I have
caused plenty of it. :-)
I drop-kicked the partitions I had set up and started over with a bare
(nothing but free space) sda block device. At some point I have
expressed doubt that my PC could handle UEFI correctly. This is not
tru
05:00)
https://lists.debian.org/debian-user/2017/11/msg00633.html
not just his/this "BIOS Can Not Find Disk" thread.
--
"Wisdom is supreme; therefore get wisdom. Whatever else you
get, get wisdom." Proverbs 4:7 (New Living Translation)
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata *** http://fm.no-ip.com/
Le 07/12/2017 à 00:03, Felix Miata a écrit :
In the context of a GPT partitioned disk,
That context was missing from post you're complaining about.
That was your post, and it had plenty enough context :
- BIOS boot partition only exists in GPT
- type EE is used in GPT protective MBR
Anyw
On 12/05/17 15:18, Pascal Hambourg wrote:
Le 05/12/2017 à 06:55, David Christensen a écrit :
4. The firmware finds the first GPT partition and file system, which
look "right" for EFI boot images.
No.
5. The firmware reads this file system and finds only one file, which
it loads and runs (s
Pascal Hambourg composed on 2017-12-06 23:16 (UTC+0100):
> Felix Miata composed:
>> Nothing in that post makes it unambiguous that an MBR (MSDOS) partitioned
>> disk
>> was not the subject of discussion.
> In the context of a GPT partitioned disk,
That context w
Le 05/12/2017 à 03:33, Felix Miata a écrit :
Pascal Hambourg composed on 2017-12-05 00:41 (UTC+0100):
You're the only one bringing additional confusion.
Nobody but you talked about doing such a stupid thing as removing a type
ee partition. Dan and I only talked about removing the BIOS boot
part
Le 05/12/2017 à 06:55, David Christensen a écrit :
I wiped the SSD, ran d-i, and chose "Partitioning method" -> "Guided -
use entire disk and set up encrypted LVM", which produced:
LVM VG debian-vg, LV home - 3.5 GB Linux device-mapper (linear)
#1 3.5 GB f ext4
lest automagic partitioning and see what happens.
I don't know anything about UEFI firmware. I'm only just inheriting
a UEFI laptop with W10 on it and hope to split a partition for linux,
but I've only booted linux from a USB stick just to have a poke about.
The OP/Subject li
On 12/04/2017 12:17 AM, David Christensen wrote:
On 12/03/17 13:44, Dan Norton wrote:
On 12/02/2017 02:35 PM, David Christensen wrote:
I'm not making progress with this PC so I'll probably abandon GPT.
The disk is 1T and it was handled by the extended partition scheme
before this experiment an
On 12/04/17 17:34, David Christensen wrote:
That's why I plan to try again with the simplest automagic partitioning
and see what happens.
I wiped the SSD, ran d-i, and chose "Partitioning method" -> "Guided -
use entire disk and set up encrypted LVM", which produced:
LVM VG debian-vg
Pascal Hambourg composed on 2017-12-05 00:41 (UTC+0100):
> You're the only one bringing additional confusion.
> Nobody but you talked about doing such a stupid thing as removing a type
> ee partition. Dan and I only talked about removing the BIOS boot
> partition sda1.
In https://lists.debian.
On 12/04/17 07:21, David Wright wrote:
I recently reformatted a disk thus:
puck: GPT-style, master
Part # filesys sizecoderôle
puck- 1007KiB partition tables and alignment space
puck01 - 3MiBEF02bios-boot for Grub (bios
On 12/04/17 06:39, Dan Norton wrote:
On 12/04/2017 12:27 AM, David Christensen wrote:
Are there any other commands that readers might find interesting
(before I wipe the SSD)?
Just out of curiosity, lvdisplay?
# lvm lvdisplay
--- Logical volume ---
LV Path/dev/vg-stretch/
Le 04/12/2017 à 00:40, Felix Miata a écrit :
Pascal Hambourg composed on 2017-12-03 23:40 (UTC+0100):
...
Then, to proceed, remove /dev/sda1 partition followed by grub-install?
Removing the partition won't help. It is just useless, it does not harm.
If sda1 is a type EEh partition, doin
On Sun 03 Dec 2017 at 21:27:20 (-0800), David Christensen wrote:
> On 12/03/17 21:17, David Christensen wrote:
> >But, it was not a total loss -- I can now dissect the SSD.
>
> More info:
>
> # lsblk /dev/sda
> NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
> sda 8:00 14.9G 0 disk
> |-sda1
On 12/04/2017 12:27 AM, David Christensen wrote:
On 12/03/17 21:17, David Christensen wrote:
But, it was not a total loss -- I can now dissect the SSD.
More info:
# lsblk /dev/sda
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 14.9G 0 disk
|-sda1 8:1 0 953M 0 part
`-sda2
On 12/03/17 21:17, David Christensen wrote:
But, it was not a total loss -- I can now dissect the SSD.
More info:
# lsblk /dev/sda
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:00 14.9G 0 disk
|-sda1 8:10 953M 0 part
`-sda2 8:20 4.7G 0 part
# parted /dev/sda u s p
On 12/03/17 13:44, Dan Norton wrote:
On 12/02/2017 02:35 PM, David Christensen wrote:
I'm not making progress with this PC so I'll probably abandon GPT. The
disk is 1T and it was handled by the extended partition scheme before
this experiment and it probably can again. I still want to do LVM an
On 12/02/2017 02:35 PM, David Christensen wrote:
[...]
Where is /boot?
Possibly, this is a better answer:
$ df -Th
Filesystem Type Size Used Avail Use% Mounted on
[...]
/dev/sda1 vfat 992K 855K 138K 87% /boot/efi
/dev/mapper/debian8--vg-tmp
Pascal Hambourg composed on 2017-12-03 23:40 (UTC+0100):
...
>>> Then, to proceed, remove /dev/sda1 partition followed by grub-install?
> Removing the partition won't help. It is just useless, it does not harm.
>> If sda1 is a type EEh partition, doing that will probably dig your hole too
>> d
On 12/03/2017 02:04 PM, Felix Miata wrote:
Dan Norton composed on 2017-12-04 08:00 (UTC-0500):
Felix Miata wrote:
Dan Norton composed on 2017-12-03 16:44 (UTC-0500):
Note the above is currently from the future. Apparently the PC you are emailing
from is advanced one day.
Must be a result of m
Le 03/12/2017 à 22:51, Felix Miata a écrit :
Dan Norton composed on 2017-12-03 15:54 (UTC-0500):
Pascal Hambourg wrote:
Dan Norton composed:
Yes, no grub in mbr - unless installer insists.
Then what you wrote earlier was wrong : GRUB is not installed in
/dev/sda1, and this partition is
Dan Norton composed on 2017-12-03 15:54 (UTC-0500):
> Pascal Hambourg wrote:
>> Dan Norton composed:
>>> Yes, no grub in mbr - unless installer insists.
>> Then what you wrote earlier was wrong : GRUB is not installed in
>> /dev/sda1, and this partition is useless. As I wrote earlier, a BIOS
On 12/03/2017 02:16 PM, Pascal Hambourg wrote:
Le 04/12/2017 à 13:32, Dan Norton a écrit :
On 12/03/2017 06:49 AM, Felix Miata wrote:
Pascal Hambourg composed on 2017-12-03 10:49 (UTC+0100):
Felix Miata composed:
...
So I guess that the OP means that the core image of GRUB is in
sda1, an
On 12/03/2017 01:04 PM, Felix Miata wrote:
Dan Norton composed on 2017-12-04 07:32 (UTC-0500):
Note your posts are still coming from the future. Today ATM in zone -0500 it
is
still the 3rd of December.
Felix Miata wrote:
I'm pretty sure that was not OP's intent, i.e., none of Grub at all i
Le 04/12/2017 à 13:32, Dan Norton a écrit :
On 12/03/2017 06:49 AM, Felix Miata wrote:
Pascal Hambourg composed on 2017-12-03 10:49 (UTC+0100):
Felix Miata composed:
...
So I guess that the OP means that the core image of GRUB is in sda1, and
the boot image of GRUB is in the MBR of sda.
(.
Dan Norton composed on 2017-12-04 07:32 (UTC-0500):
Note your posts are still coming from the future. Today ATM in zone -0500 it is
still the 3rd of December.
> Felix Miata wrote:
>> I'm pretty sure that was not OP's intent, i.e., none of Grub at all in MBR.
> Yes, no grub in mbr - unless inst
On 12/03/2017 06:49 AM, Felix Miata wrote:
Pascal Hambourg composed on 2017-12-03 10:49 (UTC+0100):
Felix Miata composed:
...
So I guess that the OP means that the core image of GRUB is in sda1, and
the boot image of GRUB is in the MBR of sda.
Based on OP's response to
https://lists.debi
Pascal Hambourg composed on 2017-12-03 10:49 (UTC+0100):
> Felix Miata composed:
...
> So I guess that the OP means that the core image of GRUB is in sda1, and
> the boot image of GRUB is in the MBR of sda.
Based on OP's response to
https://lists.debian.org/debian-user/2017/11/msg00563.html
i
Le 02/12/2017 à 05:07, Dan Norton a écrit :
On 12/01/2017 08:54 PM, David Christensen wrote:
>
> # fdisk -t dos /dev/sda
Your original post indicated a GPT partition table. Forcing an MS-DOS
MBR partition type means the tool will be looking at fake information
that your GPT formatting tool
Le 03/12/2017 à 00:09, Felix Miata a écrit :
Michael Lange composed on 2017-12-02 22:33 (UTC+0100):
On Fri, 1 Dec 2017 23:07:15 -0500 Dan Norton wrote:
(...)
What bootloader was installed -- LILO, GRUB, GRUB2, whatever? And,
where?
GRUB2 to sda1.
I did not read this thread in detail,
Michael Lange wrote:
> Windows is a pain in the neck of
> course, still booting a Live system and reinstalling grub from a chroot
> environment seems comparatively easy to me compared to the OP's
> troubles ;)
Agreed here and this is exactly what I do.
+ grub2 finds windows automatically and perh
On 12/02/2017 02:35 PM, David Christensen wrote:
On 12/01/17 20:07, Dan Norton wrote:
On 12/01/2017 08:54 PM, David Christensen wrote:
On 12/01/17 10:50, Dan Norton wrote: >>> Maybe this is the wrong
forum, but please bear with me a little bit.
This post was sent from a desktop with jessie inst
On Sat, 2 Dec 2017 18:09:56 -0500
Felix Miata wrote:
> Michael Lange composed on 2017-12-02 22:33 (UTC+0100):
>
> > On Fri, 1 Dec 2017 23:07:15 -0500 Dan Norton wrote:
>
> > (...)
> >> > What bootloader was installed -- LILO, GRUB, GRUB2, whatever? And,
> >> > where?
>
> >> GRUB2 to sda1.
>
>
Michael Lange composed on 2017-12-02 22:33 (UTC+0100):
> On Fri, 1 Dec 2017 23:07:15 -0500 Dan Norton wrote:
> (...)
>> > What bootloader was installed -- LILO, GRUB, GRUB2, whatever? And,
>> > where?
>> GRUB2 to sda1.
> I did not read this thread in detail, so maybe this has already been
> dis
On Fri, 1 Dec 2017 23:07:15 -0500
Dan Norton wrote:
(...)
> > What bootloader was installed -- LILO, GRUB, GRUB2, whatever? And,
> > where?
> >
>
>
> GRUB2 to sda1.
>
I did not read this thread in detail, so maybe this has already been
discussed, but I have just now been thinking, shouldn't g
On 12/01/17 20:07, Dan Norton wrote:
On 12/01/2017 08:54 PM, David Christensen wrote:
On 12/01/17 10:50, Dan Norton wrote: >>> Maybe this is the wrong forum, but
please bear with me a little bit.
This post was sent from a desktop with jessie installed. The problem
is it will not boot normally.
Hi,
Dan Norton wrote:
> OK, the syslinux and syslinux-efi packages are now installed
SYSLINUX and GRUB are competitors (with GRUB winning the race on hard disk
but lagging behind on ISO 9660 for old BIOS).
I mentioned the SYSLINUX file "mbr.bin" (source: mbr.S) only to
substantiate my statement a
On 12/01/2017 02:58 PM, Thomas Schmitt wrote:
Hi,
Dan Norton wrote:
# fdisk -l
...
Disklabel type: gpt
In the dim past, fdisk
could set a partition as "active", which was its euphemism for "bootable".
I guess, this applies only to MBR partition tables, not to GPT as on your
disk.
As Pascal st
On 12/01/2017 08:54 PM, David Christensen wrote:
On 12/01/17 10:50, Dan Norton wrote:
Maybe this is the wrong forum, but please bear with me a little bit.
This post was sent from a desktop with jessie installed. The problem
is it will not boot normally. Network booting has been disabled in
th
On 12/01/17 10:50, Dan Norton wrote:
Maybe this is the wrong forum, but please bear with me a little bit.
This post was sent from a desktop with jessie installed. The problem is
it will not boot normally. Network booting has been disabled in the
NVRAM setup. After POST there is a one-liner whic
Dan Norton composed on 2017-12-01 16:23 (UTC-0500):
> The PC is simply not seeing the 1T sda, which is the only disk. It's not
> even getting as far as the mbr/grub. The PC appears to be no more than 5
> years old, based on the BIOS date, but it may be old enough to have a
> flaky UEFI. Should
On 12/01/2017 02:29 PM, Pascal Hambourg wrote:
Le 01/12/2017 à 19:57, Greg Wooledge a écrit :
On Fri, Dec 01, 2017 at 01:50:12PM -0500, Dan Norton wrote:
Disklabel type: gpt
Apparently, BIOS does not see a bootable device. In the dim past, fdisk
could set a partition as "active", which was i
Hi,
Dan Norton wrote:
> # fdisk -l
> ...
> Disklabel type: gpt
> In the dim past, fdisk
> could set a partition as "active", which was its euphemism for "bootable".
I guess, this applies only to MBR partition tables, not to GPT as on your
disk.
As Pascal stated, there is a bit defined in GPT to
Le 01/12/2017 à 19:57, Greg Wooledge a écrit :
On Fri, Dec 01, 2017 at 01:50:12PM -0500, Dan Norton wrote:
Disklabel type: gpt
Apparently, BIOS does not see a bootable device. In the dim past, fdisk
could set a partition as "active", which was its euphemism for "bootable".
However now:
GPT
On Fri, Dec 01, 2017 at 01:57:37PM -0500, Greg Wooledge wrote:
> On Fri, Dec 01, 2017 at 01:50:12PM -0500, Dan Norton wrote:
> > Disklabel type: gpt
>
> > Apparently, BIOS does not see a bootable device. In the dim past, fdisk
> > could set a partition as "active", which was its euphemism for "boo
On Fri, Dec 01, 2017 at 01:50:12PM -0500, Dan Norton wrote:
> Disklabel type: gpt
> Apparently, BIOS does not see a bootable device. In the dim past, fdisk
> could set a partition as "active", which was its euphemism for "bootable".
> However now:
GPT disk labels don't have active/bootable partit
Maybe this is the wrong forum, but please bear with me a little bit.
This post was sent from a desktop with jessie installed. The problem is
it will not boot normally. Network booting has been disabled in the
NVRAM setup. After POST there is a one-liner which says it can not find
disk. It can b
50 matches
Mail list logo
