4.4.97-1-ARCH wrong NAND chip timing in the DTS? NSA310 NAS

Problems with packages? Post here, using [tags] of the package name.

Re: 4.4.97-1-ARCH wrong NAND chip timing in the DTS? NSA310

Postby summers » Thu May 10, 2018 6:35 pm

you should have been ok with
$this->bbcode_second_pass_code('', 'mkfs.ext4 -O ^metadata_csum,^64bit /dev/sda2')
That just takes out the problem bits ....
I think
$this->bbcode_second_pass_code('', 'tune2fs -O ^metadata_csum,^64bit /dev/sda2')
would also work - but have never done it ...
summers
 
Posts: 995
Joined: Sat Sep 06, 2014 12:56 pm

Re: 4.4.97-1-ARCH wrong NAND chip timing in the DTS? NSA310

Postby arti74 » Thu May 10, 2018 6:41 pm

$this->bbcode_second_pass_quote('', 't')akes out the problem bits

As far as I know I haven't given any bits to the filesystems I created - in the previous post I copied the commands I used then..

EDIT: Or... I gave wrong partuuid for the root or something (uEnv file) - If I change this just for /dev/sda2, shouldn't it be enough?
EDIT2: I'll maybe see yet what Bodhi thinks about it.
arti74
 
Posts: 75
Joined: Tue Apr 17, 2018 10:33 am

Re: 4.4.97-1-ARCH wrong NAND chip timing in the DTS? NSA310

Postby summers » Thu May 10, 2018 8:07 pm

well the error was about the wrong options set on ext4, not about the root partition. You number ended in in 02 which corresponds to the second partition - so probably right.

Yes should work with the device, but PARTUUID is more reliable, helps if other hardware plugged in, as device names can change, but not PARTUUID.

Yes the instructions on NSA device don't mention the ext4 options. Other install guides though do say that. Don't know if is cured on more modern uboot, but nsa still on the 2016 version ...
summers
 
Posts: 995
Joined: Sat Sep 06, 2014 12:56 pm

Re: 4.4.97-1-ARCH wrong NAND chip timing in the DTS? NSA310

Postby arti74 » Thu May 10, 2018 8:22 pm

For now we should be happy that the u-boot went well - thanks!! Now I completely don't know about the extra ext4 options, not sure even what to put on the google search. If no respond from Bodhi soon, I'll try this tune2fs command you've mentioned - this is to add a feature or to remove it? Well, if something new comes up, I'll let you know.
arti74
 
Posts: 75
Joined: Tue Apr 17, 2018 10:33 am

Re: 4.4.97-1-ARCH wrong NAND chip timing in the DTS? NSA310

Postby arti74 » Thu May 10, 2018 9:05 pm

