Bad eraseblocks on NSA310 (4.4.97-1-ARCH) & uboot update

This forum is for Marvell Kirkwood devices such as the GoFlex Home/Net, PogoPlug v1/v2, SheevaPlug, and ZyXEL devices.

Bad eraseblocks on NSA310 (4.4.97-1-ARCH) & uboot update

Postby arti74 » Thu Apr 26, 2018 8:56 pm

Hello
This is part of my dmesg:
$this->bbcode_second_pass_code('', '[ 17.146340] Bad eraseblock 1023 at 0x000007fe0000')
- the last bad eraseblock - after installing 4.4.97-1-ARCH on a stock uboot.
When I try to update the uboot I have error:
$this->bbcode_second_pass_code('', 'Too few good blocks within range
Error: Could not find MAC address from current U-Boot.')
then:
fw_setenv ethaddr [my mac]
$this->bbcode_second_pass_code('', 'Too few good blocks within range
Error: environment not initialized')
I'm stuck, please help...
arti74
 
Posts: 75
Joined: Tue Apr 17, 2018 10:33 am

Re: Bad eraseblocks on NSA310 (4.4.97-1-ARCH) & uboot update

Postby summers » Fri Apr 27, 2018 8:32 am

Think thats usually caused by bad blocks on the flash - which is quite bad, as that is what you boot from.

Worth checking though that /etc/fw_env.config is set correctly - check how the flash is set up during boot, you get lines line:

$this->bbcode_second_pass_code('', 'dev: size erasesize name
mtd0: 00100000 00020000 "uboot"
mtd1: 00080000 00020000 "uboot_env"
mtd2: 00080000 00020000 "key_store"
mtd3: 00080000 00020000 "info"
mtd4: 00a00000 00020000 "etc"
mtd5: 00a00000 00020000 "kernel_1"
mtd6: 02fc0000 00020000 "rootfs1"
mtd7: 00a00000 00020000 "kernel_2"
mtd8: 02fc0000 00020000 "rootfs2"')

actually that lives in /proc/mtd. I had a script that check settings for things like this - let me see if I can find it ...

Think my latest script was the below, I'll check when I get home.
$this->bbcode_second_pass_code('', ' #!/bin/bash

if { mtdinfo /dev/mtd0 | egrep "Device is writable:.*false" > /dev/null; } then
# probably the nand driver name is set wrong
{
if [ `cat /sys/devices/virtual/mtd/mtd1/offset` -eq 1048576 ]; then
# almost certainly in the stock mtd set up so uboot_env is in /dev/mtd1
echo '/dev/mtd1 0x0 0x20000 0x20000' > /etc/fw_env.config
# and the mtd driver is orion_nand
fw_setenv bootargs_linux 'console=ttyS0,115200 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) root=/dev/sda2 rw rootwait loglevel=8'
# and now we need to reboot
reboot
;
else
echo I dont know where to find the uboot env variables
;
fi
}
fi

if { mtdinfo /dev/mtd0 | egrep "Device is writable:.*true" > /dev/null ; } then
{
# we are good to write the new uboot. first grab the current mac address
# from the old uboot env variables
mac=$(fw_printenv | sed -n 's/^ethaddr=\(.*\)/\1/p')
# flash U-Boot
flash_erase /dev/mtd0 0 4
flash_erase /dev/mtd0 0xc0000 1
nandwrite /dev/mtd0 /boot/uboot-nsa325.kwb
nandwrite -s 0xc0000 /dev/mtd0 /boot/uboot-nsa325.env
# now we can update the uboot env varible area to the new area
echo '/dev/mtd0 0xc0000 0x20000 0x20000' > /etc/fw_env.config
# and set the mad address
fw_setenv ethaddr ${mac}

# is boot mounted
boot=$(mount | sed -n 's/^\([^ ]*\).* \/boot .*/\1/p')
if [ ${boot} ] ; then

# /boot is a mounted partition
# we want to set this up as part of root with new uboot (e.g. a directory)
umount /boot
mkdir /tmp/boot
mount ${boot} /tmp/boot
# copy the files from the old boot partion into the new boot directory
(cd /tmp/boot ; tar cf - . ) | ( cd /boot ; tar xf - )
sync
umount /tmp/boot


# and remove /boot from the fstab
sed '/^.*\/boot.*$/d' < /etc/fstab > /etc/fstab.new
mv /etc/fstab.new /etc/fstab
;
fi

# make sure right root is passed in uboot (should this be written to the permanent env variables?)
root=`mount | sed -n 's/^\([^ ]*\).* \/ .*/\1/p'`
echo root=${root} > /boot/uEnv.txt

}
fi
')

And looking at it it may welll need updating for the new boot.src ...
summers
 
Posts: 984
Joined: Sat Sep 06, 2014 12:56 pm

Re: Bad eraseblocks on NSA310 (4.4.97-1-ARCH) & uboot update

Postby arti74 » Fri Apr 27, 2018 9:22 am

Thanks Summers for your effort.
This is what I've got after running your script:
$this->bbcode_second_pass_code('', './summers_script
Too few good blocks within range
flash_erase: Skipping bad block at 00000000
flash_erase: Skipping bad block at 00020000
flash_erase: Skipping bad block at 00040000
flash_erase: Skipping bad block at 00060000
Erasing 128 Kibyte @ 60000 -- 100 % complete
flash_erase: Skipping bad block at 000c0000
Erasing 128 Kibyte @ c0000 -- 100 % complete
/boot/uboot-nsa325.kwb: No such file or directory
nandwrite: error!: Data was only partially written due to error
error 9 (Bad file descriptor)
/boot/uboot-nsa325.env: No such file or directory
nandwrite: error!: Data was only partially written due to error
error 9 (Bad file descriptor)
Too few good blocks within range
Error: environment not initialized
')
My dmesg in details:
$this->bbcode_second_pass_code('', '[ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] Initializing cgroup subsys cpuset
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Initializing cgroup subsys cpuacct
[ 0.000000] Linux version 4.4.97-1-ARCH (builduser@leming) (gcc version 7.2.0 (GCC) ) #1 PREEMPT Sat Nov 11 04:51:38 UTC 2017
[ 0.000000] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=0005397f
[ 0.000000] CPU: VIVT data cache, VIVT instruction cache
[ 0.000000] Machine: Zyxel NSA-310
[ 0.000000] Memory policy: Data cache writeback
[ 0.000000] On node 0 totalpages: 65536
[ 0.000000] free_area_init_node: node 0, pgdat c091b744, node_mem_map cfdba000
[ 0.000000] Normal zone: 576 pages used for memmap
[ 0.000000] Normal zone: 0 pages reserved
[ 0.000000] Normal zone: 65536 pages, LIFO batch:15
[ 0.000000] pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
[ 0.000000] pcpu-alloc: [0] 0
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 64960
[ 0.000000] Kernel command line: console=ttyS0,115200 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) root=/dev/sda2 rw rootwait loglevel=8
[ 0.000000] PID hash table entries: 1024 (order: 0, 4096 bytes)
[ 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: 249508K/262144K available (6598K kernel code, 550K rwdata, 1880K rodata, 304K init, 725K bss, 12636K reserved, 0K cma-reserved)
[ 0.000000] Virtual kernel memory layout:
vector : 0xffff0000 - 0xffff1000 ( 4 kB)
fixmap : 0xffc00000 - 0xfff00000 (3072 kB)
vmalloc : 0xd0800000 - 0xff800000 ( 752 MB)
lowmem : 0xc0000000 - 0xd0000000 ( 256 MB)
modules : 0xbf000000 - 0xc0000000 ( 16 MB)
.text : 0xc0008000 - 0xc084fc70 (8480 kB)
.init : 0xc0850000 - 0xc089c000 ( 304 kB)
.data : 0xc089c000 - 0xc0925a04 ( 551 kB)
.bss : 0xc0925a04 - 0xc09daf98 ( 726 kB)
[ 0.000000] SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[ 0.000000] Preemptible hierarchical RCU implementation.
[ 0.000000] Build-time adjustment of leaf fanout to 32.
[ 0.000000] NR_IRQS:114
[ 0.000012] sched_clock: 32 bits at 200MHz, resolution 5ns, wraps every 10737418237ns
[ 11.195100] clocksource: orion_clocksource: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 9556302233 ns
[ 11.195270] Console: colour dummy device 80x30
[ 11.195295] Calibrating delay loop... 1196.85 BogoMIPS (lpj=5984256)
[ 11.285176] pid_max: default: 32768 minimum: 301
[ 11.285258] Security Framework initialized
[ 11.285328] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[ 11.285344] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[ 11.286014] Initializing cgroup subsys io
[ 11.286045] Initializing cgroup subsys memory
[ 11.286095] Initializing cgroup subsys devices
[ 11.286118] Initializing cgroup subsys freezer
[ 11.286138] Initializing cgroup subsys net_cls
[ 11.286156] Initializing cgroup subsys perf_event
[ 11.286175] Initializing cgroup subsys net_prio
[ 11.286247] CPU: Testing write buffer coherency: ok
[ 11.286655] Setting up static identity map for 0x81e0 - 0x8238
[ 11.288433] devtmpfs: initialized
[ 11.290665] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[ 11.290702] futex hash table entries: 256 (order: -1, 3072 bytes)
[ 11.291147] pinctrl core: initialized pinctrl subsystem
[ 11.291847] NET: Registered protocol family 16
[ 11.292302] DMA: preallocated 256 KiB pool for atomic coherent allocations
[ 11.315180] cpuidle: using governor ladder
[ 11.345178] cpuidle: using governor menu
[ 11.345358] Kirkwood: MV88F6281-A1, TCLK=200000000.
[ 11.345380] Feroceon L2: Enabling L2
[ 11.345416] Feroceon L2: Cache support initialised.
[ 11.346118] initial MPP regs: 21111111 01003311 33331100 33003333 00000533 20202000 00000000
[ 11.346147] final MPP regs: 21111111 00003311 33031100 33003333 00000533 00000000 00000000
[ 11.348106] Power resume enabled
[ 11.348116] Power-off GPIO enabled
[ 11.348548] Kirkwood PCIe port 0: link up
[ 11.348559] PCI: bus0 uses PCIe port 0
[ 11.348782] PCI host bridge to bus 0000:00
[ 11.348799] pci_bus 0000:00: root bus resource [mem 0xe0000000-0xe7ffffff]
[ 11.348810] pci_bus 0000:00: root bus resource [io 0x1000-0xffff]
[ 11.348821] pci_bus 0000:00: No busn resource found for root bus, will use [bus 00-ff]
[ 11.348851] pci 0000:00:00.0: [11ab:6281] type 00 class 0x058000
[ 11.348882] pci 0000:00:00.0: reg 0x10: [mem 0xf1000000-0xf10fffff 64bit pref]
[ 11.348898] pci 0000:00:00.0: reg 0x18: [mem 0x00000000-0x0fffffff]
[ 11.348945] pci 0000:00:00.0: supports D1 D2
[ 11.349156] pci 0000:00:01.0: [10ec:8168] type 00 class 0x020000
[ 11.349203] pci 0000:00:01.0: reg 0x10: [io 0xf0000000-0xf00000ff]
[ 11.349236] pci 0000:00:01.0: reg 0x18: [mem 0x40000000-0x40000fff 64bit pref]
[ 11.349259] pci 0000:00:01.0: reg 0x20: [mem 0x40004000-0x40007fff 64bit pref]
[ 11.349278] pci 0000:00:01.0: reg 0x30: [mem 0x00000000-0x0000ffff pref]
[ 11.349345] pci 0000:00:01.0: supports D1 D2
[ 11.349355] pci 0000:00:01.0: PME# supported from D0 D1 D2 D3hot D3cold
[ 11.349617] PCI: bus0: Fast back to back transfers disabled
[ 11.349632] pci_bus 0000:00: busn_res: [bus 00-ff] end is updated to 00
[ 11.349663] pci 0000:00:01.0: BAR 6: assigned [mem 0xe0000000-0xe000ffff pref]
[ 11.349679] pci 0000:00:01.0: BAR 4: assigned [mem 0xe0010000-0xe0013fff 64bit pref]
[ 11.349701] pci 0000:00:01.0: BAR 2: assigned [mem 0xe0014000-0xe0014fff 64bit pref]
[ 11.349722] pci 0000:00:01.0: BAR 0: assigned [io 0x1000-0x10ff]
[ 11.386650] vgaarb: loaded
[ 11.386968] SCSI subsystem initialized
[ 11.387157] libata version 3.00 loaded.
[ 11.387463] usbcore: registered new interface driver usbfs
[ 11.387536] usbcore: registered new interface driver hub
[ 11.387593] usbcore: registered new device driver usb
[ 11.387750] pps_core: LinuxPPS API ver. 1 registered
[ 11.387759] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[ 11.387790] PTP clock support registered
[ 11.388838] clocksource: Switched to clocksource orion_clocksource
[ 11.427575] FS-Cache: Loaded
[ 11.440394] NET: Registered protocol family 2
[ 11.441173] TCP established hash table entries: 2048 (order: 1, 8192 bytes)
[ 11.441210] TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
[ 11.441240] TCP: Hash tables configured (established 2048 bind 2048)
[ 11.441306] UDP hash table entries: 256 (order: 0, 4096 bytes)
[ 11.441328] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[ 11.441515] NET: Registered protocol family 1
[ 11.441845] RPC: Registered named UNIX socket transport module.
[ 11.441856] RPC: Registered udp transport module.
[ 11.441863] RPC: Registered tcp transport module.
[ 11.441869] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 11.441908] PCI: CLS 32 bytes, default 32
[ 11.456033] VFS: Disk quotas dquot_6.6.0
[ 11.456290] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[ 11.458299] FS-Cache: Netfs 'nfs' registered for caching
[ 11.459490] NFS: Registering the id_resolver key type
[ 11.459537] Key type id_resolver registered
[ 11.459545] Key type id_legacy registered
[ 11.459636] jffs2: version 2.2. (NAND) \xc2\xa9 2001-2006 Red Hat, Inc.
[ 11.460919] fuse init (API version 7.23)
[ 11.462971] aufs 4.4-20170911
[ 11.468044] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 250)
[ 11.468065] io scheduler noop registered
[ 11.468078] io scheduler deadline registered
[ 11.468342] io scheduler cfq registered
[ 11.468595] io scheduler bfq registered (default)
[ 11.468604] BFQ I/O-scheduler: v7r11
[ 11.468825] mv_xor mv_xor.0: Marvell shared XOR driver
[ 11.510009] mv_xor mv_xor.0: Marvell XOR (Registers Mode): ( xor cpy )
[ 11.510241] mv_xor mv_xor.1: Marvell shared XOR driver
[ 11.550040] mv_xor mv_xor.1: Marvell XOR (Registers Mode): ( xor cpy )
[ 11.555618] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
[ 11.556645] console [ttyS0] disabled
[ 11.576747] serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 33, base_baud = 12500000) is a 16550A
[ 12.349388] console [ttyS0] enabled
[ 12.367918] brd: module loaded
[ 12.378369] loop: module loaded
[ 12.381907] sata_mv sata_mv.0: version 1.28
[ 12.386168] sata_mv sata_mv.0: cannot get optional clkdev
[ 12.391763] sata_mv sata_mv.0: slots 32 ports 2
[ 12.399452] scsi host0: sata_mv
[ 12.403124] scsi host1: sata_mv
[ 12.406604] ata1: SATA max UDMA/133 irq 21
[ 12.410768] ata2: SATA max UDMA/133 irq 21
[ 12.415523] nand: device found, Manufacturer ID: 0xec, Chip ID: 0xf1
[ 12.422142] nand: Samsung NAND 128MiB 3,3V 8-bit
[ 12.426784] nand: 128 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
[ 12.434418] Scanning device for bad blocks
[ 12.438580] Bad eraseblock 0 at 0x000000000000
[ 12.443121] Bad eraseblock 1 at 0x000000020000
[ 12.447626] Bad eraseblock 2 at 0x000000040000
[ 12.452143] Bad eraseblock 3 at 0x000000060000
[ 12.456641] Bad eraseblock 4 at 0x000000080000
[ 12.461157] Bad eraseblock 5 at 0x0000000a0000
[ 12.465658] Bad eraseblock 6 at 0x0000000c0000
[ 12.470174] Bad eraseblock 7 at 0x0000000e0000
[ 12.474675] Bad eraseblock 8 at 0x000000100000
[ 12.479189] Bad eraseblock 9 at 0x000000120000
[ 12.483691] Bad eraseblock 10 at 0x000000140000
........... - cutted
[ 12.925481] Bad eraseblock 106 at 0x000000d40000
[ 12.930155] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl F300)
[ 12.936623] Bad eraseblock 107 at 0x000000d60000
[ 12.941331] Bad eraseblock 108 at 0x000000d80000
[ 12.946008] Bad eraseblock 109 at 0x000000da0000
[ 12.950893] ata1.00: ATA-7: SAMSUNG HD753LJ, 1AA01110, max UDMA7
[ 12.956925] ata1.00: 1465149168 sectors, multi 0: LBA48 NCQ (depth 31/32)
[ 12.963810] Bad eraseblock 110 at 0x000000dc0000
...........
[ 12.996855] Bad eraseblock 117 at 0x000000ea0000
[ 13.001725] ata1.00: configured for UDMA/133
[ 13.006081] Bad eraseblock 118 at 0x000000ec0000
[ 13.010788] Bad eraseblock 119 at 0x000000ee0000
[ 13.015464] Bad eraseblock 120 at 0x000000f00000
[ 13.020288] Bad eraseblock 121 at 0x000000f20000
[ 13.024968] Bad eraseblock 122 at 0x000000f40000
[ 13.029951] scsi 0:0:0:0: Direct-Access ATA SAMSUNG HD753LJ 1110 PQ: 0 ANSI: 5
[ 13.039377] sd 0:0:0:0: Attached scsi generic sg0 type 0
[ 13.044972] Bad eraseblock 123 at 0x000000f60000
[ 13.049829] sd 0:0:0:0: [sda] 1465149168 512-byte logical blocks: (750 GB/699 GiB)
[ 13.057664] Bad eraseblock 124 at 0x000000f80000
[ 13.062565] sd 0:0:0:0: [sda] Write Protect is off
[ 13.067384] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[ 13.072549] Bad eraseblock 125 at 0x000000fa0000
[ 13.077227] Bad eraseblock 126 at 0x000000fc0000
[ 13.081996] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 13.091146] Bad eraseblock 127 at 0x000000fe0000
[ 13.095818] Bad eraseblock 128 at 0x000001000000
[ 13.101582] Bad eraseblock 129 at 0x000001020000
[ 13.106332] sda: sda1 sda2
[ 13.109453] Bad eraseblock 130 at 0x000001040000
[ 13.114131] Bad eraseblock 131 at 0x000001060000
[ 13.118803] Bad eraseblock 132 at 0x000001080000
[ 13.124747] sd 0:0:0:0: [sda] Attached SCSI disk
[ 13.129495] Bad eraseblock 133 at 0x0000010a0000
[ 13.134169] Bad eraseblock 134 at 0x0000010c0000
[ 13.138884] Bad eraseblock 135 at 0x0000010e0000
...........
[ 13.396501] Bad eraseblock 190 at 0x0000017c0000
[ 13.401172] ata2: SATA link down (SStatus 0 SControl F300)
[ 13.406759] Bad eraseblock 191 at 0x0000017e0000
...........
[ 17.294776] Bad eraseblock 1021 at 0x000007fa0000
[ 17.299554] Bad eraseblock 1022 at 0x000007fc0000
[ 17.304316] Bad eraseblock 1023 at 0x000007fe0000
[ 17.309078] 9 cmdlinepart partitions found on MTD device orion_nand
[ 17.315369] Creating 9 MTD partitions on "orion_nand":
[ 17.320546] 0x000000000000-0x000000100000 : "uboot"
[ 17.325955] 0x000000100000-0x000000180000 : "uboot_env"
[ 17.331683] 0x000000180000-0x000000200000 : "key_store"
[ 17.337391] 0x000000200000-0x000000280000 : "info"
[ 17.342656] 0x000000280000-0x000000c80000 : "etc"
[ 17.347802] 0x000000c80000-0x000001680000 : "kernel_1"
[ 17.353420] 0x000001680000-0x000004640000 : "rootfs1"
[ 17.358993] 0x000004640000-0x000005040000 : "kernel_2"
[ 17.364587] 0x000005040000-0x000008000000 : "rootfs2"
[ 17.376494] libphy: orion_mdio_bus: probed
[ 17.380734] mv643xx_eth: MV-643xx 10/100/1000 ethernet driver version 1.4
[ 17.387675] libphy: PHY orion-mdio-mii:00 not found
[ 17.392716] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
[ 17.399225] r8169 0000:00:01.0 eth0: RTL8168d/8111d at 0xd0a24000, 00:00:00:00:00:30, XID 083000c0 IRQ 9
[ 17.408747] r8169 0000:00:01.0 eth0: jumbo features [frames: 9200 bytes, tx checksumming: ko]
[ 17.417490] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 17.424100] ehci-pci: EHCI PCI platform driver
[ 17.428641] ehci-orion: EHCI orion driver
[ 17.432769] orion-ehci orion-ehci.0: EHCI Host Controller
[ 17.438215] orion-ehci orion-ehci.0: new USB bus registered, assigned bus number 1
[ 17.445968] orion-ehci orion-ehci.0: irq 19, io mem 0xf1050000
[ 17.468870] orion-ehci orion-ehci.0: USB 2.0 started, EHCI 1.00
[ 17.475752] hub 1-0:1.0: USB hub found
[ 17.479600] hub 1-0:1.0: 1 port detected
[ 17.484235] usbcore: registered new interface driver uas
[ 17.489748] usbcore: registered new interface driver usb-storage
[ 17.495836] usbcore: registered new interface driver ums-alauda
[ 17.501876] usbcore: registered new interface driver ums-cypress
[ 17.507963] usbcore: registered new interface driver ums-datafab
[ 17.514068] usbcore: registered new interface driver ums_eneub6250
[ 17.520341] usbcore: registered new interface driver ums-freecom
[ 17.526425] usbcore: registered new interface driver ums-isd200
[ 17.532437] usbcore: registered new interface driver ums-jumpshot
[ 17.538612] usbcore: registered new interface driver ums-karma
[ 17.544542] usbcore: registered new interface driver ums-onetouch
[ 17.550751] usbcore: registered new interface driver ums-realtek
[ 17.556833] usbcore: registered new interface driver ums-sddr09
[ 17.562843] usbcore: registered new interface driver ums-sddr55
[ 17.568857] usbcore: registered new interface driver ums-usbat
[ 17.575144] mousedev: PS/2 mouse device common for all mice
[ 17.581260] rtc-mv rtc-mv: rtc core: registered rtc-mv as rtc0
[ 17.587224] i2c /dev entries driver
[ 17.591895] sdhci: Secure Digital Host Controller Interface driver
[ 17.598107] sdhci: Copyright(c) Pierre Ossman
[ 17.602588] sdhci-pltfm: SDHCI platform and OF driver helper
[ 17.608922] orion_gpio_is_valid: invalid GPIO 12
[ 17.614433] ledtrig-cpu: registered to indicate activity on CPUs
[ 17.620604] usbcore: registered new interface driver r8712u
[ 17.626445] gre: GRE over IPv4 demultiplexor driver
[ 17.631423] NET: Registered protocol family 17
[ 17.636007] Key type dns_resolver registered
[ 17.641303] registered taskstats version 1
[ 17.647172] Key type encrypted registered
[ 17.651670] libphy: PHY orion-mdio-mii:00 not found
[ 17.656942] console [netcon0] enabled
[ 17.660690] netconsole: network logging started
[ 17.665650] input: gpio-keys as /devices/platform/gpio-keys/input/input0
[ 17.672818] libphy: PHY orion-mdio-mii:00 not found
[ 17.677829] rtc-mv rtc-mv: setting system clock to 2018-04-27 09:03:08 UTC (1524819788)
[ 17.693378] EXT4-fs (sda2): couldn't mount as ext3 due to feature incompatibilities
[ 17.701615] EXT4-fs (sda2): couldn't mount as ext2 due to feature incompatibilities
[ 17.798869] usb 1-1: new high-speed USB device number 2 using orion-ehci
[ 17.951340] hub 1-1:1.0: USB hub found
[ 17.958871] hub 1-1:1.0: 4 ports detected
[ 17.971530] libphy: PHY orion-mdio-mii:00 not found
[ 17.979448] EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null)
[ 17.987207] VFS: Mounted root (ext4 filesystem) on device 8:2.
[ 18.014786] devtmpfs: mounted
[ 18.018644] Freeing unused kernel memory: 304K
[ 18.845180] NET: Registered protocol family 10
[ 18.895825] ip_tables: (C) 2000-2006 Netfilter Core Team
[ 18.997225] systemd[1]: systemd 238 running in system mode. (+PAM -AUDIT -SELINUX -IMA -APPARMOR +SMACK -SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN +PCRE2 default-hierarchy=hybrid)
[ 19.019125] systemd[1]: Detected architecture arm.
[ 19.086761] systemd[1]: Set hostname to <alarm>.
[ 19.889006] systemd[1]: File /usr/lib/systemd/system/systemd-journald.service:35 configures an IP firewall (IPAddressDeny=any), but the local system does not support BPF/cgroup based firewalling.
[ 19.906560] systemd[1]: Proceeding WITHOUT firewalling in effect! (This warning is only shown for the first loaded unit using IP firewalling.)
[ 20.250952] systemd[1]: Configuration file /etc/systemd/system/led.service is marked executable. Please remove executable permission bits. Proceeding anyway.
[ 20.280605] systemd[1]: /etc/systemd/system/led.service:10: Ignoring unknown escape sequences: "/usr/bin/echo default-on > /sys/class/leds/nsa310\:green\:System/trigger"
[ 20.295933] systemd[1]: /etc/systemd/system/led.service:11: Ignoring unknown escape sequences: "/usr/bin/echo ide-disk1 > /sys/class/leds/nsa310\:green\:SATA1/trigger"
[ 20.311076] systemd[1]: /etc/systemd/system/led.service:12: Ignoring unknown escape sequences: "/usr/bin/echo none > /sys/class/leds/nsa310\:green\:System/trigger"
[ 20.325861] systemd[1]: /etc/systemd/system/led.service:13: Ignoring unknown escape sequences: "/usr/bin/echo none > /sys/class/leds/nsa310\:green\:System/trigger"
[ 20.379916] random: systemd: uninitialized urandom read (16 bytes read, 83 bits of entropy available)
[ 20.393190] systemd[1]: Created slice system-getty.slice.
[ 20.419131] random: systemd: uninitialized urandom read (16 bytes read, 83 bits of entropy available)
[ 20.429056] systemd[1]: Listening on Journal Socket (/dev/log).
[ 20.459059] random: systemd: uninitialized urandom read (16 bytes read, 83 bits of entropy available)
[ 20.469743] systemd[1]: Created slice system-serial\x2dgetty.slice.
[ 20.499071] random: systemd: uninitialized urandom read (16 bytes read, 83 bits of entropy available)
[ 20.508440] systemd[1]: Reached target Remote File Systems.
[ 20.529124] random: systemd: uninitialized urandom read (16 bytes read, 83 bits of entropy available)
[ 20.538830] systemd[1]: Listening on /dev/initctl Compatibility Named Pipe.
[ 20.569428] random: systemd: uninitialized urandom read (16 bytes read, 84 bits of entropy available)
[ 20.579412] systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point.
[ 20.609137] random: systemd: uninitialized urandom read (16 bytes read, 84 bits of entropy available)
[ 20.632031] systemd[1]: Listening on Process Core Dump Socket.
[ 20.659119] random: systemd: uninitialized urandom read (16 bytes read, 88 bits of entropy available)
[ 20.668996] systemd[1]: Listening on udev Control Socket.
[ 20.689092] random: systemd: uninitialized urandom read (16 bytes read, 88 bits of entropy available)
[ 20.698455] systemd[1]: Reached target Local File Systems.
[ 20.719087] random: systemd: uninitialized urandom read (16 bytes read, 88 bits of entropy available)
[ 20.728676] systemd[1]: Started Dispatch Password Requests to Console Directory Watch.
[ 20.759535] systemd[1]: Listening on LVM2 metadata daemon socket.
[ 20.789716] systemd[1]: Listening on Journal Socket.
[ 20.823691] systemd[1]: Starting Rebuild Dynamic Linker Cache...
[ 20.857422] systemd[1]: Starting Create System Users...
[ 20.894230] systemd[1]: Mounting POSIX Message Queue File System...
[ 20.934762] systemd[1]: Starting Rebuild Journal Catalog...
[ 21.062803] systemd[1]: Mounting Kernel Debug File System...
[ 21.320935] systemd[1]: Starting Create list of required static device nodes for the current kernel...
[ 21.444045] systemd[1]: Starting LED control service...
[ 21.533442] systemd[1]: Activating swap /swapfile...
[ 21.593536] ------------[ cut here ]------------
[ 21.598195] WARNING: CPU: 0 PID: 143 at drivers/gpio/gpiolib.c:85 gpio_to_desc+0xa4/0x118()
[ 21.609549] systemd[1]: Started Forward Password Requests to Wall Directory Watch.
[ 21.691391] invalid GPIO -813686336
[ 21.695408] Modules linked in: ip_tables x_tables ipv6
[ 21.709307] systemd[1]: Reached target Local Encrypted Volumes.
[ 21.748621] systemd[1]: Reached target Paths.

