Your message dated Sat, 11 Oct 2014 13:56:26 +0200 with message-id <[email protected]> and subject line Re: [pkg-cryptsetup-devel] Bug#707641: Bug#707641: overriding root device on TS-419 non-working has caused the Debian Bug report #707641, regarding overriding root device on TS-419 non-working to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 707641: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707641 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---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.6 broadcast: 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: bind<sdb1> [ 17.786976] md: bind<sdc1> [ 17.787305] md: bind<sdd1> [ 17.787987] md: bind<sda1> [ 17.981071] raid6: int32x1 122 MB/s [ 18.151049] raid6: int32x2 192 MB/s [ 18.321192] raid6: int32x4 200 MB/s [ 18.491240] raid6: int32x8 254 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: [email protected] [ 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] + /bin/sleep 0.1 [ 28.877808] + slumber=16 [ 28.877998] + [ 16 -gt 0 ] [ 28.878335] + [ ! -e /dev/ram ] [ 28.878678] + /bin/sleep 0.1 [ 28.980349] + slumber=15 [ 28.980538] + [ 15 -gt 0 ] [ 28.980876] + [ ! -e /dev/ram ] [ 28.981239] + /bin/sleep 0.1 [ 29.082903] + slumber=14 [ 29.083090] + [ 14 -gt 0 ] [ 29.083430] + [ ! -e /dev/ram ] [ 29.083769] + /bin/sleep 0.1 [ 29.185442] + slumber=13 [ 29.185633] + [ 13 -gt 0 ] [ 29.185977] + [ ! -e /dev/ram ] [ 29.186315] + /bin/sleep 0.1 [ 29.287976] + slumber=12 [ 29.288162] + [ 12 -gt 0 ] [ 29.288497] + [ ! -e /dev/ram ] [ 29.288835] + /bin/sleep 0.1 [ 29.390511] + slumber=11 [ 29.390698] + [ 11 -gt 0 ] [ 29.391066] + [ ! -e /dev/ram ] [ 29.391399] + /bin/sleep 0.1 [ 29.493045] + slumber=10 [ 29.493238] + [ 10 -gt 0 ] [ 29.493575] + [ ! -e /dev/ram ] [ 29.493914] + /bin/sleep 0.1 [ 29.595577] + slumber=9 [ 29.595763] + [ 9 -gt 0 ] [ 29.596103] + [ ! -e /dev/ram ] [ 29.596441] + /bin/sleep 0.1 [ 29.698122] + slumber=8 [ 29.698314] + [ 8 -gt 0 ] [ 29.698651] + [ ! -e /dev/ram ] [ 29.698993] + /bin/sleep 0.1 [ 29.800691] + slumber=7 [ 29.800882] + [ 7 -gt 0 ] [ 29.801242] + [ ! -e /dev/ram ] [ 29.801583] + /bin/sleep 0.1 [ 29.903261] + slumber=6 [ 29.903451] + [ 6 -gt 0 ] [ 29.903790] + [ ! -e /dev/ram ] [ 29.904129] + /bin/sleep 0.1 [ 30.005795] + slumber=5 [ 30.005982] + [ 5 -gt 0 ] [ 30.006319] + [ ! -e /dev/ram ] [ 30.006661] + /bin/sleep 0.1 [ 30.108320] + slumber=4 [ 30.108509] + [ 4 -gt 0 ] [ 30.108848] + [ ! -e /dev/ram ] [ 30.109185] + /bin/sleep 0.1 [ 30.210854] + slumber=3 [ 30.211062] + [ 3 -gt 0 ] [ 30.211404] + [ ! -e /dev/ram ] [ 30.211728] + /bin/sleep 0.1 [ 30.313385] + slumber=2 [ 30.313571] + [ 2 -gt 0 ] [ 30.313908] + [ ! -e /dev/ram ] [ 30.314244] + /bin/sleep 0.1 [ 30.415913] + slumber=1 [ 30.416102] + [ 1 -gt 0 ] [ 30.416442] + [ ! -e /dev/ram ] [ 30.416784] + /bin/sleep 0.1 [ 30.518439] + slumber=0 [ 30.518629] + [ 0 -gt 0 ] [ 30.518956] + break [ 30.519107] + [ 0 -gt 0 ] [ 30.519434] + log_end_msg 1 [ 30.519612] + _log_msg done.\n [ 30.519795] + [ n = y ] [ 30.520108] + printf done.\n [ 30.520259] done. [ 30.520329] + [ ! -e /dev/ram ] [ 30.520671] + echo Gave up waiting for root device. Common problems: [ 30.520824] Gave up waiting for root device. Common problems: [ 30.520888] + echo - Boot args (cat /proc/cmdline) [ 30.521056] - Boot args (cat /proc/cmdline) [ 30.521129] + echo - Check rootdelay= (did the system wait long enough?) [ 30.521281] - Check rootdelay= (did the system wait long enough?) [ 30.521354] + echo - Check root= (did the system wait for the right device?) [ 30.521508] - Check root= (did the system wait for the right device?) [ 30.521574] + echo - Missing modules (cat /proc/modules; ls /dev) [ 30.521720] - Missing modules (cat /proc/modules; ls /dev) [ 30.521788] + panic ALERT! /dev/ram does not exist. Dropping to a shell! [ 30.522005] + command -v chvt [ 30.522243] + chvt 1 [ 30.524437] + echo ALERT! /dev/ram does not exist. Dropping to a shell! [ 30.524650] ALERT! /dev/ram does not exist. Dropping to a shell! [ 30.524736] + [ -n ] [ 30.525018] + modprobe -v i8042 [ 30.528594] modprobe: module i8042 not found in modules.dep [ 30.528875] + true [ 30.529058] + modprobe -v atkbd [ 30.531966] + modprobe -v ehci-hcd [ 30.535580] modprobe: module ehci-hcd not found in modules.dep [ 30.535854] + true [ 30.536031] + modprobe -v uhci-hcd [ 30.539640] modprobe: module uhci-hcd not found in modules.dep [ 30.539916] + true [ 30.540100] + modprobe -v ohci-hcd [ 30.543704] modprobe: module ohci-hcd not found in modules.dep [ 30.543977] + true [ 30.544157] + modprobe -v usbhid [ 30.547765] modprobe: module usbhid not found in modules.dep [ 30.548045] + true [ 30.548283] + REASON=ALERT! /dev/ram does not exist. Dropping to a shell! PS1=(initramfs) /bin/sh -i -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.4-trunk-amd64 (SMP w/6 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash
--- End Message ---
--- Begin Message ---Am 02.03.2014 um 00:31 schrieb Jonas Meurer: > Am 22.10.2013 16:41, schrieb Agustin Martin: >> On Thu, May 09, 2013 at 10:55:52PM +0200, Christoph Egger wrote: >>>> I don't see anything flash-kernel related here. Is this right >>>> after an installation with d-i? Actually it might be related to flash-kernel after all. I just fixed #759720 which was about flash-kernels failing to boot with encrypted rootfs due to unusual root-parameter handling. The original submitter suggested that this bugreport (#707641) might have the same cause. >> From what I looked QNAP TS-419 seems to be an ARM box (Note that >> your original bug report provides the architecture of the amd64 box >> used to file the bug report, not that of the QNAP box), > >>> [0] >>> http://www.hellion.org.uk/blog/posts/debugging-initramfs-over-netconsole/ > >>> >> with no console, so I do not think cryptsetup maintainer can have a >> look at this unless you provide extensive information, not only >> about messages shown during the boot process, but also about the >> details of the installaiton process. > > Augustin is perfectly right here. Can you please elaborate on the bug > and provide further explanation and details? I'l close this bugreport now as it might be the same one as #759720. Additionally, I'm neither able to reproduce it (due to missing access to similar hardware) nor to understand it (due to missing details). Kind regards, jonas
--- End Message ---
