Zyxel NSA325 problem with new kernel 4.11

on Zyxel NSA325, new kernel 4.11 doesn't recognize partitions properly and cannot mount root filesystem.

Works ok on 3.16

[   24.327055] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl F300)
[   24.387079] ata1.00: ATA-8: WDC WD3200BPVT-00ZEST0, 01.01A01, max UDMA/133
[   24.393983] ata1.00: 625142448 sectors, multi 0: LBA48 NCQ (depth 31/32)
[   24.457081] ata1.00: configured for UDMA/133
[   24.477341] scsi 1:0:0:0: Direct-Access     ATA      WDC WD3200BPVT-0 1A01 PQ: 0 ANSI: 5
[   24.717916] scsi 0:0:0:0: Direct-Access     Verbatim STORE N GO       1.00 PQ: 0 ANSI: 2
[   24.751085] sd 1:0:0:0: [sda] 625142448 512-byte logical blocks: (320 GB/298 GiB)
[   24.760140] sd 0:0:0:0: [sdb] 7831552 512-byte logical blocks: (4.00 GB/3.73 GiB)
[   24.768152] sd 1:0:0:0: [sda] 4096-byte physical blocks
[   24.773766] sd 1:0:0:0: [sda] Write Protect is off
[   24.778803] sd 1:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[   24.787978] sd 0:0:0:0: [sdb] Write Protect is off
[   24.794965] sd 0:0:0:0: [sdb] No Caching mode page found
[   24.800367] sd 0:0:0:0: [sdb] Assuming drive cache: write through
[   24.811825]  sdb: sdb1 sdb2
[   24.818115] sd 0:0:0:0: [sdb] Attached SCSI removable disk
[   24.835148]  sda: sda1 sda2 sda4
[   24.840508] sd 1:0:0:0: [sda] Attached SCSI disk

Doesn't show partitions on 4.11

[    4.663553] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl F300)
[    4.670392] ata1.00: ATA-8: WDC WD3200BPVT-00ZEST0, 01.01A01, max UDMA/133
[    4.670399] ata1.00: 625142448 sectors, multi 0: LBA48 NCQ (depth 31/32)
[    4.684753] NET: Registered protocol family 17
[    4.689287] ata1.00: configured for UDMA/133
[    4.693986] scsi 0:0:0:0: Direct-Access     ATA      WDC WD3200BPVT-0 1A01 PQ: 0 ANSI: 5
[    4.703071] Key type dns_resolver registered
[    4.708031] registered taskstats version 1
[    4.712195] Loading compiled-in X.509 certificates
[    4.717052] zswap: loaded using pool lzo/zbud
[    4.723259] Key type big_key registered
[    4.728436] Key type encrypted registered
[    4.735224] rtc-pcf8563 0-0051: setting system clock to 2017-07-12 23:17:26 UTC (1499901446)
[    4.744534] Waiting 4 sec before mounting root device...
[    4.859606] usb 1-1: new high-speed USB device number 2 using orion-ehci
[    5.051187] usb 1-1: New USB device found, idVendor=05e3, idProduct=0608
[    5.057929] usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[    5.065122] usb 1-1: Product: USB2.0 Hub
[    5.069852] hub 1-1:1.0: USB hub found
[    5.073941] hub 1-1:1.0: 4 ports detected
[    5.199613] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl F300)
[    5.208330] ata2.00: ATA-9: WDC WD20EFRX-68EUZN0, 80.00A80, max UDMA/133
[    5.215083] ata2.00: 3907029168 sectors, multi 0: LBA48 NCQ (depth 31/32)
[    5.224418] ata2.00: configured for UDMA/133
[    5.239166] scsi 1:0:0:0: Direct-Access     ATA      WDC WD20EFRX-68E 0A80 PQ: 0 ANSI: 5
[    5.399602] usb 1-1.2: new high-speed USB device number 3 using orion-ehci
[    5.550561] usb 1-1.2: New USB device found, idVendor=18a5, idProduct=0302
[    5.557471] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    5.564839] usb 1-1.2: Product: STORE N GO
[    5.570713] usb 1-1.2: Manufacturer: Verbatim
[    5.577010] usb 1-1.2: SerialNumber: 1226000000006EFD
[    5.679600] usb 1-1.3: new high-speed USB device number 4 using orion-ehci
[    5.831310] usb 1-1.3: New USB device found, idVendor=04a9, idProduct=1909
[    5.838220] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    5.845586] usb 1-1.3: Product: CanoScan
[    5.849521] usb 1-1.3: Manufacturer: Canon
[    8.809735] VFS: Cannot open root device "sda2" or unknown-block(0,0): error -6

