Message below was sent to debian-arm describing a problem with
upgrading my QNAP TS-219P (armel) from lenny to squeeze.
For this platform it's a major problem as it has no console by default.
I was told that email@example.com and
firstname.lastname@example.org where better point for
answering my original questions. Can anyone answer me? THNX!
Below are the messages generated during upgrade.
W: mdadm: the array /dev/md/0 with UUID 1125740e:0f27573d:802988f7:5090deea
W: mdadm: is currently active, but it is not listed in mdadm.conf. if
W: mdadm: it is needed for boot, then YOUR SYSTEM IS NOW UNBOOTABLE!
W: mdadm: please inspect the output of /usr/share/mdadm/mkconf, compare
W: mdadm: it to /etc/mdadm/mdadm.conf, and make the necessary changes.
I ran /usr/share/mdadm/mkconf and updated the existing mdadm.conf to look like
# Please refer to mdadm.conf(5) for information about this file.
# by default, scan all partitions (/proc/partitions) for MD superblocks.
# alternatively, specify devices to scan, using wildcards if desired.
# auto-create devices with Debian standard permissions
CREATE owner=root group=disk mode=0660 auto=yes
# automatically tag new arrays as belonging to the local system
# instruct the monitoring daemon where to send mail alerts
# This file was auto-generated on Sun, 25 Jan 2009 18:17:30 +0100
# by mkconf $Id$
I'd like to
---------- Forwarded message ----------
From: Rob J. Epping <email@example.com>
Date: Sat, Jan 22, 2011 at 11:01 PM
Subject: QNAP TS-219P upgrade from lenny to squeeze
Today I decided to upgrade my TS-219P to squeeze. This went reasonably
well. I had a struggle with insserv, rsyslogd and initscripts, but
that is not arm related I guess.
An other problem I had was that my device would not boot anymore after
removal of linux-image-2.6.32-bpo.5-kirkwood.
During the upgrade I got a message from mdadm that UUID of the
raid-set changed. After upgrade and reboot I noticed
linux-image-2.6.32-bpo.5-kirkwood kernel was load instead of
linux-image-2.6.32-5-kirkwood. So I removed the BPO kernel and
rebooted once more.
That's when I needed to make a console cable.
I found that the wrong UUID was in the initrd and after some tweaking
I got everything back to work.
Does anyone on this list know why the UUID would change? And if this
is documented somewhere?
BTW: some more details about my setup:
* 2 identical hard drives. Both with 2 partitions. 1 raid and 1 swap.
* both raid partitions form a raid1
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact firstname.lastname@example.org
Archive: AANLkTi=vGVt4ioTPP_SAdoMgoNayDSOAymbjJcLBSbu9@mail .gmail.com">http://lists.debian.org/AANLkTi=vGVt4ioTPP_SAdoMgoNayDSOAymbjJcLBSbu9@mail .gmail.com