Debian Bug report logs - #699437
[Wheezy] dmraid (Promise Fastrak 100) boot issue

version graph

Package: dmraid; Maintainer for dmraid is Debian QA Group <packages@qa.debian.org>; Source for dmraid is src:dmraid.

Reported by: "Andreas Meile" <info@andreas-meile.ch>

Date: Thu, 31 Jan 2013 13:36:01 UTC

Severity: normal

Found in version dmraid/1.0.0.rc16-4.2

Reply or subscribe to this bug.

Toggle useless messages

View this report as an mbox folder, status mbox, maintainer mbox


Report forwarded to debian-bugs-dist@lists.debian.org, Giuseppe Iuculano <iuculano@debian.org>, unknown-package@qa.debian.org:
Bug#699437; Package dmraid / os setup general. (Thu, 31 Jan 2013 13:36:04 GMT) Full text and rfc822 format available.

Acknowledgement sent to "Andreas Meile" <info@andreas-meile.ch>:
New Bug report received and forwarded. Copy sent to Giuseppe Iuculano <iuculano@debian.org>, unknown-package@qa.debian.org. (Thu, 31 Jan 2013 13:36:04 GMT) Full text and rfc822 format available.

Message #5 received at submit@bugs.debian.org (full text, mbox):

From: "Andreas Meile" <info@andreas-meile.ch>
To: <submit@bugs.debian.org>
Subject: [Wheezy] dmraid (Promise Fastrak 100) boot issue
Date: Thu, 31 Jan 2013 14:31:47 +0100
[Message part 1 (text/plain, inline)]
Package: dmraid / OS setup general
Version: 1.0.0.rc16-4.2

root@smbserv:~# dpkg -l|grep dmraid
ii  dmraid                               1.0.0.rc16-4.2               i386
Device-Mapper Software RAID support tool
ii  libdmraid1.0.0.rc16                  1.0.0.rc16-4.2               i386
Device-Mapper Software RAID support tool - shared library
root@smbserv:~# _

Detailed description:

I set up a small server according to the hints shown at

http://wiki.debian.org/DebianInstaller/SataRaid

Hardware is a IBM NetFinity A40 tower PC (model 6840-QDG) with a Promise
Fastrak 100 RAID controller, two EIDE hard drives on it (configured as
RAID-1 mirror) and a SCSI tape drive.

Details about the setup itself: As shown at

http://beilagen.dreael.ch/Diverses/dmraid_Wheezy_Bugs/Fata_Morgana_Partitionen.jpg

I cannot use the partitions shown below "pdc_iicbbhfc (mirror)" (I even must
unselect the swap partition there), instead using the separate entries shown
at

http://beilagen.dreael.ch/Diverses/dmraid_Wheezy_Bugs/Partitionen_korrekt.jpg

