Package: debian-boot
Version: jessie rc1
Severity: critical
Justification: breaks the whole system
Dear Maintainer,
* What led up to the situation?
/ was installed on first RAID1 pair of partitions,
2nd RAID1 pair not used at first,
/srv on 3rd RAID1 pair.
I had a problem during configuration, and attempted to re-boot.
A single-line message appeared
Recovering Journal.
Gave up waiting and installed a new / on to the second RAID1
pair with the first as /oldroot and the third as /srv.
Continued with configuration until forced to shut down.
On re-boot the same 0ne-line message appeared
Recovering Journal.
I waited again, but there was no other message or any mention
of mdadm, so eventually gave up and looked using a knoppix
disk to find around 10 bytes on each of the 6 partitions (3 pairs)
* What exactly did you do (or not do) that was effective (or
ineffective)?
I did not see any mention of mdadm starting, nor was there any
oportunity to escape (apart from crashing out again)
* What was the outcome of this action?
Two disks that had been fully tested before use now totally wiped.
All I can do is attempt data recovery using testdisk
* What outcome did you expect instead?
I expected the system to start mdadm and then boot as usual.
-- System Information:
Sent from another system!
Pentium 3 used as a moderate resource but reliable residential
mailserver/archiver to run 24/7
# -- System Information:
# Debian Release: 7.8
# APT prefers stable-updates
# APT policy: (500, 'stable-updates'), (500, 'stable')
# Architecture: amd64 (x86_64)
# Kernel: Linux 3.2.0-4-amd64 (SMP w/8 CPU cores)
# Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
# Shell: /bin/sh linked to /bin/dash
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