I'm not sure if it brings anything, but after those two commands I get:
$this->bbcode_second_pass_code('', 'NSA310> setenv bootdir
NSA310> run startboot
starting USB...
USB0: USB EHCI 1.00
scanning bus 0 for devices... 2 USB Device(s) found
scanning usb for storage devices... 0 Storage Device(s) found

Reset IDE: Bus 0: OK Bus 1: not available
Device 0: Model: SAMSUNG HD753LJ Firm: 1AA01110 Ser#: S13UJ1DQ400383
Type: Hard Disk
Supports 48-bit addressing
Capacity: 715404.8 MB = 698.6 GB (1465149168 x 512)

USB device 0: unknown device

Device 0: Model: SAMSUNG HD753LJ Firm: 1AA01110 Ser#: S13UJ1DQ400383
Type: Hard Disk
Supports 48-bit addressing
Capacity: 715404.8 MB = 698.6 GB (1465149168 x 512)
... is now current device
ide found on device 0
Checking for: /uEnv.txt ...
** File not found /zImage **
5155808 bytes read in 1868 ms (2.6 MiB/s)
loading /boot/dtbs/kirkwood-nsa310.dtb ...
** File not found /boot/dtbs/kirkwood-nsa310.dtb **
5530551 bytes read in 1972 ms (2.7 MiB/s)
Booting uImage with initrd
## Booting kernel from Legacy Image at 00810000 ...
Image Name: Linux 4.16.7-1 with nsa310 dt
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 5155744 Bytes = 4.9 MiB
Load Address: 00810000
Entry Point: 00810000
Verifying Checksum ... OK
Loading Kernel Image ... OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
[ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] Linux version 4.16.7-1-ARCH (builduser@leming) (gcc version 7.3.1 20180406 (GCC)) #1 PREEMPT Thu May 3 00:35:40 UTC 2018
[ 0.000000] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=0005397f
[ 0.000000] CPU: VIVT data cache, VIVT instruction cache
[ 0.000000] OF: fdt: Machine model: ZyXEL NSA310
[ 0.000000] Memory policy: Data cache writeback
[ 0.000000] random: get_random_bytes called from start_kernel+0x80/0x424 with crng_init=0
[ 0.000000] Built 1 zonelists, mobility grouping on. Total pages: 64960
[ 0.000000] Kernel command line: console=ttyS0,115200 mtdparts=orion_nand:1M(u-boot),-(rootfs) root=PARTUUID=ab197877-01 rw rootwait
[ 0.000000] Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
[ 0.000000] Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
[ 0.000000] Memory: 243040K/262144K available (7543K kernel code, 599K rwdata, 1692K rodata, 356K init, 681K bss, 19104K reserved, 0K cma-reserved)
[ 0.000000] Virtual kernel memory layout:
[ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB)
[ 0.000000] fixmap : 0xffc00000 - 0xfff00000 (3072 kB)
[ 0.000000] vmalloc : 0xd0800000 - 0xff800000 ( 752 MB)
[ 0.000000] lowmem : 0xc0000000 - 0xd0000000 ( 256 MB)
[ 0.000000] modules : 0xbf000000 - 0xc0000000 ( 16 MB)
[ 0.000000] .text : 0x(ptrval) - 0x(ptrval) (7544 kB)
[ 0.000000] .init : 0x(ptrval) - 0x(ptrval) ( 356 kB)
[ 0.000000] .data : 0x(ptrval) - 0x(ptrval) ( 600 kB)
[ 0.000000] .bss : 0x(ptrval) - 0x(ptrval) ( 682 kB)
[ 0.000000] SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[ 0.000000] Preemptible hierarchical RCU implementation.
[ 0.000000] Tasks RCU enabled.
[ 0.000000] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16
[ 0.000000] clocksource: orion_clocksource: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 9556302233 ns
[ 0.000008] sched_clock: 32 bits at 200MHz, resolution 5ns, wraps every 10737418237ns
[ 0.000039] Switching to timer-based delay loop, resolution 5ns
[ 0.000255] Console: colour dummy device 80x30
[ 0.000289] Calibrating delay loop (skipped), value calculated using timer frequency.. 400.00 BogoMIPS (lpj=2000000)
[ 0.000311] pid_max: default: 32768 minimum: 301
[ 0.000662] Security Framework initialized
[ 0.000834] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.000855] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.001820] CPU: Testing write buffer coherency: ok
[ 0.002877] Setting up static identity map for 0x8200 - 0x8258
[ 0.003150] mvebu-soc-id: MVEBU SoC ID=0x6281, Rev=0x3
[ 0.003385] Hierarchical SRCU implementation.
[ 0.004638] devtmpfs: initialized
[ 0.009509] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[ 0.009536] futex hash table entries: 256 (order: -1, 3072 bytes)
[ 0.009904] pinctrl core: initialized pinctrl subsystem
[ 0.011197] NET: Registered protocol family 16
[ 0.011647] DMA: preallocated 256 KiB pool for atomic coherent allocations
[ 0.013057] cpuidle: using governor ladder
[ 0.013125] cpuidle: using governor menu
[ 0.013609] Feroceon L2: Enabling L2
[ 0.013655] Feroceon L2: Cache support initialised.
[ 0.018599] No ATAGs?
[ 0.028128] vgaarb: loaded
[ 0.028438] SCSI subsystem initialized
[ 0.028859] usbcore: registered new interface driver usbfs
[ 0.028914] usbcore: registered new interface driver hub
[ 0.028999] usbcore: registered new device driver usb
[ 0.029105] pps_core: LinuxPPS API ver. 1 registered
[ 0.029114] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[ 0.029143] PTP clock support registered
[ 0.030159] clocksource: Switched to clocksource orion_clocksource
[ 0.095086] VFS: Disk quotas dquot_6.6.0
[ 0.095182] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[ 0.095394] FS-Cache: Loaded
[ 0.104866] NET: Registered protocol family 2
[ 0.105614] tcp_listen_portaddr_hash hash table entries: 512 (order: 0, 4096 bytes)
[ 0.105651] TCP established hash table entries: 2048 (order: 1, 8192 bytes)
[ 0.105685] TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
[ 0.105715] TCP: Hash tables configured (established 2048 bind 2048)
[ 0.105814] UDP hash table entries: 256 (order: 0, 4096 bytes)
[ 0.105837] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[ 0.106062] NET: Registered protocol family 1
[ 0.106568] RPC: Registered named UNIX socket transport module.
[ 0.106580] RPC: Registered udp transport module.
[ 0.106587] RPC: Registered tcp transport module.
[ 0.106594] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 0.106837] Trying to unpack rootfs image as initramfs...
[ 0.558873] Freeing initrd memory: 5404K
[ 0.560825] Initialise system trusted keyrings
[ 0.561090] workingset: timestamp_bits=14 max_order=16 bucket_order=2
[ 0.570789] FS-Cache: Netfs 'nfs' registered for caching
[ 0.571457] NFS: Registering the id_resolver key type
[ 0.571487] Key type id_resolver registered
[ 0.571495] Key type id_legacy registered
[ 0.571539] jffs2: version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
[ 0.572149] fuse init (API version 7.26)
[ 0.579110] Key type asymmetric registered
[ 0.579125] Asymmetric key parser 'x509' registered
[ 0.579217] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 249)
[ 0.579230] io scheduler noop registered
[ 0.579238] io scheduler deadline registered
[ 0.579589] io scheduler cfq registered (default)
[ 0.579601] io scheduler mq-deadline registered
[ 0.579609] io scheduler kyber registered
[ 0.579908] io scheduler bfq registered
[ 0.581580] kirkwood-pinctrl f1010000.pin-controller: registered pinctrl driver
[ 0.583471] mvebu-pcie mbus@f1000000:pcie@82000000: PCI host bridge to bus 0000:00
[ 0.583491] pci_bus 0000:00: root bus resource [io 0x1000-0xfffff]
[ 0.583503] pci_bus 0000:00: root bus resource [mem 0xe0000000-0xefffffff]
[ 0.583515] pci_bus 0000:00: root bus resource [bus 00-ff]
[ 0.583794] PCI: bus0: Fast back to back transfers disabled
[ 0.583811] pci 0000:00:01.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[ 0.584343] PCI: bus1: Fast back to back transfers disabled
[ 0.584396] pci 0000:00:01.0: BAR 8: assigned [mem 0xe0000000-0xe00fffff]
[ 0.584411] pci 0000:00:01.0: BAR 7: assigned [io 0x10000-0x10fff]
[ 0.584428] pci 0000:01:00.0: BAR 6: assigned [mem 0xe0000000-0xe000ffff pref]
[ 0.584443] pci 0000:01:00.0: BAR 4: assigned [mem 0xe0010000-0xe0013fff 64bit pref]
[ 0.584464] pci 0000:01:00.0: BAR 2: assigned [mem 0xe0014000-0xe0014fff 64bit pref]
[ 0.584484] pci 0000:01:00.0: BAR 0: assigned [io 0x10000-0x100ff]
[ 0.584498] pci 0000:00:01.0: PCI bridge to [bus 01]
[ 0.584509] pci 0000:00:01.0: bridge window [io 0x10000-0x10fff]
[ 0.584523] pci 0000:00:01.0: bridge window [mem 0xe0000000-0xe00fffff]
[ 0.584999] mv_xor f1060800.xor: Marvell shared XOR driver
[ 0.641336] mv_xor f1060800.xor: Marvell XOR (Registers Mode): ( xor cpy intr )
[ 0.641570] mv_xor f1060900.xor: Marvell shared XOR driver
[ 0.701314] mv_xor f1060900.xor: Marvell XOR (Registers Mode): ( xor cpy intr )
[ 0.705426] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
[ 0.706632] console [ttyS0] disabled
[ 0.706699] f1012000.serial: ttyS0 at MMIO 0xf1012000 (irq = 26, base_baud = 12500000) is a 16550A
[ 1.391710] console [ttyS0] enabled
[ 1.406030] brd: module loaded
[ 1.416491] loop: module loaded
[ 1.420346] sata_mv f1080000.sata: slots 32 ports 2
[ 1.427907] scsi host0: sata_mv
[ 1.431688] scsi host1: sata_mv
[ 1.435042] ata1: SATA max UDMA/133 irq 32
[ 1.439163] ata2: SATA max UDMA/133 irq 32
[ 1.443980] nand: device found, Manufacturer ID: 0xec, Chip ID: 0xf1
[ 1.450641] nand: Samsung NAND 128MiB 3,3V 8-bit
[ 1.455316] nand: 128 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
[ 1.462949] Scanning device for bad blocks
[ 1.534127] Bad eraseblock 631 at 0x000004ee0000
[ 1.580405] 2 cmdlinepart partitions found on MTD device orion_nand
[ 1.586702] Creating 2 MTD partitions on "orion_nand":
[ 1.591892] 0x000000000000-0x000000100000 : "u-boot"
[ 1.597260] 0x000000100000-0x000008000000 : "rootfs"
[ 1.603768] libphy: Fixed MDIO Bus: probed
[ 1.608596] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
[ 1.614271] pci 0000:00:01.0: enabling device (0140 -> 0143)
[ 1.619974] r8169 0000:01:00.0: enabling device (0140 -> 0143)
[ 1.626527] r8169 0000:01:00.0 eth0: RTL8168d/8111d at 0x(ptrval), 00:00:00:00:00:30, XID 083000c0 IRQ 35
[ 1.636177] r8169 0000:01:00.0 eth0: jumbo features [frames: 9200 bytes, tx checksumming: ko]
[ 1.644880] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 1.651466] ehci-pci: EHCI PCI platform driver
[ 1.655980] ehci-orion: EHCI orion driver
[ 1.660228] orion-ehci f1050000.ehci: EHCI Host Controller
[ 1.665763] orion-ehci f1050000.ehci: new USB bus registered, assigned bus number 1
[ 1.673665] orion-ehci f1050000.ehci: irq 30, io mem 0xf1050000
[ 1.700187] orion-ehci f1050000.ehci: USB 2.0 started, EHCI 1.00
[ 1.707035] hub 1-0:1.0: USB hub found
[ 1.710906] hub 1-0:1.0: 1 port detected
[ 1.715472] usbcore: registered new interface driver uas
[ 1.720995] usbcore: registered new interface driver usb-storage
[ 1.727090] usbcore: registered new interface driver ums-alauda
[ 1.733128] usbcore: registered new interface driver ums-cypress
[ 1.739224] usbcore: registered new interface driver ums-datafab
[ 1.745334] usbcore: registered new interface driver ums_eneub6250
[ 1.751611] usbcore: registered new interface driver ums-freecom
[ 1.757700] usbcore: registered new interface driver ums-isd200
[ 1.763723] usbcore: registered new interface driver ums-jumpshot
[ 1.769899] usbcore: registered new interface driver ums-karma
[ 1.775834] usbcore: registered new interface driver ums-onetouch
[ 1.782101] usbcore: registered new interface driver ums-realtek
[ 1.788169] usbcore: registered new interface driver ums-sddr09
[ 1.794175] usbcore: registered new interface driver ums-sddr55
[ 1.800180] usbcore: registered new interface driver ums-usbat
[ 1.806355] mousedev: PS/2 mouse device common for all mice
[ 1.812421] rtc-mv f1010300.rtc: rtc core: registered f1010300.rtc as rtc0
[ 1.819410] i2c /dev entries driver
[ 1.823962] orion_wdt: Initial timeout 21 sec
[ 1.829208] sdhci: Secure Digital Host Controller Interface driver
[ 1.835487] sdhci: Copyright(c) Pierre Ossman
[ 1.839945] sdhci-pltfm: SDHCI platform and OF driver helper
[ 1.847230] ledtrig-cpu: registered to indicate activity on CPUs
[ 1.853390] usbcore: registered new interface driver r8712u
[ 1.859228] gre: GRE over IPv4 demultiplexor driver
[ 1.864199] NET: Registered protocol family 17
[ 1.868744] Key type dns_resolver registered
[ 1.873845] registered taskstats version 1
[ 1.877959] Loading compiled-in X.509 certificates
[ 1.895354] Key type encrypted registered
[ 1.901364] console [netcon0] enabled
[ 1.905044] netconsole: network logging started
[ 1.910532] input: gpio_keys as /devices/platform/gpio_keys/input/input0
[ 1.917568] rtc-mv f1010300.rtc: setting system clock to 2018-05-10 21:02:15 UTC (1525986135)
[ 1.950278] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl F300)
[ 1.980541] ata1.00: ATA-7: SAMSUNG HD753LJ, 1AA01110, max UDMA7
[ 1.986676] ata1.00: 1465149168 sectors, multi 0: LBA48 NCQ (depth 31/32)
[ 2.020559] ata1.00: configured for UDMA/133
[ 2.035746] scsi 0:0:0:0: Direct-Access ATA SAMSUNG HD753LJ 1110 PQ: 0 ANSI: 5
[ 2.044968] sd 0:0:0:0: [sda] 1465149168 512-byte logical blocks: (750 GB/699 GiB)
[ 2.052947] sd 0:0:0:0: Attached scsi generic sg0 type 0
[ 2.058525] sd 0:0:0:0: [sda] Write Protect is off
[ 2.063716] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 2.078059] sda: sda1 sda2
[ 2.080937] usb 1-1: new high-speed USB device number 2 using orion-ehci
[ 2.089121] sd 0:0:0:0: [sda] Attached SCSI disk
[ 2.293583] hub 1-1:1.0: USB hub found
[ 2.297833] hub 1-1:1.0: 4 ports detected
[ 2.304417] random: fast init done
[ 2.404749] ata2: SATA link down (SStatus 0 SControl F300)
[ 2.422035] Freeing unused kernel memory: 356K
[ 2.426568] This architecture does not have kernel memory protection.
:: running early hook [udev]
Warning: /lib/modules/4.16.7-1-ARCH/modules.devname not found - ignoring
starting version 238
:: running hook [udev]
:: Triggering uevents...
:: performing fsck on '/dev/sda1'
boot was not cleanly unmounted, check forced.
/lost+found not found. CREATED.
boot: 13/4096 files (15.4% non-contiguous), 11130/16384 blocks
:: mounting '/dev/sda1' on real root
[ 4.267618] EXT4-fs (sda1): mounting ext2 file system using the ext4 subsystem
[ 4.302724] EXT4-fs (sda1): mounted filesystem without journal. Opts: (null)
:: running cleanup hook [udev]
ERROR: Root device mounted successfully, but /sbin/init does not exist.
Bailing out, you are on your own. Good luck.