works fine. Note: For Norton Ghost compatibility I prepartitioned and
formatted the hard drive first before starting the Debian setup. GRUB
installs successfully with the right special device (note: I use a separate
/boot parition with bootable flag so a standard MBR will work, i.e. "fdisk
/mbr" at MS-DOS 6.22 does not destroy GRUB) as shown at

http://beilagen.dreael.ch/Diverses/dmraid_Wheezy_Bugs/GRUB_Partition.jpg

The actual issue: Each second time, my Debian box fails to boot with the
message shown at

http://beilagen.dreael.ch/Diverses/dmraid_Wheezy_Bugs/Boot_Fehler_sporadisch.jpg
http://beilagen.dreael.ch/Diverses/dmraid_Wheezy_Bugs/dmesg.txt

When I do "exit" the BusyBox, I even get a kernel panic:

http://beilagen.dreael.ch/Diverses/dmraid_Wheezy_Bugs/Kernelpanic_bei_BusyBox_exit.jpg

Details about the Promise controller and RAID setup:

http://beilagen.dreael.ch/Diverses/dmraid_Wheezy_Bugs/BIOS_Meldung_Promise.jpg

Note: The PXE boot shown there is a known issue on the Intel Pro 100S NICs
and has nothing to do with the bug described before.

In case of a successful boot (no update-grub needed - just powering off and
on), "dmesg" shows like

http://beilagen.dreael.ch/Diverses/dmraid_Wheezy_Bugs/dmesg_Start_erfolgreich.txt

Used partitioning layout (run after successful boot):

root@smbserv:~# fdisk -l /dev/mapper/pdc_iicbbhfc

Disk /dev/mapper/pdc_iicbbhfc: 250.0 GB, 250000000000 bytes
255 heads, 63 sectors/track, 30394 cylinders, total 488281250 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
Disk identifier: 0x00000000

                  Device Boot      Start         End      Blocks   Id
System
/dev/mapper/pdc_iicbbhfc1              63      514079      257008+   6
FAT16
/dev/mapper/pdc_iicbbhfc2   *      514080     1333394      409657+  83
Linux
/dev/mapper/pdc_iicbbhfc3         1333395     4417874     1542240   83
Linux
/dev/mapper/pdc_iicbbhfc4         4417875   488279609   241930867+   f  W95
Ext'd (LBA)
/dev/mapper/pdc_iicbbhfc5         4417938    22860494     9221278+  83
Linux
/dev/mapper/pdc_iicbbhfc6        22860558   104791994    40965718+  83
Linux
/dev/mapper/pdc_iicbbhfc7       104792058   110944889     3076416   83
Linux
/dev/mapper/pdc_iicbbhfc8       110944953   114430994     1743021   82
Linux swap / Solaris
/dev/mapper/pdc_iicbbhfc9       114431058   134913869    10241406   83
Linux
/dev/mapper/pdc_iicbbhfc10      134913933   142094924     3590496   83
Linux
/dev/mapper/pdc_iicbbhfc11      142094988   488279609   173092311   83
Linux
root@smbserv:~# _

For more details (I hope to have collected all important details inside the
BusyBox state) see all additional files at

http://beilagen.dreael.ch/Diverses/dmraid_Wheezy_Bugs/

I hope these informations will help you improve the next Debian release. :-)

           Andreas
-- 
meile.biz IT solutions, Hauptstrasse 63, CH-8242 Hofen SH
PC/Netzwerk-Support, Web-Entwicklung und -Hosting, IT Security
Tel. +41 52 640 04 72 * Fax +41 52 640 04 73 * Mobile +41 79 334 05 67
Postfach 169, CH-8240 Thayngen * info@meile.biz * http://www.meile.biz 
[smime.p7s (application/x-pkcs7-signature, attachment)]

Bug reassigned from package 'dmraid / os setup general' to 'dmraid'. Request was from Gergely Nagy <algernon@balabit.hu> to control@bugs.debian.org. (Thu, 31 Jan 2013 15:36:04 GMT) Full text and rfc822 format available.

No longer marked as found in versions 1.0.0.rc16-4.2. Request was from Gergely Nagy <algernon@balabit.hu> to control@bugs.debian.org. (Thu, 31 Jan 2013 15:36:05 GMT) Full text and rfc822 format available.

Marked as found in versions dmraid/1.0.0.rc16-4.2. Request was from Gergely Nagy <algernon@balabit.hu> to control@bugs.debian.org. (Thu, 31 Jan 2013 15:36:05 GMT) Full text and rfc822 format available.

Information forwarded to debian-bugs-dist@lists.debian.org, Giuseppe Iuculano <iuculano@debian.org>:
Bug#699437; Package dmraid. (Thu, 14 Mar 2013 21:27:04 GMT) Full text and rfc822 format available.

Acknowledgement sent to "Andreas Meile" <info@andreas-meile.ch>:
Extra info received and forwarded to list. Copy sent to Giuseppe Iuculano <iuculano@debian.org>. (Thu, 14 Mar 2013 21:27:04 GMT) Full text and rfc822 format available.

Message #16 received at 699437@bugs.debian.org (full text, mbox):

From: "Andreas Meile" <info@andreas-meile.ch>
To: <699437@bugs.debian.org>
Subject: Addiditions: Same issue with Promise Fastrak TX2300
Date: Thu, 14 Mar 2013 21:58:02 +0100
[Message part 1 (text/plain, inline)]
Today, I tested a similar installation with a Promise Fastrak TX2300 
controller and two SATA hard drives as RAID-1. Result is exactly the same: 
Installation fully suceeds including GRUB but the system randomly produces 
the same