[ 21.765868] CPU: 0 PID: 143 Comm: echo Not tainted 4.4.97-1-ARCH #1
[ 21.778030] systemd[1]: Listening on Device-mapper event daemon FIFOs.
[ 21.793654] Hardware name: Zyxel NSA-310
[ 21.801820] [<c001047c>] (unwind_backtrace) from [<c000d978>] (show_stack+0x10/0x14)
[ 21.833799] systemd[1]: Starting Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling...
[ 21.844328] [<c000d978>] (show_stack) from [<c002086c>] (warn_slowpath_common+0x80/0xb8)
[ 21.879009] [<c002086c>] (warn_slowpath_common) from [<c00208d4>] (warn_slowpath_fmt+0x30/0x40)
[ 21.923521] systemd[1]: Created slice User and Session Slice.
[ 21.929432] [<c00208d4>] (warn_slowpath_fmt) from [<c03bd0a8>] (gpio_to_desc+0xa4/0x118)
[ 21.969328] [<c03bd0a8>] (gpio_to_desc) from [<c001c308>] (nsa310_gpio_blink_set+0x40/0x50)
[ 21.983665] systemd[1]: Reached target Slices.
[ 22.050727] [<c001c308>] (nsa310_gpio_blink_set) from [<c05337f8>] (gpio_led_set+0x40/0x74)
[ 22.088949] [<c05337f8>] (gpio_led_set) from [<c0533068>] (led_trigger_set+0xb8/0x1c8)
[ 22.098949] [<c0533068>] (led_trigger_set) from [<c053326c>] (led_trigger_store+0xc8/0x124)
[ 22.107351] [<c053326c>] (led_trigger_store) from [<c01a2630>] (kernfs_fop_write+0xb8/0x1b0)
[ 22.138910] [<c01a2630>] (kernfs_fop_write) from [<c012bd54>] (vfs_write+0x90/0x1a4)
[ 22.146698] [<c012bd54>] (vfs_write) from [<c012c70c>] (SyS_write+0x40/0x98)
[ 22.178954] [<c012c70c>] (SyS_write) from [<c000a400>] (ret_fast_syscall+0x0/0x38)
[ 22.186568] ---[ end trace 08b92a1fc8f0cc1d ]---
[ 22.243071] systemd[1]: Starting Journal Service...
[ 22.333158] systemd[1]: Listening on udev Kernel Socket.
[ 22.394009] systemd[1]: Starting udev Coldplug all Devices...
[ 22.428135] random: nonblocking pool is initialized
[ 22.489944] systemd[1]: Listening on LVM2 poll daemon socket.
[ 22.613640] systemd[1]: Mounting FUSE Control File System...
[ 22.714216] systemd[1]: Starting Apply Kernel Variables...
[ 22.869164] systemd[1]: Listening on Network Service Netlink Socket.
[ 22.935336] systemd[1]: Starting Load/Save Random Seed...
[ 23.067241] systemd[1]: Started Create System Users.
[ 23.120052] Adding 1048572k swap on /swapfile. Priority:-1 extents:2 across:1179644k
[ 23.169864] systemd[1]: Activated swap /swapfile.
[ 23.221750] systemd[1]: Started Rebuild Dynamic Linker Cache.
[ 23.291787] systemd[1]: Mounted POSIX Message Queue File System.
[ 23.321756] systemd[1]: Started Rebuild Journal Catalog.
[ 23.357210] systemd[1]: Mounted Kernel Debug File System.
[ 23.391637] systemd[1]: Started Create list of required static device nodes for the current kernel.
[ 23.447582] systemd[1]: Mounted FUSE Control File System.
[ 23.561706] systemd[1]: Started Apply Kernel Variables.
[ 23.621730] systemd[1]: Started Load/Save Random Seed.
[ 23.681775] systemd[1]: Started LED control service.
[ 23.782064] systemd[1]: Started LVM2 metadata daemon.
[ 23.811358] systemd[1]: Reached target Swap.
[ 23.854174] systemd[1]: Starting Create Static Device Nodes in /dev...
[ 23.983952] systemd[1]: Starting Update is Completed...
[ 24.241668] systemd[1]: Started Update is Completed.
[ 24.321547] systemd[1]: Started Create Static Device Nodes in /dev.
[ 24.364618] systemd[1]: Starting udev Kernel Device Manager...
[ 24.738476] systemd[1]: Started udev Kernel Device Manager.
[ 24.789813] systemd[1]: Started Journal Service.
[ 25.287078] systemd-journald[154]: Received request to flush runtime journal from PID 1
[ 25.660497] rtc-pcf8563 0-0051: chip found, driver version 0.4.4
[ 25.681503] MV-CESA:Could not register sha1 driver
[ 25.686322] MV-CESA:Could not register hmac-sha1 driver
[ 25.699431] rtc-pcf8563 0-0051: pcf8563_write_block_data: err=-6 addr=0e, data=03
[ 25.716184] libphy: PHY orion-mdio-mii:00 not found
[ 25.721830] rtc-pcf8563 0-0051: pcf8563_probe: write error
[ 25.727382] rtc-pcf8563: probe of 0-0051 failed with error -5
[ 25.919633] r8169 0000:00:01.0 enp0s1: renamed from eth0
[ 26.790422] r8169 0000:00:01.0 enp0s1: link down
[ 26.795087] r8169 0000:00:01.0 enp0s1: link down
[ 26.846121] IPv6: ADDRCONF(NETDEV_UP): enp0s1: link is not ready
[ 28.830320] r8169 0000:00:01.0 enp0s1: link up
[ 28.836573] IPv6: ADDRCONF(NETDEV_CHANGE): enp0s1: link becomes ready
[ 31.358885] USB power enabled
[END]
')
$this->bbcode_second_pass_quote('', 'y')ou get lines line:

