Synology DS214+ unbricken

[MsG]

Vanwege het topic van @rikadoo (Synology DS214Play tot leven wekken) werd mijn interesse gewekt om weer eens te prutsen met een gebrickte DS214+ die ik in bezit heb.

Ik hing mijn FTDI adapter er aan, en voila ik had inderdaad terminal output via putty. De initiële fout is een Checksum CRC error.

Deze handleiding heb ik gevolgd: https://conetix.com.au/blog/synology-nas-bootrom-recovery/

Toen heb ik na het een en ander qua DHCP en IP instellen met

tftpboot

de zImage geladen.

Daarna heb ik dan gedaan:

bootm

Dan krijg ik in eerste instantie dat de checksum error weg is.

Maar vervolgens krijg ik deze output:

Marvell>> bootm
## Booting kernel from Legacy Image at 02000000 ...
   Image Name:   Linux-3.2.40
   Created:      2019-05-09  18:48:48 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2123888 Bytes = 2 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
[    0.000000] Booting Linux on physical CPU 0
[    0.000000] Linux version 3.2.40 (root@build10) (gcc version 4.9.3 20150311 (prerelease) (crosstool-NG 1.20.0) ) #24922 SMP Fri May 10 02:48:25 CST 2019
[    0.000000] CPU: Marvell PJ4Bv7 Processor [562f5842] revision 2 (ARMv7), cr=10c53c7d
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction cache
[    0.000000] Machine: Marvell Armada XP Development Board
[    0.000000] Using UBoot passing parameters structure
[    0.000000] Reserving training memory: base=0x  (null) size=0x2800
[    0.000000] Memory policy: ECC disabled, Data cache writealloc
[    0.000000] SMP: init cpus
[    0.000000] PERCPU: Embedded 7 pages/cpu @80dd2000 s5216 r8192 d15264 u32768
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 260096
[    0.000000] Kernel command line: console=ttyS0,115200 ip=off initrd=0x8000040,8M root=/dev/md0 rw syno_hw_version=DS214+ ihd_num=2 netif_num=2 flash_size=8 SataLedSpecial=1 HddHotplug=1
[    0.000000] Synology Hardware Version: DS214+-j
[    0.000000] Internal HD num: 2
[    0.000000] Internal netif num: 2
[    0.000000] Special Sata LEDs.
[    0.000000] Support HDD Hotplug.
[    0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes)
[    0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[    0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[    0.000000] Memory: 1024MB = 1024MB total
[    0.000000] Memory: 1025304k/1025304k available, 23272k reserved, 0K highmem
[    0.000000] Virtual kernel memory layout:
[    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
[    0.000000]     fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
[    0.000000]     vmalloc : 0xc0800000 - 0xfa800000   ( 928 MB)
[    0.000000]     lowmem  : 0x80000000 - 0xc0000000   (1024 MB)
[    0.000000]     modules : 0x7f000000 - 0x80000000   (  16 MB)
[    0.000000]       .text : 0x80008000 - 0x80513000   (5164 kB)
[    0.000000]       .init : 0x80513000 - 0x80544460   ( 198 kB)
[    0.000000]       .data : 0x80546000 - 0x8056cee0   ( 156 kB)
[    0.000000]        .bss : 0x8056cf04 - 0x805cbbcc   ( 380 kB)
[    0.000000] Hierarchical RCU implementation.
[    0.000000]  RCU dyntick-idle grace-period acceleration is enabled.
[    0.000000] NR_IRQS:211
[    0.000000] Initializing ArmadaXP SOC Timer 0
[    0.000000] sched_clock: 32 bits at 25MHz, resolution 40ns, wraps every 171798ms
[   61.942549] Calibrating delay loop... 1332.01 BogoMIPS (lpj=6660096)
[   62.032469] pid_max: default: 32768 minimum: 301
[   62.032600] Security Framework initialized
[   62.032626] AppArmor: AppArmor initialized
[   62.032686] Mount-cache hash table entries: 512
[   62.033107] CPU: Testing write buffer coherency: ok
[   62.033235] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[   62.033248] SMP: prepare CPUs (4 cores)
[   62.033427] Setting Clocks for secondary CPUs
[   62.034200] SMP: CPU 0 Waking up CPU 1
[   62.039023] CPU1: Booted secondary processor
[   62.072459] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
[   62.072512] Brought up 2 CPUs
[   62.072526] SMP: Total of 2 processors activated (2664.03 BogoMIPS).
[   62.073137] devtmpfs: initialized
[   62.076741] xor: measuring software checksum speed
[   62.122426]    arm4regs  :  1292.000 MB/sec
[   62.172422]    8regs     :   963.600 MB/sec
[   62.222420]    32regs    :  1114.400 MB/sec
[   62.222428] xor: using function: arm4regs (1292.000 MB/sec)
[   62.222594] NET: Registered protocol family 16
[   62.224863] L0 cache Enabled
[   62.224873] Speculative Prefetch Disabled
[   62.224894] Aurora L2 Cache Enabled
[   62.225073] Support IO coherency.
[   62.328407]
[   62.328412]   Marvell Armada-XP Synology AXP 78230 Board -  Soc: MV78230 B0 LE
[   62.328431]   Detected Tclk 250000000, SysClk 667000000, FabricClk 667000000, PClk 1333000000
[   62.328439]   LSP version: linux-3.2.y-2013_Q1.2p2
[   62.328444]
[   62.329682] Synology ArmadaXP 4-bay GPIO Init
[   62.330135] registered dev#0 asa ehci_marvell
[   62.330446] Marvell USB EHCI Host controller #0: bf8aaa00
[   62.330551] registered dev#1 asa ehci_marvell
[   62.330857] Marvell USB EHCI Host controller #1: bf8aa800
[   62.330967] registered dev#2 asa mv_udc
[   62.331273] Marvell USB Gadget controller #2: bf8aa600
[   62.339089] bio: create slab <bio-0> at 0
[   62.502636] raid6: int32x1    162 MB/s
[   62.672515] raid6: int32x2    246 MB/s
[   62.842544] raid6: int32x4    303 MB/s
[   63.012547] raid6: int32x8    325 MB/s
[   63.012554] raid6: using algorithm int32x8 (325 MB/s)
[   63.013083] SCSI subsystem initialized
[   63.014287] Switching to clocksource axp_clocksource
[   63.014551] AppArmor: AppArmor Filesystem Enabled
[   63.016280] NET: Registered protocol family 2
[   63.016378] IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
[   63.016630] TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
[   63.017637] TCP bind hash table entries: 65536 (order: 7, 524288 bytes)
[   63.018041] TCP: Hash tables configured (established 131072 bind 65536)
[   63.018049] TCP reno registered
[   63.018059] UDP hash table entries: 512 (order: 2, 16384 bytes)
[   63.018086] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
[   63.018222] NET: Registered protocol family 1
[   63.018397] RPC: Registered named UNIX socket transport module.
[   63.018406] RPC: Registered udp transport module.
[   63.018412] RPC: Registered tcp transport module.
[   63.018418] RPC: Registered tcp NFSv4.1 backchannel transport module.
[   63.018577] Trying to unpack rootfs image as initramfs...
[   64.586746] rootfs image is not initramfs (LZMA data is corrupt); looks like an initrd
[   64.600669] Freeing initrd memory: 8192K
[   64.600766] PCI-E: Cheking physical bus #0 (controller #0): Enabled - Link UP
[   64.600957] PCI-E: Cheking physical bus #1 (controller #4): Enabled - Link UP
[   64.601129] PCI-E: Cheking physical bus #2 (controller #5): Enabled - No Link
[   64.601295] PCI-E: Cheking physical bus #3 (controller #6): Enabled - No Link
[   64.602041] PCI: bus0: Fast back to back transfers disabled
[   64.602616] PCI: bus1: Fast back to back transfers disabled
[   64.602824] pci 0000:01:00.0: BAR 0: assigned [mem 0xf2800000-0xf2807fff 64bit]
[   64.602842] pci 0000:01:00.0: BAR 0: set to [mem 0xf2800000-0xf2807fff 64bit] (PCI address [0xf2800000-0xf2807fff])
[   64.602856] pci 0000:00:00.0: BAR 0: assigned [mem 0xf2000000-0xf20fffff 64bit]
[   64.602872] pci 0000:00:00.0: BAR 0: set to [mem 0xf2000000-0xf20fffff 64bit] (PCI address [0xf2000000-0xf20fffff])
[   64.602884] pci 0000:00:00.0: BAR 2: can't assign io (size 0x100)
[   64.603280] cesadev_init(8051bdb0)
[   64.603841] Armada XP hwmon thermal sensor initialized.
[   64.603933] ArmadaXP Power Managament Suspend Operations Initialized
[   64.603942] Initializing Armada-XP CPU power management  (WFI)
[   64.604594] audit: initializing netlink socket (disabled)
[   64.604626] type=2000 audit(2.660:1): initialized
[   64.605082] VFS: Disk quotas dquot_6.5.2
[   64.605149] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[   64.605831] msgmni has been set to 2018
[   64.606650] async_tx: api initialized (async)
[   64.606794] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 254)
[   64.606805] io scheduler noop registered
[   64.606852] io scheduler cfq registered (default)
[   64.606910] mv_xor_shared mv_xor_shared.0: Marvell shared XOR driver
[   64.606944] mv_xor_shared mv_xor_shared.1: Marvell shared XOR driver
[   64.644374] mv_xor mv_xor.0: Marvell XOR: ( xor cpy )
[   64.684350] mv_xor mv_xor.1: Marvell XOR: ( xor fill cpy )
[   64.704340] mv_xor mv_xor.2: Marvell XOR: ( xor )
[   64.724341] mv_xor mv_xor.3: Marvell XOR: ( fill cpy )
[   64.724770] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
[   64.804519] serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 41) is a 16550A
[   65.511044] console [ttyS0] enabled
[   65.544483] serial8250.1: ttyS1 at MMIO 0xf1012100 (irq = 42) is a 16550A
[   65.600281] brd: module loaded
[   65.603347] Loading iSCSI transport class v2.0-870.
[   65.609167] sata_mv 0000:00:00.0: Gen-IIE 32 slots 4 ports SCSI mode IRQ via INTx
[   65.618918] scsi0 : sata_mv
[   65.622100] scsi1 : sata_mv
[   65.625233] scsi2 : sata_mv
[   65.628360] scsi3 : sata_mv
[   65.631453] ata1: SATA max UDMA/133 mmio m1048576@0xf2000000 port 0xf2022000 irq 58
[   65.639155] ata2: SATA max UDMA/133 mmio m1048576@0xf2000000 port 0xf2024000 irq 58
[   65.646841] ata3: SATA max UDMA/133 mmio m1048576@0xf2000000 port 0xf2026000 irq 58
[   65.654527] ata4: SATA max UDMA/133 mmio m1048576@0xf2000000 port 0xf2028000 irq 58
[   69.164351] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[   69.184702] ata1.00: ATA-7: ST980813ASG, 3.ADD, max UDMA/133
[   69.190372] ata1.00: 156301488 sectors, multi 0: LBA48 NCQ (depth 31/32)
[   69.234692] ata1.00: configured for UDMA/133
[   69.254566] scsi 0:0:0:0: Direct-Access     ATA      ST980813ASG              3.AD PQ: 0 ANSI: 5
[   69.263928] sd 0:0:0:0: [sda] 156301488 512-byte logical blocks: (80.0 GB/74.5 GiB)
[   69.271811] sd 0:0:0:0: [sda] Write Protect is off
[   69.276710] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[   69.418131]  sda: sda1 sda2
[   69.421866] sd 0:0:0:0: [sda] Attached SCSI disk
[   69.614344] ata2: SATA link down (SStatus 0 SControl 300)
[   69.964341] ata3: SATA link down (SStatus 0 SControl 300)
[   70.314342] ata4: SATA link down (SStatus 0 SControl 300)
[   70.319966] sata_mv sata_mv.0: cannot get clkdev
[   70.324685] sata_mv sata_mv.0: slots 32 ports 2
[   70.330403] scsi4 : sata_mv
[   70.333543] scsi5 : sata_mv
[   70.336630] ata5: SATA max UDMA/133 irq 55
[   70.340742] ata6: SATA max UDMA/133 irq 55
[   70.694331] ata5: SATA link down (SStatus 0 SControl F300)
[   71.764327] ata6: failed to resume link (SControl 4)
[   71.769315] ata6: SATA link down (SStatus 0 SControl 4)
[   71.775480] physmap platform flash device: 00800000 at f0000000
[   71.784230] SPI Serial flash detected @ 0xf0000000, 8192KB (128sec x 64KB)
[   71.791153] Searching for RedBoot partition table in SYNOMTD-0 at offset 0x7f0000
[   71.836380] 6 RedBoot partitions found on MTD device SYNOMTD-0
[   71.842231] SYNOMTD flash bank 0: Using RedBoot partition definition
[   71.848611] Creating 6 MTD partitions on "SYNOMTD-0":
[   71.853680] 0x000000000000-0x0000000d0000 : "RedBoot"
[   71.859557] 0x0000000d0000-0x0000003a0000 : "zImage"
[   71.865314] 0x0000003a0000-0x0000007d0000 : "rd.gz"
[   71.870968] 0x0000007d0000-0x0000007e0000 : "vendor"
[   71.876042] vender Mac0 address : 00:11:32:27:2a:53
[   71.880937] vender Mac1 address : 00:11:32:27:2a:54
[   71.885837] vender Mac2 doesn't set ucSum:0x00 Buf:0x00 Sum:0.
[   71.891687] vender Mac3 doesn't set ucSum:0x00 Buf:0x00 Sum:0.
[   71.897544] serial number='13A0M7N005418'
[   71.902160] 0x0000007e0000-0x0000007f0000 : "RedBoot Config"
[   71.908815] 0x0000007f0000-0x000000800000 : "FIS directory"
[   71.915305] mv_eth_probe: port_mask=0xf, cpu_mask=0x3
[   71.920652]   o 4 Giga ports supported
[   71.924442]   o SKB recycle supported (Enabled)
[   71.928985]   o NETA acceleration mode 2
[   71.932918]   o BM supported for CPU: 4 BM pools
[   71.937556]   o RX Queue support: 1 Queues * 128 Descriptors
[   71.943232]   o TX Queue support: 1 Queues * 532 Descriptors
[   71.948912]   o GSO supported
[   71.951887]   o GRO supported
[   71.954868]   o Receive checksum offload supported
[   71.959673]   o Transmit checksum offload supported
[   71.964568]   o Driver ERROR statistics enabled
[   71.969110]
[   71.970781]   o Loading network interface(s)
[   71.975076]
[   71.976572]   o Port 0 is connected to Linux netdevice
[   71.982131]  giga p=0: mtu=1500, mac=bf835e44
[   71.990390]     o eth0, ifindex = 2, GbE port = 0
[   71.994970]     o eth0, phy chipid = 1410dd0, Support WOL = 32
[   72.001003]
[   72.002507]
[   72.004002]   o Port 1 is connected to Linux netdevice
[   72.009570]  giga p=1: mtu=1500, mac=bf835e44
[   72.017798]     o eth1, ifindex = 3, GbE port = 1
[   72.022343]     o eth1, phy chipid = 1410dd0, Support WOL = 32
[   72.028415]
[   72.029913]
[   72.029915]   o Warning: GbE port 2 is powered off
[   72.029918]
[   72.037707]
[   72.039443] i2c /dev entries driver
[   72.043479] Syno_HddMon: Initialization completed.
[   72.048302] md: linear personality registered for level -1
[   72.053804] md: raid0 personality registered for level 0
[   72.059137] md: raid1 personality registered for level 1
[   72.064469] md: raid10 personality registered for level 10
[   72.069971] md: raid6 personality registered for level 6
[   72.075302] md: raid5 personality registered for level 5
[   72.080629] md: raid4 personality registered for level 4
[   72.086258] device-mapper: ioctl: 4.22.0-ioctl (2011-10-19) initialised: [e-mail]
[   72.094912] cpuidle: using governor ladder
[   72.099345] cpuidle: using governor menu
[   72.103410] TCP cubic registered
[   72.106659] NET: Registered protocol family 17
[   72.111147] Registering the dns_resolver key type
[   72.115974] VFP support v0.3: implementor 56 architecture 2 part 20 variant 9 rev 6
[   72.124123] registered taskstats version 1
[   72.128528] md: Waiting for all devices to be available before autodetect
[   72.135344] md: If you don't use raid, use raid=noautodetect
[   72.141506] md: Autodetecting RAID arrays.
[   72.145630] md: Scanned 0 and added 0 devices.
[   72.150086] md: autorun ...
[   72.152888] md: ... autorun DONE.
[   72.156299] RAMDISK: lzma image found at block 0
[   73.722472] LZMA data is corrupt
[   73.740827] EXT3-fs (md0): error: unable to read superblock
[   73.746592] EXT2-fs (md0): error: unable to read superblock
[   73.752305] EXT4-fs (md0): unable to read superblock
[   73.757332] List of all partitions:
[   73.760846] 0800        78150744 sda  driver: sd
[   73.765502]   0801          120456 sda1 00000000-0000-0000-0000-000000000000
[   73.772585]   0802        78019672 sda2 00000000-0000-0000-0000-000000000000
[   73.779678] 1f00             832 mtdblock0  (driver?)
[   73.784764] 1f01            2880 mtdblock1  (driver?)
[   73.789845] 1f02            4288 mtdblock2  (driver?)
[   73.794930] 1f03              64 mtdblock3  (driver?)
[   73.800010] 1f04              64 mtdblock4  (driver?)
[   73.805095] 1f05              64 mtdblock5  (driver?)
[   73.810172] No filesystem could mount root, tried:  ext3 ext2 ext4
[   73.816428] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(9,0)
[   73.824719] Backtrace:
[   73.827202] [<80011f60>] (dump_backtrace+0x0/0x108) from [<803edd20>] (dump_stack+0x18/0x1c)
[   73.835671]  r7:bb79c260 r6:bb77400f r5:8053ba2c r4:8056eb50
[   73.841399] [<803edd08>] (dump_stack+0x0/0x1c) from [<803ee05c>] (panic+0x70/0x190)
[   73.849093] [<803edfec>] (panic+0x0/0x190) from [<80513f34>] (change_floppy+0x0/0xec)
[   73.856953]  r3:bf835f38 r2:00000020 r1:bf835f38 r0:8049eb3c
[   73.862678]  r7:bb79c260
[   73.865241] [<80513be4>] (mount_block_root+0x0/0x350) from [<80514088>] (mount_root+0x68/0x6c)
[   73.873882] [<80514020>] (mount_root+0x0/0x6c) from [<80514228>] (prepare_namespace+0x19c/0x1e0)
[   73.882697]  r5:8053ba2c r4:8056d060
[   73.886317] [<8051408c>] (prepare_namespace+0x0/0x1e0) from [<80513a80>] (kernel_init+0x1cc/0x1d4)
[   73.895308]  r6:8056d000 r5:8053ba08 r4:00000008
[   73.899984] [<805138b4>] (kernel_init+0x0/0x1d4) from [<80059848>] (do_exit+0x0/0x70c)
[   73.907928]  r7:00000013
[   73.910485] CPU0: stopping
[   73.913201] Backtrace:
[   73.915676] [<80011f60>] (dump_backtrace+0x0/0x108) from [<803edd20>] (dump_stack+0x18/0x1c)
[   73.924139]  r7:80546030 r6:00000000 r5:80550978 r4:8056d2ec
[   73.929867] [<803edd08>] (dump_stack+0x0/0x1c) from [<80013bec>] (handle_IPI+0x158/0x174)
[   73.938072] [<80013a94>] (handle_IPI+0x0/0x174) from [<8000835c>] (do_IPI+0x10/0x14)
[   73.945838]  r9:80546000 r8:805c5900 r7:80547f1c r6:fbc21000 r5:80000013
[   73.952433] r4:80043980
[   73.955086] [<8000834c>] (do_IPI+0x0/0x14) from [<8000de74>] (__irq_svc+0x34/0xe8)
[   73.962677] Exception stack(0x80547ee8 to 0x80547f30)
[   73.967746] 7ee0:                   5318d269 0000000b 0000000b 000ebe20 00000000 80dd20e8
[   73.975952] 7f00: 805580e0 00000000 805c5900 80546000 00000000 80547f54 0000000b 80547f30
[   73.984154] 7f20: 027ffffc 80043980 80000013 ffffffff
[   73.989231] [<8004392c>] (armadaxp_enter_idle+0x0/0xb0) from [<8032b490>] (cpuidle_idle_call+0xb8/0x12c)
[   73.998738]  r5:00000000 r4:80dd20e8
[   74.002351] [<8032b3d8>] (cpuidle_idle_call+0x0/0x12c) from [<8000f880>] (cpu_idle+0xa0/0xf8)
[   74.010900]  r9:80546000 r8:803f5d18 r7:80553c44 r6:80546000 r5:80546000
[   74.017495] r4:8056d0c4
[   74.020150] [<8000f7e0>] (cpu_idle+0x0/0xf8) from [<803e3c24>] (rest_init+0x78/0x7c)
[   74.027915]  r9:562f5842 r8:8053d43c r7:80dcf120 r6:8056d000 r5:00000000
[   74.034510] r4:80550798
[   74.037166] [<803e3bac>] (rest_init+0x0/0x7c) from [<805138a8>] (start_kernel+0x310/0x31c)
[   74.045459] [<80513598>] (start_kernel+0x0/0x31c) from [<00008040>] (0x8040)
[   74.052527]  r8:0000406a r7:80553c3c r6:8053d438 r5:80550700 r4:10c53c7d

Relevante gegevens:

Environment

Marvell>> printenv
CASset=min
MALLOC_len=5
MPmode=smp
amp_enable=no
autoload=no
baudrate=115200
boot_order=hd_scr hd_img pxe net_img net_scr
bootargs=console=ttyS0,115200 ip=off initrd=0x8000040,8M root=/dev/md0 rw syno_hw_version=DS214+ ihd_num=2 netif_num=2 flash_size=8 SataLedSpecial=1 HddHotplug=1
bootargs_dflt=$console $mtdparts $bootargs_root nfsroot=$serverip:$rootpath ip=$ipaddr:$serverip$bootargs_end $mvNetConfig video=dovefb:lcd0:$lcd0_params clcd.lcd0_enable=$lcd0_enable clcd.lcd_panel=$lcd_panel
bootargs_end=:10.4.50.254:255.255.255.0:DSMP:eth0:none
bootargs_root=root=/dev/nfs rw
bootcmd=bootm 0xf40d0000 0xf43a0000
bootcmd_auto=stage_boot $boot_order
bootcmd_lgcy=tftpboot 0x2000000 $image_name; setenv bootargs $bootargs_dflt; bootm 0x2000000;
bootdelay=3
cacheShare=no
console=console=ttyS0,115200
device_partition=0:1
disL2Cache=yes
disL2Prefetch=yes
disaMvPnp=no
eeeEnable=no
enaAutoRecovery=yes
enaClockGating=no
enaCpuStream=no
enaDCPref=yes
enaFPU=yes
enaICPref=yes
enaLPAE=no
enaWrAllo=no
eth1addr=00:50:43:02:00:00
eth1mtu=1500
eth2addr=00:50:43:00:00:02
eth2mtu=1500
eth3addr=00:50:43:00:02:02
eth3mtu=1500
ethact=egiga0
ethaddr=00:50:43:02:02:00
ethmtu=1500
ethprime=egiga0
fdt_addr=2040000
ide_path=/
image_name=uImage
initrd_name=uInitrd
ipaddr=10.4.50.165
kernel_addr_r=2080000
lcd0_enable=0
lcd0_params=640x480-16@60
lcd_panel=0
loadaddr=0x02000000
loads_echo=0
mvNetConfig=mv_net_config=4,(00:50:43:11:11:11,0:1:2:3),mtu=1500
mv_pon_addr=00:50:43:00:00:02
netbsd_en=no
netmask=255.255.255.0
netretry=no
pcieTune=no
pexMode=rc
pxe_files_load=:default.arm-armadaxp-db:default.arm-armadaxp:default.arm
pxefile_addr_r=3100000
ramdisk_addr_r=2880000
rcvrip=169.254.100.100
rootpath=/srv/nfs/
sata_delay_reset=0
sata_dma_mode=yes
script_addr_r=3000000
script_name=boot.scr
serverip=10.4.50.5
setL2CacheWT=no
standalone=fsload 0x2000000 $image_name;setenv bootargs $console $mtdparts root=/dev/mtdblock0 rw ip=$ipaddr:$serverip$bootargs_end; bootm 0x2000000;
stderr=serial
stdin=serial
stdout=serial
usb0Mode=host
usb1Mode=host
usb2Mode=device
usbActive=0
vxworks_en=no
yuk_ethaddr=00:00:00:EE:51:81

Uboot

Marvell>> reset
resetting ...
Marvell>>
BootROM 1.20
Booting from SPI flash
High speed PHY - Version: 2.1.2 (COM-PHY-V20)
Update PEX Device ID 0x78230
High speed PHY - Ended Successfully
                                   DDR3 Training Sequence - Ver 4.5.0
DDR3 Training Sequence - Ended Successfully
Status = MV_OK
BootROM: Image checksum verification PASSED

 __   __                      _ _
|  \/  | __ _ _ ____   _____| | |
| |\/| |/ _` | '__\ \ / / _ \ | |
| |  | | (_| | |   \ V /  __/ | |
|_|  |_|\__,_|_|    \_/ \___|_|_|
         _   _     ____              _
        | | | |   | __ )  ___   ___ | |_
        | | | |___|  _ \ / _ \ / _ \| __|
        | |_| |___| |_) | (_) | (_) | |_
         \___/    |____/ \___/ \___/ \__|
 ** LOADER **


U-Boot 2011.12-SYNO-4484c15-2013-08-06 (Aug 06 2013 - 15:51:15) Marvell version: v2011.12 2013_Q1.2

Board: Synology AXP 78230 4-bay/2-bay
SoC:   MV78230 B0
       running 2 CPUs
       Custom configuration
CPU:   Marvell PJ4B (584) v7 (Rev 2) LE
       CPU 0
       CPU    @ 1333 [MHz]
       L2     @ 667 [MHz]
       TClock @ 250 [MHz]
       DDR    @ 667 [MHz]
       DDR 32Bit Width, FastPath Memory Access
       DDR ECC Disabled
DRAM:  1 GiB

Map:   Code:            0x3fefb000:0x3ff9f56c
       BSS:             0x3ffef33c
       Stack:           0x3f9eaef8
       Heap:            0x3f9eb000:0x3fefb000

MMC:   MRVL_MMC: 0
SF: Detected M25P64 with page size 64 KiB, total 8 MiB
*** Warning - bad CRC, using default environment

PEX 0.0(0): Root Complex Interface, Detected Link X4, GEN 1.1
PEX 1.0(1): Root Complex Interface, Detected Link X1, GEN 2.0
PEX 1.1(2): Detected No Link.
PEX 1.2(3): Detected No Link.
FPU initialized to Run Fast Mode.
USB 0: Host Mode
USB 1: Host Mode
USB 2: Device Mode
Modules Detected:

Synology Model: DS214+
Fan Status: Good

Net:   egiga0 [PRIME], egiga1
Press Ctrl+C to abort autoboot in 3 second
## Booting kernel from Legacy Image at f40d0000 ...
   Image Name:   Linux-3.2.40
   Created:      2019-05-09  18:48:48 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2123888 Bytes = 2 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at f43a0000 ...
   Image Name:   synology_armadaxp_ds214+ 24922
   Created:      2019-05-09  21:23:02 UTC
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    3699905 Bytes = 3.5 MiB
   Load Address: 08000000
   Entry Point:  08000000
   Verifying Checksum ... Bad Data CRC
Ramdisk image is corrupt or invalid

Ik kan na het bootm commando de NAS ook niet pingen, noch zie ik hem in de Synology Windows tool. De NAS blijft tot het eind aan, maar ik kan ook geen nieuwe commando's meer geven, na 'bootm' en de bovenstaande output. Dan moet ik de NAS weer van het stroom halen, en weer via Putty verbinden, waar ik dan eerst weer via tftp de zimage moet downloaden.

Kan iemand me wellicht hiermee verder helpen? Ik zie dat maar heel erg weinig mensen op internet hun Synology NAS überhaupt aan een seriële verbinding gooien, en veelal gewoon blind een nieuwe kopen.

Ik gebruik de NAS nu trouwens zonder schijven. Hij komt defect rechtstreeks uit iemand's RAID setup. Ik heb ook al geprobeerd met een lege schijf de bovenstaande commando's uit te voeren, maar het komt steevast op hetzelfde uit.

[ Voor 11% gewijzigd door MsG op 25-09-2019 21:35 ]

[Thralas]

Je moet óók een ramdisk laden. Of vanaf nand, of via tftp. Vervolgens bootm uitvoeren met 2 argumenten (kernel addr, inird addr).

Post eens de originele bootlog, want uit de u-boot env haal ik nergens dát hij de ramdisk laadt en zoals je de kernel args nu hebt luistert het nogal nauw waar 'ie terechtkomt (zie initrd=).

[rikadoo]

Je moet inderdaad zoals hierboven gezegd is, de zImage bestand en rd.bin bestand laden via tftp. Vervolgens kun je booten met bootm (kernel) (randisk) (als je de exacte locaties weet.

En ik denk dat je de gegevens ook nog naar het flash moet schrijven maar wellicht gebeurd dat automatisch al.

[MsG]

Doet het commando

tftpboot

niet ook al meer dan alleen het bestand verzenden?

Mijn uboot is alsvolgt (reset zelf uitgevoerd, anders heb ik pas te laat een seriële connectie en mis ik het hele Uboot gedeelte):

Marvell>> reset
resetting ...
Marvell>>
BootROM 1.20
Booting from SPI flash
High speed PHY - Version: 2.1.2 (COM-PHY-V20)
Update PEX Device ID 0x78230
High speed PHY - Ended Successfully
                                   DDR3 Training Sequence - Ver 4.5.0
DDR3 Training Sequence - Ended Successfully
Status = MV_OK
BootROM: Image checksum verification PASSED

 __   __                      _ _
|  \/  | __ _ _ ____   _____| | |
| |\/| |/ _` | '__\ \ / / _ \ | |
| |  | | (_| | |   \ V /  __/ | |
|_|  |_|\__,_|_|    \_/ \___|_|_|
         _   _     ____              _
        | | | |   | __ )  ___   ___ | |_
        | | | |___|  _ \ / _ \ / _ \| __|
        | |_| |___| |_) | (_) | (_) | |_
         \___/    |____/ \___/ \___/ \__|
 ** LOADER **