mount: mounting /dev/disk/by-uuid/xxxxx on /root failed: Device or resource 
busy

while booting as shown at

http://beilagen.dreael.ch/Diverses/dmraid_Wheezy_Bugs/Boot_Fehler_sporadisch.jpg

Details see

http://beilagen.dreael.ch/Diverses/dmraid_Wheezy_Bugs/dmesg_fastrak2300_erfolg.txt
http://beilagen.dreael.ch/Diverses/dmraid_Wheezy_Bugs/dmesg_fastrak2300_fehlgeschlagen.txt
http://beilagen.dreael.ch/Diverses/dmraid_Wheezy_Bugs/lsmod_fastrak2300_busybox.txt

Note: The hardware is the same IBM NetVista A40 model. Installation was done 
with "mini.iso" from a FTP mirror.

          Andreas
-- 
meile.biz IT solutions, Hauptstrasse 63, CH-8242 Hofen SH
PC/Netzwerk-Support, Web-Entwicklung und -Hosting, IT Security
Tel. +41 52 640 04 72 * Fax +41 52 640 04 73 * Mobile +41 79 334 05 67
Postfach 169, CH-8240 Thayngen * info@meile.biz * http://www.meile.biz 
[smime.p7s (application/x-pkcs7-signature, attachment)]

Information forwarded to debian-bugs-dist@lists.debian.org, Giuseppe Iuculano <iuculano@debian.org>:
Bug#699437; Package dmraid. (Sun, 07 Apr 2013 17:27:07 GMT) Full text and rfc822 format available.

Acknowledgement sent to "Andreas Meile" <info@andreas-meile.ch>:
Extra info received and forwarded to list. Copy sent to Giuseppe Iuculano <iuculano@debian.org>. (Sun, 07 Apr 2013 17:27:07 GMT) Full text and rfc822 format available.

Message #21 received at 699437@bugs.debian.org (full text, mbox):

From: "Andreas Meile" <info@andreas-meile.ch>
To: <699437@bugs.debian.org>
Subject: Addition: No successful boot when using 2 TB disks and/or ext4 file system
Date: Sun, 7 Apr 2013 19:24:22 +0200
[Message part 1 (text/plain, inline)]
After fixing bug #704635 I tested a new Debian Wheezy setup today. To 
exclude any partition layout specific issues, I allowed Debian to use the 
whole disk with the automatic partitioning layout including ext4.

Result: Setup (using mini.iso, FTP source=mirror.switch.ch) completely runs 
fine but startup of the installed system fails after OS selection in GRUB:

http://beilagen.dreael.ch/Diverses/dmraid_Wheezy_Bugs/Boot_failure_20130407.jpg

Difference to the earlier tests with the small disks: It always fails (I 
repeated booting several times).

More details:

http://beilagen.dreael.ch/Diverses/dmraid_Wheezy_Bugs/Kernel_panic_after_exit_20130407.jpg
http://beilagen.dreael.ch/Diverses/dmraid_Wheezy_Bugs/Promise_BIOS_details_20130407.jpg
http://beilagen.dreael.ch/Diverses/dmraid_Wheezy_Bugs/dmesg_20130407.txt
http://beilagen.dreael.ch/Diverses/dmraid_Wheezy_Bugs/proc_partitions_20130407.txt
http://beilagen.dreael.ch/Diverses/dmraid_Wheezy_Bugs/ls_dev_mapper_20130407.txt
http://beilagen.dreael.ch/Diverses/dmraid_Wheezy_Bugs/proc_bus_pci_devices_20130407.txt

Hardware is a IBM NetVista A40 (model 6840-QDG) equipped with a Promise 
Fastrak TX2300 PCI RAID controller and two Western Digital 2 TB Caviar Red 
NAS SATA hard drives configured as RAID-1.

I hope this hint better helps to reproduce this bug. Also worth to note: On 
the CD boot, using dmraid=yes always works fine, this bug occurs only when 
booting from hard drive.

           Andreas