Yes, as you see above I have those lines.
Regarding nand errors I found this:
http://forum.nas-central.org/viewtopic. ... 607#p22755
I think it's highly related, but I don't know if/how I can apply this patch somehow on my kernel...
[EDIT]and this: viewtopic.php?f=53&t=9299&start=20#p48851
arti74
 
Posts: 75
Joined: Tue Apr 17, 2018 10:33 am

Re: Bad eraseblocks on NSA310 (4.4.97-1-ARCH) & uboot update

Postby summers » Fri Apr 27, 2018 11:07 am

The critical line in the dmesg is:

$this->bbcode_second_pass_code('', '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) root=/dev/sda2 rw rootwait loglevel=8')

Check how /etc/fw_env.config is set up - is it just access /dev/mtd0 and trying to go beyond 0x100000, if so thats all your kernel has set up.

Oh yes - not my script was for nsa325 - so you'll need to check it for the nsa310. My advice is change it to print things out - so you can see if things are defined right. So you'll need to read the install script, see what it is trying to do, then try and work out why it doesn't work on your machine ...

And the scary bit of the log:

$this->bbcode_second_pass_code('', '[ 12.415523] nand: device found, Manufacturer ID: 0xec, Chip ID: 0xf1
[ 12.422142] nand: Samsung NAND 128MiB 3,3V 8-bit
[ 12.426784] nand: 128 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
[ 12.434418] Scanning device for bad blocks
[ 12.438580] Bad eraseblock 0 at 0x000000000000
[ 12.443121] Bad eraseblock 1 at 0x000000020000
[ 12.447626] Bad eraseblock 2 at 0x000000040000
[ 12.452143] Bad eraseblock 3 at 0x000000060000
[ 12.456641] Bad eraseblock 4 at 0x000000080000
[ 12.461157] Bad eraseblock 5 at 0x0000000a0000
[ 12.465658] Bad eraseblock 6 at 0x0000000c0000
[ 12.470174] Bad eraseblock 7 at 0x0000000e0000
[ 12.474675] Bad eraseblock 8 at 0x000000100000
[ 12.479189] Bad eraseblock 9 at 0x000000120000
[ 12.483691] Bad eraseblock 10 at 0x000000140000
........... - cutted
[ 12.925481] Bad eraseblock 106 at 0x000000d40000
[ 12.930155] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl F300)
[ 12.936623] Bad eraseblock 107 at 0x000000d60000
[ 12.941331] Bad eraseblock 108 at 0x000000d80000
[ 12.946008] Bad eraseblock 109 at 0x000000da0000
[ 12.950893] ata1.00: ATA-7: SAMSUNG HD753LJ, 1AA01110, max UDMA7
[ 12.956925] ata1.00: 1465149168 sectors, multi 0: LBA48 NCQ (depth 31/32)
[ 12.963810] Bad eraseblock 110 at 0x000000dc0000
...........
[ 12.996855] Bad eraseblock 117 at 0x000000ea0000
[ 13.001725] ata1.00: configured for UDMA/133
[ 13.006081] Bad eraseblock 118 at 0x000000ec0000
[ 13.010788] Bad eraseblock 119 at 0x000000ee0000
[ 13.015464] Bad eraseblock 120 at 0x000000f00000
[ 13.020288] Bad eraseblock 121 at 0x000000f20000
[ 13.024968] Bad eraseblock 122 at 0x000000f40000
[ 13.029951] scsi 0:0:0:0: Direct-Access ATA SAMSUNG HD753LJ 1110 PQ: 0 ANSI: 5
[ 13.039377] sd 0:0:0:0: Attached scsi generic sg0 type 0
[ 13.044972] Bad eraseblock 123 at 0x000000f60000
[ 13.049829] sd 0:0:0:0: [sda] 1465149168 512-byte logical blocks: (750 GB/699 GiB)
[ 13.057664] Bad eraseblock 124 at 0x000000f80000
[ 13.062565] sd 0:0:0:0: [sda] Write Protect is off
[ 13.067384] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[ 13.072549] Bad eraseblock 125 at 0x000000fa0000
[ 13.077227] Bad eraseblock 126 at 0x000000fc0000
[ 13.081996] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 13.091146] Bad eraseblock 127 at 0x000000fe0000
[ 13.095818] Bad eraseblock 128 at 0x000001000000
[ 13.101582] Bad eraseblock 129 at 0x000001020000
[ 13.106332] sda: sda1 sda2
[ 13.109453] Bad eraseblock 130 at 0x000001040000
[ 13.114131] Bad eraseblock 131 at 0x000001060000
[ 13.118803] Bad eraseblock 132 at 0x000001080000
[ 13.124747] sd 0:0:0:0: [sda] Attached SCSI disk
[ 13.129495] Bad eraseblock 133 at 0x0000010a0000
[ 13.134169] Bad eraseblock 134 at 0x0000010c0000
[ 13.138884] Bad eraseblock 135 at 0x0000010e0000
...........
[ 13.396501] Bad eraseblock 190 at 0x0000017c0000
[ 13.401172] ata2: SATA link down (SStatus 0 SControl F300)
[ 13.406759] Bad eraseblock 191 at 0x0000017e0000
...........
[ 17.294776] Bad eraseblock 1021 at 0x000007fa0000
[ 17.299554] Bad eraseblock 1022 at 0x000007fc0000
[ 17.304316] Bad eraseblock 1023 at 0x000007fe0000
[ 17.309078] 9 cmdlinepart partitions found on MTD device orion_nand
[ 17.315369] Creating 9 MTD partitions on "orion_nand":
[ 17.320546] 0x000000000000-0x000000100000 : "uboot"
[ 17.325955] 0x000000100000-0x000000180000 : "uboot_env"
[ 17.331683] 0x000000180000-0x000000200000 : "key_store"
[ 17.337391] 0x000000200000-0x000000280000 : "info"
[ 17.342656] 0x000000280000-0x000000c80000 : "etc"
[ 17.347802] 0x000000c80000-0x000001680000 : "kernel_1"
[ 17.353420] 0x000001680000-0x000004640000 : "rootfs1"
[ 17.358993] 0x000004640000-0x000005040000 : "kernel_2"
[ 17.364587] 0x000005040000-0x000008000000 : "rootfs2"')