U-Boot 2011.12-SYNO-4484c15-2013-08-06 (Aug 06 2013 - 15:51:15) Marvell version: v2011.12 2013_Q1.2

Board: Synology AXP 78230 4-bay/2-bay
SoC:   MV78230 B0
       running 2 CPUs
       Custom configuration
CPU:   Marvell PJ4B (584) v7 (Rev 2) LE
       CPU 0
       CPU    @ 1333 [MHz]
       L2     @ 667 [MHz]
       TClock @ 250 [MHz]
       DDR    @ 667 [MHz]
       DDR 32Bit Width, FastPath Memory Access
       DDR ECC Disabled
DRAM:  1 GiB

Map:   Code:            0x3fefb000:0x3ff9f56c
       BSS:             0x3ffef33c
       Stack:           0x3f9eaef8
       Heap:            0x3f9eb000:0x3fefb000

MMC:   MRVL_MMC: 0
SF: Detected M25P64 with page size 64 KiB, total 8 MiB
*** Warning - bad CRC, using default environment

PEX 0.0(0): Root Complex Interface, Detected Link X4, GEN 1.1
PEX 1.0(1): Root Complex Interface, Detected Link X1, GEN 2.0
PEX 1.1(2): Detected No Link.
PEX 1.2(3): Detected No Link.
FPU initialized to Run Fast Mode.
USB 0: Host Mode
USB 1: Host Mode
USB 2: Device Mode
Modules Detected:

Synology Model: DS214+
Fan Status: Good

Net:   egiga0 [PRIME], egiga1
Press Ctrl+C to abort autoboot in 3 second
## Booting kernel from Legacy Image at f40d0000 ...
   Image Name:   Linux-3.2.40
   Created:      2019-05-09  18:48:48 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2123888 Bytes = 2 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at f43a0000 ...
   Image Name:   synology_armadaxp_ds214+ 24922
   Created:      2019-05-09  21:23:02 UTC
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    3699905 Bytes = 3.5 MiB
   Load Address: 08000000
   Entry Point:  08000000
   Verifying Checksum ... Bad Data CRC
Ramdisk image is corrupt or invalid

[rikadoo]

Ramdisk image is corrupt or invalid

Lijkt me al genoeg te zeggen.

Zou eens de laatste firmware die je erop had staan (er zit een volgorde van update 5.0->5.2->6.0->6.2), daar de zImage en rd.bin van pakken en die uploaden met tftboot.

Bij mijn intel bootloader werden automatisch de goede locaties gepakt tijdens het uploaden via ymodem, ik hoefde niet de locaties handmatig in te vullen.

tftpboot 0xf40d0000 zImage
tftpboot 0xf43a0000 rd.bin

Zoiets?

[ Voor 7% gewijzigd door rikadoo op 25-09-2019 14:55 ]