-- 
meile.biz IT solutions, Hauptstrasse 63, CH-8242 Hofen SH
PC/Netzwerk-Support, Web-Entwicklung und -Hosting, IT Security
Tel. +41 52 640 04 72 * Fax +41 52 640 04 73 * Mobile +41 79 334 05 67
Postfach 169, CH-8240 Thayngen * info@meile.biz * http://www.meile.biz 
[smime.p7s (application/x-pkcs7-signature, attachment)]

Information forwarded to debian-bugs-dist@lists.debian.org, Giuseppe Iuculano <iuculano@debian.org>:
Bug#699437; Package dmraid. (Wed, 08 May 2013 14:03:11 GMT) Full text and rfc822 format available.

Acknowledgement sent to "Andreas Meile" <info@andreas-meile.ch>:
Extra info received and forwarded to list. Copy sent to Giuseppe Iuculano <iuculano@debian.org>. (Wed, 08 May 2013 14:03:11 GMT) Full text and rfc822 format available.

Message #26 received at 699437@bugs.debian.org (full text, mbox):

From: "Andreas Meile" <info@andreas-meile.ch>
To: <699437@bugs.debian.org>
Subject: Test with the first Wheezy stable release
Date: Wed, 8 May 2013 16:01:39 +0200
[Message part 1 (text/plain, inline)]
Severity: grave
Package: initrd(?)

In the meantime, I tested the first stable Wheezy release on the hardware as 
described in the previous messages of this bug, i.e. IBM NetVista A40 (model 
6840-QDG), Promise Fastrak TX2300 PCI and two Western Digital Caviar Red 2 
TB SATA drives configured as RAID-1 (mirror).

Result: Still the same problem. :-(
Because this bug affects Debian's basic setup (=getting a bootable and 
running system where one can do the first root login and applying further 
"apt-get install"/configuration), the severity level should be increased.

Because dmraid itself always works fine in the emergency system as well as 
in the installation environment, I strongly believe that the dmraid package 
itself is 100% ok but something in the initrd boot configuration creation 
process causes that bug (probably a missing "insmod dmraid", wrong special 
device file for root system or something similar).

It's also to note that dmraid on the same hardware works flawlessly withing 
Debian Squeeze (the old-stable release now) when applying the steps at [1].

To exclude any hardware specific issue from the IBM motherboard (the 
6840-QDG is an older model), I moved the Fastrak TX2300 controller and the 
two hard drives into another hardware equipped with an Asus P5B-VM 
motherboard and Intel Pentium Core Duo CPU (full x64 capable) and retested 
the basic setup using a Debian default partitioning layout.

Result: Installation also succeeds but booting the installed system fails. 
Details:

http://beilagen.dreael.ch/Diverses/dmraid_Wheezy_Bugs/Asus_P5B-VM_20130508/

Differences to the IBM NetVista hardware:
- the boot failure message is a little another one, see the .jpg in the link 
above
- "exit" in the BusyBox does not produce a kernel panic, it just calls the 
BusyBox again
- While installation, the question for placing GRUB into the MBR didn't 
appear, I directly had to complete the /dev/mapper/pdc_cacjhiccia there

I hope this helps fix the bug for the next 7.0.1 release so I don't need to 
use an oldstable Debian release on this kind of hardware. :-)

             Andreas

[1] http://wiki.debian.org/DebianInstaller/SataRaid
-- 
meile.biz IT solutions, Hauptstrasse 63, CH-8242 Hofen SH
PC/Netzwerk-Support, Web-Entwicklung und -Hosting, IT Security
Tel. +41 52 640 04 72 * Fax +41 52 640 04 73 * Mobile +41 79 334 05 67
Postfach 169, CH-8240 Thayngen * info@meile.biz * http://www.meile.biz 
[smime.p7s (application/x-pkcs7-signature, attachment)]

Information forwarded to debian-bugs-dist@lists.debian.org, Giuseppe Iuculano <iuculano@debian.org>:
Bug#699437; Package dmraid. (Tue, 28 May 2013 16:09:04 GMT) Full text and rfc822 format available.

