Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #161932 > unrolled thread
| Started by | David Baron <d_baron@012.net.il> |
|---|---|
| First post | 2015-12-20 12:10 +0100 |
| Last post | 2015-12-21 20:00 +0100 |
| Articles | 7 on this page of 47 — 12 participants |
Back to article view | Back to linux.debian.user
Attempt to Move Root David Baron <d_baron@012.net.il> - 2015-12-20 12:10 +0100
Re: Attempt to Move Root Stephen Powell <zlinuxman@wowway.com> - 2015-12-20 19:20 +0100
Re: Attempt to Move Root David Baron <d_baron@012.net.il> - 2015-12-20 22:00 +0100
Re: Attempt to Move Root Stephen Powell <zlinuxman@wowway.com> - 2015-12-20 22:40 +0100
Re: Attempt to Move Root David Christensen <dpchrist@holgerdanske.com> - 2015-12-21 10:00 +0100
Re: Attempt to Move Root David Baron <d_baron@012.net.il> - 2015-12-21 11:00 +0100
Re: Attempt to Move Root Stephen Powell <zlinuxman@wowway.com> - 2015-12-21 16:30 +0100
Re: Attempt to Move Root Lisi Reisz <lisi.reisz@gmail.com> - 2015-12-21 16:40 +0100
Re: Attempt to Move Root Stephen Powell <zlinuxman@wowway.com> - 2015-12-21 21:40 +0100
Re: Attempt to Move Root David Baron <d_baron@012.net.il> - 2015-12-21 16:40 +0100
Re: Attempt to Move Root Stephen Powell <zlinuxman@wowway.com> - 2015-12-21 21:00 +0100
Re: Attempt to Move Root David Baron <d_baron@012.net.il> - 2015-12-21 21:50 +0100
Re: Attempt to Move Root Stephen Powell <zlinuxman@wowway.com> - 2015-12-21 22:20 +0100
Re: Attempt to Move Root David Baron <d_baron@012.net.il> - 2015-12-22 08:50 +0100
Re: Attempt to Move Root Nicolas George <george@nsup.org> - 2015-12-22 17:00 +0100
Re: Attempt to Move Root John Hasler <jhasler@newsguy.com> - 2015-12-22 18:40 +0100
Re: Attempt to Move Root Nicolas George <george@nsup.org> - 2015-12-22 18:40 +0100
Re: Attempt to Move Root Nicolas George <george@nsup.org> - 2015-12-22 19:50 +0100
Re: Attempt to Move Root Sven Hartge <sven@svenhartge.de> - 2015-12-22 20:50 +0100
Re: Attempt to Move Root Brian <ad44@cityscape.co.uk> - 2015-12-22 21:20 +0100
Re: Attempt to Move Root Nicolas George <george@nsup.org> - 2015-12-22 23:10 +0100
Re: Attempt to Move Root Sven Hartge <sven@svenhartge.de> - 2015-12-22 23:30 +0100
Re: Attempt to Move Root Nicolas George <george@nsup.org> - 2015-12-23 10:40 +0100
Re: Attempt to Move Root Sven Hartge <sven@svenhartge.de> - 2015-12-24 02:20 +0100
Re: Attempt to Move Root Nicolas George <george@nsup.org> - 2015-12-24 12:20 +0100
Re: Attempt to Move Root Pascal Hambourg <pascal@plouf.fr.eu.org> - 2015-12-27 14:10 +0100
Re: Attempt to Move Root Nicolas George <george@nsup.org> - 2015-12-27 14:50 +0100
Re: Attempt to Move Root Pascal Hambourg <pascal@plouf.fr.eu.org> - 2015-12-27 15:20 +0100
Re: Attempt to Move Root Nicolas George <george@nsup.org> - 2015-12-27 15:40 +0100
Re: Attempt to Move Root Pascal Hambourg <pascal@plouf.fr.eu.org> - 2015-12-27 16:00 +0100
Re: Attempt to Move Root Nicolas George <george@nsup.org> - 2015-12-27 16:20 +0100
Re: Attempt to Move Root Nicolas George <george@nsup.org> - 2015-12-28 03:50 +0100
Re: Attempt to Move Root Pascal Hambourg <pascal@plouf.fr.eu.org> - 2015-12-28 03:50 +0100
Re: Attempt to Move Root Gene Heskett <gheskett@shentel.net> - 2015-12-27 16:10 +0100
Re: Attempt to Move Root Petter Adsen <petter@synth.no> - 2016-01-01 10:20 +0100
Re: Attempt to Move Root Pascal Hambourg <pascal@plouf.fr.eu.org> - 2016-01-01 11:40 +0100
Re: Attempt to Move Root Sven Hartge <sven@svenhartge.de> - 2015-12-28 03:50 +0100
Re: Attempt to Move Root Pascal Hambourg <pascal@plouf.fr.eu.org> - 2015-12-28 03:50 +0100
Re: Attempt to Move Root Brian <ad44@cityscape.co.uk> - 2015-12-22 23:40 +0100
Re: Attempt to Move Root Stephen Powell <zlinuxman@wowway.com> - 2015-12-25 17:10 +0100
Re: Attempt to Move Root John Hasler <jhasler@newsguy.com> - 2015-12-22 19:50 +0100
Re: Attempt to Move Root (SOLVED!!) David Baron <d_baron@012.net.il> - 2015-12-23 10:00 +0100
Re: Attempt to Move Root (SOLVED!!) Anders Andersson <pipatron@gmail.com> - 2015-12-23 12:50 +0100
Re: Attempt to Move Root (SOLVED!!) David Baron <d_baron@012.net.il> - 2015-12-23 13:20 +0100
Re: Attempt to Move Root Stephen Powell <zlinuxman@wowway.com> - 2015-12-25 16:40 +0100
Re: Attempt to Move Root Stephen Powell <zlinuxman@wowway.com> - 2015-12-28 05:00 +0100
Re: Attempt to Move Root David Christensen <dpchrist@holgerdanske.com> - 2015-12-21 20:00 +0100
Page 3 of 3 — ← Prev page 1 2 [3]
| From | John Hasler <jhasler@newsguy.com> |
|---|---|
| Date | 2015-12-22 19:50 +0100 |
| Message-ID | <qIAat-7yZ-7@gated-at.bofh.it> |
| In reply to | #161994 |
I wrote: > "Unused" is the problem with this design. The space is unused on by > accident. There is no standard (even an informal one) that reserves it. Nicolas George writes: > This is theoretical. In practice, it works pretty well, because people > (at least competent sysadmins and authors of installers) do not mess > randomly with their partition table. Think about multiboot home user systems. -- John Hasler jhasler@newsguy.com Elmwood, WI USA
[toc] | [prev] | [next] | [standalone]
| From | David Baron <d_baron@012.net.il> |
|---|---|
| Date | 2015-12-23 10:00 +0100 |
| Subject | Re: Attempt to Move Root (SOLVED!!) |
| Message-ID | <qINr4-7o4-15@gated-at.bofh.it> |
| In reply to | #161997 |
On reboot (to old system or otherwise), the UUID of the target partition was CHANGED! If the problem was not hidden behind a screenfull of lvm errors, I would/should have seen that right away, huh?
[toc] | [prev] | [next] | [standalone]
| From | Anders Andersson <pipatron@gmail.com> |
|---|---|
| Date | 2015-12-23 12:50 +0100 |
| Subject | Re: Attempt to Move Root (SOLVED!!) |
| Message-ID | <qIQ5A-Cl-15@gated-at.bofh.it> |
| In reply to | #162024 |
On Wed, Dec 23, 2015 at 9:52 AM, David Baron <d_baron@012.net.il> wrote: > On reboot (to old system or otherwise), the UUID of the target partition was > CHANGED! Unlikely, how do you know? What would change them during a reboot? > If the problem was not hidden behind a screenfull of lvm errors, I > would/should have seen that right away, huh? To my knowledge, lvm does not care about UUIDs. What were these errors?
[toc] | [prev] | [next] | [standalone]
| From | David Baron <d_baron@012.net.il> |
|---|---|
| Date | 2015-12-23 13:20 +0100 |
| Subject | Re: Attempt to Move Root (SOLVED!!) |
| Message-ID | <qIQyC-11R-15@gated-at.bofh.it> |
| In reply to | #162034 |
On Wednesday 23 December 2015 12:39:18 Anders Andersson wrote: > On Wed, Dec 23, 2015 at 9:52 AM, David Baron <d_baron@012.net.il> wrote: > > On reboot (to old system or otherwise), the UUID of the target partition > > was CHANGED! > > Unlikely, how do you know? What would change them during a reboot? When I resized the target partition, /dev/disk/by-uuid showed what I afterwards placed in fstab and lilo.conf. Today, a desperate try, placed the new fstab on the old root and rebooted. Root could not be mounted and the original mounted read-only (correct behavior in this case). I, of course, could not fix it this way. When I tried to remount it or mount the new root over it, got error that the uuid could not be found. listing the /dev/disk/by-uuid now showed a new uuid for the target partition. Mounted the new partition by /dev/sd..., placed the correct(ed) uuid in fstab and lilo.conf, went through the recommended procedure and voile. > > > If the problem was not hidden behind a screenfull of lvm errors, I > > would/should have seen that right away, huh? > > To my knowledge, lvm does not care about UUIDs. What were these errors? The lvm error on a functional boot up is once and spurious. This is a bug somewhere in the initramfs, I suppose. The repeated lvm error meant it could not find incorrectly uuid'd partition. I repeat, I am using no logical volumes. I did not notice the errant uuid as cited in the error messages. Might have indeed been but it did not catch my eye at the times.
[toc] | [prev] | [next] | [standalone]
| From | Stephen Powell <zlinuxman@wowway.com> |
|---|---|
| Date | 2015-12-25 16:40 +0100 |
| Message-ID | <qJCDf-5gd-5@gated-at.bofh.it> |
| In reply to | #161991 |
On Tue, 22 Dec 2015 10:57:41 -0500 (EST), Nicolas George wrote: > > What you write is slightly inaccurate. The core of your inaccuracy is this: > LILO does not use the BIOS to read FILES, but SECTORS. How to map files to > sectors is entirely LILO's problem. That depends on your point of view. To lilo's map installer (the lilo command that runs at a Linux shell prompt) they are files. The LILO boot loader itself reads an ordered list of sectors created for it by the map installer. But it is still a file. If what you mean is that the LILO boot loader, at boot time, cannot determine which sectors to read based on examining the file system structures, then yes, that is true. > > IIRC, the mapping is computed when (re)installing LILO on the boot-sector > and hard-coded in the boot-sector itself, with one level of indirection (the > map file). After a quick glance at the sources, it uses the FIBMAP ioctl and > various others to ask the kernel the blocks used by a file and converts to > sectors. At the same time, I noticed that LILO seems to be actually capable > of finding the sectors for files on LVM. In the general case, the sectors of a file on an LVM2 logical volume may reside on multiple physical partitions on multiple physical disks. But if all of those disks are addressable via the BIOS, and all of the sectors are accessible via the BIOS, then it may be theoretically possible for LILO to read the map file, the kernel image file, and the initial RAM file system image file from an LVM2 logical volume at boot time. I guess I was making an implicit assumption that they would all have to be on the same physical device. But maybe that's not true. I'll have to look into that. > > I have not read this thread carefully, so maybe it has already been > addressed, but all this suggest that the OP should install GRUB instead of > LILO and be done with that kind of trouble. As subsequent posts have indicated, the trouble was with an incorrect UUID. It had nothing to do with the OP's choice of boot loader. -- .''`. Stephen Powell <zlinuxman@wowway.com> : :' : `. `'` `-
[toc] | [prev] | [next] | [standalone]
| From | Stephen Powell <zlinuxman@wowway.com> |
|---|---|
| Date | 2015-12-28 05:00 +0100 |
| Message-ID | <qKx8u-4RN-1@gated-at.bofh.it> |
| In reply to | #162107 |
On Fri, 25 Dec 2015 10:33:56 -0500 (EST), Stephen Powell wrote:
> On Tue, 22 Dec 2015 10:57:41 -0500 (EST), Nicolas George wrote:
>> ...
>> I noticed that LILO seems to be actually capable
>> of finding the sectors for files on LVM.
>
> In the general case, the sectors of a file on an LVM2 logical volume may
> reside on multiple physical partitions on multiple physical disks. But if
> all of those disks are addressable via the BIOS, and all of the sectors
> are accessible via the BIOS, then it may be theoretically possible for LILO
> to read the map file, the kernel image file, and the initial RAM file system
> image file from an LVM2 logical volume at boot time. I guess I was making
> an implicit assumption that they would all have to be on the same physical
> device. But maybe that's not true. I'll have to look into that.
Looking at the source package for lilo, in src/geometry.c, I find the following:
if (lbm.lv_dev != geo->base_dev)
die("LVM boot LV cannot be on multiple PVs\n");
Therefore, it appears from a cursory examination that an LVM2 logical volume
may be used for /boot if the logical volume maps to a single
physical volume. It is not clear to me from this cursory examination whether
this "physical volume" actually means a partition; or if it means a physical disk,
which may consist of multiple partitions. In any case, I would not recommend
putting /boot on an LVM2 logical volume. It's just one more layer of
complexity, and one more potential thing to go wrong.
--
.''`. Stephen Powell <zlinuxman@wowway.com>
: :' :
`. `'`
`-
[toc] | [prev] | [next] | [standalone]
| From | David Christensen <dpchrist@holgerdanske.com> |
|---|---|
| Date | 2015-12-21 20:00 +0100 |
| Message-ID | <qIdQB-1Js-7@gated-at.bofh.it> |
| In reply to | #161961 |
On 12/21/2015 01:50 AM, David Baron wrote: > On Monday 21 December 2015 00:50:43 David Christensen wrote: >> On 12/20/2015 03:36 AM, David Baron wrote: >>> my goal is to remove and older 80gig IDE disk from the system >> Debian version? > Sid >> >> What drive is root on? How is the drive partitioned? RAID? LVM? >> LUKS? Other? What is the file system type? How big? > Currently on partition of old IDE drive. Nothing else remaining on > this drive. Partition is 10gig >> >> Where do you want to move root? > To an available partition of similar size on the first SATA drive. >> >> What else is on the same drive as root? Boot? Swap? Do you want >> to move these? Where? > These are currently on first and second SATA drives, all set up and > working. On 12/21/2015 07:36 AM, David Baron wrote: > The boot is not a separate partition but is a directory on the root > so travels with it. Copy on both old and new directories. > So, what do I do next? You information regarding /boot is unclear. I will assume /boot and root are on the same file system in the same partition of the 80 GB IDE. I would: 1. Backup everything on the source and destination drives. 2. Move everything off the destination drive. 3. Run the factory diagnostics on the destination drive to verify it is good. 4. Wipe the destination drive. 5. dd the contents of the source drive from sector 0 through the last sector of the partition containing root to the destination drive. 6. Alternative to #5, or if #5 doesn't produce good results, do a fresh install on the destination drive and restore/ configure. David
[toc] | [prev] | [standalone]
Page 3 of 3 — ← Prev page 1 2 [3]
Back to top | Article view | linux.debian.user
csiph-web