[MsG]

rikadoo schreef op woensdag 25 september 2019 @ 14:45:
Ramdisk image is corrupt or invalid

Lijkt me al genoeg te zeggen.

Zou eens de laatste firmware die je erop had staan (er zit een volgorde van update 5.0->5.2->6.0->6.2), daar de zImage en rd.bin van pakken en die uploaden met tftboot.

Bij mijn intel bootloader werden automatisch de goede locaties gepakt tijdens het uploaden via ymodem, ik hoefde niet de locaties handmatig in te vullen.

tftpboot 0xf40d0000 zImage
tftpboot 0xf43a0000 rd.bin

Zoiets?

Die geheugenadressen haal je uit mijn logs? Die Load Adressen zijn weer iets heel anders?

Ik ga eens even spelen met jouw nieuwe inzichten.

Ik weet overigens niet welke firmware er op stond. Is dat nog ergens af te leiden uit logs?


EDIT:

Nu gedaan:

Marveltftpboot 0xf40d0000 zImage
Using egiga0 device
TFTP from server 192.168.1.123; our IP address is 192.168.1.21
Filename 'zImage'.
Load address: 0xf40d0000
Loading: #################################################################
         #################################################################
         ###############
done
Bytes transferred = 2123952 (2068b0 hex)
Marvell>> tftpboot 0xf43a0000 rd.bin
Using egiga0 device
TFTP from server 192.168.1.123; our IP address is 192.168.1.21
Filename 'rd.bin'.
Load address: 0xf43a0000
Loading: #################################################################
         #################################################################
         #################################################################
         ##########################################################