sh: can't access tty; job control turned off
[rootfs ]#
')
arti74
 
Posts: 75
Joined: Tue Apr 17, 2018 10:33 am

Re: 4.4.97-1-ARCH wrong NAND chip timing in the DTS? NSA310

Postby summers » Thu May 10, 2018 9:21 pm

didn't partition 1 contain your boot partition, so only contained uImage and an initramdisk? didn't you mean /dev/sda2?

Your kernel booted fine, but when it tried to pass control to init - it didn't find it. So its probably left you in the init file system, that has a few commands IIRC, but is very limited ... So you gave the wrong address for root ...
summers
 
Posts: 995
Joined: Sat Sep 06, 2014 12:56 pm

Re: 4.4.97-1-ARCH wrong NAND chip timing in the DTS? NSA310

Postby arti74 » Thu May 10, 2018 9:29 pm

/dev/sda1 should be my 16M boot partition on ext2
/dev/sda2 is the root - do you think changing uEnv will fix it?
Now on the limited console I have
$this->bbcode_second_pass_code('', '[rootfs ]# df
Filesystem 1K-blocks Used Available Use% Mounted on
dev 121520 0 121520 0% /dev
run 124400 4 124396 0% /run
/dev/sda1 15863 10609 4435 71% /new_root
')
And my boot was on the /dev/sda1, so what's there:
$this->bbcode_second_pass_code('', '[rootfs ]# ls new_root/
initramfs-linux.img lost+found uImage')
And where is for ex. uEnv.txt? If I'm not mistaken I had there also a copy from the uImage...

EDIT
$this->bbcode_second_pass_code('', '[rootfs ]# mkdir /uss
[rootfs ]# mount /dev/sda2 /uss
[ 1810.128625] EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null)')
$this->bbcode_second_pass_code('', '[rootfs ]# ls /uss/
bin etc mnt root skrypty sys var
boot home opt run srv tmp
dev lib proc sbin swapfile usr
[rootfs ]# ls /uss/boot/
dtbs uEnv.txt uboot-nsa310.kwb
initramfs-linux.img uImage zImage.ok
kirkwood.dtb uboot-nsa310.env')
So the boot is somehow on the sda2 now!?
$this->bbcode_second_pass_code('', '[rootfs ]# cat /uss/boot/uEnv.txt
#root=/dev/sda2
root=PARTUUID=ab197877-02
mtdparts=mtdparts=orion_nand:0x100000(uboot),0x80000(uboot_env),0x80000(key_store),0x80000(info),0xA00000(etc),0xA00000(kernel_1),0x2FC0000(rootfs1),0xA00000(kernel_2),0x2FC0000(rootfs2)
loadfdt=echo loading ${fdtdir}/${fdtfile} ...; load ${devtype} ${bootpart} ${fdtaddr} ${fdtdir}/${fdtfile}; fdt addr ${fdtaddr}; fdt set /mbus@f1000000/nand@12f chip-delay <35>
ethaddr=CC:5D:4E:C9:F5:4A')
And if I remember good the boot partition PARTUUID was ab197877-01

How to set up everything properly now?
EDIT
I just copied uEnv.txt to the new_root directory, and also the kirkwood-nsa310 file there. After restart - again 'setenv bootdir' and 'run startboot' and I'm in Arch again :)
Must just set up the proper env now...

EDIT - DONE!! It's working now

THANK YOU @summers for bringing a new life to my nsa310! :D
arti74
 
Posts: 75
Joined: Tue Apr 17, 2018 10:33 am

Re: 4.4.97-1-ARCH wrong NAND chip timing in the DTS? NSA310

Postby summers » Fri May 11, 2018 9:02 am

Glad it worked.

Oh yes the problem you had when booting, clue is in the command line:
$this->bbcode_second_pass_code('', '[ 0.000000] Kernel command line: console=ttyS0,115200 mtdparts=orion_nand:1M(u-boot),-(rootfs) root=PARTUUID=ab197877-01 rw rootwait')
You can see that the PARTUUID ends -01, and that means sda1 - and so its why the machine didn't boot well. sda1 is confirmed lower in the boot log as well. Now the mtdparts is also whats in the default env, and not what you set in uEnv.txt. So its clear that the uEnv.txt wasn't read.

Now going back earlier you can also see that the zImage wasn't found, and it ended up booting the uImage we created for the update. So looks like it didn't find /boot on sda2. So still an issue, not clear why.

Now ideally long term you would get it to boot from sda2, and so just ignore the old boot partition on sda1, but need to find out why uboot doesn't like sda2.

With a uEnv.txt in both sda1 and sda2, uboot will use the first it finds, and that would usually be sda1. Its not clear this is what we want, as makes things harder in the long term. So probably a good idea to resolve what is wrong.

is sda2 still ext4? What did "tune2fs -l /dev/sda2" say - that will show the options so we can see if the checksum and 64bit are set ...

Oh yes - also looks like /boot on sda2 doesn't contain a zImage, thats a mistake - you should have a zImage in there, so worth reinstalling the kernel ...
summers
 
Posts: 995
Joined: Sat Sep 06, 2014 12:56 pm

Re: 4.4.97-1-ARCH wrong NAND chip timing in the DTS? NSA310

Postby arti74 » Fri May 11, 2018 10:19 am

Thank you for your presence ;)
It is just new kernel tn the repos and I installed it - it boots without problem and I'm glad.
$this->bbcode_second_pass_quote('', 'i')s sda2 still ext4?

Yes it is, and I don't intend to change it in the near time ;)
This is the result of your 'tune2fs -l /dev/sda2' command:
$this->bbcode_second_pass_code('', 'tune2fs 1.44.1 (24-Mar-2018)
Filesystem volume name: rootfs
Last mounted on: /
Filesystem UUID: 88f49752-68db-4f08-908e-75c688363624
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: has_journal ext_attr resize_inode dir_index filetype needs_recovery extent 64bit flex_bg sparse_super large_file huge_file dir_nlink extra_isize metadata_csum
Filesystem flags: signed_directory_hash
Default mount options: user_xattr acl
Filesystem state: clean
Errors behavior: Continue
Filesystem OS type: Linux
Inode count: 45785088
Block count: 183139294
Reserved block count: 9156964
Free blocks: 166503757
Free inodes: 45695077
First block: 0
Block size: 4096
Fragment size: 4096
Group descriptor size: 64
Reserved GDT blocks: 1024
Blocks per group: 32768
Fragments per group: 32768
Inodes per group: 8192
Inode blocks per group: 512
RAID stripe width: 8191
Flex block group size: 16
Filesystem created: Tue Apr 17 10:07:25 2018
Last mount time: Fri May 11 12:03:38 2018
Last write time: Fri May 11 12:03:38 2018
Mount count: 77
Maximum mount count: -1
Last checked: Tue Apr 17 10:07:25 2018
Check interval: 0 (<none>)
Lifetime writes: 77 GB
Reserved blocks uid: 0 (user root)
Reserved blocks gid: 0 (group root)
First inode: 11
Inode size: 256
Required extra isize: 32
Desired extra isize: 32
Journal inode: 8
Default directory hash: half_md4
Directory Hash Seed: 2667642d-abc8-4e63-9be5-676a171bf91b
Journal backup: inode blocks
Checksum type: crc32c
Checksum: 0x36e4dfcb')
This is part of the booting log (before kernel starts) which shows that not everything is clean yet:
$this->bbcode_second_pass_code('', 'U-Boot 2016.09.01-1 (Oct 10 2016 - 23:14:18 -0600) Arch Linux ARM
Zyxel NSA310

SoC: Kirkwood 88F6281_A1
DRAM: 256 MiB
WARNING: Caches not enabled
NAND: 128 MiB
In: serial
Out: serial
Err: serial
Net: egiga0
Error: egiga0 address not set.

PHY reset timed out
MV88E1318 PHY initialized on egiga0
IDE: Bus 0: OK Bus 1: not available
Device 0: Model: SAMSUNG HD753LJ Firm: 1AA01110 Ser#: S13UJ1DQ400383
Type: Hard Disk
Supports 48-bit addressing
Capacity: 715404.8 MB = 698.6 GB (1465149168 x 512)
*** ERROR: `ethaddr' not set
ping failed; host 10.10.10.5 is not alive
Hit any key to stop autoboot: 0
starting USB...
USB0: USB EHCI 1.00
scanning bus 0 for devices... 2 USB Device(s) found
scanning usb for storage devices... 0 Storage Device(s) found

Reset IDE: Bus 0: OK Bus 1: not available
Device 0: Model: SAMSUNG HD753LJ Firm: 1AA01110 Ser#: S13UJ1DQ400383
Type: Hard Disk
Supports 48-bit addressing
Capacity: 715404.8 MB = 698.6 GB (1465149168 x 512)

USB device 0: unknown device

Device 0: Model: SAMSUNG HD753LJ Firm: 1AA01110 Ser#: S13UJ1DQ400383
Type: Hard Disk
Supports 48-bit addressing
Capacity: 715404.8 MB = 698.6 GB (1465149168 x 512)
... is now current device
ide found on device 0
Checking for: /uEnv.txt ...
432 bytes read in 6 ms (70.3 KiB/s)
Loaded environment from /uEnv.txt
Checking if uenvcmd is set ...
** File not found /zImage **
5155808 bytes read in 1873 ms (2.6 MiB/s)
root has been defined by user
loading /boot/dtbs/kirkwood-nsa310.dtb ...
** File not found /boot/dtbs/kirkwood-nsa310.dtb **
libfdt fdt_check_header(): FDT_ERR_BADMAGIC
No FDT memory address configured. Please configure
the FDT address via "fdt addr <address>" command.
Aborting!
5530551 bytes read in 1965 ms (2.7 MiB/s)
Booting uImage with initrd
')
Beside of this I have a problem with sensors, I thought a new kernell will maybe resolve this, but no - still no sensors detected after 'sensors-detect' command:
$this->bbcode_second_pass_code('', 'Now follows a summary of the probes I have just done.
Just press ENTER to continue:

Driver `to-be-written':
* ISA bus, address 0xca0
Chip `IPMI BMC KCS' (confidence: 4)
* ISA bus, address 0xca8
Chip `IPMI BMC SMIC' (confidence: 4)

Note: there is no driver for IPMI BMC KCS yet.
Check http://www.lm-sensors.org/wiki/Devices for updates.

No modules to load, skipping modules configuration.')
Without it my system fan is spinning at full which is very loud.
arti74
 
Posts: 75
Joined: Tue Apr 17, 2018 10:33 am

Re: 4.4.97-1-ARCH wrong NAND chip timing in the DTS? NSA310

Postby summers » Fri May 11, 2018 10:54 am

Ah yes problem with the tune2ls is
$this->bbcode_second_pass_code('', 'Filesystem features: has_journal ext_attr resize_inode dir_index filetype needs_recovery extent [b]64bit[/b] flex_bg sparse_super large_file huge_file dir_nlink extra_isize [b]metadata_csum[/b]')
So those are bit bits we want to switch off, as they are stopping uboot accessing sda2, which is what is giving remaining problems.

In uboot, after setting the ethaddr, did you do a "saveenv"? As looks like its not saved ...

IIRC fan is a stange set up on nsa devices, there is some info on it in nas central. In the rebuild of my nsa, its one thing I'm changing - the fan to ones thats quieter and spins slower ... http://zyxel.nas-central.org/wiki/Fan_control_%28NSA325%29
summers
 
Posts: 995
Joined: Sat Sep 06, 2014 12:56 pm

PreviousNext

Return to Packages

Who is online

Users browsing this forum: No registered users and 10 guests

cron