Bug#707641: overriding root device on TS-419 non-working

2013-05-09 Thread Christoph Egger
Package: flash-kernel
Version: 3.3
Severity: serious

Hi!

  Overriding the RootFS device for the initramfs doesn't seem to
work. Might well also be a bug in initramfs-tools. Setting serious
because it prevents this system from booting, feel free to change.

[   17.714542] IP-Config: eth0 hardware address 00:08:9b:d1:4b:10 mtu 1500 DHCP 
RARP
[   17.714549] IP-Config: eth0 complete (dhcp from 10.70.255.1):
[   17.714552]  address: 10.42.0.6broadcast: 10.255.255.255   netmask: 
255.0.0.0   
[   17.714556]  gateway: 10.130.130.130   dns0 : 172.16.0.1   dns1   : 
0.0.0.0 
[   17.714559]  domain : asgard 
 
[   17.714563]  rootserver: 10.42.23.2 rootpath: 
[   17.714566]  filename  : F_TS-419P2+
[   17.728125] Begin: Assembling all MD arrays ... 
[   17.776829] md: md0 stopped.
[   17.786608] md: bindsdb1
[   17.786976] md: bindsdc1
[   17.787305] md: bindsdd1
[   17.787987] md: bindsda1
[   17.981071] raid6: int32x1122 MB/s
[   18.151049] raid6: int32x2192 MB/s
[   18.321192] raid6: int32x4200 MB/s
[   18.491240] raid6: int32x8254 MB/s
[   18.491265] raid6: using algorithm int32x8 (254 MB/s)
[   18.494632] async_tx: api initialized (async)
[   18.495755] xor: measuring software checksum speed
[   18.541021]arm4regs  :  1810.400 MB/sec
[   18.591022]8regs :  1086.000 MB/sec
[   18.641019]32regs:  1503.600 MB/sec
[   18.641042] xor: using function: arm4regs (1810.400 MB/sec)
[   18.667005] md: raid6 personality registered for level 6
[   18.667054] md: raid5 personality registered for level 5
[   18.667073] md: raid4 personality registered for level 4
[   18.667836] bio: create slab bio-1 at 1
[   18.667889] md/raid:md0: not clean -- starting background reconstruction
[   18.667926] md/raid:md0: device sda1 operational as raid disk 0
[   18.667950] md/raid:md0: device sdd1 operational as raid disk 3
[   18.667972] md/raid:md0: device sdc1 operational as raid disk 2
[   18.667992] md/raid:md0: device sdb1 operational as raid disk 1
[   18.668728] md/raid:md0: allocated 4218kB
[   18.668834] md/raid:md0: raid level 5 active with 4 out of 4 devices, 
algorithm 2
[   18.668983] md0: detected capacity change from 0 to 6000789159936
[   18.669072] mdadm: /dev/md/0 has been started with 4 drives.
[   18.685574]  md0: unknown partition table
[   18.869802] Success: assembled all arrays.
[   18.869948] done.
[   18.871347] + [ -e /conf/param.conf ]
[   18.871682] + . /conf/param.conf
[   18.871914] + ROOT=/dev/mapper/root-root
[   18.872071] + debug=y
[   18.872208] + rootdelay=2
[   18.872366] + /scripts/local-top/lvm2
[   18.882717] device-mapper: uevent: version 1.0.3
[   18.883977] device-mapper: ioctl: 4.22.0-ioctl (2011-10-19) initialised: 
dm-de...@redhat.com
[   18.922123]   Volume group root not found
[   18.922443]   Skipping volume group root
[   18.923555] Unable to find LVM volume root/root
[   18.924038] + [ -e /conf/param.conf ]
[   18.924365] + . /conf/param.conf
[   18.924596] + ROOT=/dev/mapper/root-root
[   18.924752] + debug=y
[   18.924889] + rootdelay=2
[   18.925046] + /scripts/local-top/cryptroot
[   18.959385] Unlocking the disk 
/dev/disk/by-uuid/b55ee1d9-d00e-42c4-946c-a4d85e169d3b (md0_crypt)
[   18.959467] Enter passphrase: [   26.957381]   Reading all physical volumes. 
 This may take a while...
[   26.971742]   Found volume group root using metadata type lvm2
[   27.038792]   1 logical volume(s) in volume group root now active
[   28.453053] /scripts/local-top/cryptroot: line 1: can't open /dev/ram: no 
such file
[   28.453760] cryptsetup: md0_crypt set up successfully
[   28.458560] + [ -e /conf/param.conf ]
[   28.458905] + . /conf/param.conf
[   28.459138] + ROOT=/dev/mapper/root-root
[   28.459293] + debug=y
[   28.459430] + rootdelay=2
[   28.459566] + ROOT=/dev/ram
[   28.459749] + [ n != y ]
[   28.460065] + log_end_msg
[   28.460194] + _log_msg done.\n
[   28.460374] + [ n = y ]
[   28.460684] + printf done.\n
[   28.460832] done.
[   28.460892] + wait_for_udev 10
[   28.461121] + command -v udevadm
[   28.461408] + udevadm settle --timeout=10
[   28.465738] + [ -n  ]
[   28.466096] + [ /ram = /dev/ram ]
[   28.466429] + [ ! -e /dev/ram ]
[   28.466765] + log_begin_msg Waiting for root file system
[   28.466958] + _log_msg Begin: Waiting for root file system ... 
[   28.467149] + [ n = y ]
[   28.467469] + printf Begin: Waiting for root file system ... 
[   28.467623] Begin: Waiting for root file system ... + slumber=2
[   28.467868] + slumber=20
[   28.468017] + [ ! -e /dev/ram ]
[   28.468337] + /bin/sleep 0.1
[   28.570103] + slumber=19
[   28.570297] + [ 19 -gt 0 ]
[   28.570654] + [ ! -e /dev/ram ]
[   28.570988] + /bin/sleep 0.1
[   28.672723] + slumber=18
[   28.672912] + [ 18 -gt 0 ]
[   28.673252] + [ ! -e /dev/ram ]
[   28.673579] + /bin/sleep 0.1
[   28.775280] + slumber=17
[   28.775468] + [ 17 -gt 0 ]
[   28.775805] + [ ! -e /dev/ram ]
[   28.776141] 

Processed: Re: Bug#707641: overriding root device on TS-419 non-working

2013-05-09 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 reassign 707641 initramfs-tools
Bug #707641 [flash-kernel] overriding root device on TS-419 non-working
Bug reassigned from package 'flash-kernel' to 'initramfs-tools'.
No longer marked as found in versions flash-kernel/3.3.
Ignoring request to alter fixed versions of bug #707641 to the same values 
previously set
 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
707641: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707641
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/handler.s.c.136813238023905.transcr...@bugs.debian.org



Bug#707641: overriding root device on TS-419 non-working

2013-05-09 Thread Christoph Egger
Martin Michlmayr t...@cyrius.com writes:
 reassign 707641 initramfs-tools
 thanks

 I don't see anything flash-kernel related here.  Is this right after
 an installation with d-i?

Actually it's cryptsetup's fault.

I'ts not pristine from the installer. Got dropbear / cryptroot to run
untill there and enabled netconsole via [0] basically. Never really
bootet into the installed system though (doesn't boot)

Christoph

[0] http://www.hellion.org.uk/blog/posts/debugging-initramfs-over-netconsole/
-- 
9FED 5C6C E206 B70A 5857  70CA 9655 22B9 D49A E731
Debian Developer | Lisp Hacker | CaCert Assurer


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/87obcj98kn@hepworth.siccegge.de