done
Bytes transferred = 3699969 (387501 hex)

Maar als ik bootm doe krijg ik dit:

Marvell>> bootm
## Booting kernel from Legacy Image at f43a0000 ...
   Image Name:   synology_armadaxp_ds214+ 24922
   Created:      2019-05-09  21:23:02 UTC
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    3699905 Bytes = 3.5 MiB
   Load Address: 08000000
   Entry Point:  08000000
   Verifying Checksum ... Bad Data CRC
ERROR: can't get kernel image!
Marvell>> bootm 0xf40d0000 0xf43a0000
## Booting kernel from Legacy Image at f40d0000 ...
   Image Name:   Linux-3.2.40
   Created:      2019-05-09  18:48:48 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2123888 Bytes = 2 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... Bad Data CRC
ERROR: can't get kernel image!

Hoe weet ik nou welke parameters ik moet gebruiken? Het is me net niet helemaal duidelijk. Op internet zie ik vooral geheugenadressen voor oudere of nieuwere synology's.

[ Voor 60% gewijzigd door MsG op 25-09-2019 21:25 ]

[Thralas]

MsG schreef op woensdag 25 september 2019 @ 15:51:
Die geheugenadressen haal je uit mijn logs? Die Load Adressen zijn weer iets heel anders?

Load address is waar de kernel (of ramdisk) hoort te staan, de bootloader handelt de relocation voor je af, je kunt hem dus in principe overal in het geheugen neerzetten.

Ik weet overigens niet welke firmware er op stond. Is dat nog ergens af te leiden uit logs?

Als die boot helemaal vers is: exact dezelfde, kijk maar naar de build times van de ramdisk/kernel. En je kunt natuurlijk de kernel/ramdisk van nand lezen.

Maar als ik bootm doe krijg ik dit:

Niet enkel bootm, dan laadt hij geen initrd.

Hoe weet ik nou welke parameters ik moet gebruiken? Het is me net niet helemaal duidelijk.

Dat was o.a. de reden waarom ik een volledige bootlog vroeg. Meestal is het wijs om gewoon exact dezelfde load adresses aan te houden, want anders moet je weten (1) waar het RAM geheugen is gemapped en (2) waar de bootloader is gemapped en waar de kernel uiteindelijk uitgevoerd wordt. Dáár dus niet.

Nu blijkt dat hij inderdaad gewoon het default boot command volgt: bootm 0xf40d0000 0xf43a0000, dat lijkt dus op het eerste gezicht ook de meest logische plek voor je tftp images zoals @rikadoo suggereerde.

Maarrrrrrrrrr

Dat werkt niet, zo blijkt. want de geladen data lijkt corrupt. Ook:

*** Warning - bad CRC, using default environment

Dus de desbetreffende bootcmd hoeft niet perse te kloppen. Integendeel, ik denk dat hij niet kán kloppen, want:

## Booting kernel from Legacy Image at 02000000 ...
   Image Name:   Linux-3.2.40
   Created:      2019-05-09  18:48:48 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2123888 Bytes = 2 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK

• Kernel load address is 0x8000, én dat werkt, dus je hebt RAM gemapped vanaf 0x0
• Je hebt 1 GB RAM, dus dat is waarschijnlijk 0x00000000 - 0x40000000.
• De bootloader vertelt waar hij gemapped is: mooi aan het ~einde van 1GB
• Alle andere addressen uit je uboot env wijzen er ook naar, bijvoorbeeld die 0x2000000 waar je eerst heen tftpde en een kernel kon booten

Op 0xf0000000 zitten peripherals (spi flash), op 0xf2000000 een SATA controller - allemaal IO memory, geen RAM. Dus op 0xf4000000 óók niet. Er blijven wel wat bitjes plakken (u-boot vindt de kernel/ramdisk header, maar het is sowieso corrupt).

tl;dr

Ik stel voor dat je eens 0x02000000 en 0x02500000 (+5MB) probeert voor kernel resp. ramdisk.

[MsG]

Thanks voor je uitgebreide post. Ik ga met die geheugenplekken aan de slag.

De kernel image is dus die zImage en die rd.bin is dan het initrd/ramdisk ding?

En bedoel je dus dat ik puur een

bootm 0x02000000 0x02500000

draai (na het ftp'en van die bestanden), of dat ik het ook weer eerst op die nieuwe plekken die je aangeeft, in het geheugen laadt middels de tftpboot 0x02000000 zImage en tftpboot 0x02500000 rd.bin ?

Uit ongeduld maar even het laatste gedaan ;-).

En hij lijkt wel door te booten:

Marvell>> tftpboot 0x02000000 zImage
Using egiga0 device
TFTP from server 192.168.1.123; our IP address is 192.168.1.21
Filename 'zImage'.
Load address: 0x2000000
Loading: #################################################################
         #################################################################
         ###############
done
Bytes transferred = 2123952 (2068b0 hex)
Marvell>> tftpboot 0x02500000 rd.bin
Using egiga0 device
TFTP from server 192.168.1.123; our IP address is 192.168.1.21
Filename 'rd.bin'.
Load address: 0x2500000
Loading: #################################################################
         #################################################################
         #################################################################
         ##########################################################
done
Bytes transferred = 3699969 (387501 hex)
Marvell>> bootm 0x02000000 0x02500000
## Booting kernel from Legacy Image at 02000000 ...
   Image Name:   Linux-3.2.40
   Created:      2019-05-09  18:48:48 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2123888 Bytes = 2 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 02500000 ...
   Image Name:   synology_armadaxp_ds214+ 24922
   Created:      2019-05-09  21:23:02 UTC
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    3699905 Bytes = 3.5 MiB
   Load Address: 08000000
   Entry Point:  08000000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
