Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #189403
| From | Dan Norton <dnorton@mindspring.com> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: Debian 8 and Debian 9 Dual Boot |
| Date | 2017-11-29 19:00 +0100 |
| Message-ID | <uReOl-4nN-3@gated-at.bofh.it> (permalink) |
| References | (1 earlier) <uLlzc-5Eu-1@gated-at.bofh.it> <uLpt7-8fl-3@gated-at.bofh.it> <uLs7E-1ek-5@gated-at.bofh.it> <uR14J-4iq-3@gated-at.bofh.it> <uR6xs-7RM-27@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On 11/29/2017 03:59 AM, Joe wrote: > On Tue, 28 Nov 2017 22:15:22 -0500 > Dan Norton <dnorton@mindspring.com> wrote: > >> On 11/13/2017 01:55 PM, Joe wrote: >>> On Mon, 13 Nov 2017 11:01:27 -0500 >>> Dan Norton <dnorton@mindspring.com> wrote: >>> >>> >>>> Although I didn't say so, each install would have its own set of >>>> directories. Please say more about how to mount the other >>>> installation and share data. How to mount things in another volume >>>> group? >>>> >>> Good advice so far, but to add a bit: all LVM groups will be seen at >>> boot, and /dev will know about them. See man lvm2 and also here: >>> >>> https://wiki.debian.org/LVM for complete information about the >>> commands you have available. There are also numerous tutorials on >>> the Net which show basic usage of the simpler commands. It's worth >>> having a look when you have some spare time, as one day you'll need >>> to know some of this and won't have any spare time. >> Reading the wiki reveals "Grub and ? >> <https://wiki.debian.org/LiLo>LiLo are not compatible with LVM, >> so /bootshould be outside the storage disk managed by LVM." > Not many people are using lilo today, and a recent grub2 should have no > problem at all with lvm. But there's no harm in a separate /boot, and > I've always done it that way. > >> Here's >> what I have: >> >> Attempts to boot normally do not work. But using Super Grub2 on a >> bootable cd and selecting "Boot manually" and picking the hd1 entry >> brings up the jessie system that the installer reports as >> successfully installed on sda3. Using fdisk to take a look: >> >> dan@debian8:~$ sudo fdisk /dev/sda >> Command (m for help): p >> Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 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: gpt >> Disk identifier: A615A904-0620-459F-BF44-5E53E54FDF24 >> >> Device Start End Sectors Size Type >> /dev/sda1 2048 411647 409600 200M BIOS boot >> /dev/sda2 411648 16783359 16371712 7.8G Linux swap >> /dev/sda3 16783360 151001087 134217728 64G Linux LVM >> /dev/sda4 151001088 285218815 134217728 64G Linux LVM >> /dev/sda5 285218816 419436543 134217728 64G Linux LVM >> /dev/sda6 419436544 553654271 134217728 64G Linux LVM >> /dev/sda7 553654272 1953525134 1399870863 667.5G Linux filesystem >> >> Is there a problem here? > Not obviously so. But you know that you have a working installation, > just one with a booting problem, which suggests this is all plausible. > >> dan@debian8:~$ df -h >> Filesystem Size Used Avail Use% Mounted on >> /dev/dm-0 9.1G 3.0G 5.7G 35% / >> udev 10M 0 10M 0% /dev >> tmpfs 775M 9.0M 766M 2% /run >> tmpfs 1.9G 68K 1.9G 1% /dev/shm >> tmpfs 5.0M 4.0K 5.0M 1% /run/lock >> tmpfs 1.9G 0 1.9G 0% /sys/fs/cgroup >> /dev/sda1 992K 142K 851K 15% /boot/efi >> /dev/mapper/debian8--vg-var 8.2G 1.3G 6.4G 17% /var >> /dev/mapper/debian8--vg-home 9.1G 356M 8.3G 5% /home >> /dev/mapper/debian8--vg-tmp 268M 2.1M 247M 1% /tmp >> tmpfs 388M 4.0K 388M 1% /run/user/115 >> tmpfs 388M 12K 388M 1% /run/user/1000 >> >> >> Doesn't this satisfy the statement that "/boot should be outside the >> storage disk managed by LVM" since it is on sda1? >> >>> Look in /etc/fstab for lines beginning /dev/mapper/[volume] which >>> will be the volumes mounted in the running installation. The >>> 'mapper' is turning LVM volumes into things which look like >>> partitions for many purposes. >> Here is fstab: >> # /etc/fstab: static file system information. >> # >> # Use 'blkid' to print the universally unique identifier for a >> # device; this may be used with UUID= as a more robust way to name >> devices # that works even if disks are added and removed. See >> fstab(5). # >> # <file system> <mount point> <type> <options> <dump> <pass> >> /dev/mapper/debian8--vg-root / ext4 errors=remount-ro >> 0 1 # /boot/efi was on /dev/sda1 during installation >> UUID=B07E-1F0B /boot/efi vfat umask=0077 0 1 >> /dev/mapper/debian8--vg-home /home ext4 defaults >> 0 2 /dev/mapper/debian8--vg-tmp /tmp ext4 >> defaults 0 2 /dev/mapper/debian8--vg-var /var >> ext4 defaults 0 2 # swap was on /dev/sda2 during >> installation UUID=6aa1846f-34dd-424d-b02c-dbd0af037a23 >> none swap sw 0 0 >> /dev/sr0 /media/cdrom0 udf,iso9660 user,noauto 0 0 >> >> >> Why won't it boot normally, that is without using the bootable Grub2 >> cd? >> > I've had enormous amounts of trouble with grub/grub2 over the years. > Could be anything. > > We have to start from the exact screen messages you get when you try > booting. There are different classes of grub problem, and it will drop > you in different shells depending on what it has found. > > Please, the error messages, word for word... > It doesn't get as far as grub. These are coming from bios(?) after POST: [...] DHCP... (spins for about a minute, then:) Realtek PCIe GBE Family Controller Series v2.38 (12/24/10) CLIENT MAC ADDR: <hex addr> GUID: <hex id> PXE-E53: No boot filename received PXE-MOF: Exiting PXE ROM. ERROR:No boot disk has been detected or the disk has failed. (full stop)
Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Debian 8 and Debian 9 Dual Boot Dan Norton <dnorton@mindspring.com> - 2017-11-13 04:50 +0100
Re: Debian 8 and Debian 9 Dual Boot David Christensen <dpchrist@holgerdanske.com> - 2017-11-13 07:20 +0100
Re: Debian 8 and Debian 9 Dual Boot Dan Norton <dnorton@mindspring.com> - 2017-11-13 16:30 +0100
Re: Debian 8 and Debian 9 Dual Boot Felix Miata <mrmazda@earthlink.net> - 2017-11-13 20:10 +0100
Re: Debian 8 and Debian 9 Dual Boot Dan Norton <dnorton@mindspring.com> - 2017-11-13 21:10 +0100
Re: Debian 8 and Debian 9 Dual Boot Dan Norton <dnorton@mindspring.com> - 2017-11-14 00:10 +0100
Re: Debian 8 and Debian 9 Dual Boot Felix Miata <mrmazda@earthlink.net> - 2017-11-14 01:50 +0100
Re: Debian 8 and Debian 9 Dual Boot Dan Norton <dnorton@mindspring.com> - 2017-11-14 03:40 +0100
Re: Debian 8 and Debian 9 Dual Boot Felix Miata <mrmazda@earthlink.net> - 2017-11-14 04:00 +0100
Re: Debian 8 and Debian 9 Dual Boot Dan Norton <dnorton@mindspring.com> - 2017-11-14 04:50 +0100
Re: Debian 8 and Debian 9 Dual Boot Dan Norton <dnorton@mindspring.com> - 2017-11-16 19:40 +0100
Re: Debian 8 and Debian 9 Dual Boot Felix Miata <mrmazda@earthlink.net> - 2017-11-16 20:10 +0100
Re: Debian 8 and Debian 9 Dual Boot Dan Norton <dnorton@mindspring.com> - 2017-11-16 23:40 +0100
Re: Debian 8 and Debian 9 Dual Boot Joe <joe@jretrading.com> - 2017-11-16 20:30 +0100
Re: Debian 8 and Debian 9 Dual Boot Felix Miata <mrmazda@earthlink.net> - 2017-11-16 21:20 +0100
Re: Debian 8 and Debian 9 Dual Boot Dan Norton <dnorton@mindspring.com> - 2017-11-29 19:10 +0100
Re: Debian 8 and Debian 9 Dual Boot Joe <joe@jretrading.com> - 2017-11-29 19:20 +0100
Re: Debian 8 and Debian 9 Dual Boot Joe <joe@jretrading.com> - 2017-11-29 19:50 +0100
Re: Debian 8 and Debian 9 Dual Boot Felix Miata <mrmazda@earthlink.net> - 2017-11-29 19:40 +0100
Re: Debian 8 and Debian 9 Dual Boot Dan Norton <dnorton@mindspring.com> - 2017-11-29 21:40 +0100
Re: Debian 8 and Debian 9 Dual Boot Joe <joe@jretrading.com> - 2017-11-29 22:00 +0100
Re: Debian 8 and Debian 9 Dual Boot Dan Norton <dnorton@mindspring.com> - 2017-11-29 22:40 +0100
Re: Debian 8 and Debian 9 Dual Boot Dan Norton <dnorton@mindspring.com> - 2017-11-30 03:20 +0100
Re: Debian 8 and Debian 9 Dual Boot Dan Norton <dnorton@mindspring.com> - 2017-11-29 22:10 +0100
Re: Debian 8 and Debian 9 Dual Boot Joe <joe@jretrading.com> - 2017-11-29 23:10 +0100
Re: Debian 8 and Debian 9 Dual Boot Dan Norton <dnorton@mindspring.com> - 2017-11-17 00:00 +0100
Re: Debian 8 and Debian 9 Dual Boot Jonathan Dowland <jmtd@debian.org> - 2017-11-29 10:10 +0100
Re: Debian 8 and Debian 9 Dual Boot David Christensen <dpchrist@holgerdanske.com> - 2017-11-13 20:20 +0100
Re: Debian 8 and Debian 9 Dual Boot Dan Norton <dnorton@mindspring.com> - 2017-11-14 00:30 +0100
Re: Debian 8 and Debian 9 Dual Boot David Christensen <dpchrist@holgerdanske.com> - 2017-11-14 00:40 +0100
Re: Debian 8 and Debian 9 Dual Boot Jochen Spieker <ml@well-adjusted.de> - 2017-11-13 10:00 +0100
Re: Debian 8 and Debian 9 Dual Boot Dan Norton <dnorton@mindspring.com> - 2017-11-13 17:00 +0100
Re: Debian 8 and Debian 9 Dual Boot Jochen Spieker <ml@well-adjusted.de> - 2017-11-13 21:30 +0100
Re: Debian 8 and Debian 9 Dual Boot Roberto C. Sánchez <roberto@debian.org> - 2017-11-13 13:00 +0100
Re: Debian 8 and Debian 9 Dual Boot Roberto C. Sánchez <roberto@debian.org> - 2017-11-13 17:10 +0100
Re: Debian 8 and Debian 9 Dual Boot Dan Norton <dnorton@mindspring.com> - 2017-11-13 18:10 +0100
Re: Debian 8 and Debian 9 Dual Boot Dan Norton <dnorton@mindspring.com> - 2017-11-13 17:10 +0100
Re: Debian 8 and Debian 9 Dual Boot Joe <joe@jretrading.com> - 2017-11-13 20:00 +0100
Re: Debian 8 and Debian 9 Dual Boot Dan Norton <dnorton@mindspring.com> - 2017-11-29 04:20 +0100
Re: Debian 8 and Debian 9 Dual Boot Michael Fothergill <michael.fothergill@gmail.com> - 2017-11-29 08:10 +0100
Re: Debian 8 and Debian 9 Dual Boot Joe <joe@jretrading.com> - 2017-11-29 10:10 +0100
Re: Debian 8 and Debian 9 Dual Boot Dan Norton <dnorton@mindspring.com> - 2017-11-29 19:00 +0100
Re: Debian 8 and Debian 9 Dual Boot Felix Miata <mrmazda@earthlink.net> - 2017-11-29 20:00 +0100
Re: Debian 8 and Debian 9 Dual Boot Felix Miata <mrmazda@earthlink.net> - 2017-11-29 20:40 +0100
csiph-web