Acknowledgement sent to Quentin Lefebvre <qlefebvre_pro@yahoo.com>:
Extra info received and forwarded to list. Copy sent to Giuseppe Iuculano <iuculano@debian.org>. (Tue, 28 May 2013 16:09:04 GMT) Full text and rfc822 format available.

Message #31 received at 699437@bugs.debian.org (full text, mbox):

From: Quentin Lefebvre <qlefebvre_pro@yahoo.com>
To: 699437@bugs.debian.org
Subject: Error in /usr/share/initramfs-tools/hooks/dmraid ?
Date: Tue, 28 May 2013 18:07:40 +0200
Hi,

I have the exact same problem with my Wheezy stable installation.

My computer has a Silicon Image SiI 3112 A SATA RAID controller, and 
also randomly fails to boot.

I found a first fix :

edit the /usr/share/initramfs-tools/hooks/dmraid file
and change the line :
	force_load dm-raid45
into :
	force_load dm-raid .

This allows to get rid of the message :
	modprobe: module dm-raid45 not found in modules.dep
on kernel 3.2.
But with the kernel 2.6,
	modprobe: module dm-raid not found in modules.dep
appears.
So maybe both lines are necessary :
	force_load dm-raid45
	force_load dm-raid
one for each kernel.

But then the bug reproduced with :
modprobe: module ehci-hcd not found in modules.dep.
modprobe: module uhci-hcd not found in modules.dep.
modprobe: module ohci-hcd not found in modules.dep.
modprobe: module usbhid not found in modules.dep.

So I also added in /usr/share/initramfs-tools/hooks/dmraid :
	force_load ehci-hcd
	force_load uhci-hcd
	force_load ohci-hcd
	force_load usbhid
(maybe /usr/share/initramfs-tools/hooks/dmraid is not the right place 
for that...)

Then the bug reproduced again, but with no modprobe error message.

Trying a rootdelay=5 option didn't change anything.

At last, I'd like to stress an important point, that is the bug only 
appears for kernel 3.2. Kernel 2.6 seems to load each time perfectly (at 
least I had no bug with it yet).

Some clues or feedback would be most appreciated.

Best regards,
Quentin Lefebvre



Information forwarded to debian-bugs-dist@lists.debian.org, Giuseppe Iuculano <iuculano@debian.org>:
Bug#699437; Package dmraid. (Tue, 28 May 2013 17:21:04 GMT) Full text and rfc822 format available.

Acknowledgement sent to Quentin Lefebvre <qlefebvre_perso@yahoo.com>:
Extra info received and forwarded to list. Copy sent to Giuseppe Iuculano <iuculano@debian.org>. (Tue, 28 May 2013 17:21:04 GMT) Full text and rfc822 format available.

Message #36 received at 699437@bugs.debian.org (full text, mbox):

From: Quentin Lefebvre <qlefebvre_perso@yahoo.com>
To: 699437@bugs.debian.org
Subject: Modifying GRUB config file
Date: Tue, 28 May 2013 19:17:08 +0200
Hi again,

I found something new.
If I modify my /boot/grub/grub.cfg file as follows :
	linux vmlinuz... root=/dev/mapper/sil_bia...cdf2 ...
instead of
	linux vmlinuz root=UUID=... ...

then the bug doesn't occur anymore.

Andreas, could you try this and confirm ?

It seems to me that with this syntax, initrd is waiting the 
/dev/mapper/... device to be ready and set up, while there is a problem 
with UUIDs.

Unfortunately, the grub-update command can not generate the appropriate 
grub.cfg file.

There's still a problem, either in dmraid or kernel-related packages, as 
UUIDs should work with dmraid (I mean work all the time, and not randomly).

Best regards,
Quentin



Information forwarded to debian-bugs-dist@lists.debian.org, Giuseppe Iuculano <iuculano@debian.org>:
Bug#699437; Package dmraid. (Tue, 28 May 2013 18:39:07 GMT) Full text and rfc822 format available.