[    0.000000] Booting Linux on physical CPU 0
[    0.000000] Linux version 3.2.40 (root@build10) (gcc version 4.9.3 20150311 (prerelease) (crosstool-NG 1.20.0) ) #24922 SMP Fri May 10 02:48:25 CST 2019
[    0.000000] CPU: Marvell PJ4Bv7 Processor [562f5842] revision 2 (ARMv7), cr=10c53c7d
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction cache
[    0.000000] Machine: Marvell Armada XP Development Board
[    0.000000] Using UBoot passing parameters structure
[    0.000000] Reserving training memory: base=0x  (null) size=0x2800
[    0.000000] Memory policy: ECC disabled, Data cache writealloc
[    0.000000] SMP: init cpus
[    0.000000] PERCPU: Embedded 7 pages/cpu @80dd2000 s5216 r8192 d15264 u32768
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 260096
[    0.000000] Kernel command line: console=ttyS0,115200 ip=off initrd=0x8000040,8M root=/dev/md0 rw syno_hw_version=DS214+ ihd_num=2 netif_num=2 flash_size=8 SataLedSpecial=1 HddHotplug=1
[    0.000000] Synology Hardware Version: DS214+-j
[    0.000000] Internal HD num: 2
[    0.000000] Internal netif num: 2
[    0.000000] Special Sata LEDs.
[    0.000000] Support HDD Hotplug.
[    0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes)
[    0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[    0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[    0.000000] Memory: 1024MB = 1024MB total
[    0.000000] Memory: 1025304k/1025304k available, 23272k reserved, 0K highmem
[    0.000000] Virtual kernel memory layout:
[    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
[    0.000000]     fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
[    0.000000]     vmalloc : 0xc0800000 - 0xfa800000   ( 928 MB)
[    0.000000]     lowmem  : 0x80000000 - 0xc0000000   (1024 MB)
[    0.000000]     modules : 0x7f000000 - 0x80000000   (  16 MB)
[    0.000000]       .text : 0x80008000 - 0x80513000   (5164 kB)
[    0.000000]       .init : 0x80513000 - 0x80544460   ( 198 kB)
[    0.000000]       .data : 0x80546000 - 0x8056cee0   ( 156 kB)
[    0.000000]        .bss : 0x8056cf04 - 0x805cbbcc   ( 380 kB)
[    0.000000] Hierarchical RCU implementation.
[    0.000000]  RCU dyntick-idle grace-period acceleration is enabled.
[    0.000000] NR_IRQS:211
[    0.000000] Initializing ArmadaXP SOC Timer 0
[    0.000000] sched_clock: 32 bits at 25MHz, resolution 40ns, wraps every 171798ms
[   71.358996] Calibrating delay loop... 1332.01 BogoMIPS (lpj=6660096)
[   71.448917] pid_max: default: 32768 minimum: 301
[   71.449047] Security Framework initialized
[   71.449073] AppArmor: AppArmor initialized
[   71.449133] Mount-cache hash table entries: 512
[   71.449552] CPU: Testing write buffer coherency: ok
[   71.449678] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[   71.449691] SMP: prepare CPUs (4 cores)
[   71.449871] Setting Clocks for secondary CPUs
[   71.450650] SMP: CPU 0 Waking up CPU 1
[   71.455473] CPU1: Booted secondary processor
[   71.488906] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
[   71.488963] Brought up 2 CPUs
[   71.488977] SMP: Total of 2 processors activated (2664.03 BogoMIPS).
[   71.489588] devtmpfs: initialized
[   71.493182] xor: measuring software checksum speed
[   71.538874]    arm4regs  :  1292.000 MB/sec
[   71.588868]    8regs     :   963.600 MB/sec
[   71.638868]    32regs    :  1114.400 MB/sec
[   71.638876] xor: using function: arm4regs (1292.000 MB/sec)
[   71.639042] NET: Registered protocol family 16
[   71.641329] L0 cache Enabled
[   71.641338] Speculative Prefetch Disabled
[   71.641360] Aurora L2 Cache Enabled
[   71.641539] Support IO coherency.
[   71.744873]
[   71.744878]   Marvell Armada-XP Synology AXP 78230 Board -  Soc: MV78230 B0 LE
[   71.744896]   Detected Tclk 250000000, SysClk 667000000, FabricClk 667000000, PClk 1333000000
[   71.744904]   LSP version: linux-3.2.y-2013_Q1.2p2
[   71.744910]
[   71.746143] Synology ArmadaXP 4-bay GPIO Init
[   71.746596] registered dev#0 asa ehci_marvell
[   71.746907] Marvell USB EHCI Host controller #0: bf8aaa00
[   71.747012] registered dev#1 asa ehci_marvell
[   71.747319] Marvell USB EHCI Host controller #1: bf8aa800
[   71.747427] registered dev#2 asa mv_udc
[   71.747733] Marvell USB Gadget controller #2: bf8aa600
[   71.755547] bio: create slab <bio-0> at 0
[   71.919083] raid6: int32x1    162 MB/s
[   72.088963] raid6: int32x2    246 MB/s
[   72.258993] raid6: int32x4    303 MB/s
[   72.428995] raid6: int32x8    325 MB/s
[   72.429002] raid6: using algorithm int32x8 (325 MB/s)
[   72.429532] SCSI subsystem initialized
[   72.430739] Switching to clocksource axp_clocksource
[   72.431004] AppArmor: AppArmor Filesystem Enabled
[   72.432734] NET: Registered protocol family 2
[   72.432833] IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
[   72.433085] TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
[   72.434092] TCP bind hash table entries: 65536 (order: 7, 524288 bytes)
[   72.434497] TCP: Hash tables configured (established 131072 bind 65536)
[   72.434505] TCP reno registered
[   72.434514] UDP hash table entries: 512 (order: 2, 16384 bytes)
[   72.434543] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
[   72.434675] NET: Registered protocol family 1
[   72.434847] RPC: Registered named UNIX socket transport module.
[   72.434856] RPC: Registered udp transport module.
[   72.434862] RPC: Registered tcp transport module.
[   72.434868] RPC: Registered tcp NFSv4.1 backchannel transport module.
[   72.435027] Trying to unpack rootfs image as initramfs...
[   74.003170] rootfs image is not initramfs (LZMA data is corrupt); looks like an initrd
[   74.017084] Freeing initrd memory: 8192K
[   74.017180] PCI-E: Cheking physical bus #0 (controller #0): Enabled - Link UP
[   74.017372] PCI-E: Cheking physical bus #1 (controller #4): Enabled - Link UP
[   74.017543] PCI-E: Cheking physical bus #2 (controller #5): Enabled - No Link
[   74.017709] PCI-E: Cheking physical bus #3 (controller #6): Enabled - No Link
[   74.018452] PCI: bus0: Fast back to back transfers disabled
[   74.019025] PCI: bus1: Fast back to back transfers disabled
[   74.019233] pci 0000:01:00.0: BAR 0: assigned [mem 0xf2800000-0xf2807fff 64bit]
[   74.019250] pci 0000:01:00.0: BAR 0: set to [mem 0xf2800000-0xf2807fff 64bit] (PCI address [0xf2800000-0xf2807fff])
[   74.019265] pci 0000:00:00.0: BAR 0: assigned [mem 0xf2000000-0xf20fffff 64bit]
[   74.019280] pci 0000:00:00.0: BAR 0: set to [mem 0xf2000000-0xf20fffff 64bit] (PCI address [0xf2000000-0xf20fffff])
[   74.019292] pci 0000:00:00.0: BAR 2: can't assign io (size 0x100)
[   74.019689] cesadev_init(8051bdb0)
[   74.020250] Armada XP hwmon thermal sensor initialized.
[   74.020341] ArmadaXP Power Managament Suspend Operations Initialized
[   74.020350] Initializing Armada-XP CPU power management  (WFI)
[   74.021001] audit: initializing netlink socket (disabled)
[   74.021033] type=2000 audit(2.660:1): initialized
[   74.021488] VFS: Disk quotas dquot_6.5.2
[   74.021556] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[   74.022238] msgmni has been set to 2018
[   74.023059] async_tx: api initialized (async)
[   74.023205] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 254)
[   74.023216] io scheduler noop registered
[   74.023263] io scheduler cfq registered (default)
[   74.023321] mv_xor_shared mv_xor_shared.0: Marvell shared XOR driver
[   74.023355] mv_xor_shared mv_xor_shared.1: Marvell shared XOR driver
[   74.060826] mv_xor mv_xor.0: Marvell XOR: ( xor cpy )
[   74.100803] mv_xor mv_xor.1: Marvell XOR: ( xor fill cpy )
[   74.120793] mv_xor mv_xor.2: Marvell XOR: ( xor )
[   74.140794] mv_xor mv_xor.3: Marvell XOR: ( fill cpy )
[   74.141220] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
[   74.220971] serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 41) is a 16550A
[   74.927491] console [ttyS0] enabled
[   74.970939] serial8250.1: ttyS1 at MMIO 0xf1012100 (irq = 42) is a 16550A
[   75.006725] brd: module loaded
[   75.009792] Loading iSCSI transport class v2.0-870.
[   75.015609] sata_mv 0000:00:00.0: Gen-IIE 32 slots 4 ports SCSI mode IRQ via INTx
[   75.025364] scsi0 : sata_mv
[   75.028547] scsi1 : sata_mv
[   75.031681] scsi2 : sata_mv
[   75.034806] scsi3 : sata_mv
[   75.037899] ata1: SATA max UDMA/133 mmio m1048576@0xf2000000 port 0xf2022000 irq 58
[   75.045601] ata2: SATA max UDMA/133 mmio m1048576@0xf2000000 port 0xf2024000 irq 58
[   75.053288] ata3: SATA max UDMA/133 mmio m1048576@0xf2000000 port 0xf2026000 irq 58
[   75.060973] ata4: SATA max UDMA/133 mmio m1048576@0xf2000000 port 0xf2028000 irq 58
[   75.410806] ata1: SATA link down (SStatus 0 SControl 300)
[   75.760796] ata2: SATA link down (SStatus 0 SControl 300)
[   76.110794] ata3: SATA link down (SStatus 0 SControl 300)
[   76.460795] ata4: SATA link down (SStatus 0 SControl 300)
[   76.466411] sata_mv sata_mv.0: cannot get clkdev
[   76.471129] sata_mv sata_mv.0: slots 32 ports 2
[   76.476823] scsi4 : sata_mv
[   76.479952] scsi5 : sata_mv
[   76.483054] ata5: SATA max UDMA/133 irq 55
[   76.487165] ata6: SATA max UDMA/133 irq 55
[   76.840784] ata5: SATA link down (SStatus 0 SControl F300)
[   77.910775] ata6: failed to resume link (SControl 4)
[   77.915764] ata6: SATA link down (SStatus 0 SControl 4)
[   77.921937] physmap platform flash device: 00800000 at f0000000
[   77.930695] SPI Serial flash detected @ 0xf0000000, 8192KB (128sec x 64KB)
[   77.937621] Searching for RedBoot partition table in SYNOMTD-0 at offset 0x7f0000
[   77.982716] 6 RedBoot partitions found on MTD device SYNOMTD-0
[   77.988567] SYNOMTD flash bank 0: Using RedBoot partition definition
[   77.994947] Creating 6 MTD partitions on "SYNOMTD-0":
[   78.000018] 0x000000000000-0x0000000d0000 : "RedBoot"
[   78.005934] 0x0000000d0000-0x0000003a0000 : "zImage"
[   78.011671] 0x0000003a0000-0x0000007d0000 : "rd.gz"
[   78.017327] 0x0000007d0000-0x0000007e0000 : "vendor"
[   78.022399] vender Mac0 address : 00:11:32:27:2a:53
[   78.027294] vender Mac1 address : 00:11:32:27:2a:54
[   78.032194] vender Mac2 doesn't set ucSum:0x00 Buf:0x00 Sum:0.
[   78.038044] vender Mac3 doesn't set ucSum:0x00 Buf:0x00 Sum:0.
[   78.043902] serial number='13A0M7N005418'
[   78.048514] 0x0000007e0000-0x0000007f0000 : "RedBoot Config"
[   78.055176] 0x0000007f0000-0x000000800000 : "FIS directory"
[   78.061669] mv_eth_probe: port_mask=0xf, cpu_mask=0x3
[   78.067017]   o 4 Giga ports supported
[   78.070796]   o SKB recycle supported (Enabled)
[   78.075339]   o NETA acceleration mode 2
[   78.079272]   o BM supported for CPU: 4 BM pools
[   78.083909]   o RX Queue support: 1 Queues * 128 Descriptors
[   78.089585]   o TX Queue support: 1 Queues * 532 Descriptors
[   78.095264]   o GSO supported
[   78.098239]   o GRO supported
[   78.101221]   o Receive checksum offload supported
[   78.106025]   o Transmit checksum offload supported
[   78.110921]   o Driver ERROR statistics enabled
[   78.115463]
[   78.117136]   o Loading network interface(s)
[   78.121431]
[   78.122926]   o Port 0 is connected to Linux netdevice
[   78.128462]  giga p=0: mtu=1500, mac=bf835e44
[   78.136714]     o eth0, ifindex = 2, GbE port = 0
[   78.141297]     o eth0, phy chipid = 1410dd0, Support WOL = 32
[   78.147330]
[   78.148833]
[   78.150328]   o Port 1 is connected to Linux netdevice
[   78.155867]  giga p=1: mtu=1500, mac=bf835e44
[   78.164076]     o eth1, ifindex = 3, GbE port = 1
[   78.168622]     o eth1, phy chipid = 1410dd0, Support WOL = 32
[   78.174690]
[   78.176188]
[   78.176190]   o Warning: GbE port 2 is powered off
[   78.176194]
[   78.183983]
[   78.185704] i2c /dev entries driver
[   78.189731] Syno_HddMon: Initialization completed.
[   78.194553] md: linear personality registered for level -1
[   78.200055] md: raid0 personality registered for level 0
[   78.205387] md: raid1 personality registered for level 1
[   78.210715] md: raid10 personality registered for level 10
[   78.216220] md: raid6 personality registered for level 6
[   78.221551] md: raid5 personality registered for level 5
[   78.226878] md: raid4 personality registered for level 4
[   78.232507] device-mapper: ioctl: 4.22.0-ioctl (2011-10-19) initialised: [e-mail]
[   78.241165] cpuidle: using governor ladder
[   78.245599] cpuidle: using governor menu
[   78.249666] TCP cubic registered
[   78.252915] NET: Registered protocol family 17
[   78.257400] Registering the dns_resolver key type
[   78.262231] VFP support v0.3: implementor 56 architecture 2 part 20 variant 9 rev 6
[   78.270384] registered taskstats version 1
[   78.274788] md: Waiting for all devices to be available before autodetect
[   78.281604] md: If you don't use raid, use raid=noautodetect
[   78.287789] md: Autodetecting RAID arrays.
[   78.291912] md: Scanned 0 and added 0 devices.
[   78.296369] md: autorun ...
[   78.299169] md: ... autorun DONE.
[   78.302579] RAMDISK: lzma image found at block 0
[   79.868839] LZMA data is corrupt
[   79.887138] EXT3-fs (md0): error: unable to read superblock
[   79.892905] EXT2-fs (md0): error: unable to read superblock
[   79.898616] EXT4-fs (md0): unable to read superblock
[   79.903643] List of all partitions:
[   79.907157] 1f00             832 mtdblock0  (driver?)
[   79.912246] 1f01            2880 mtdblock1  (driver?)
[   79.917326] 1f02            4288 mtdblock2  (driver?)
[   79.922416] 1f03              64 mtdblock3  (driver?)
[   79.927497] 1f04              64 mtdblock4  (driver?)
[   79.932583] 1f05              64 mtdblock5  (driver?)
[   79.937661] No filesystem could mount root, tried:  ext3 ext2 ext4
[   79.943915] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(9,0)
[   79.952206] Backtrace:
[   79.954690] [<80011f60>] (dump_backtrace+0x0/0x108) from [<803edd20>] (dump_stack+0x18/0x1c)
[   79.963161]  r7:bb78c280 r6:bf87900f r5:8053ba2c r4:8056eb50
[   79.968893] [<803edd08>] (dump_stack+0x0/0x1c) from [<803ee05c>] (panic+0x70/0x190)
[   79.976587] [<803edfec>] (panic+0x0/0x190) from [<80513f34>] (change_floppy+0x0/0xec)
[   79.984444]  r3:bf835f38 r2:00000020 r1:bf835f38 r0:8049eb3c
[   79.990169]  r7:bb78c280
[   79.992732] [<80513be4>] (mount_block_root+0x0/0x350) from [<80514088>] (mount_root+0x68/0x6c)
[   80.001379] [<80514020>] (mount_root+0x0/0x6c) from [<80514228>] (prepare_namespace+0x19c/0x1e0)
[   80.010189]  r5:8053ba2c r4:8056d060
[   80.013808] [<8051408c>] (prepare_namespace+0x0/0x1e0) from [<80513a80>] (kernel_init+0x1cc/0x1d4)
[   80.022798]  r6:8056d000 r5:8053ba08 r4:00000008
[   80.027472] [<805138b4>] (kernel_init+0x0/0x1d4) from [<80059848>] (do_exit+0x0/0x70c)
[   80.035416]  r7:00000013
[   80.037974] CPU1: stopping
[   80.040689] Backtrace:
[   80.043164] [<80011f60>] (dump_backtrace+0x0/0x108) from [<803edd20>] (dump_stack+0x18/0x1c)
[   80.051626]  r7:bf86a028 r6:00000000 r5:80550978 r4:8056d2ec
[   80.057355] [<803edd08>] (dump_stack+0x0/0x1c) from [<80013bec>] (handle_IPI+0x158/0x174)
[   80.065559] [<80013a94>] (handle_IPI+0x0/0x174) from [<8000835c>] (do_IPI+0x10/0x14)
[   80.073325]  r9:bf86a000 r8:805c5900 r7:bf86bf54 r6:fbc21000 r5:80000013
[   80.079920] r4:80043980
[   80.082572] [<8000834c>] (do_IPI+0x0/0x14) from [<8000de74>] (__irq_svc+0x34/0xe8)
[   80.090164] Exception stack(0xbf86bf20 to 0xbf86bf68)
[   80.095234] bf20: 1eeeb429 00000008 00000008 000a555b 00000000 80dda0e8 805580e0 00000000
[   80.103439] bf40: 805c5900 bf86a000 00000000 bf86bf8c 00000008 bf86bf68 027ffffc 80043980
[   80.111640] bf60: 80000013 ffffffff
[   80.115149] [<8004392c>] (armadaxp_enter_idle+0x0/0xb0) from [<8032b490>] (cpuidle_idle_call+0xb8/0x12c)
[   80.124655]  r5:00000000 r4:80dda0e8
[   80.128268] [<8032b3d8>] (cpuidle_idle_call+0x0/0x12c) from [<8000f880>] (cpu_idle+0xa0/0xf8)
[   80.136818]  r9:bf86a000 r8:803f5d18 r7:80553c44 r6:bf86a038 r5:bf86a000
[   80.143413] r4:8056d0c4
[   80.146066] [<8000f7e0>] (cpu_idle+0x0/0xf8) from [<803eb374>] (secondary_start_kernel+0x164/0x16c)
[   80.155138]  r9:562f5842 r8:0000406a r7:8056d2d4 r6:10c03c7d r5:000001d3
[   80.161733] r4:00000001
[   80.164385] [<803eb210>] (secondary_start_kernel+0x0/0x16c) from [<003eac34>] (0x3eac34)
[   80.172498]  r5:00000015 r4:3f86c06a

Hij lijkt in het Linux-deel er alleen wel uit te klappen met een kernel panic. Ik kan met mijn putty dan niks meer. Ook zie ik verontrustende berichten als

[   78.302579] RAMDISK: lzma image found at block 0
[   79.868839] LZMA data is corrupt

Thralas schreef op woensdag 25 september 2019 @ 20:28:
[...]


Als die boot helemaal vers is: exact dezelfde, kijk maar naar de build times van de ramdisk/kernel. En je kunt natuurlijk de kernel/ramdisk van nand lezen.

Exact dezelfde als wat precies? Want de kernel en die initrd heb ik nu toch juist uit een nieuwe firmware? Wat kan ik uit de uboot nog afleiden wat verder wel 'oud' is gebleven? Zodat ik weet welke firmware ik kan gebruiken.

[ Voor 146% gewijzigd door MsG op 25-09-2019 21:46 ]

[Thralas]

MsG schreef op woensdag 25 september 2019 @ 21:27:
De kernel image is dus die zImage en die rd.bin is dan het initrd/ramdisk ding?

En bedoel je dus dat ik puur een

bootm 0x02000000 0x02500000

Ja & ja.

En hij lijkt wel door te booten:

Ja, dat ziet er stukken beter uit.

Hij lijkt in het Linux-deel er alleen wel uit te klappen met een kernel panic. Ik kan met mijn putty dan niks meer. Ook zie ik verontrustende berichten als

[   78.302579] RAMDISK: lzma image found at block 0
[   79.868839] LZMA data is corrupt

Dat is vreemd. Ten eerste omdat de uImage header zegt dat het gzip is, terwijl het inderdaad lzma is (I checked).

Maar daarnaast staat er nog steeds initrd=0x8000040,8M op de kernel commandline. Volgens mij is het loadaddr waar de uitgepakte image staat (zonder uImage header), dus dan zit je er met die regel precies 0x40 (64) bytes naast.

Ik zou met 'printenv bootargs' en 'set bootargs <command line zonder initrd=>' even de initrd-optie verwijderen en kijken wat 'ie dan doet.

Mocht dat niet werken, dan kun je de uImage altijd nog uitpakken, uncompressen en opnieuw inpakken (uboot-tools zonder compressie. Maar dat zou het verschil niet mogen maken.

Exact dezelfde als wat precies? Want de kernel en die initrd heb ik nu toch juist uit een nieuwe firmware? Wat kan ik uit de uboot nog afleiden wat verder wel 'oud' is gebleven? Zodat ik weet welke firmware ik kan gebruiken.

Als wat hij vanzelf (probeerde) te booten. Maar dat leek dus sowieso niet juist, dus ik betwijfel of hij die ook van nand heeft gelezen.

Als je het echt wilt weten: ramdisk of kernel van nand laden. Maar wat je nu hebt is prima - zolang de kernel en initramfs maar bij elkaar horen.

[MsG]

Ik ga morgen even kijken naar je adviezen. Tot zover weer bedankt. Wel moet ik zeggen dat ik met de gelinkte tutorial uit de TS ook helemaal doorbootte tot het Linux systeem. Hierbij hoefde ik handmatig niet eens geheugenadressen in te vullen.

Met het kale tftpboot commando zoekt de nas zelf naar een bestand die een bepaalde filename moet hebben. Daarna met bootm zonder parameters kreeg ik hetzelfde als wat ik nu als output kreeg. De log uit de ts lijkt qua fouten ook behoorlijk op de laatste log.

Ik ga morgen even kijken wat de tips die je in het laatste bericht stuurde nog kunnen brengen.

Er is natuurlijk altijd een mogelijkheid dat er hardwarematig wel iets stuk is. Maar daar lijkt het nog niet noodzakelijkerwijs op te duiden.

EDIT:

Thralas schreef op woensdag 25 september 2019 @ 23:58:
[...]
Ik zou met 'printenv bootargs' en 'set bootargs <command line zonder initrd=>' even de initrd-optie verwijderen en kijken wat 'ie dan doet.

Dit deed het hem! Gecombineerd met het eerdere boote het systeem warempel keurig door naar Linux, en kon ik hem zien in de Synology Manager. Boel nu helemaal mooi opnieuw kunnen installeren. Super! Ook bedankt @rikadoo voor je eerdere topic waar ik door werd getriggerd.

Ben wel een beetje geschokt van het standaardadvies op meer 'noob'-sites. Die luidt namelijk vrijwel altijd "knippert je NAS oneindig met het blauwe ledje? Dan is er een hardware-defect, dus gooi hem maar in de container (bij wijze van).

[ Voor 44% gewijzigd door MsG op 27-09-2019 15:28 ]

[bignellrp]

Sorry, this was the only page i could find on Synology unbrick that was technical enough. All the other pages do not go into enough detail. I had to use google translate.

I need some help unbricking a DS414r1 where the power was removed during a firmware upgrade. I managed to get to the console and got the following errors:

*** Warning - bad CRC, using default environment

Wrong Image Format for bootm command
ERROR: can't get kernel image!

So i loaded the kernel back on by downloading the latest 414 firmware from Synology, unpacking the pat file and using a USB formatted with rufus to fat16 to copy zImage and rd.bin

Marvell>> usb start

(Re)start USB...
USB: Active port: 0
Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... 2 USB Device(s) found
scanning bus for storage devices... 1 Storage Device(s) found


Marvell>> fatload usb 0:1 2000000 zImage
reading zImage


2123952 bytes read

Marvell>> fatload usb 0:1 8000000 rd.bin
reading rd.bin

3698039 bytes read

Marvell>> sf probe 0 50000000

SF: Detected M25P64 with page size 64 KiB, total 8 MiB

Marvell>> save

Saving Environment to SPI Flash...
SF: Detected M25P64 with page size 64 KiB, total 8 MiB
Erasing SPI flash....Writing to SPI flash.....done

Marvell>> bootm 0x2000000 0x8000000

Great i thought, its booting. It booted back to the DS login page but when i rebooted the console now gets stuck at "modules detected"


MMC: MRVL_MMC: 0
SF: Detected M25P64 with page size 64 KiB, total 8 MiB
PEX 0.0(0): Root Complex Interface, Detected Link X4, GEN 1.1
PEX 1.0(1): Root Complex Interface, Detected Link X1, GEN 2.0
PEX 1.1(2): Detected No Link.
PEX 1.2(3): Detected No Link.
FPU initialized to Run Fast Mode.
USB 0: Host Mode
USB 1: Host Mode
USB 2: Device Mode
Modules Detected:


Is there a way to get back to the Marvell>> shell from here? Will it time out looking for modules? Is there a key i can press on the keyboard when it boots to go straight to Marvell shell?

[Thralas]

Sorry, deze doe ik even in 't Engels. We kennen allemaal de ik-heb-iets-helemaal-stukgemaakt-en-Google-geeft-maar-1-hit-in-een-taal-die-ik-niet-spreek immers. Bovendien zijn topics met echte technische inhoud hier schaars

I don't fully understand the reasoning applied in my old posts, but a few things seemed to be off:

• uboot fails to load its environment due to an alleged checksum error, falling back to defaults
• The defaults don't make sense - at least not for vanilla uboot
• Yet it boots without ever touch the environment..

Unfortunately that means this bit is rather worrisome:

Marvell>> save

Saving Environment to SPI Flash...
SF: Detected M25P64 with page size 64 KiB, total 8 MiB
Erasing SPI flash....Writing to SPI flash.....done

While this would generally just save the (fallback) defaults with a correct checksum, plenty of things about Synology's uboot seem off (ie. it's probably modified).

Saving the environment might've interfered with the way it normally boots, somehow resulting in a different environment (or erasing other parts of the flash). I doubt it'll get any further - either it's hung or the stdin/stdout variables are now incorrect - breaking the console altogether.

I'm afraid you might've bricked it beyond simple serial access - the most obvious way forward would be to dump the M25P64, compare it to a working machine's flash and rewrite it as necessary..

[bignellrp]

How do I dump the flash and compare?

I’m guessing if I can’t get to the Marvell prompt I’m going to need to restore uBoot using a SOIC clip?

https://www.ebay.co.uk/itm/402001223600

Before I order one of these is there any other way of forcing it to the Marvell prompt? A key press on boot maybe?

Any help is appreciated as the Synology forum has been no help at all.

[Thralas]

bignellrp schreef op zaterdag 4 april 2020 @ 14:49:
I’m guessing if I can’t get to the Marvell prompt I’m going to need to restore uBoot using a SOIC clip?

Yes. M25P64 is probably SO16 (datasheet) though, assuming it's not the VDFPN8.

I suppose you might be able to restore it trivially by just copying a working device's flash (do back it up first), although you would lose board specific data (ie. MAC addresses and the like). See this thread for a related discussion. Further discussion might be more appropriate elsewhere in any case - English is frowned upon over here.

[bignellrp]

Hi Thralas:

Kunnen wij het gesprek hier verder voeren?

https://community.synology.com/enu/forum/1/post/132794