Error attempting to install grml-live

Hi All,
  I am using ;
  deb     http://ftp.us.debian.org/debian       
unstable        main contrib no
n-free
  deb-src http://ftp.us.debian.org/debian/      
unstable        main contrib no
n-free

in /etc/apt/sources.list as I am in Seattle.

  I get the following error when I try to install
grml-live;

Selecting previously deselected package
squashfs-tools.
(Reading database ... 126198 files and directories
currently installed.)
Unpacking squashfs-tools (from
.../squashfs-tools_1%3a3.2r2-8_i386.deb) ...
dpkg: error processing
/var/cache/apt/archives/squashfs-tools_1%3a3.2r2-8_i386.deb
(--unpack):
 trying to overwrite
`/usr/share/man/man1/mksquashfs.1.gz', which is also
in package squashfs
Selecting previously deselected package fai-client.
Unpacking fai-client (from
.../fai-client_3.2.1_all.deb) ...
Selecting previously deselected package fai-server.

Re: Error attempting to install grml-live

* Charles Hewson <cahewson2003 <at> yahoo.com> [20071001 21:08]:

[...]
> dpkg: error processing
> /var/cache/apt/archives/squashfs-tools_1%3a3.2r2-8_i386.deb
> (--unpack):
>  trying to overwrite
> `/usr/share/man/man1/mksquashfs.1.gz', which is also
> in package squashfs
[...]

The squashfs stuff is in package squashfs-tools now, so just get rid
of package squashfs:

dpkg --purge squashfs

regards,
-mika-
--

-- 
 http://grml.org/            # Linux for texttool-users and sysadmins
 http://wiki.grml.org/       # share your knowledge
 http://grml.supersized.org/ # the grml development weblog
 #grml  <at>  irc.freenode.org    # meet us on irc

* Charles Hewson <cahewson2003 <at> yahoo.com> [20071001 21:08]:

[...]
> dpkg: error processing
> /var/cache/apt/archives/squashfs-tools_1%3a3.2r2-8_i386.deb

[Grml 1.0] cannot boot anymore after upgrade

Hi all, 

I am quite new to GRML (and Debian/Knoppix based distributions). 
However, I have some experience with other Linux distris. 

So recently I got a virtual appliance with Grml installed already. 
One of the first things was to use apt-get (first attempt) and
aptitude (second attempt) to upgrade all upgradable packages. 
The results was the same: 
I could not boot anymore. The only thing that appears is 'GRUB'
without any further error message. 

I have spent two days already to figure out what happens. I have 
seen reports about similar errors when updating ubuntu versions. 
The reason was a switch from hdX to sdX (and a mismatch of the UUIDs). 

I checked all that: UUIDs are fine. And even with the device names the 
symptoms are the same. 

I then tried to reinstall GRUB. The installation process yielded no 
errors (the menu.lst and the device map are fine). Nevertheless
I get the same error 

Then I thought: Maybe it's only a GRUB problem and tried LILO. With 
lilo I get some more information, but also the boot process stops very 
early. I get error messages about some modules that cannot be loaded. 
(I currently have no access and, thus, cannot type the exact error message here.)

I am wondering whether this has something to do with the 
linux-kernel-header-grml package which apt-get/aptitude were keen to 

Re: [Grml 1.0] cannot boot anymore after upgrade

* Ja Bu <jb_int <at> care2.com> [20071003 01:53]:

> I am quite new to GRML (and Debian/Knoppix based distributions). 
> However, I have some experience with other Linux distris. 

> So recently I got a virtual appliance with Grml installed already. 
> One of the first things was to use apt-get (first attempt) and
> aptitude (second attempt) to upgrade all upgradable packages. 
> The results was the same: 
> I could not boot anymore. The only thing that appears is 'GRUB'
> without any further error message. 

> I have spent two days already to figure out what happens. I have 
> seen reports about similar errors when updating ubuntu versions. 
> The reason was a switch from hdX to sdX (and a mismatch of the UUIDs). 

> I checked all that: UUIDs are fine. And even with the device names the 
> symptoms are the same. 

> I then tried to reinstall GRUB. The installation process yielded no 
> errors (the menu.lst and the device map are fine). Nevertheless
> I get the same error 

Ok.

> Then I thought: Maybe it's only a GRUB problem and tried LILO. With 
> lilo I get some more information, but also the boot process stops very 
> early. I get error messages about some modules that cannot be loaded. 
> (I currently have no access and, thus, cannot type the exact error message here.)

Re: [Grml 1.0] cannot boot anymore after upgrade

* Michael Prokop <mika <at> grml.org> [20071003 07:46]:
> * Ja Bu <jb_int <at> care2.com> [20071003 01:53]:

[...]

> > I am also wondering: I surely am not the only one who ever upgraded 
> > a GRML 1.0 system, or? Did noone ever encountered a similar problem? 

> > I appreciate every hint which might bring me closer to a solution
> > of this most annoying problem. 

> Can you please provide the output of:

> dpkg --list mdadm lvm2 initramfs-tools lilo grub udev

> of the system? (Just boot grml live and chroot into your system)

> If you change the root=UUID=... line within grub/lilo to something
> like root=/dev/... (where the later device corresponds with your
> root partition) - does it boot then?

> JFYI: I'll try to reproduce the problem on my own here, so
> you definitely won't be lost with a not-bootable system.

Just verified it on my own: root=UUID=... still/again does not work
with initramfs-tools. So just use root=/dev/... on your grub cmdline
in the meanwhile to boot your system, I'm debugging the problem....
Stay tuned...

regards,

Re: [Grml 1.0] cannot boot anymore after upgrade