Acknowledgement sent to Quentin Lefebvre <qlefebvre_pro@yahoo.com>:
Extra info received and forwarded to list. Copy sent to Giuseppe Iuculano <iuculano@debian.org>. (Tue, 28 May 2013 18:39:07 GMT) Full text and rfc822 format available.

Message #41 received at 699437@bugs.debian.org (full text, mbox):

From: Quentin Lefebvre <qlefebvre_pro@yahoo.com>
To: 699437@bugs.debian.org
Subject: /etc/default/grub involved
Date: Tue, 28 May 2013 20:34:30 +0200
You can try to uncomment the line

	GRUB_DISABLE_LINUX_UUID=true

in /etc/default/grub, and then run

	update-grub .

You should have linux lines with

	root=/dev/mapper/...

in your /boot/grub/grub.cfg file, which seems to solve the bug.

Best regards,
Quentin



Information forwarded to debian-bugs-dist@lists.debian.org, Giuseppe Iuculano <iuculano@debian.org>:
Bug#699437; Package dmraid. (Sat, 29 Jun 2013 14:06:04 GMT) Full text and rfc822 format available.

Acknowledgement sent to "Andreas Meile" <info@andreas-meile.ch>:
Extra info received and forwarded to list. Copy sent to Giuseppe Iuculano <iuculano@debian.org>. (Sat, 29 Jun 2013 14:06:04 GMT) Full text and rfc822 format available.

Message #46 received at 699437@bugs.debian.org (full text, mbox):

From: "Andreas Meile" <info@andreas-meile.ch>
To: <699437@bugs.debian.org>
Subject: Feedback Wheezy test setup with current mini.iso
Date: Sat, 29 Jun 2013 15:32:58 +0200
[Message part 1 (text/plain, inline)]
Hello Quentin

Thanks for your hints. Because there is a new "mini.iso" online in the meantime, I repeated a basic "out of the box" setup on my hardware (IBM NetVista A40 model 6840-QDG, Promise Fastrak TX2300, two Western Digital Caviar Red 2 TB NAS disks).

All partitions are deleted, MBR is zeroed completely, i.e. classic "starting from green grass" (bare metal) scenario.

- boot parameters on CD: removed the "vga=788" parameter, added "dmraid=true" according [1].
- partitioning: "Guided - Use complete disk", RAID volume detected correctly, option "Use separate /usr, /home, /var, ..." (gives a very large /home)
- packet selection as usual, i.e. "SSH server", unselection "Desktop environment" in my case
- question about GRUB's location answered with "Yes" into MBR
- "Continue" - finishing installation as usual and reboot
Everything worked flawlessly until this point

BTW small minor bug (offtopic): CD drive drawer stays locked -> sending "eject" command like the GParted CD does may helpful - I built a small MS-DOS start floppy tool containing a CD-ROM driver and a QBasic tool[2] for that to avoid unnecessary power off/on cycles as temporary workaround...

First boot from hard drive: GRUB menu appears correctly but boot fails with the message as shown ("Device or resource busy" and BusyBox prompt) in the past.

=> Ctrl+Alt+Del, booting from mini.iso CD, "Advanced options", "Rescue mode" <Tab> "dmraid=true" instead "vga=788"
- After successful loading: "/dev/dm-1" as root system, start a shell

*** First important bug: Wrong special device file names in /etc/fstab; there is a extra "p" which must be removed, i.e.

# ls -al /dev/mapper
drwxr-xr-x  2 root root      200 Jun 29 14:44 .
drwxr-xr-x 15 root root     3740 Jun 29 14:44 ..
crw------T  1 root root  10, 236 Jun 29 14:44 control
brw-rw----  1 root disk 254,   0 Jun 29 14:44 pdc_ehdiebaf
brw-rw----  1 root disk 254,   1 Jun 29 14:44 pdc_ehdiebaf1
brw-rw----  1 root disk 254,   2 Jun 29 14:44 pdc_ehdiebaf5
brw-rw----  1 root disk 254,   3 Jun 29 14:44 pdc_ehdiebaf6
brw-rw----  1 root disk 254,   4 Jun 29 14:44 pdc_ehdiebaf7
brw-rw----  1 root disk 254,   5 Jun 29 14:44 pdc_ehdiebaf8
brw-rw----  1 root disk 254,   6 Jun 29 14:44 pdc_ehdiebaf9