doing this mainly, because my Canon Lide 110 scanner stopped to work. xhci_hcd resets usb when I try to scan.
This used to work fine before updating jessie to stretch, so there was some bug introduced and cannot find it...



Edited 2 time(s). Last edit at 07/13/2017 03:31AM by bodhi.

I went through the logs again, and there appears to be something wrong with initrd

[ 0.203889] Initramfs unpacking failed: junk in compressed archive

mkinitrd command however worked fine...

#mkimage -A arm -O linux -T ramdisk -C gzip -a 0x00000000 -e 0x00000000 -n initramfs-4.11.3-kirkwood-tld-2 -d zImage-4.11.3-kirkwood-tld-2 uInitrd_4.11
Image Name: initramfs-4.11.3-kirkwood-tld-2
Created: Thu Jul 13 10:11:41 2017
Image Type: ARM Linux RAMDisk Image (gzip compressed)
Data Size: 3901568 Bytes = 3810.12 kB = 3.72 MB
Load Address: 00000000
Entry Point: 00000000



Edited 1 time(s). Last edit at 07/13/2017 03:26AM by bodhi.

Please, next time post in new thread for problem booting.

I'll take a look at the log to see if I can spot anything.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

rasto,

> Image Name: initramfs-4.11.3-kirkwood-tld-2
> Created: Thu Jul 13 10:11:41 2017
> Image Type: ARM Linux RAMDisk Image (gzip compre
> ssed)
> Data Size: 3901568 Bytes = 3810.12 kB = 3.72 MB
> Load Address: 00000000
> Entry Point: 00000000

1. This iniramfs seems a little bit too small, only 3.72MB.

2, Which u-boot are you running? it's not my latest release u-boot. Your u-boot envs are not set up to boot with the rootfs label. But that is not the problem, if you got this "junk" message in dmesg then try to regenerate it again.

Initramfs unpacking failed: junk incompressed archive

3. please post the entire serial console log (from the u-boot banner).

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 1 time(s). Last edit at 07/13/2017 04:10AM by bodhi.

I see. Here is the problem:

#mkimage -A arm -O linux -T ramdisk -C gzip -a 0x00000000 -e 0x00000000 -n initramfs-4.11.3-kirkwood-tld-2 -d zImage-4.11.3-kirkwood-tld-2 uInitrd_4.11

That should be initrd.img-4.11.3-kirkwood-tld-2.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Hello,

what about dependency of kernel to libssl-1.0.0 on Stretch?

dpkg -i linux-headers-4.11.3-kirkwood-tld-2_2.0_armel.deb

Unpacking linux-headers-4.11.3-kirkwood-tld-2 (2.0) ...
dpkg: dependency problems prevent configuration of linux-headers-4.11.3-kirkwood-tld-2:
linux-headers-4.11.3-kirkwood-tld-2 depends on libssl1.0.0 (>= 1.0.0); however:
Package libssl1.0.0:armel is not installed.

I had to config jessie source and install this 1 package to get linux-image and linux-headers installed.

Stretch uses libssl1.0.2 package not libssl1.0.0



Edited 1 time(s). Last edit at 07/14/2017 06:38AM by rasto.

rasto,

If you have libssl 1.0.0 before upgrading to stretch, then it would still be there. Which rootfs are you running?

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Hello,

thanks for reply, I've installed debian using netboot quite long ago.
Currently I've updated to debian stretch and things (usb, cups) are not running well.

#cat /etc/debian_version
9.0

Box is sharing data through samba, scanning documents using scanbd, using openvpn to connect outside, syncing data using unison, printing using cups (thus able to copy papers if needed),avahi printer and running logitechmediaserver

I wonder, what would be the easiest way to transfer packages and configuration to blank rootfs...



Edited 1 time(s). Last edit at 07/18/2017 12:49PM by rasto.

scanimage works fine with Canon Lide 110 scanner using debian 4.4.0 rootfs with its kernel.
I'll try harder route, to update Your rootfs with my current packages configuration.

rasto,

> I'll try harder route, to update Your rootfs with
> my current packages configuration.

If you can hold on for a day. For an easier way, let me write a new general post regarding upgrading to stretch today.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

rasto,

Hope that this is useful for you:

http://forum.doozan.com/read.php?2,35581

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

wow, You're fast.
Thanks for all Your help, will read and proceed with upgrade to stretch as You wrote.

Will do env update to Your latest "smart" one while I'm at it. I was doing lot's of changes to env parameters when booting temporarily from usb and switching systemd (to see whether USB still works).

Thanks