Package: installation-reports
Severity: important
Usertags: pca.it-installation
Hi there!
Last Sunday (sorry for the delay, RL took most of my free time) I
upgraded the QNAP TS-409U to 4x2TB RAID-5 and LVM (no separate /boot
partition, given that the machine boots from flash) and thus proceeded
to a new installation. Unfortunately, after the installation finished
successfully, the machine did not reboot: the system light keeps
blinking red/green and network does not work.
Thx, bye,
Gismo / Luca
-- Package-specific info:
Boot method: network-console
Image version: 20110106+squeeze4+b1
Date: started on 2012-09-23T23:47:26+0000
Machine: QNAP TS-409U
Partitions: <df -Tl will do; the raw partition table is preferred>
root@debian:/# df -Tl
Filesystem Type 1K-blocks Used Available Use% Mounted on
/dev/mapper/jem-root
ext3 3842104 556568 3090364 16% /
/dev/mapper/jem-srv
ext3 3842104 556568 3090364 16% /srv
tmpfs tmpfs 257932 52 257880 1% /dev
tmpfs tmpfs 257932 52 257880 1% /dev
devpts devpts 257932 52 257880 1% /dev/pts
root@debian:/# sfdisk -d /dev/sda
WARNING: GPT (GUID Partition Table) detected on '/dev/sda'! The util sfdisk doesn't support GPT. Use GNU Parted.
# partition table of /dev/sda
unit: sectors
/dev/sda1 : start= 1, size=3907029167, Id=ee
/dev/sda2 : start= 0, size= 0, Id= 0
/dev/sda3 : start= 0, size= 0, Id= 0
/dev/sda4 : start= 0, size= 0, Id= 0
root@debian:/#
Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it
Initial boot: [O]
Detect network card: [O]
Configure network: [E]
Detect CD: [ ]
Load installer modules: [O]
Clock/timezone setup: [O]
User/password setup: [O]
Detect hard drives: [O]
Partition hard drives: [E]
Install base system: [O]
Install tasks: [O]
Install boot loader: [O]
Overall install: [E]
Comments/Problems:
1) the QNAP did not take its IP from the DHCP server (dnsmasq_2.55-2,
MAC address in /etc/ethers and IP in /etc/hosts, tested to work with
different machines). While at the first time I did not spend so much
time on this issue, thinking about a temporary problem on the
internal network (which has not yet completely migrated to the
dnsmasq-based infrastructure), it happened again later on. The DHCP
server seems to work OK, but the QNAP does not accept the DHCP offer:
--8<---------------cut here---------------start------------->8---
Sep 25 03:10:04 karon dnsmasq-dhcp[2575]: DHCPDISCOVER(eth1) 00:08:9b:ac:ff:8e
Sep 25 03:10:04 karon dnsmasq-dhcp[2575]: DHCPOFFER(eth1) 192.168.210.236 00:08:9b:ac:ff:8e
Sep 25 03:10:04 karon dnsmasq-dhcp[2575]: DHCPREQUEST(eth1) 192.168.210.236 00:08:9b:ac:ff:8e
Sep 25 03:10:04 karon dnsmasq-dhcp[2575]: DHCPACK(eth1) 192.168.210.236 00:08:9b:ac:ff:8e jem
Sep 25 03:10:07 karon dnsmasq-dhcp[2575]: DHCPDISCOVER(eth1) 00:08:9b:ac:ff:8e
Sep 25 03:10:07 karon dnsmasq-dhcp[2575]: DHCPOFFER(eth1) 192.168.210.236 00:08:9b:ac:ff:8e
Sep 25 03:10:07 karon dnsmasq-dhcp[2575]: DHCPREQUEST(eth1) 192.168.210.236 00:08:9b:ac:ff:8e
Sep 25 03:10:07 karon dnsmasq-dhcp[2575]: DHCPACK(eth1) 192.168.210.236 00:08:9b:ac:ff:8e jem
Sep 25 03:10:10 karon dnsmasq-dhcp[2575]: DHCPDISCOVER(eth1) 00:08:9b:ac:ff:8e
Sep 25 03:10:10 karon dnsmasq-dhcp[2575]: DHCPOFFER(eth1) 192.168.210.236 00:08:9b:ac:ff:8e
Sep 25 03:10:10 karon dnsmasq-dhcp[2575]: DHCPREQUEST(eth1) 192.168.210.236 00:08:9b:ac:ff:8e
Sep 25 03:10:10 karon dnsmasq-dhcp[2575]: DHCPACK(eth1) 192.168.210.236 00:08:9b:ac:ff:8e jem
Sep 25 03:10:14 karon dnsmasq-dhcp[2575]: DHCPDISCOVER(eth1) 00:08:9b:ac:ff:8e
Sep 25 03:10:14 karon dnsmasq-dhcp[2575]: DHCPOFFER(eth1) 192.168.210.236 00:08:9b:ac:ff:8e
Sep 25 03:10:14 karon dnsmasq-dhcp[2575]: DHCPREQUEST(eth1) 192.168.210.236 00:08:9b:ac:ff:8e
Sep 25 03:10:14 karon dnsmasq-dhcp[2575]: DHCPACK(eth1) 192.168.210.236 00:08:9b:ac:ff:8e jem
Sep 25 03:10:16 karon dnsmasq-dhcp[2575]: DHCPDISCOVER(eth1) 00:08:9b:ac:ff:8e
Sep 25 03:10:16 karon dnsmasq-dhcp[2575]: DHCPOFFER(eth1) 192.168.210.236 00:08:9b:ac:ff:8e
--8<---------------cut here---------------end--------------->8---
Luckily, the network-console falls back to a static IP address
(192.168.1.100), so I logged in via SSH and *manually* changed the
configuration via `ip`. After the installation, however, /e/n/i
contains the static values and not the manual one, which should be:
<http://bugs.debian.org/688650>
NB, I tried to use the "Configure the network" step, but this cut the
SSH connection, which is why I ended up using `ip`.
2) the partition problem is not really a problem, but an annoyance:
--8<---------------cut here---------------start------------->8---
Sep 24 00:15:18 kernel: [ 1442.413720] mdadm: sending ioctl 1261 to a partition!
Sep 24 00:15:18 kernel: [ 1442.413746] mdadm: sending ioctl 1261 to a partition!
Sep 24 00:15:18 kernel: [ 1442.414479] mdadm: sending ioctl 1261 to a partition!
Sep 24 00:15:18 kernel: [ 1442.414505] mdadm: sending ioctl 1261 to a partition!
Sep 24 00:15:18 kernel: [ 1442.414943] mdadm: sending ioctl 1261 to a partition!
Sep 24 00:15:18 kernel: [ 1442.414968] mdadm: sending ioctl 1261 to a partition!
Sep 24 00:15:18 kernel: [ 1442.418768] mdadm: sending ioctl 1261 to a partition!
Sep 24 00:15:18 kernel: [ 1442.418796] mdadm: sending ioctl 1261 to a partition!
Sep 24 00:15:18 kernel: [ 1442.427283] mdadm: sending ioctl 800c0910 to a partition!
Sep 24 00:15:18 kernel: [ 1442.427312] mdadm: sending ioctl 800c0910 to a partition!
--8<---------------cut here---------------end--------------->8---
This has already been fixed in linux/3.2.23-1, see:
<http://bugs.debian.org/656899>
3) at reboot the QNAP did not came back, with the system light keeping
blinking red/green and network does not work. Despite having a
serial console, the serial cable was not with me, thus I decided to
reflash d-i and check what was wrong.
a. According to the Debian wiki, there is no way to start rescue-mode
after having booted, which means that network-console does not
offer any rescue-mode:
<http://wiki.debian.org/DebianInstaller/FAQ#Q:_Can_I_use_d-i_as_a_rescue_system.3F_What_pitfalls_are_there.3F>
However, d-i's step "Download installer components" offers
"rescue-mode: mount requested partition and start a rescue shell":
is this actually usable within an install session? If so, how?
Otherwise I would say that adding a rescue-mode to network-console
would be welcomed.
b. At a first sight nothing was wrong: the RAID-5 was automatically
recognized during the "Partition disk" step, `vgscan` found the VG
and `vgchange -a y` activates the LVs. mdadm told me that the
RAID-5 was being rebuilt, which should mean that the machine in
some sort booted after the installation: the power button does not
send the correct software shutdown signal, instead it causes an
hard shutdown.
In-target's /etc/mdadm/mdadm.conf missed entries after "#
definitions of existing MD arrays", actually there was the "###
WARNING: scan failed." line. I thus manually added:
ARRAY /dev/md/0 metadata=1.2 UUID=a79d76f0:d98fecfb:5375bcd6:5fd506f0 name=jem:0
After having chrooted into /target, rebuilt the initramfs and
rebooted, however, the QNAP stayed quite as after the
installation.
c. I reflashed d-i for the second time and better investigated the
problem doing each step manually:
=====
~ # mdadm --assemble --scan
mdadm: /dev/md/0 has been started with 4 drives.
*** glibc detected *** mdadm: double free or corruption (!prev): 0x00079e00 ***
Aborted
~ # mdadm --detail /dev/md0
/dev/md0:
Version : 1.2
Creation Time : Mon Sep 24 00:41:04 2012
Raid Level : raid5
Array Size : 5860538880 (5589.05 GiB 6001.19 GB)
Used Dev Size : 1953512960 (1863.02 GiB 2000.40 GB)
Raid Devices : 4
Total Devices : 4
Persistence : Superblock is persistent
Update Time : Tue Sep 25 01:24:54 2012
State : clean, resyncing
Active Devices : 4
Working Devices : 4
Failed Devices : 0
Spare Devices : 0
Layout : left-symmetric
Chunk Size : 512K
Rebuild Status : 14% complete
Name : debian:0 (local to host debian)
UUID : a79d76f0:d98fecfb:5375bcd6:5fd506f0
Events : 15
Number Major Minor RaidDevice State
0 8 1 0 active sync /dev/sda1
1 8 17 1 active sync /dev/sdb1
2 8 33 2 active sync /dev/sdc1
3 8 49 3 active sync /dev/sdd1
~ # vgscan
Reading all physical volumes. This may take a while...
Found volume group "jem" using metadata type lvm2
~ # vgchange -a y
/proc/misc: No entry for device-mapper found
Is device-mapper driver missing from kernel?
Failure to communicate with kernel device-mapper driver.
0 logical volume(s) in volume group "jem" now active
[going back to the d-i's step "Download installer components" and chose
lvmcfg and mdcfg, nothing changed. Launched the d-i's step "Partition
disk" exiting after the first screen.]
~ # vgchange -a y
3 logical volume(s) in volume group "jem" now active
~ # mkdir /target
~ # mount /dev/mapper/jem-root /target/
~ # mount /dev /target/dev -o bind
~ # mount /sys /target/sys -o bind
~ # mount /proc /target/proc -o bind
~ # chroot /target /bin/bash
root@debian:/# mdadm --detail /dev/md0
/dev/md0:
Version : 1.2
Creation Time : Mon Sep 24 02:41:04 2012
Raid Level : raid5
Array Size : 5860538880 (5589.05 GiB 6001.19 GB)
Used Dev Size : 1953512960 (1863.02 GiB 2000.40 GB)
Raid Devices : 4
Total Devices : 4
Persistence : Superblock is persistent
Update Time : Tue Sep 25 03:25:03 2012
State : active, resyncing
Active Devices : 4
Working Devices : 4
Failed Devices : 0
Spare Devices : 0
Layout : left-symmetric
Chunk Size : 512K
Rebuild Status : 14% complete
Name : debian:0 (local to host debian)
UUID : a79d76f0:d98fecfb:5375bcd6:5fd506f0
Events : 17
Number Major Minor RaidDevice State
0 8 1 0 active sync /dev/sda1
1 8 17 1 active sync /dev/sdb1
2 8 33 2 active sync /dev/sdc1
3 8 49 3 active sync /dev/sdd1
root@debian:/# cat /etc/mdadm/mdadm.conf
# mdadm.conf
#
# 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.
DEVICE partitions
# 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
HOMEHOST <system>
# instruct the monitoring daemon where to send mail alerts
MAILADDR root
# definitions of existing MD arrays
### WARNING: scan failed.
ARRAY /dev/md/0 metadata=1.2 UUID=a79d76f0:d98fecfb:5375bcd6:5fd506f0 name=jem:0
# This file was auto-generated on Mon, 24 Sep 2012 05:20:31 +0200
# by mkconf 3.1.4-1+8efb9d1+squeeze1
root@debian:/# update-initramfs -k 2.6.32-5-orion5x -u
update-initramfs: Generating /boot/initrd.img-2.6.32-5-orion5x
Segmentation fault
^C
[I am sorry, I do not remember why I needed to press ^C.]
root@debian:/# update-initramfs -k 2.6.32-5-orion5x -u
update-initramfs: Generating /boot/initrd.img-2.6.32-5-orion5x
Generating kernel u-boot image... done.
Flashing kernel... done.
Flashing initramfs...
done.
root@debian:/# cat /etc/resolv.conf
search pca.it
nameserver 192.168.210.1
root@debian:/# cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
allow-hotplug eth0
iface eth0 inet static
address 192.168.210.236
netmask 255.255.255.0
network 192.168.210.0
broadcast 192.168.210.255
gateway 192.168.210.1
# dns-* options are implemented by the resolvconf package, if installed
dns-nameservers 192.168.210.1
dns-search pca.it
root@debian:/#
=====
Unfortunately, at reboot the QNAP was still unresponsive with the
same system light.
There are various bugs related to flash-kernel, which from the log
above I would say do not apply to my case:
<http://bugs.debian.org/550584>
<http://bugs.debian.org/640220>
<http://bugs.debian.org/656877>
I am know lost and IMHO the only way to know what is going on is
through the serial console, something I could probably do in the
second week of October (the machine is not with me).
--
Please make sure that the hardware-summary log file, and any other
installation logs that you think would be useful are attached to this
report. Please compress large files using gzip.
Once you have filled out this report, mail it to submit@bugs.debian.org.
==============================================
Installer lsb-release:
==============================================
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="6.0 (squeeze) - installer build 20110106+squeeze4+b1"
X_INSTALLATION_MEDIUM=network-console
==============================================
Installer hardware-summary:
==============================================
uname -a: Linux debian 2.6.32-5-orion5x #1 Sun May 6 21:27:49 UTC 2012 armv5tel GNU/Linux
lspci -knn: 00:00.0 Memory controller [0580]: Marvell Technology Group Ltd. 88f5281 [Orion-2] ARM SoC [11ab:5281] (rev 04)
lspci -knn: Subsystem: Marvell Technology Group Ltd. Device [11ab:11ab]
lspci -knn: 00:01.0 SCSI storage controller [0100]: Marvell Technology Group Ltd. 88SX7042 PCI-e 4-port SATA-II [11ab:7042] (rev 02)
lspci -knn: Subsystem: Marvell Technology Group Ltd. Device [11ab:11ab]
lspci -knn: Kernel driver in use: sata_mv
lspci -knn: 01:00.0 Memory controller [0580]: Marvell Technology Group Ltd. 88f5281 [Orion-2] ARM SoC [11ab:5281] (rev 04)
usb-list:
usb-list: Bus 01 Device 01: Marvell Orion EHCI [1d6b:0002]
usb-list: Level 00 Parent 00 Port 00 Class 09(hub ) Subclass 00 Protocol 01
usb-list: Manufacturer: Linux 2.6.32-5-orion5x ehci_hcd
usb-list: Interface 00: Class 09(hub ) Subclass 00 Protocol 00 Driver hub
usb-list:
usb-list: Bus 01 Device 02: USB2.0 Hub [05e3:0608]
usb-list: Level 01 Parent 01 Port 00 Class 09(hub ) Subclass 00 Protocol 01
usb-list: Interface 00: Class 09(hub ) Subclass 00 Protocol 00 Driver hub
lsmod: Module Size Used by
lsmod: raid456 50923 1
lsmod: async_raid6_recov 4240 1 raid456
lsmod: async_pq 3424 2 raid456,async_raid6_recov
lsmod: raid6_pq 75781 2 async_raid6_recov,async_pq
lsmod: async_xor 2563 3 raid456,async_raid6_recov,async_pq
lsmod: xor 4819 1 async_xor
lsmod: async_memcpy 956 2 raid456,async_raid6_recov
lsmod: async_tx 2008 5 raid456,async_raid6_recov,async_pq,async_xor,async_memcpy
lsmod: dm_mod 56891 9
lsmod: md_mod 80506 2 raid456
lsmod: jfs 157231 0
lsmod: ext4 288593 0
lsmod: jbd2 64351 1 ext4
lsmod: crc16 1113 1 ext4
lsmod: ext3 111204 2
lsmod: jbd 37738 1 ext3
lsmod: btrfs 539502 0
lsmod: zlib_deflate 19940 1 btrfs
lsmod: crc32c 2562 1
lsmod: libcrc32c 896 1 btrfs
lsmod: vfat 8152 0
lsmod: fat 43613 1 vfat
lsmod: usb_storage 34988 0
lsmod: ehci_hcd 34051 0
lsmod: usbcore 111811 3 usb_storage,ehci_hcd
lsmod: nls_base 5367 4 jfs,vfat,fat,usbcore
lsmod: ext2 55323 0
lsmod: mbcache 4860 3 ext4,ext3,ext2
lsmod: sd_mod 31232 8
lsmod: crc_t10dif 1106 1 sd_mod
lsmod: evdev 6582 0
lsmod: sata_mv 24398 4
lsmod: libata 135716 1 sata_mv
lsmod: mv643xx_eth 22542 0
lsmod: inet_lro 5060 1 mv643xx_eth
lsmod: gpio_keys 2655 0
lsmod: scsi_mod 124468 3 usb_storage,sd_mod,libata
df: Filesystem 1K-blocks Used Available Use% Mounted on
df: tmpfs 257932 52 257880 0% /dev
df: /dev/mapper/jem-root 3842104 514432 3132500 14% /target
df: /dev/mapper/jem-srv 5763773240 190540 5470799804 0% /target/srv
df: /dev/mapper/jem-root 3842104 514432 3132500 14% /dev/.static/dev
df: tmpfs 257932 52 257880 0% /target/dev
free: total used free shared buffers
free: Mem: 515868 375680 140188 0 3996
free: Swap: 974840 0 974840
free: Total: 1490708 375680 1115028
/proc/cmdline: console=ttyS0,115200n8 root=/dev/ram rw initrd=0x800000,0x3fffff
/proc/cpuinfo: Processor : Feroceon rev 0 (v5l)
/proc/cpuinfo: BogoMIPS : 498.07
/proc/cpuinfo: Features : swp half thumb fastmult vfp edsp
/proc/cpuinfo: CPU implementer : 0x41
/proc/cpuinfo: CPU architecture: 5TEJ
/proc/cpuinfo: CPU variant : 0x0
/proc/cpuinfo: CPU part : 0x926
/proc/cpuinfo: CPU revision : 0
/proc/cpuinfo:
/proc/cpuinfo: Hardware : QNAP TS-409
/proc/cpuinfo: Revision : 0000
/proc/cpuinfo: Serial : 0000000000000000
/proc/ioports: 00000000-000fffff : PCIe I/O Space
/proc/ioports: 00001000-000010ff : 0000:00:01.0
/proc/ioports: 00100000-001fffff : PCI I/O Space
/proc/iomem: 00000000-0fffffff : System RAM
/proc/iomem: 00028000-0034efff : Kernel text
/proc/iomem: 00364000-003f3a13 : Kernel data
/proc/iomem: 10000000-1fffffff : System RAM
/proc/iomem: e0000000-e7ffffff : PCIe Memory Space
/proc/iomem: e0000000-e00fffff : 0000:00:01.0
/proc/iomem: e0000000-e00fffff : sata_mv
/proc/iomem: e8000000-efffffff : PCI Memory Space
/proc/iomem: f1011000-f101101f : mv64xxx_i2c.0
/proc/iomem: f1011000-f101101f : mv64xxx_i2c adapter
/proc/iomem: f1012000-f10120ff : serial8250.0
/proc/iomem: f1012000-f101201f : serial
/proc/iomem: f1012100-f10121ff : serial8250.1
/proc/iomem: f1012100-f101211f : serial
/proc/iomem: f1050000-f1050fff : orion-ehci.0
/proc/iomem: f1050000-f1050fff : ehci_hcd
/proc/iomem: f1072000-f1073fff : mv643xx_eth.0
/proc/iomem: ff800000-ffffffff : physmap-flash.0
/proc/iomem: ff800000-ffffffff : physmap-flash.0
/proc/interrupts: CPU0
/proc/interrupts: 0: 3006585 orion_irq orion_tick
/proc/interrupts: 3: 267 orion_irq serial
/proc/interrupts: 5: 1476 orion_irq mv64xxx_i2c
/proc/interrupts: 11: 20140760 orion_irq sata_mv
/proc/interrupts: 17: 26 orion_irq ehci_hcd:usb1
/proc/interrupts: 21: 173575 orion_irq eth0
/proc/interrupts: 22: 48 orion_irq mv643xx_eth
/proc/interrupts: 46: 0 orion_gpio_irq Reset Button
/proc/interrupts: 47: 1 orion_gpio_irq USB Copy Button
/proc/interrupts: Err: 0
/proc/meminfo: MemTotal: 515868 kB
/proc/meminfo: MemFree: 140188 kB
/proc/meminfo: Buffers: 3996 kB
/proc/meminfo: Cached: 316244 kB
/proc/meminfo: SwapCached: 0 kB
/proc/meminfo: Active: 153744 kB
/proc/meminfo: Inactive: 159416 kB
/proc/meminfo: Active(anon): 932 kB
/proc/meminfo: Inactive(anon): 16732 kB
/proc/meminfo: Active(file): 152812 kB
/proc/meminfo: Inactive(file): 142684 kB
/proc/meminfo: Unevictable: 24692 kB
/proc/meminfo: Mlocked: 0 kB
/proc/meminfo: SwapTotal: 974840 kB
/proc/meminfo: SwapFree: 974840 kB
/proc/meminfo: Dirty: 3428 kB
/proc/meminfo: Writeback: 0 kB
/proc/meminfo: AnonPages: 17640 kB
/proc/meminfo: Mapped: 2960 kB
/proc/meminfo: Shmem: 52 kB
/proc/meminfo: Slab: 25932 kB
/proc/meminfo: SReclaimable: 22116 kB
/proc/meminfo: SUnreclaim: 3816 kB
/proc/meminfo: KernelStack: 520 kB
/proc/meminfo: PageTables: 368 kB
/proc/meminfo: NFS_Unstable: 0 kB
/proc/meminfo: Bounce: 0 kB
/proc/meminfo: WritebackTmp: 0 kB
/proc/meminfo: CommitLimit: 1232772 kB
/proc/meminfo: Committed_AS: 23412 kB
/proc/meminfo: VmallocTotal: 475136 kB
/proc/meminfo: VmallocUsed: 12084 kB
/proc/meminfo: VmallocChunk: 457400 kB
/proc/bus/input/devices: I: Bus=0019 Vendor=0001 Product=0001 Version=0100
/proc/bus/input/devices: N: Name="gpio-keys"
/proc/bus/input/devices: P: Phys=gpio-keys/input0
/proc/bus/input/devices: S: Sysfs=/devices/platform/gpio-keys/input/input0
/proc/bus/input/devices: U: Uniq=
/proc/bus/input/devices: H: Handlers=kbd event0
/proc/bus/input/devices: B: EV=3
/proc/bus/input/devices: B: KEY=1000000 0 0 0 0 0 0 0 20 0 0 0 0
/proc/bus/input/devices:
-- System Information:
Debian Release: 6.0.5
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: armel (armv5tel)
Kernel: Linux 2.6.32-5-orion5x
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Attachment:
pgpO7hR6mGZ6s.pgp
Description: PGP signature