but

# cat /etc/fstab
...
<file system> <mount point>   <type>  <options>       <dump>  <pass>
/dev/mapper/pdc_ehdiebafp1 /               ext4    errors=remount-ro 0       1
/dev/mapper/pdc_ehdiebafp9 /home           ext4    defaults        0       2
/dev/mapper/pdc_ehdiebafp8 /tmp            ext4    defaults        0       2
/dev/mapper/pdc_ehdiebafp5 /usr            ext4    defaults        0       2
/dev/mapper/pdc_ehdiebafp6 /var            ext4    defaults        0       2
/dev/mapper/pdc_ehdiebafp7 none            swap    sw              0       0
/dev/sr0        /media/cdrom0   udf,iso9660 user,noauto     0       0
/dev/fd0        /media/floppy0  auto    rw,user,noauto  0       0

(look to the extra "p" at the end in all "pdc_ehdiebafpX" entries!) => must be changed into

# <file system> <mount point>   <type>  <options>       <dump>  <pass>
/dev/mapper/pdc_ehdiebaf1 /               ext4    errors=remount-ro 0       1
/dev/mapper/pdc_ehdiebaf9 /home           ext4    defaults        0       2
/dev/mapper/pdc_ehdiebaf8 /tmp            ext4    defaults        0       2
/dev/mapper/pdc_ehdiebaf5 /usr            ext4    defaults        0       2
/dev/mapper/pdc_ehdiebaf6 /var            ext4    defaults        0       2
/dev/mapper/pdc_ehdiebaf7 none            swap    sw              0       0
/dev/sr0        /media/cdrom0   udf,iso9660 user,noauto     0       0
/dev/fd0        /media/floppy0  auto    rw,user,noauto  0       0

=> 
bash
mount -o remount /
mount /dev/mapper/pdc_ehdiebaf9 /home
mount /dev/mapper/pdc_ehdiebaf8 /tmp
mount /dev/mapper/pdc_ehdiebaf5 /usr
mount /dev/mapper/pdc_ehdiebaf6 /var
pico /etc/fstab
(removing the extra "p"s)

Applying UUID disabling (Quentin's hint):

pico /etc/default/grub
=> enabling "GRUB_DISABLE_LINUX_UUID=true" by uncommenting
update-grub
grub-install /dev/mapper/pdc_ehdiebaf

(the second command is also important else you get a mess [and the boot failure issue still remains!] with some extra entries in the GRUB boot menu)

=> "exit" twice from rescue mode and reboot - removing CD with the trick (start floppy tool) above - et voilĂ  - it successfully boots. :-)

Done several root logins and "shutdown -r now" - it always boots successfully - i.e. the problem seems to be fixed. :-)

To the Debian maintainers: Changing the last installation step to allow selection GRUB UUID on/off (or automatically disabling UUID in case of dmraid=true before creating GRUB) seems to be a useful way to getting rid with this bug. Also don't forget to fix this extra "p" issue in /etc/fstab and sending an CD drawer unlock (or even eject) command to the CD/DVD drive at the tidy up end stage of installation.

    Andreas

[1] http://wiki.debian.org/DebianInstaller/SataRaid
[2] http://beilagen.dreael.ch/QB/CDSCHUBL.BAS
-- 
meile.biz IT solutions, Hauptstrasse 63, CH-8242 Hofen SH
PC/Netzwerk-Support, Web-Entwicklung und -Hosting, IT Security
Tel. +41 52 640 04 72 * Fax +41 52 640 04 73 * Mobile +41 79 334 05 67
Postfach 169, CH-8240 Thayngen * info@meile.biz * http://www.meile.biz
[smime.p7s (application/x-pkcs7-signature, attachment)]

Send a report that this bug log contains spam.


Debian bug tracking system administrator <owner@bugs.debian.org>. Last modified: Wed Apr 16 23:58:33 2014; Machine Name: beach.debian.org

Debian Bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.