* Michael Prokop <mika <at> grml.org> [20071003 12:49]:
> * Michael Prokop <mika <at> grml.org> [20071003 07:46]:
> > * Ja Bu <jb_int <at> care2.com> [20071003 01:53]:

> > JFYI: I'll try to reproduce the problem on my own here, so
> > you definitely won't be lost with a not-bootable system.

> Just verified it on my own: root=UUID=... still/again does not work
> with initramfs-tools. So just use root=/dev/... on your grub cmdline
> in the meanwhile to boot your system, I'm debugging the problem....
> Stay tuned...

See http://bugs.debian.org/431291 for more information, as soon as
we found a persistent solution I'll provide it here as well.

regards,
-mika-
--

-- 
 http://grml.org/            # Linux for texttool-users and sysadmins
 http://wiki.grml.org/       # share your knowledge
 http://grml.supersized.org/ # the grml development weblog
 #grml  <at>  irc.freenode.org    # meet us on irc

* Michael Prokop <mika <at> grml.org> [20071003 12:49]:
> * Michael Prokop <mika <at> grml.org> [20071003 07:46]:
> > * Ja Bu <jb_int <at> care2.com> [20071003 01:53]:

> > JFYI: I'll try to reproduce the problem on my own here, so
> > you definitely won't be lost with a not-bootable system.

Re: Re: [Grml 1.0] cannot boot anymore after upgrade

Hi Mika,

first of all, thank you very much for the fast reply.
I guess you know how frustrating it can be to spend many hours
on a problem and finally ending up with no idea how to go on.
So I was very glad to find your reply in my inbox so soon 

> The last 1-2 lines of the output would be interesting.

Here are the error messages when booting with LILO:
----
[....]
No root-on-loop configured, skipping
Begin: Loading MD modules ...
Failure: failed to load module linear.
Failure: failed to load module multipath.
Failure: failed to load module raid0.
Failure: failed to load module raid1.
[....]
Success: loaded module raid456.
[...]
Failure: failed to load module raid10.
Done.
Warning: missing mdaadm.conf file, trying to create one...
Segmentation fault
Done.
Begin: Waiting for root file system... ...
----

> Can you please provide the output of:

Re: [Grml 1.0] cannot boot anymore after upgrade

* Ja Bu <jb_int <at> care2.com> [20071003 18:18]:

> > The last 1-2 lines of the output would be interesting.

> Here are the error messages when booting with LILO:
[...]
> Begin: Waiting for root file system... ...

Thanks, definitely helps debugging the problem.

> > Can you please provide the output of:
> > dpkg --list mdadm lvm2 initramfs-tools lilo grub udev
> > of the system? (Just boot grml live and chroot into your system)

> ----
> Desired=Unknown/Install/Remove/Purge/Hold
> | Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed
> |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)
> ||/ Name            Version        Description
> +++-===============-==============-============================================
> ii  grub            0.97-19        GRand Unified Bootloader
> ii  initramfs-tools 0.85c          tools for generating an initramfs
> ii  lilo            22.6.1-9       LInux LOader - The Classic OS loader can loa
> ii  lvm2            2.02.06-3      The Linux Logical Volume Manager
> ii  mdadm           2.5.6-6        tool to administer Linux MD arrays (software
> ii  udev            0.103-1grml2   /dev/ and hotplug management daemon

You are sure, that this is the output of the affected grml2hd
installation? This would be interesting. :)

Re: Re: [Grml 1.0] cannot boot anymore after upgrade

Hi Mika, 

> > ----
> > Desired=Unknown/Install/Remove/Purge/Hold
[...]
> > ii  udev            0.103-1grml2   /dev/ and hotplug management daemon
> 
> You are sure, that this is the output of the affected grml2hd
> installation? This would be interesting. :)

I did a chroot /mnt/sda1 (where I had previously mounted the
affected grml installation) and then entered the dpkg command that you
have sent. So I assume that should be the correct output, shouldn 
it? Is there room for mistakes? 

> > Here is lilo.conf (which I currently use):
[...]
> > => the hard disk is really sda (the only existing partition is sda1)
> 
> Ok, so just replace the:
> append="grml_from_hd root=UUID=ffb575cc-c8df-4063-e0f8cb6aff03  "
> with
> append="grml_from_hd root=/dev/sda1"

That worked! Thanks a lot!!

> You can edit the commandline of grub interactive (just press 'e',
> then edit the according line(s) and after pressing 'enter' to
> activate the changes, finally boot the entry using 'b') as well.

Re: [Grml 1.0] cannot boot anymore after upgrade

* Ja Bu <jb_int <at> care2.com> [20071003 20:19]:

> > You are sure, that this is the output of the affected grml2hd
> > installation? This would be interesting. :)

> I did a chroot /mnt/sda1 (where I had previously mounted the
> affected grml installation) and then entered the dpkg command that you
> have sent. So I assume that should be the correct output, shouldn 
> it? Is there room for mistakes? 

Yes, this should provide the correct output. Confuses me a little
bit now, as you are using an very old initramfs-tools version which
I don't think suffers from this problem.

> > > Here is lilo.conf (which I currently use):
> [...]
> > > => the hard disk is really sda (the only existing partition is sda1)

> > Ok, so just replace the:
> > append="grml_from_hd root=UUID=ffb575cc-c8df-4063-e0f8cb6aff03  "
> > with
> > append="grml_from_hd root=/dev/sda1"

> That worked! Thanks a lot!!

Great to hear that.

> > You can edit the commandline of grub interactive (just press 'e',
> > then edit the according line(s) and after pressing 'enter' to
> > activate the changes, finally boot the entry using 'b') as well.