Don't think I've ever seen bad blocks like that - something strange going on.
Last edited by summers on Fri Apr 27, 2018 12:08 pm, edited 1 time in total.
summers
 
Posts: 984
Joined: Sat Sep 06, 2014 12:56 pm

Re: Bad eraseblocks on NSA310 (4.4.97-1-ARCH) & uboot update

Postby arti74 » Fri Apr 27, 2018 11:19 am

$this->bbcode_second_pass_quote('', 'C')heck how /etc/fw_env.config is set up

I can only show you this:
$this->bbcode_second_pass_code('', 'cat /etc/fw_env.config
/dev/mtd0 0xc0000 0x20000 0x20000')
That's all there.
I appreciate your help, but I'm new to this...
Regarding the script, I'll try utilize it line by line, I guess.

[EDIT]first commands from your script:
$this->bbcode_second_pass_code('', 'sudo mtdinfo /dev/mtd0 | egrep "Device is writable"
Device is writable: true')
$this->bbcode_second_pass_code('', 'sudo fw_printenv | sed -n 's/^ethaddr=\(.*\)/\1/p'
Too few good blocks within range')
$this->bbcode_second_pass_code('', 'cat /sys/devices/platform/orion_nand/mtd/mtd1/offset
1048576')
$this->bbcode_second_pass_code('', 'cat /etc/fw_env.config
/dev/mtd0 0xc0000 0x20000 0x20000')
arti74
 
Posts: 75
Joined: Tue Apr 17, 2018 10:33 am

Re: Bad eraseblocks on NSA310 (4.4.97-1-ARCH) & uboot update

Postby summers » Fri Apr 27, 2018 12:13 pm

$this->bbcode_second_pass_code('', '/dev/mtd0 0xc0000 0x20000 0x20000')

Trying to remember how that file is set up. Your mtd0 is only 0x100000 long. Ah OK - so can access 0xc0000.

But fw_printenv is giving bad blocks, so it seems to access the right memory.

does $this->bbcode_second_pass_code('', 'dd if=/dev/mtd0 of=/dev/null') work?
summers
 
Posts: 984
Joined: Sat Sep 06, 2014 12:56 pm

Re: Bad eraseblocks on NSA310 (4.4.97-1-ARCH) & uboot update

Postby arti74 » Fri Apr 27, 2018 12:20 pm

$this->bbcode_second_pass_code('', 'dd if=/dev/mtd0 of=/dev/null
2048+0 records in
2048+0 records out
1048576 bytes (1.0 MB, 1.0 MiB) copied, 6.62893 s, 158 kB/s
')
arti74
 
Posts: 75
Joined: Tue Apr 17, 2018 10:33 am

Re: Bad eraseblocks on NSA310 (4.4.97-1-ARCH) & uboot update

Postby summers » Fri Apr 27, 2018 12:50 pm

Also can compare with the stock nand set up from: http://zyxel.nas-central.org/wiki/Some_information_from_slash_proc_%28NSA-310%29

$this->bbcode_second_pass_code('', 'dev: size erasesize name
mtd0: 00100000 00020000 "uboot"
mtd1: 00080000 00020000 "uboot_env"
mtd2: 00080000 00020000 "key_store"
mtd3: 00080000 00020000 "info"
mtd4: 00a00000 00020000 "etc"
mtd5: 00a00000 00020000 "kernel_1"
mtd6: 02fc0000 00020000 "rootfs1"
mtd7: 00a00000 00020000 "kernel_2"
mtd8: 02fc0000 00020000 "rootfs2"')

Whilst you have:

$this->bbcode_second_pass_code('', 'mtd0: 0x100000(uboot)
mtd1: 0x80000(uboot_env)
mtd2: 0x80000(key_store)
mtd3: 0x80000(info)
mtd4: 0xA00000(etc)
mtd5: 0xA00000(kernel_1)
mtd6: 0x2FC0000(rootfs1)
mtd7: 0xA00000(kernel_2)
mtd8: 0x2FC0000(rootfs2)')

So you still seem to have stock nand set up, you can read from it OK via "dd", but fw_printend doesn't work ...

Seems a bit odd.

Ah if the names are correct then /etc/fw_env.config should be
$this->bbcode_second_pass_code('', '/dev/mtd1 0x00000 0x20000 0x20000')
summers
 
Posts: 984
Joined: Sat Sep 06, 2014 12:56 pm

Re: Bad eraseblocks on NSA310 (4.4.97-1-ARCH) & uboot update

Postby arti74 » Fri Apr 27, 2018 1:05 pm

the cat /proc/mtd seems ok..
$this->bbcode_second_pass_code('', 'cat /proc/mtd
dev: size erasesize name
mtd0: 00100000 00020000 "uboot"
mtd1: 00080000 00020000 "uboot_env"
mtd2: 00080000 00020000 "key_store"
mtd3: 00080000 00020000 "info"
mtd4: 00a00000 00020000 "etc"
mtd5: 00a00000 00020000 "kernel_1"
mtd6: 02fc0000 00020000 "rootfs1"
mtd7: 00a00000 00020000 "kernel_2"
mtd8: 02fc0000 00020000 "rootfs2"')
arti74
 
Posts: 75
Joined: Tue Apr 17, 2018 10:33 am

Re: Bad eraseblocks on NSA310 (4.4.97-1-ARCH) & uboot update

Postby summers » Fri Apr 27, 2018 2:23 pm

Yes, so if naming is right suggests making the change above to /etc/fw_env.config, and the running fw_printenv.

If that works - then we know what is going wrong, you have the original uboot that came on the device, and we can work from there on upgrading to new uboot. It was one of the hassles i have with arm arch - that it didn't take into account the default uboot set up ....
summers
 
Posts: 984
Joined: Sat Sep 06, 2014 12:56 pm

Next

Return to Marvell Kirkwood

Who is online

Users browsing this forum: No registered users and 23 guests