|
Bricked Synology DS213 (Kirkwood) so close September 25, 2020 12:35PM |
Registered: 4 years ago Posts: 78 |
Attempts to migrate from another unit to this one resulted in a boot loop. After accessing it through a serial connection I was happy to see that U-Boot came up and attempted to load which ends in a bad crc statement and then reboot.
Console output and printenv is below. I did TFTP into it and send the zimage, but the same result after reboot. I think that I may need to know what specific address to send to, or maybe the rd.bin is what also needs to be re-flashed.
There are an incredible number of these 2 bay and 4 bay Synology boxes that people have which are bricked with the same problem of flashing blue light which I believe is a corrupt firmware issue. A lot of people would be grateful for a solution that would cost them a few dollar USB/com cable. I am not one to take and not give back so the results and how to would be here and the Synology forums as well.
Thank you to the Doozan community in advance.
----------------------------------------
Edited 1 time(s). Last edit at 09/25/2020 12:38PM by itangoii.
Console output and printenv is below. I did TFTP into it and send the zimage, but the same result after reboot. I think that I may need to know what specific address to send to, or maybe the rd.bin is what also needs to be re-flashed.
There are an incredible number of these 2 bay and 4 bay Synology boxes that people have which are bricked with the same problem of flashing blue light which I believe is a corrupt firmware issue. A lot of people would be grateful for a solution that would cost them a few dollar USB/com cable. I am not one to take and not give back so the results and how to would be here and the Synology forums as well.
Thank you to the Doozan community in advance.
----------------------------------------
__ __ _ _
| \/ | __ _ _ ____ _____| | |
| |\/| |/ _` | '__\ \ / / _ \ | |
| | | | (_| | | \ V / __/ | |
|_| |_|\__,_|_| \_/ \___|_|_|
_ _ ____ _
| | | | | __ ) ___ ___ | |_
| | | |___| _ \ / _ \ / _ \| __|
| |_| |___| |_) | (_) | (_) | |_
\___/ |____/ \___/ \___/ \__| ** LOADER **
** MARVELL BOARD: Synology Disk Station LE
U-Boot 1.1.4 (Apr 19 2012 - 18:47:44) Marvell version: 3.5.9
U-Boot code: 00600000 -> 0067FFF0 BSS: -> 0068B3D4
Soc: 88F6282 A1CPU running @ 2000Mhz L2 running @ 500Mhz
SysClock = 500Mhz , TClock = 200Mhz
DRAM (DDR3) CAS Latency = 7 tRP = 7 tRAS = 20 tRCD=7
DRAM CS[0] base 0x00000000 size 512MB
DRAM Total size 512MB 16bit width
Addresses 8M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (8M - 7M): Done
Using default environment
[8192kB@f8000000] Flash: 8 MB
CPU : Marvell Feroceon (Rev 1)
Streaming disabled
Write allocate disabled
USB 0: host mode
PEX 0: interface detected no Link.
PEX 1: PCI Express Root Complex Interface
PEX interface detected Link X1
Synology Model: DS213
Fan Status: Not Good
Fan 1: Not Good
Net: egiga0 [PRIME], egiga1
Hit any key to stop autoboot: 0
## Booting image at f8090000 ...
Image Name: Linux-2.6.32.12
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 1550700 Bytes = 1.5 MB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
OK
## Loading Ramdisk Image at f8390000 ...
Image Name: synology_88f6282_213 5644
Image Type: ARM Linux RAMDisk Image (gzip compressed)
Data Size: 3449313 Bytes = 3.3 MB
Load Address: 00800000
Entry Point: 00800000
Verifying Checksum ... Bad Data CRC
<Result of printenv and ver>
Marvell>> ver
U-Boot 1.1.4 (Apr 19 2012 - 18:47:44) Marvell version: 3.5.9
Marvell>> printenv
bootcmd=bootm F8090000 F8390000
baudrate=115200
loads_echo=0
ipaddr=192.168.1.154
serverip=192.168.1.155
rootpath=/mnt/ARM_FS/
netmask=255.255.254.0
run_diag=yes
stdin=serial
stdout=serial
stderr=serial
console=console=ttyS0,115200 mtdparts=spi_flash:0x80000@0(uboot)ro,0x700000@0x100000(root)
mainlineLinux=no
enaMonExt=no
enaCpuStream=no
enaWrAllo=no
pexMode=RC
disL2Cache=no
setL2CacheWT=yes
disL2Prefetch=yes
enaICPref=yes
enaDCPref=yes
sata_dma_mode=yes
MALLOC_len=1
ethprime=egiga0
netbsd_en=no
vxworks_en=no
bootargs_root=root=/dev/nfs rw
bootargs_end=:::DB88FXX81:eth0:none
image_name=uImage
standalone=fsload 0x2000000 $(image_name);setenv bootargs $(console) root=/dev/mtdblock0 rw ip=$(ipaddr):$(serverip)$(bootargs_end) $(mvPhoneConfig); bootm 0x2000000;
lcd0_enable=0
lcd0_params=640x480-16@60
bootdelay=3
disaMvPnp=no
ethaddr=00:50:43:3c:3b:5d
ethmtu=1500
mvPhoneConfig=mv_phone_config=dev[0]:fxs,dev[1]:fxo
mvNetConfig=mv_net_config=(00:11:88:0f:62:81,0:1:2:3),mtu=1500
usb0Mode=host
pcieTune=no
pcieTune1=no
bootargs=console=ttyS0,115200 ip=off initrd=0x00800040,8M root=/dev/md0 rw syno_hw_version=DS213v10 ihd_num=2 netif_num=1 flash_size=8
ethact=egiga0
Environment size: 1173/4092 bytes
Edited 1 time(s). Last edit at 09/25/2020 12:38PM by itangoii.
|
Re: Bricked Synology DS213 (Kirkwood) so close September 25, 2020 07:33PM |
Admin Registered: 13 years ago Posts: 18,997 |
itangoii,
> Attempts to migrate from another unit to this one
> resulted in a boot loop. After accessing it
> through a serial connection I was happy to see
> that U-Boot came up and attempted to load which
> ends in a bad crc statement and then reboot.
>
> Console output and printenv is below. I did TFTP
> into it and send the zimage, but the same result
> after reboot. I think that I may need to know
> what specific address to send to, or maybe the
> rd.bin is what also needs to be re-flashed.
Looks like your kernel image is OK. But the intitrd image was corrupted.
> There are an incredible number of these 2 bay and
> 4 bay Synology boxes that people have which are
> bricked with the same problem of flashing blue
> light which I believe is a corrupt firmware issue.
Since you have already set up TFTP, you can try booting this way:
Put both kernel uImage (not zImage) and initrd image at tftproot. rd.bin is the initrd image. Not sure what uImage is called in this box stock FW.
Power up the box, interrupt serial console and, tftp the images to the below 2 addresses.
And set the boot addresses
and then
Those addresses above usually work for Kirkwood boxes. However, in some stock Kirkwood boxes, the addresses might need to be:
Try the above and post the entire serial console bootlog here.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> Attempts to migrate from another unit to this one
> resulted in a boot loop. After accessing it
> through a serial connection I was happy to see
> that U-Boot came up and attempted to load which
> ends in a bad crc statement and then reboot.
>
> Console output and printenv is below. I did TFTP
> into it and send the zimage, but the same result
> after reboot. I think that I may need to know
> what specific address to send to, or maybe the
> rd.bin is what also needs to be re-flashed.
Looks like your kernel image is OK. But the intitrd image was corrupted.
> There are an incredible number of these 2 bay and
> 4 bay Synology boxes that people have which are
> bricked with the same problem of flashing blue
> light which I believe is a corrupt firmware issue.
Since you have already set up TFTP, you can try booting this way:
Put both kernel uImage (not zImage) and initrd image at tftproot. rd.bin is the initrd image. Not sure what uImage is called in this box stock FW.
Power up the box, interrupt serial console and, tftp the images to the below 2 addresses.
And set the boot addresses
setenv load_uimage_addr 0x800000 setenv load_initrd_addr 0x1100000
and then
bootm 0x800000 0x1100000
Those addresses above usually work for Kirkwood boxes. However, in some stock Kirkwood boxes, the addresses might need to be:
setenv load_uimage_addr 0x2000000 setenv load_initrd_addr 0x3000000 bootm 0x2000000 0x3000000
Try the above and post the entire serial console bootlog here.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Bricked Synology DS213 (Kirkwood) so close September 25, 2020 08:44PM |
Registered: 9 years ago Posts: 461 |
I believe there is support in the mainline Linux kernel for this device. See kirkwood-ds212.dts which supports the following Synology devices:
model = "Synology DS212, DS212p v10, v20, DS213air v10, DS213 v10"
There are also other kirkwood-ds*.dts files that support other Synology models.
Ray
model = "Synology DS212, DS212p v10, v20, DS213air v10, DS213 v10"
There are also other kirkwood-ds*.dts files that support other Synology models.
Ray
|
Re: Bricked Synology DS213 (Kirkwood) so close September 25, 2020 10:56PM |
Admin Registered: 13 years ago Posts: 18,997 |
rayknight Wrote:
-------------------------------------------------------
> I believe there is support in the mainline Linux
> kernel for this device. See kirkwood-ds212.dts
> which supports the following Synology devices:
>
> model = "Synology DS212, DS212p v10, v20, DS213air
> v10, DS213 v10"
>
> There are also other kirkwood-ds*.dts files that
> support other Synology models.
>
> Ray
Yes. I'm sure this box can run with my released kernel and rootfs:
https://forum.doozan.com/read.php?2,12096
However, lots of people are just trying to unbrick their boxes and are happy with stock FW (Synology stock SW is much better than other vendors). I can see that this stock u-boot was substantially patched by Synology.
So first thing first, I want to see if there is an easy way to recover from what itangoii described as "There are an incredible number of these 2 bay and 4 bay Synology boxes that people have which are bricked".
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
-------------------------------------------------------
> I believe there is support in the mainline Linux
> kernel for this device. See kirkwood-ds212.dts
> which supports the following Synology devices:
>
> model = "Synology DS212, DS212p v10, v20, DS213air
> v10, DS213 v10"
>
> There are also other kirkwood-ds*.dts files that
> support other Synology models.
>
> Ray
Yes. I'm sure this box can run with my released kernel and rootfs:
https://forum.doozan.com/read.php?2,12096
However, lots of people are just trying to unbrick their boxes and are happy with stock FW (Synology stock SW is much better than other vendors). I can see that this stock u-boot was substantially patched by Synology.
So first thing first, I want to see if there is an easy way to recover from what itangoii described as "There are an incredible number of these 2 bay and 4 bay Synology boxes that people have which are bricked".
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Bricked Synology DS213 (Kirkwood) so close September 25, 2020 10:59PM |
Registered: 4 years ago Posts: 78 |
Thank you both!
I did some more searching and it seams that zimage may be it. I found more than one message saying they flashed zimage and rd.bin. This person (you will need to translate from german) brought back his DS213+ (Different hardware and addresses though)
https://www.synology-forum.de/threads/ds213-stromausfall-bei-firmware-update.67253/
So I gave it a shot with your addresses and it went a great deal further ending in a kernel panic.
I did some more searching and it seams that zimage may be it. I found more than one message saying they flashed zimage and rd.bin. This person (you will need to translate from german) brought back his DS213+ (Different hardware and addresses though)
https://www.synology-forum.de/threads/ds213-stromausfall-bei-firmware-update.67253/
So I gave it a shot with your addresses and it went a great deal further ending in a kernel panic.
▒
__ __ _ _
| \/ | __ _ _ ____ _____| | |
| |\/| |/ _` | '__\ \ / / _ \ | |
| | | | (_| | | \ V / __/ | |
|_| |_|\__,_|_| \_/ \___|_|_|
_ _ ____ _
| | | | | __ ) ___ ___ | |_
| | | |___| _ \ / _ \ / _ \| __|
| |_| |___| |_) | (_) | (_) | |_
\___/ |____/ \___/ \___/ \__| ** LOADER **
** MARVELL BOARD: Synology Disk Station LE
U-Boot 1.1.4 (Apr 19 2012 - 18:47:44) Marvell version: 3.5.9
U-Boot code: 00600000 -> 0067FFF0 BSS: -> 0068B3D4
Soc: 88F6282 A1CPU running @ 2000Mhz L2 running @ 500Mhz
SysClock = 500Mhz , TClock = 200Mhz
DRAM (DDR3) CAS Latency = 7 tRP = 7 tRAS = 20 tRCD=7
DRAM CS[0] base 0x00000000 size 512MB
DRAM Total size 512MB 16bit width
Addresses 8M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (8M - 7M): Done
Using default environment
[8192kB@f8000000] Flash: 8 MB
CPU : Marvell Feroceon (Rev 1)
Streaming disabled
Write allocate disabled
USB 0: host mode
PEX 0: interface detected no Link.
PEX 1: PCI Express Root Complex Interface
PEX interface detected Link X1
Synology Model: DS213
Fan Status: Not Good
Fan 1: Not Good
Net: egiga0 [PRIME], egiga1
Hit any key to stop autoboot: 0
Marvell>> setenv ipaddr 192.168.0.3
Marvell>> setenv serverip 192.168.0.15
Unknown command 'setenv' - try 'help'
Marvell>> setenv serverip 192.168.0.15
Marvell>> tftpboot 0x800000 zimage
Using egiga0 device
TFTP from server 192.168.0.15; our IP address is 192.168.0.3
Filename 'zimage'.
Load address: 0x800000
Loading: #################################################################
#################################################################
#################################################################
#################################################################
############################################
done
Bytes transferred = 1553576 (17b4a8 hex)
Marvell>> tftpboot 0x1100000 rd.bin
Using egiga0 device
TFTP from server 192.168.0.15; our IP address is 192.168.0.3
Filename 'rd.bin'.
Load address: 0x1100000
Loading: #################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
###########################################################
done
Bytes transferred = 3297068 (324f2c hex)
Marvell>> setenv load_uimage_addr 0x800000
Marvell>> setenv load_initrd_addr 0x1100000
Marvell>> bootm 0x800000 0x1100000
## Booting image at 00800000 ...
Image Name: Linux-2.6.32.12
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 1553512 Bytes = 1.5 MB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
OK
## Loading Ramdisk Image at 01100000 ...
Image Name: synology_88f6282_213 25426
Image Type: ARM Linux RAMDisk Image (gzip compressed)
Data Size: 3297004 Bytes = 3.1 MB
Load Address: 00800000
Entry Point: 00800000
Verifying Checksum ... OK
Starting kernel ...
Uncompressing Linux... done, booting the kernel.
[ 0.000000] Linux version 2.6.32.12 (root@build4) (gcc version 4.6.4 (Marvell GCC release 20150204-c4af733b 64K MAXPAGESIZE ALIGN CVE-2015-0235) ) #25426 Tue May 12 04:42:15 CST 2020
[ 0.000000] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=00053977
[ 0.000000] CPU: VIVT data cache, VIVT instruction cache
[ 0.000000] Machine: Synology 6282 board
[ 0.000000] Using UBoot passing parameters structure
[ 0.000000] Sys Clk = 200000000, Tclk = 166666667
[ 0.000000] Synology Board ID: 27
[ 0.000000] Memory policy: ECC disabled, Data cache writeback
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping off. Total pages: 130048
[ 0.000000] Kernel command line: console=ttyS0,115200 ip=off initrd=0x00800040,8M root=/dev/md0 rw syno_hw_version=DS213v10 ihd_num=2 netif_num=1 flash_size=8
[ 0.000000] Synology Hardware Version: DS213v10-j
[ 0.000000] Internal HD num: 2
[ 0.000000] Internal netif num: 1
[ 0.000000] Flash Memory Size: 8 MB
[ 0.000000] PID hash table entries: 2048 (order: 1, 8192 bytes)
[ 0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
[ 0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
[ 0.000000] Memory: 512MB = 512MB total
[ 0.000000] Memory: 502784KB available (3656K code, 519K data, 124K init, 0K highmem)
[ 0.000000] Hierarchical RCU implementation.
[ 0.000000] NR_IRQS:128
[ 0.000000] Console: colour dummy device 80x30
[ 0.000000] Calibrating delay loop... 1985.74 BogoMIPS (lpj=9928704)
[ 0.250000] Mount-cache hash table entries: 512
[ 0.250000] CPU: Testing write buffer coherency: ok
[ 0.250000] devtmpfs: initialized
[ 0.250000] xor: measuring software checksum speed
[ 0.300000] arm4regs : 1810.800 MB/sec
[ 0.350000] 8regs : 1086.400 MB/sec
[ 0.400000] 32regs : 1402.400 MB/sec
[ 0.400000] xor: using function: arm4regs (1810.800 MB/sec)
[ 0.400000] NET: Registered protocol family 16
[ 0.400000] Feroceon L2: Enabling L2
[ 0.400000] Feroceon L2: Cache support initialised, in WT override mode.
[ 0.420000]
[ 0.420000] CPU Interface
[ 0.420000] -------------
[ 0.420000] SDRAM_CS0 ....base 00000000, size 512MB
[ 0.420000] SDRAM_CS1 ....disable
[ 0.420000] SDRAM_CS2 ....disable
[ 0.420000] SDRAM_CS3 ....disable
[ 0.420000] PEX0_MEM ....base e0000000, size 128MB
[ 0.420000] PEX0_IO ....base f2000000, size 1MB
[ 0.420000] PEX1_MEM ....base e8000000, size 128MB
[ 0.420000] PEX1_IO ....base f2100000, size 1MB
[ 0.420000] INTER_REGS ....base f1000000, size 1MB
[ 0.420000] NFLASH_CS ....base fa000000, size 2MB
[ 0.420000] SPI_CS ....base f4000000, size 16MB
[ 0.420000] BOOT_ROM_CS ....no such
[ 0.420000] DEV_BOOTCS ....no such
[ 0.420000] CRYPT_ENG ....base f0000000, size 2MB
[ 0.420000] Detected Tclk 200000000 and SysClk 500000000
[ 0.420000] Apply DS 212 GPIO
[ 0.420000] Synology 6282 1, 2 bay GPIO Init
[ 0.920000] PEX0 interface detected no Link.
[ 1.420000] PEX1 interface detected Link X1
[ 1.420000] PCI: bus0: Fast back to back transfers enabled
[ 1.420000] pci 0000:01:01.0: PME# supported from D0 D3hot
[ 1.420000] pci 0000:01:01.0: PME# disabled
[ 1.420000] PCI: bus1: Fast back to back transfers disabled
[ 1.430000] bio: create slab <bio-0> at 0
[ 1.430000] vgaarb: loaded
[ 1.430000] SCSI subsystem initialized
[ 1.600000] raid6: int32x1 146 MB/s
[ 1.770000] raid6: int32x2 211 MB/s
[ 1.940000] raid6: int32x4 215 MB/s
[ 2.110000] raid6: int32x8 238 MB/s
[ 2.110000] raid6: using algorithm int32x8 (238 MB/s)
[ 2.110000] Switching to clocksource kw_clocksource
[ 2.110000] NET: Registered protocol family 2
[ 2.110000] IP route cache hash table entries: 4096 (order: 2, 16384 bytes)
[ 2.110000] TCP established hash table entries: 16384 (order: 5, 131072 bytes)
[ 2.110000] TCP bind hash table entries: 16384 (order: 4, 65536 bytes)
[ 2.110000] TCP: Hash tables configured (established 16384 bind 16384)
[ 2.110000] TCP reno registered
[ 2.110000] NET: Registered protocol family 1
[ 2.110000] RPC: Registered udp transport module.
[ 2.110000] RPC: Registered tcp transport module.
[ 2.110000] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 2.110000] Trying to unpack rootfs image as initramfs...
[ 2.110000] Freeing initrd memory: 8192K
[ 2.110000] XOR registered 4 channels
[ 2.110000] XOR 2nd invalidate WA enabled
[ 2.110000] VFS: Disk quotas dquot_6.5.2
[ 2.110000] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[ 2.110000] msgmni has been set to 998
[ 2.110000] alg: No test for md5 (md5-generic)
[ 2.110000] alg: No test for des (des-generic)
[ 2.110000] alg: No test for des3_ede (des3_ede-generic)
[ 2.110000] alg: No test for stdrng (krng)
[ 2.110000] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 254)
[ 2.110000] io scheduler noop registered
[ 2.110000] io scheduler anticipatory registered (default)
[ 2.120000] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
[ 2.120000] serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 33) is a 16550A
[ 2.130000] console [ttyS0] enabled
[ 2.130000] serial8250.1: ttyS1 at MMIO 0xf1012100 (irq = 34) is a 16550A
[ 2.140000] brd: module loaded
[ 2.150000] sata_mv sata_mv.0: version 1.28
[ 2.150000] sata_mv sata_mv.0: slots 32 ports 2
[ 2.150000] scsi0 : sata_mv
[ 2.160000] scsi1 : sata_mv
[ 2.160000] ata1: SATA max UDMA/133 irq 21
[ 2.160000] ata2: SATA max UDMA/133 irq 21
[ 5.510000] ata1: SATA link down (SStatus 0 SControl F300)
[ 8.500000] Delay 5 seconds to wait for disk 2 ready.
[ 13.850000] ata2: SATA link down (SStatus 0 SControl F300)
[ 13.850000] physmap platform flash device: 00400000 at f8000000
[ 13.860000] SPI Serial flash detected @ 0xf8000000, 8192KB (128sec x 64KB)
[ 13.870000] Searching for RedBoot partition table in SYNOMTD-0 at offset 0x7f0000
[ 13.880000] 6 RedBoot partitions found on MTD device SYNOMTD-0
[ 13.890000] SYNOMTD flash bank 0: Using RedBoot partition definition
[ 13.890000] Creating 6 MTD partitions on "SYNOMTD-0":
[ 13.900000] 0x000000000000-0x000000090000 : "RedBoot"
[ 13.910000] 0x000000090000-0x000000390000 : "zImage"
[ 13.910000] 0x000000390000-0x0000007d0000 : "rd.gz"
[ 13.920000] 0x0000007d0000-0x0000007e0000 : "vendor"
[ 13.920000] vender Mac1 checksum error ucSum:0x00 Buf:0x00 Sum:0.
[ 13.930000] vender Mac2 checksum error ucSum:0x00 Buf:0x00 Sum:0.
[ 13.930000] vender Mac3 checksum error ucSum:0x00 Buf:0x00 Sum:0.
[ 13.940000] serial number='D4L5N00728'
[ 13.940000] 0x0000007e0000-0x0000007f0000 : "RedBoot Config"
[ 13.950000] 0x0000007f0000-0x000000800000 : "FIS directory"
[ 13.960000] SPI Serial flash detected @ 0xf4000000, 8192KB (128sec x 64KB)
[ 13.970000] cmdlinepart partition parsing not available
[ 13.970000] Loading Marvell Ethernet Driver:
[ 13.980000] o Cached descriptors in DRAM
[ 13.980000] o DRAM SW cache-coherency
[ 13.980000] o 2 Giga ports supported
[ 13.990000] o Single RX Queue support - ETH_DEF_RXQ=0
[ 13.990000] o Single TX Queue support - ETH_DEF_TXQ=0
[ 14.000000] o TCP segmentation offload (TSO) supported
[ 14.000000] o Receive checksum offload supported
[ 14.010000] o Transmit checksum offload supported
[ 14.010000] o SKB Recycle supported - (Enabled)
[ 14.020000] o Rx descripors: q0=128
[ 14.020000] o Tx descripors: q0=532
[ 14.020000] o Loading network interface(s):
[ 14.030000] o register under mv88fx_eth platform
[ 14.040000] o eth0, ifindex = 2, GbE port = 0
[ 14.040000] o eth0, phy chipid = 1410e90, Support WOL = 32
[ 14.050000]
[ 14.050000] md: linear personality registered for level -1
[ 14.050000] md: raid0 personality registered for level 0
[ 14.060000] md: raid1 personality registered for level 1
[ 14.060000] md: raid10 personality registered for level 10
[ 14.070000] md: raid6 personality registered for level 6
[ 14.070000] md: raid5 personality registered for level 5
[ 14.080000] md: raid4 personality registered for level 4
[ 14.090000] device-mapper: ioctl: 4.15.0-ioctl (2009-04-01) initialised: dm-devel@redhat.com
[ 14.090000] cpuidle: using governor ladder
[ 14.100000] TCP cubic registered
[ 14.100000] NET: Registered protocol family 17
[ 14.110000] NET: Registered protocol family 15
[ 14.110000] registered taskstats version 1
[ 14.120000] md: Waiting for all devices to be available before autodetect
[ 14.120000] md: If you don't use raid, use raid=noautodetect
[ 14.130000] md: Autodetecting RAID arrays.
[ 14.130000] md: Scanned 0 and added 0 devices.
[ 14.140000] md: autorun ...
[ 14.140000] md: ... autorun DONE.
[ 14.140000] EXT3-fs: unable to read superblock
[ 14.150000] EXT2-fs: unable to read superblock
[ 14.150000] EXT4-fs (md0): unable to read superblock
[ 14.160000] List of all partitions:
[ 14.160000] 1f00 576 mtdblock0 (driver?)
[ 14.170000] 1f01 3072 mtdblock1 (driver?)
[ 14.170000] 1f02 4352 mtdblock2 (driver?)
[ 14.180000] 1f03 64 mtdblock3 (driver?)
[ 14.180000] 1f04 64 mtdblock4 (driver?)
[ 14.190000] 1f05 64 mtdblock5 (driver?)
[ 14.190000] 1f06 8192 mtdblock6 (driver?)
[ 14.200000] No filesystem could mount root, tried: ext3 ext2 ext4
[ 14.200000] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(9,0)
|
Re: Bricked Synology DS213 (Kirkwood) so close September 25, 2020 11:03PM |
Registered: 4 years ago Posts: 78 |
bodhi Wrote:
> So first thing first, I want to see if there is an
> easy way to recover from what itangoii described
> as "There are an incredible number of these 2 bay
> and 4 bay Synology boxes that people have which
> are bricked".
I've done a good 25 hours of reading to resolve this and the lack of support in the Synology forums is sad. Many of them left hanging after things like a power failure during an update.
> So first thing first, I want to see if there is an
> easy way to recover from what itangoii described
> as "There are an incredible number of these 2 bay
> and 4 bay Synology boxes that people have which
> are bricked".
I've done a good 25 hours of reading to resolve this and the lack of support in the Synology forums is sad. Many of them left hanging after things like a power failure during an update.
|
Re: Bricked Synology DS213 (Kirkwood) so close September 26, 2020 12:26AM |
Admin Registered: 13 years ago Posts: 18,997 |
itangoii,
I see. The kernel has booted fine. This is now the problem with mounting rootfs.
From the bootargs envs, we can see that the rootfs is on the RAID array
The device mapper seems to be OK.
But the RAID devices are nowhere to be found:
So my observation is that the RAID array also has problem. Either md0 is corrupted, or u-boot envs were corrupted so the kernel cannot initialize the array, and thus cannot see md0.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
I see. The kernel has booted fine. This is now the problem with mounting rootfs.
[ 14.200000] No filesystem could mount root, tried: ext3 ext2 ext4 [ 14.200000] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(9,0)
From the bootargs envs, we can see that the rootfs is on the RAID array
[ 0.000000] Kernel command line: console=ttyS0,115200 ip=off initrd=0x00800040,8M root=/dev/md0 rw syno_hw_version=DS213v10 ihd_num=2 netif_num=1 flash_size=8
The device mapper seems to be OK.
[ 14.050000] md: linear personality registered for level -1 [ 14.050000] md: raid0 personality registered for level 0 [ 14.060000] md: raid1 personality registered for level 1 [ 14.060000] md: raid10 personality registered for level 10 [ 14.070000] md: raid6 personality registered for level 6 [ 14.070000] md: raid5 personality registered for level 5 [ 14.080000] md: raid4 personality registered for level 4 [ 14.090000] device-mapper: ioctl: 4.15.0-ioctl (2009-04-01) initialised: dm-devel@redhat.com
But the RAID devices are nowhere to be found:
[ 14.120000] md: Waiting for all devices to be available before autodetect [ 14.120000] md: If you don't use raid, use raid=noautodetect [ 14.130000] md: Autodetecting RAID arrays. [ 14.130000] md: Scanned 0 and added 0 devices. [ 14.140000] md: autorun ... [ 14.140000] md: ... autorun DONE.
So my observation is that the RAID array also has problem. Either md0 is corrupted, or u-boot envs were corrupted so the kernel cannot initialize the array, and thus cannot see md0.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Bricked Synology DS213 (Kirkwood) so close September 26, 2020 12:37AM |
Admin Registered: 13 years ago Posts: 18,997 |
Let that sink in a bit. And I'll come back for more. The question in the mean time is:
- Does Synology have a USB recovery procedure? i.e. prepare a specially formatted USB and that will be detected during power up and boot, and then started by u-boot to restore stock u-boot and envs.
- Can you find original stock u-boot envs listing (like in the 1st time booting the box) that we can compare with the current settings to see if any envs need to be reset?
======
If the answers are negative, then perhaps it's time to try to boot with USB rootfs using Debian-5.2.9-kirkwood-tld-1-rootfs-bodhi.tar.bz2 from my release thread:
https://forum.doozan.com/read.php?2,12096
And from a running Debian system, you will have more flexibility to go forward. Either keep running with the new system on USB, or try to recover stock FW from there.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
- Does Synology have a USB recovery procedure? i.e. prepare a specially formatted USB and that will be detected during power up and boot, and then started by u-boot to restore stock u-boot and envs.
- Can you find original stock u-boot envs listing (like in the 1st time booting the box) that we can compare with the current settings to see if any envs need to be reset?
======
If the answers are negative, then perhaps it's time to try to boot with USB rootfs using Debian-5.2.9-kirkwood-tld-1-rootfs-bodhi.tar.bz2 from my release thread:
https://forum.doozan.com/read.php?2,12096
And from a running Debian system, you will have more flexibility to go forward. Either keep running with the new system on USB, or try to recover stock FW from there.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Bricked Synology DS213 (Kirkwood) so close September 26, 2020 12:13PM |
Registered: 4 years ago Posts: 78 |
bodhi Wrote:
>
> From the bootargs envs, we can see that the rootfs
> is on the RAID array
>
> So my observation is that the RAID array also has
> problem. Either md0 is corrupted, or u-boot envs
> were corrupted so the kernel cannot initialize the
> array, and thus cannot see md0.
That's odd, as there has never been any raid array on this box. I have a fresh drive in it which should allow the box to be discoverable on the network with the Synology discovery software for first time setup of a single or two drives. But that discovery software is not seeing it. This would have to be in the firmware.
>
> From the bootargs envs, we can see that the rootfs
> is on the RAID array
>
> So my observation is that the RAID array also has
> problem. Either md0 is corrupted, or u-boot envs
> were corrupted so the kernel cannot initialize the
> array, and thus cannot see md0.
That's odd, as there has never been any raid array on this box. I have a fresh drive in it which should allow the box to be discoverable on the network with the Synology discovery software for first time setup of a single or two drives. But that discovery software is not seeing it. This would have to be in the firmware.
|
Re: Bricked Synology DS213 (Kirkwood) so close September 26, 2020 02:34PM |
Registered: 4 years ago Posts: 78 |
bodhi Wrote:
-------------------------------------------------------
> Let that sink in a bit. And I'll come back for
> more. The question in the mean time is:
>
> - Does Synology have a USB recovery procedure?
> i.e. prepare a specially formatted USB and that
> will be detected during power up and boot, and
> then started by u-boot to restore stock u-boot and
> envs.
Not that I'm aware of.
> - Can you find original stock u-boot envs listing
> (like in the 1st time booting the box) that we can
> compare with the current settings to see if any
> envs need to be reset?
>
I do have a DS212 which is what I was migrating from that is currently running two drives in non array. It is the same processor with less memory from what I understand. Unless there is another method to access the ENVS I would have to crack the case though and hook up the serial cable.
-------------------------------------------------------
> Let that sink in a bit. And I'll come back for
> more. The question in the mean time is:
>
> - Does Synology have a USB recovery procedure?
> i.e. prepare a specially formatted USB and that
> will be detected during power up and boot, and
> then started by u-boot to restore stock u-boot and
> envs.
Not that I'm aware of.
> - Can you find original stock u-boot envs listing
> (like in the 1st time booting the box) that we can
> compare with the current settings to see if any
> envs need to be reset?
>
I do have a DS212 which is what I was migrating from that is currently running two drives in non array. It is the same processor with less memory from what I understand. Unless there is another method to access the ENVS I would have to crack the case though and hook up the serial cable.
|
Re: Bricked Synology DS213 (Kirkwood) so close September 26, 2020 04:08PM |
Admin Registered: 13 years ago Posts: 18,997 |
itangoii,
> I do have a DS212 which is what I was migrating
> from that is currently running two drives in non
> array. It is the same processor with less memory
> from what I understand. Unless there is another
> method to access the ENVS I would have to crack
> the case though and hook up the serial cable.
Or you can ask people who have a functional DS213 to get this info.
Log in as root. At command line,
If the 1st commands failed to show the mtds definition then you need serial console to get the envs listing. The last 2 commands check the necessary setup, which we can do if stock OS does not have.
and please post the log here.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> I do have a DS212 which is what I was migrating
> from that is currently running two drives in non
> array. It is the same processor with less memory
> from what I understand. Unless there is another
> method to access the ENVS I would have to crack
> the case though and hook up the serial cable.
Or you can ask people who have a functional DS213 to get this info.
Log in as root. At command line,
cat /proc/mtd cat /etc/fw_env.config which fw_printenv
If the 1st commands failed to show the mtds definition then you need serial console to get the envs listing. The last 2 commands check the necessary setup, which we can do if stock OS does not have.
and please post the log here.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Bricked Synology DS213 (Kirkwood) so close September 26, 2020 07:36PM |
Registered: 4 years ago Posts: 78 |
|
Re: Bricked Synology DS213 (Kirkwood) so close September 26, 2020 09:37PM |
Admin Registered: 13 years ago Posts: 18,997 |
itangoii,
Please post a little more info when describing your problem.
"Uboot will no longer come up when powered on". Did you mean with serial console connected, power on the box and see no output like it was before?
If that's true then, see this post in the Wiki thread:
Basically, from your serial console host, you would run kwboot to load a u-boot image over serial. This u-boot image could be a backup file that you have dump the mtd0 content to. Or the image could come from FW Upgrade package for your box.
Take a look and post back with question if you're not sure about something.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Please post a little more info when describing your problem.
"Uboot will no longer come up when powered on". Did you mean with serial console connected, power on the box and see no output like it was before?
If that's true then, see this post in the Wiki thread:
Quote
Unbricking with Serial Console & JTAG console
Repair Pogo E02 with Raspberry PI (JTAG) and OpenOCD
Serial Port connector - what are people using to make it work
Serial Console hookup - GoFlex Net (external link)
Serial Console hookup - Pogoplug E02 and Pogoplug Pro V3 (external link)
OSX Serial/Net Console
Use Phone Jack - Phone Jack Serial Console Pics
Adding serial connector to Pogoplug Mobile (external link)
WD Mycloud EX2100/4100 Serial Console pic1, also pic2, pic3
Dreamplug Serial Console
How to unbrick your box using serial console with kwboot
kwboot on Mac OSX 10
Unbrick a Pogoplug Pro v3 OXNAS by flashing u-boot in serial console
Unbricking Synology Diskstation DS414 - See also the working thread for this unbricking session
Basically, from your serial console host, you would run kwboot to load a u-boot image over serial. This u-boot image could be a backup file that you have dump the mtd0 content to. Or the image could come from FW Upgrade package for your box.
Take a look and post back with question if you're not sure about something.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Bricked Synology DS213 (Kirkwood) so close September 27, 2020 09:36AM |
Registered: 4 years ago Posts: 78 |
bodhi Wrote:
-------------------------------------------------------
> itangoii,
>
> Please post a little more info when describing
> your problem.
>
> "Uboot will no longer come up when powered on".
> Did you mean with serial console connected, power
> on the box and see no output like it was before?
>
That is correct. Putty is opened with the correct settings as before, power is given to the synology and not a single character is displayed. I've reset the com port on the computer with same results.
>
> Basically, from your serial console host, you
> would run kwboot to load a u-boot image over
> serial. This u-boot image could be a backup file
> that you have dump the mtd0 content to. Or the
> image could come from FW Upgrade package for your
> box.
>
> Take a look and post back with question if you're
> not sure about something.
I've read other posts of people successfully flashing the uboot bin file with success, but more than 10 hours of searching has not been able to find the uboot bin file for the DS213 and I've looked through years of Synology update packages.
I'll look into your suggested reading, but I don't think kwboot will have any different success if the com port is not responding.
Thanks. I'll post back on what the result is with kwboot.
Edited 1 time(s). Last edit at 09/27/2020 02:15PM by itangoii.
-------------------------------------------------------
> itangoii,
>
> Please post a little more info when describing
> your problem.
>
> "Uboot will no longer come up when powered on".
> Did you mean with serial console connected, power
> on the box and see no output like it was before?
>
That is correct. Putty is opened with the correct settings as before, power is given to the synology and not a single character is displayed. I've reset the com port on the computer with same results.
>
> Basically, from your serial console host, you
> would run kwboot to load a u-boot image over
> serial. This u-boot image could be a backup file
> that you have dump the mtd0 content to. Or the
> image could come from FW Upgrade package for your
> box.
>
> Take a look and post back with question if you're
> not sure about something.
I've read other posts of people successfully flashing the uboot bin file with success, but more than 10 hours of searching has not been able to find the uboot bin file for the DS213 and I've looked through years of Synology update packages.
I'll look into your suggested reading, but I don't think kwboot will have any different success if the com port is not responding.
Thanks. I'll post back on what the result is with kwboot.
Edited 1 time(s). Last edit at 09/27/2020 02:15PM by itangoii.
|
Re: Bricked Synology DS213 (Kirkwood) so close September 27, 2020 03:20PM |
Registered: 4 years ago Posts: 78 |
I may hove gotten lucky after 30 hours. Would you care to take a look inside this and tell me what you think? Especially the DS*.*.sh files.
https://sourceforge.net/projects/dsgpl/files/Synology%20NAS%20GPL%20Source/8451branch/hi3535-source/u-boot-mv-3.5.9.txz/download.
Thanks
https://sourceforge.net/projects/dsgpl/files/Synology%20NAS%20GPL%20Source/8451branch/hi3535-source/u-boot-mv-3.5.9.txz/download.
Thanks
|
Re: Bricked Synology DS213 (Kirkwood) so close September 27, 2020 03:50PM |
Admin Registered: 13 years ago Posts: 18,997 |
itangoii,
> but I don't
> think kwboot will have any different success if
> the com port is not responding.
That's OK. As long as the serial port is working, kwboot can run. This is the recovery path when your NAND u-boot is wiped out, or a wrong file was flashed.
And you cannot use Window to run kwboot. It can be run only from a Linux box.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> but I don't
> think kwboot will have any different success if
> the com port is not responding.
That's OK. As long as the serial port is working, kwboot can run. This is the recovery path when your NAND u-boot is wiped out, or a wrong file was flashed.
And you cannot use Window to run kwboot. It can be run only from a Linux box.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Bricked Synology DS213 (Kirkwood) so close September 27, 2020 04:50PM |
Registered: 4 years ago Posts: 78 |
bodhi Wrote:
-------------------------------------------------------
> itangoii,
>
> > but I don't
> > think kwboot will have any different success if
> > the com port is not responding.
>
> That's OK. As long as the serial port is working,
> kwboot can run. This is the recovery path when
> your NAND u-boot is wiped out, or a wrong file
> was flashed.
>
> And you cannot use Window to run kwboot. It can be
> run only from a Linux box.
I have confirmed through a loopback that the serial port is communicating. I have a VM running Ubuntu 20 that has been configured for com and USB access as well as having loaded u-boot tools and kwboot as I knew it might be needed.
I don't think with all the searching I've done that I'm going to find a pre-compiled uboot for the DS213. Please let me know if you think I can get there with that file I linked to for you. I haven't done much code work other than some resent .net and wayyyy back in the 80's converting Fortran to Basic some of it on a main frame Vax ;-).
If that file is what it appears to be, then it would be a uboot goldmine for Synology people.
Thanks again bodhi.
-------------------------------------------------------
> itangoii,
>
> > but I don't
> > think kwboot will have any different success if
> > the com port is not responding.
>
> That's OK. As long as the serial port is working,
> kwboot can run. This is the recovery path when
> your NAND u-boot is wiped out, or a wrong file
> was flashed.
>
> And you cannot use Window to run kwboot. It can be
> run only from a Linux box.
I have confirmed through a loopback that the serial port is communicating. I have a VM running Ubuntu 20 that has been configured for com and USB access as well as having loaded u-boot tools and kwboot as I knew it might be needed.
I don't think with all the searching I've done that I'm going to find a pre-compiled uboot for the DS213. Please let me know if you think I can get there with that file I linked to for you. I haven't done much code work other than some resent .net and wayyyy back in the 80's converting Fortran to Basic some of it on a main frame Vax ;-).
If that file is what it appears to be, then it would be a uboot goldmine for Synology people.
Thanks again bodhi.
|
Re: Bricked Synology DS213 (Kirkwood) so close September 27, 2020 04:51PM |
Registered: 6 years ago Posts: 183 |
There seems to be uboot source code and a script to build for DS213 in the following archive:
https://sourceforge.net/projects/dsgpl/files/Synology%20NAS%20GPL%20Source/8451branch/6281-source/u-boot-mv-3.5.9.txz/download
https://sourceforge.net/projects/dsgpl/files/Synology%20NAS%20GPL%20Source/8451branch/6281-source/u-boot-mv-3.5.9.txz/download
|
Re: Bricked Synology DS213 (Kirkwood) so close September 27, 2020 05:42PM |
Admin Registered: 13 years ago Posts: 18,997 |
@Koen,
Thanks! I think it is the same as what itangoii post above.
@itangoii,
In the mean time. It seems the closest u-boot to this box is the NSA325 u-boot (also KIrkwood 6282 SoC)
https://forum.doozan.com/read.php?3,12381
When you're ready to try kwboot, I'd like you to try the NSA315 u-boot. Use this kwboot in the tarball:
uboot.2017.07-tld-1.nsa325.mtd0.kwb
=====
Let me take a look at that archive, also look in mainline u-boot.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Thanks! I think it is the same as what itangoii post above.
@itangoii,
In the mean time. It seems the closest u-boot to this box is the NSA325 u-boot (also KIrkwood 6282 SoC)
https://forum.doozan.com/read.php?3,12381
Quote
Download U-Boot images at Dropbox:
....
uboot.2017.07-tld-1.nsa325.bodhi.tar
md5
102be464341ec77de08725998dfca00b
sha256
93968d24efbe9fa1641f93340a4d3c476475c9d63f61573b365976d0770937ad
When you're ready to try kwboot, I'd like you to try the NSA315 u-boot. Use this kwboot in the tarball:
uboot.2017.07-tld-1.nsa325.mtd0.kwb
=====
Let me take a look at that archive, also look in mainline u-boot.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Bricked Synology DS213 (Kirkwood) so close September 27, 2020 05:50PM |
Registered: 4 years ago Posts: 78 |
Koen Wrote:
-------------------------------------------------------
> There seems to be uboot source code and a script
> to build for DS213 in the following archive:
>
> https://sourceforge.net/projects/dsgpl/files/Synology%20NAS%20GPL%20Source/8451branch/6281-source/u-boot-mv-3.5.9.txz/download
Thanks koen. I found that this morning and pointed bodhi at it a couple messages up. The odd thing is that if you look at the ds213.sh it tries to fire off a ds213_config which i have not been able to find in the package. I did find mv_foroceon directory in the board directory which is what the 213 runs on.
Getting closer. I assume this ds213_config is the setup of includes for the particular board for the compile. Soooo close ;-)
-------------------------------------------------------
> There seems to be uboot source code and a script
> to build for DS213 in the following archive:
>
> https://sourceforge.net/projects/dsgpl/files/Synology%20NAS%20GPL%20Source/8451branch/6281-source/u-boot-mv-3.5.9.txz/download
Thanks koen. I found that this morning and pointed bodhi at it a couple messages up. The odd thing is that if you look at the ds213.sh it tries to fire off a ds213_config which i have not been able to find in the package. I did find mv_foroceon directory in the board directory which is what the 213 runs on.
Getting closer. I assume this ds213_config is the setup of includes for the particular board for the compile. Soooo close ;-)
|
Re: Bricked Synology DS213 (Kirkwood) so close September 28, 2020 01:55PM |
Registered: 4 years ago Posts: 78 |
Gave it a try, had to use the -p option in the davygravy article and used your suggested .kwb. The result is below.
./kwboot -t -B 115200 /dev/ttyUSB0 -b uboot.2017.07-tld-1.nsa325.mtd0.kwb -p
Sending boot message. Please reboot the target...-
Sending boot image...
0 % [......................................................................]
1 % [......................................................................]
3 % [......................................................................]
5 % [......................................................................]
6 % [......................................................................]
8 % [......................................................................]
10 % [......................................................................]
11 % [......................................................................]
13 % [......................................................................]
15 % [......................................................................]
17 % [......................................................................]
18 % [......................................................................]
20 % [......................................................................]
22 % [......................................................................]
23 % [......................................................................]
25 % [......................................................................]
27 % [......................................................................]
29 % [......................................................................]
30 % [......................................................................]
32 % [......................................................................]
34 % [......................................................................]
35 % [......................................................................]
37 % [......................................................................]
39 % [......................................................................]
41 % [......................................................................]
42 % [......................................................................]
44 % [......................................................................]
46 % [......................................................................]
47 % [......................................................................]
49 % [......................................................................]
51 % [......................................................................]
53 % [......................................................................]
54 % [......................................................................]
56 % [......................................................................]
58 % [......................................................................]
59 % [......................................................................]
61 % [......................................................................]
63 % [......................................................................]
64 % [......................................................................]
66 % [......................................................................]
68 % [......................................................................]
70 % [......................................................................]
71 % [......................................................................]
73 % [......................................................................]
75 % [......................................................................]
76 % [......................................................................]
78 % [......................................................................]
80 % [......................................................................]
82 % [......................................................................]
83 % [......................................................................]
85 % [......................................................................]
87 % [......................................................................]
88 % [......................................................................]
90 % [......................................................................]
92 % [......................................................................]
94 % [......................................................................]
95 % [......................................................................]
97 % [......................................................................]
99 % [....................................]
[Type Ctrl-\ + c to quit]
U-Boot 2017.07-tld-1 (Sep 05 2017 - 00:42:03 -0700)
ZyXEL NSA325 2-Bay Power Media Server
SoC: Kirkwood 88F6282_A1
DRAM: 512 MiB
WARNING: Caches not enabled
NAND: 0 MiB
*** Warning - readenv() failed, using default environment
In: serial
Out: serial
Err: serial
Net: egiga0
MV88E1318 PHY initialized on egiga0
Hit any key to stop autoboot: 0
starting USB...
USB0: USB EHCI 1.00
scanning bus 0 for devices... 4 USB Device(s) found
scanning usb for storage devices...
Use USB retry period from the environment: 15 second(s)
Use USB retry period from the environment: 15 second(s)
Device NOT ready
Request Sense returned 02 3A 00
Use USB retry period from the environment: 15 second(s)
Device NOT ready
Request Sense returned 02 3A 00
1 Storage Device(s) found
Reset IDE: ide_preinit failed
Partition Map for USB device 0 -- Partition Type: DOS
Part Start Sector Num Sectors UUID Type
1 2048 60602368 ac0e13c9-01 83
## Unknown partition table type 0
## Unknown partition table type 0
## Unknown partition table type 0
## Unknown partition table type 0
## Unknown partition table type 0
## Unknown partition table type 0
loading envs from usb 0 ...
** File not found /boot/uEnv.txt **
no IDE devices available
running scan_disk ...
Scan device usb
device usb 0:1
1 bytes read in 754 ms (0 Bytes/s)
Found bootable drive on usb 0
loading uImage ...
5007680 bytes read in 1039 ms (4.6 MiB/s)
loading uInitrd ...
EHCI timed out on TD - token=0x800d8d80
9713936 bytes read in 6576 ms (1.4 MiB/s)
loading DTB /boot/dts/kirkwood-nsa325.dtb ...
14006 bytes read in 1615 ms (7.8 KiB/s)
## Booting kernel from Legacy Image at 00800000 ...
Image Name: Linux-5.2.9-kirkwood-tld-1
Created: 2020-09-27 17:30:02 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 5007616 Bytes = 4.8 MiB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
Image Name: initramfs-5.2.9-kirkwood-tld-1
Created: 2019-08-25 2:22:50 UTC
Image Type: ARM Linux RAMDisk Image (gzip compressed)
Data Size: 9713872 Bytes = 9.3 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
## Flattened Device Tree blob at 01c00000
Booting using the fdt blob at 0x1c00000
Loading Kernel Image ... OK
Loading Ramdisk to 1f1ca000, end 1fb0d8d0 ... OK
Loading Device Tree to 1f1c3000, end 1f1c96b5 ... OK
Starting kernel ...
Uncompressing Linux... done, booting the kernel.
[ 0.000000][ T0] Booting Linux on physical CPU 0x0
[ 0.000000][ T0] Linux version 5.2.9-kirkwood-tld-1 (root@tldDebian) (gcc version 6.3.0 20170516 (Debian 6.3.0-18+deb9u1)) #1 PREEMPT Sat Aug 17 15:00:56 PDT 2019
[ 0.000000][ T0] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=0005397f
[ 0.000000][ T0] CPU: VIVT data cache, VIVT instruction cache
[ 0.000000][ T0] OF: fdt: Machine model: Synology DS212, DS212p v10, v20, DS213air v10, DS213 v10
[ 0.000000][ T0] Memory policy: Data cache writeback
[ 0.000000][ T0] Built 1 zonelists, mobility grouping on. Total pages: 32512
[ 0.000000][ T0] Kernel command line: console=ttyS0,115200n8
[ 0.000000][ T0] Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
[ 0.000000][ T0] Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
[ 0.000000][ T0] Memory: 114280K/131072K available (9216K kernel code, 868K rwdata, 3400K rodata, 1024K init, 301K bss, 16792K reserved, 0K cma-reserved)
[ 0.000000][ T0] random: get_random_u32 called from cache_alloc_refill+0x38c/0x928 with crng_init=0
[ 0.000000][ T0] rcu: Preemptible hierarchical RCU implementation.
[ 0.000000][ T0] Tasks RCU enabled.
[ 0.000000][ T0] rcu: RCU calculated value of scheduler-enlistment delay is 10 jiffies.
[ 0.000000][ T0] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16
[ 0.000000][ T0] clocksource: orion_clocksource: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 9556302233 ns
[ 0.000007][ T0] sched_clock: 32 bits at 200MHz, resolution 5ns, wraps every 10737418237ns
[ 0.000039][ T0] Switching to timer-based delay loop, resolution 5ns
[ 0.000608][ T0] Console: colour dummy device 80x30
[ 0.000651][ T0] Calibrating delay loop (skipped), value calculated using timer frequency.. 400.00 BogoMIPS (lpj=2000000)
[ 0.000672][ T0] pid_max: default: 32768 minimum: 301
[ 0.000948][ T0] LSM: Security Framework initializing
[ 0.001091][ T0] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.001113][ T0] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.001847][ T0] *** VALIDATE proc ***
[ 0.002077][ T0] *** VALIDATE cgroup1 ***
[ 0.002098][ T0] *** VALIDATE cgroup2 ***
[ 0.002189][ T0] CPU: Testing write buffer coherency: ok
[ 0.003675][ T1] Setting up static identity map for 0x100000 - 0x100058
[ 0.003933][ T1] mvebu-soc-id: MVEBU SoC ID=0x6282, Rev=0x1
[ 0.004181][ T1] rcu: Hierarchical SRCU implementation.
[ 0.006432][ T1] devtmpfs: initialized
[ 0.013486][ T1] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[ 0.013513][ T1] futex hash table entries: 256 (order: -1, 3072 bytes)
[ 0.013728][ T1] xor: measuring software checksum speed
[ 0.110101][ T1] arm4regs : 1806.800 MB/sec
[ 0.210060][ T1] 8regs : 1084.800 MB/sec
[ 0.310061][ T1] 32regs : 1577.200 MB/sec
[ 0.310077][ T1] xor: using function: arm4regs (1806.800 MB/sec)
[ 0.310092][ T1] prandom: seed boundary self test passed
[ 0.312614][ T1] prandom: 100 self tests passed
[ 0.312622][ T1] pinctrl core: initialized pinctrl subsystem
[ 0.313813][ T1] NET: Registered protocol family 16
[ 0.314147][ T1] DMA: preallocated 256 KiB pool for atomic coherent allocations
[ 0.314777][ T1] audit: initializing netlink subsys (disabled)
[ 0.315848][ T14] audit: type=2000 audit(0.310:1): state=initialized audit_enabled=0 res=1
[ 0.315954][ T1] cpuidle: using governor ladder
[ 0.316019][ T1] cpuidle: using governor menu
[ 0.316382][ T1] Feroceon L2: Enabling L2
[ 0.316425][ T1] Feroceon L2: Cache support initialised.
[ 0.320707][ T1] No ATAGs?
[ 2.560045][ C0] random: fast init done
[ 3.878764][ T71] alg: No test for lzo-rle (lzo-rle-generic)
[ 3.879035][ T73] alg: No test for lzo-rle (lzo-rle-scomp)
[ 4.050671][ T1] raid6: int32x8 gen() 208 MB/s
[ 4.220373][ T1] raid6: int32x8 xor() 142 MB/s
[ 4.390209][ T1] raid6: int32x4 gen() 209 MB/s
[ 4.560127][ T1] raid6: int32x4 xor() 137 MB/s
[ 4.730229][ T1] raid6: int32x2 gen() 209 MB/s
[ 4.900199][ T1] raid6: int32x2 xor() 151 MB/s
[ 5.070275][ T1] raid6: int32x1 gen() 156 MB/s
[ 5.240049][ T1] raid6: int32x1 xor() 108 MB/s
[ 5.240056][ T1] raid6: using algorithm int32x2 gen() 209 MB/s
[ 5.240062][ T1] raid6: .... xor() 151 MB/s, rmw enabled
[ 5.240067][ T1] raid6: using intx1 recovery algorithm
[ 5.240300][ T1] vgaarb: loaded
[ 5.240689][ T1] SCSI subsystem initialized
[ 5.241081][ T1] usbcore: registered new interface driver usbfs
[ 5.241126][ T1] usbcore: registered new interface driver hub
[ 5.241189][ T1] usbcore: registered new device driver usb
[ 5.241316][ T1] pps_core: LinuxPPS API ver. 1 registered
[ 5.241324][ T1] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[ 5.241342][ T1] PTP clock support registered
[ 5.242271][ T1] clocksource: Switched to clocksource orion_clocksource
[ 5.870763][ T1] VFS: Disk quotas dquot_6.6.0
[ 5.870840][ T1] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[ 5.877748][ T1] NET: Registered protocol family 2
[ 5.878390][ T1] tcp_listen_portaddr_hash hash table entries: 512 (order: 0, 4096 bytes)
[ 5.878421][ T1] TCP established hash table entries: 1024 (order: 0, 4096 bytes)
[ 5.878441][ T1] TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
[ 5.878459][ T1] TCP: Hash tables configured (established 1024 bind 1024)
[ 5.878533][ T1] UDP hash table entries: 256 (order: 0, 4096 bytes)
[ 5.878556][ T1] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[ 5.878729][ T1] NET: Registered protocol family 1
[ 5.879249][ T1] RPC: Registered named UNIX socket transport module.
[ 5.879259][ T1] RPC: Registered udp transport module.
[ 5.879264][ T1] RPC: Registered tcp transport module.
[ 5.879269][ T1] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 5.879280][ T1] PCI: CLS 0 bytes, default 32
[ 5.879522][ T1] NetWinder Floating Point Emulator V0.97 (double precision)
[ 5.880363][ T1] Initialise system trusted keyrings
[ 5.880405][ T1] Key type blacklist registered
[ 5.880594][ T1] workingset: timestamp_bits=30 max_order=15 bucket_order=0
[ 5.880660][ T1] zbud: loaded
[ 5.881449][ T1] NFS: Registering the id_resolver key type
[ 5.881472][ T1] Key type id_resolver registered
[ 5.881479][ T1] Key type id_legacy registered
[ 5.881493][ T1] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[ 5.881505][ T1] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
[ 5.881715][ T1] jffs2: version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc.
[ 5.881881][ T1] fuse: init (API version 7.31)
[ 5.882173][ T1] orangefs_debugfs_init: called with debug mask: :none: :0:
[ 5.882404][ T1] orangefs_init: module version upstream loaded
[ 5.882415][ T1] SGI XFS with ACLs, security attributes, realtime, scrub, no debug enabled
[ 5.884553][ T1] async_tx: api initialized (async)
[ 5.884570][ T1] Key type asymmetric registered
[ 5.884577][ T1] Asymmetric key parser 'x509' registered
[ 5.884622][ T1] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 246)
[ 5.885614][ T1] kirkwood-pinctrl f1010000.pin-controller: registered pinctrl driver
[ 5.887062][ T1] mvebu-pcie mbus@f1000000:pcie@82000000: PCI host bridge to bus 0000:00
[ 5.887081][ T1] pci_bus 0000:00: root bus resource [bus 00-ff]
[ 5.887091][ T1] pci_bus 0000:00: root bus resource [mem 0xe0000000-0xefffffff]
[ 5.887100][ T1] pci_bus 0000:00: root bus resource [io 0x1000-0xeffff]
[ 5.887234][ T1] pci 0000:00:01.0: [11ab:6282] type 01 class 0x060400
[ 5.887266][ T1] pci 0000:00:01.0: reg 0x38: [mem 0x00000000-0x000007ff pref]
[ 5.887523][ T1] pci 0000:00:02.0: [11ab:6282] type 01 class 0x060400
[ 5.887549][ T1] pci 0000:00:02.0: reg 0x38: [mem 0x00000000-0x000007ff pref]
[ 5.889044][ T1] PCI: bus0: Fast back to back transfers disabled
[ 5.889062][ T1] pci 0000:00:01.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[ 5.889080][ T1] pci 0000:00:02.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[ 5.890609][ T1] PCI: bus1: Fast back to back transfers enabled
[ 5.890627][ T1] pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01
[ 5.892140][ T1] PCI: bus2: Fast back to back transfers enabled
[ 5.892156][ T1] pci_bus 0000:02: busn_res: [bus 02-ff] end is updated to 02
[ 5.892388][ T1] pci 0000:00:01.0: BAR 6: assigned [mem 0xe0000000-0xe00007ff pref]
[ 5.892403][ T1] pci 0000:00:02.0: BAR 6: assigned [mem 0xe0100000-0xe01007ff pref]
[ 5.892414][ T1] pci 0000:00:01.0: PCI bridge to [bus 01]
[ 5.892430][ T1] pci 0000:00:02.0: PCI bridge to [bus 02]
[ 5.892929][ T1] mv_xor f1060800.xor: Marvell shared XOR driver
[ 5.952819][ T1] mv_xor f1060800.xor: Marvell XOR (Registers Mode): ( xor cpy intr )
[ 5.954147][ T1] mv_xor f1060900.xor: Marvell shared XOR driver
[ 6.012859][ T1] mv_xor f1060900.xor: Marvell XOR (Registers Mode): ( xor cpy intr )
[ 6.014398][ T1] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
[ 6.015388][ T1] printk: console [ttyS0] disabled
[ 6.015449][ T1] f1012000.serial: ttyS0 at MMIO 0xf1012000 (irq = 27, base_baud = 12500000) is a 16550A
[ 6.889565][ T1] printk: console [ttyS0] enabled
[ 6.894967][ T1] f1012100.serial: ttyS1 at MMIO 0xf1012100 (irq = 28, base_baud = 12500000) is a 16550A
[ 6.910069][ T1] loop: module loaded
[ 6.914544][ T1] sata_mv f1080000.sata: slots 32 ports 2
[ 6.922101][ T1] scsi host0: sata_mv
[ 6.926459][ T1] scsi host1: sata_mv
[ 6.930512][ T1] ata1: SATA max UDMA/133 irq 34
[ 6.935371][ T1] ata2: SATA max UDMA/133 irq 34
[ 6.941515][ T1] m25p80 spi0.0: found n25q064, expected m25p80
[ 6.947836][ T1] m25p80 spi0.0: n25q064 (8192 Kbytes)
[ 6.953220][ T1] 6 fixed-partitions partitions found on MTD device spi0.0
[ 6.960300][ T1] Creating 6 MTD partitions on "spi0.0":
[ 6.965825][ T1] 0x000000000000-0x000000080000 : "RedBoot"
[ 6.972595][ T1] 0x000000080000-0x000000280000 : "zImage"
[ 6.979167][ T1] 0x000000280000-0x0000003c0000 : "rd.gz"
[ 6.985687][ T1] 0x0000003c0000-0x0000003d0000 : "vendor"
[ 6.992239][ T1] 0x0000003d0000-0x0000003f0000 : "RedBoot config"
[ 6.999550][ T1] 0x0000003f0000-0x000000400000 : "FIS directory"
[ 7.007585][ T1] libphy: Fixed MDIO Bus: probed
[ 7.013005][ T1] libphy: orion_mdio_bus: probed
[ 7.018025][ T1] mdio_bus f1072004.mdio-bus-mii: MDIO device at address 8 is missing.
[ 7.026374][ T1] mdio_bus f1072004.mdio-bus-mii: MDIO device at address 9 is missing.
[ 7.034653][ T1] mv643xx_eth: MV-643xx 10/100/1000 ethernet driver version 1.4
[ 7.042514][ T1] mv643xx_eth_port mv643xx_eth_port.0: DMA mask not set
[ 7.049459][ T1] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 7.056786][ T1] ehci-pci: EHCI PCI platform driver
[ 7.061992][ T1] ehci-orion: EHCI orion driver
[ 7.066890][ T1] orion-ehci f1050000.ehci: EHCI Host Controller
[ 7.073153][ T1] orion-ehci f1050000.ehci: new USB bus registered, assigned bus number 1
[ 7.081675][ T1] orion-ehci f1050000.ehci: irq 32, io mem 0xf1050000
[ 7.112294][ T1] orion-ehci f1050000.ehci: USB 2.0 started, EHCI 1.00
[ 7.119240][ T1] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.02
[ 7.128366][ T1] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 7.136336][ T1] usb usb1: Product: EHCI Host Controller
[ 7.141930][ T1] usb usb1: Manufacturer: Linux 5.2.9-kirkwood-tld-1 ehci_hcd
[ 7.149287][ T1] usb usb1: SerialNumber: f1050000.ehci
[ 7.155183][ T1] hub 1-0:1.0: USB hub found
[ 7.159676][ T1] hub 1-0:1.0: 1 port detected
[ 7.164869][ T1] usbcore: registered new interface driver usb-storage
[ 7.171898][ T1] mousedev: PS/2 mouse device common for all mice
[ 7.178460][ T1] i2c /dev entries driver
[ 7.183897][ T1] rtc-s35390a 0-0030: error resetting chip
[ 7.189991][ T1] rtc-s35390a: probe of 0-0030 failed with error -5
[ 7.197027][ T1] device-mapper: uevent: version 1.0.3
[ 7.202656][ T1] device-mapper: ioctl: 4.40.0-ioctl (2019-01-18) initialised: dm-devel@redhat.com
[ 7.212138][ T1] device-mapper: multipath round-robin: version 1.2.0 loaded
[ 7.219457][ T1] device-mapper: multipath queue-length: version 0.2.0 loaded
[ 7.226842][ T1] device-mapper: multipath service-time: version 0.3.0 loaded
[ 7.234273][ T1] device-mapper: dm-log-userspace: version 1.3.0 loaded
[ 7.241117][ T1] device-mapper: raid: Loading target version 1.14.0
[ 7.248161][ T1] kirkwood-pinctrl f1010000.pin-controller: pin PIN21 already requested by f1080000.sata; cannot claim for gpio-leds-hdd-21-2
[ 7.261139][ T1] kirkwood-pinctrl f1010000.pin-controller: pin-21 (gpio-leds-hdd-21-2) status -22
[ 7.270341][ T112] ata1: SATA link down (SStatus 0 SControl F300)
[ 7.276668][ T1] kirkwood-pinctrl f1010000.pin-controller: could not request pin 21 (PIN21) from group mpp21 on device f1010000.pin-controller
[ 7.289923][ T1] leds-gpio gpio-leds-hdd-21-2: Error applying setting, reverse things back
[ 7.298517][ T1] leds-gpio: probe of gpio-leds-hdd-21-2 failed with error -22
[ 7.306148][ T1] hidraw: raw HID events driver (C) Jiri Kosina
[ 7.312545][ T1] drop_monitor: Initializing network drop monitor service
[ 7.319746][ T1] NET: Registered protocol family 17
[ 7.325133][ T1] Key type dns_resolver registered
[ 7.330645][ T1] registered taskstats version 1
[ 7.335491][ T1] Loading compiled-in X.509 certificates
[ 7.341066][ T1] zswap: loaded using pool lzo/zbud
[ 7.356305][ T1] Key type big_key registered
[ 7.363241][ T1] Key type encrypted registered
[ 7.369701][ T1] hctosys: unable to open rtc device (rtc0)
[ 7.532305][ T15] usb 1-1: new high-speed USB device number 2 using orion-ehci
[ 7.646050][ T114] ata2: SATA link down (SStatus 0 SControl F300)
[ 7.662430][ T1] md: Waiting for all devices to be available before autodetect
[ 7.669941][ T1] md: If you don't use raid, use raid=noautodetect
[ 7.676860][ T1] md: Autodetecting RAID arrays.
[ 7.681670][ T1] md: autorun ...
[ 7.685255][ T1] md: ... autorun DONE.
[ 7.689481][ T1] VFS: Cannot open root device "(null)" or unknown-block(0,0): error -6
[ 7.697742][ T1] Please append a correct "root=" boot option; here are the available partitions:
[ 7.706907][ T1] 1f00 512 mtdblock0
[ 7.706910][ T1] (driver?)
[ 7.714907][ T1] 1f01 2048 mtdblock1
[ 7.714909][ T1] (driver?)
[ 7.722895][ T1] 1f02 1280 mtdblock2
[ 7.722897][ T1] (driver?)
[ 7.730853][ T1] 1f03 64 mtdblock3
[ 7.730855][ T1] (driver?)
[ 7.738864][ T1] 1f04 128 mtdblock4
[ 7.738866][ T1] (driver?)
[ 7.746916][ T1] 1f05 64 mtdblock5
[ 7.746919][ T1] (driver?)
[ 7.754940][ T1] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
[ 7.763938][ T1] CPU: 0 PID: 1 Comm: swapper Not tainted 5.2.9-kirkwood-tld-1 #1
[ 7.771625][ T1] Hardware name: Marvell Kirkwood (Flattened Device Tree)
[ 7.778633][ T1] [<c010f6ac>] (unwind_backtrace) from [<c010bb00>] (show_stack+0x10/0x14)
[ 7.787116][ T1] [<c010bb00>] (show_stack) from [<c0119fa0>] (panic+0xe0/0x30c)
[ 7.794728][ T1] [<c0119fa0>] (panic) from [<c0e01628>] (mount_block_root+0x1bc/0x2a4)
[ 7.802944][ T1] [<c0e01628>] (mount_block_root) from [<c0e017f8>] (mount_root+0xe8/0x154)
[ 7.811507][ T1] [<c0e017f8>] (mount_root) from [<c0e019b0>] (prepare_namespace+0x14c/0x18c)
[ 7.820244][ T1] [<c0e019b0>] (prepare_namespace) from [<c0e011c8>] (kernel_init_freeable+0x270/0x2dc)
[ 7.829857][ T1] [<c0e011c8>] (kernel_init_freeable) from [<c09dcee0>] (kernel_init+0x8/0x10c)
[ 7.838767][ T1] [<c09dcee0>] (kernel_init) from [<c01010e0>] (ret_from_fork+0x14/0x34)
[ 7.847063][ T1] Exception stack(0xc7881fb0 to 0xc7881ff8)
[ 7.852828][ T1] 1fa0: 00000000 00000000 00000000 00000000
[ 7.861741][ T1] 1fc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[ 7.870652][ T1] 1fe0: 00000000 00000000 00000000 00000000 00000013 00000000
[ 7.877992][ T1] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) ]---
|
Re: Bricked Synology DS213 (Kirkwood) so close September 28, 2020 05:19PM |
Registered: 4 years ago Posts: 78 |
|
Re: Bricked Synology DS213 (Kirkwood) so close September 28, 2020 05:23PM |
Admin Registered: 13 years ago Posts: 18,997 |
itangoii,
Congrats! you now have a recovery method to unbrick the box should anything goes wrong.
This looks bad. But most likely because these 2 boxes have different flash and/or envs location.
Let me reorient myself to your current status and suggest what to do next.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> U-Boot 2017.07-tld-1 (Sep 05 2017 - 00:42:03 > -0700) > ZyXEL NSA325 2-Bay Power Media Server > > SoC: Kirkwood 88F6282_A1 > DRAM: 512 MiB ..... Hit any key to stop autoboot: 0
Congrats! you now have a recovery method to unbrick the box should anything goes wrong.
> NAND: 0 MiB > *** Warning - readenv() failed, using default > environment
This looks bad. But most likely because these 2 boxes have different flash and/or envs location.
Let me reorient myself to your current status and suggest what to do next.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Bricked Synology DS213 (Kirkwood) so close September 28, 2020 05:27PM |
Registered: 4 years ago Posts: 78 |
|
Re: Bricked Synology DS213 (Kirkwood) so close September 28, 2020 05:36PM |
Admin Registered: 13 years ago Posts: 18,997 |
itangoii,
> I may be able to acquire another identical
> machine, would it be possible to pull
> anything/everything needed of of it? I'm just
> throwing things out here.
That would be the best way to unbrick this current box.
You could restore the SPI flash MTD partitions on this box using the backup MTDs from the good box.
And on the good box, you can see what the u-boot envs look like, so the restore will be a lot easier.
And yes, everything you need, you can get from the good box.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> I may be able to acquire another identical
> machine, would it be possible to pull
> anything/everything needed of of it? I'm just
> throwing things out here.
That would be the best way to unbrick this current box.
You could restore the SPI flash MTD partitions on this box using the backup MTDs from the good box.
And on the good box, you can see what the u-boot envs look like, so the restore will be a lot easier.
And yes, everything you need, you can get from the good box.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Bricked Synology DS213 (Kirkwood) so close September 28, 2020 05:51PM |
Admin Registered: 13 years ago Posts: 18,997 |
itangoii,
Now you are also very close to be able to run this DS213 box with latest Linux kernel and Debian permanently, if you'd like to.
We only need to adjust the bootargs a bit. The error you saw at the end was the kernel could not mount the rootfs on USB drive.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Now you are also very close to be able to run this DS213 box with latest Linux kernel and Debian permanently, if you'd like to.
We only need to adjust the bootargs a bit. The error you saw at the end was the kernel could not mount the rootfs on USB drive.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Bricked Synology DS213 (Kirkwood) so close September 28, 2020 05:56PM |
Registered: 4 years ago Posts: 78 |
bodhi Wrote:
-------------------------------------------------------
> itangoii,
>
> Now you are also very close to be able to run this
> DS213 box with latest Linux kernel and Debian
> permanently, if you'd like to.
>
> We only need to adjust the bootargs a bit. The
> error you saw at the end was the kernel could not
> mount the rootfs on USB drive.
Should I have had a USB in it?
What would I have if we did flash it to Debian? If it winds up being an empty box it does not help much.
I would not be able to acquire the other DS213 for two weeks so if at all possible would like to proceed forward. Are there any other .KWB that I might try?
Thanks
-------------------------------------------------------
> itangoii,
>
> Now you are also very close to be able to run this
> DS213 box with latest Linux kernel and Debian
> permanently, if you'd like to.
>
> We only need to adjust the bootargs a bit. The
> error you saw at the end was the kernel could not
> mount the rootfs on USB drive.
Should I have had a USB in it?
What would I have if we did flash it to Debian? If it winds up being an empty box it does not help much.
I would not be able to acquire the other DS213 for two weeks so if at all possible would like to proceed forward. Are there any other .KWB that I might try?
Thanks
|
Re: Bricked Synology DS213 (Kirkwood) so close September 28, 2020 06:45PM |
Admin Registered: 13 years ago Posts: 18,997 |
> Should I have had a USB in it?
I thought you already did. The rootfs Debian-5.2.9-kirkwood-tld-1-rootfs-bodhi.tar.bz2 is the full Debian rootfs.
>
> What would I have if we did flash it to Debian?
> If it winds up being an empty box it does not help
> much.
Exactly. When you run Debian-5.2.9-kirkwood-tld-1-rootfs-bodhi.tar.bz2 on USB, you are in a mainline Debian system. At that point, you have an easy way to restore your FW using a good box MTDs backup files. But if you don't want to see Debian running then there is no need to have USB.
You can skip that, and just flash the backup files to SPI flash in u-boot. To do this, it is a little bit more difficult (see 3 alternatives I listed below).
> I would not be able to acquire the other DS213 for
> two weeks so if at all possible would like to
> proceed forward. Are there any other .KWB that I
> might try?
What you need is a good set of u-boot envs, and backup SPI flash MTDs. But let me see if another u-boot can be tried and post back.
=====
The perfect match for u-boot would be a mtd0 backup file from a good box. Or newly built u-boot from source.
These alternatives are listed in order of preference:
1. If you can find stock u-boot image from the Synology FW release, that would be good to go.
2. Backed up mtd0 from a good box. This is done using dd (since this is SPI flash) to dump mtd0 while inside stock OS.
3. Build stock u-boot from GPL source (you do have a link, I have not have some free time to look into this yet).
=====
EDITED for clarity
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 09/28/2020 10:52PM by bodhi.
I thought you already did. The rootfs Debian-5.2.9-kirkwood-tld-1-rootfs-bodhi.tar.bz2 is the full Debian rootfs.
>
> What would I have if we did flash it to Debian?
> If it winds up being an empty box it does not help
> much.
Exactly. When you run Debian-5.2.9-kirkwood-tld-1-rootfs-bodhi.tar.bz2 on USB, you are in a mainline Debian system. At that point, you have an easy way to restore your FW using a good box MTDs backup files. But if you don't want to see Debian running then there is no need to have USB.
You can skip that, and just flash the backup files to SPI flash in u-boot. To do this, it is a little bit more difficult (see 3 alternatives I listed below).
> I would not be able to acquire the other DS213 for
> two weeks so if at all possible would like to
> proceed forward. Are there any other .KWB that I
> might try?
What you need is a good set of u-boot envs, and backup SPI flash MTDs. But let me see if another u-boot can be tried and post back.
=====
The perfect match for u-boot would be a mtd0 backup file from a good box. Or newly built u-boot from source.
These alternatives are listed in order of preference:
1. If you can find stock u-boot image from the Synology FW release, that would be good to go.
2. Backed up mtd0 from a good box. This is done using dd (since this is SPI flash) to dump mtd0 while inside stock OS.
3. Build stock u-boot from GPL source (you do have a link, I have not have some free time to look into this yet).
=====
EDITED for clarity
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 09/28/2020 10:52PM by bodhi.
|
Re: Bricked Synology DS213 (Kirkwood) so close September 28, 2020 10:52PM |
Admin Registered: 13 years ago Posts: 18,997 |
I've edited the post above.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Bricked Synology DS213 (Kirkwood) so close September 29, 2020 10:26AM |
Registered: 4 years ago Posts: 78 |
Well, I built the Debian USB per your instructions with the ds212 dtb. I then booted the box with the usb in it with the nsa325 kwb. Results follow.
Edited 1 time(s). Last edit at 09/29/2020 01:06PM by itangoii.
.......................................................]
92 % [......................................................................]
94 % [......................................................................]
95 % [......................................................................]
97 % [......................................................................]
99 % [....................................]
[Type Ctrl-\ + c to quit]
U-Boot 2017.07-tld-1 (Sep 05 2017 - 00:42:03 -0700)
ZyXEL NSA325 2-Bay Power Media Server
SoC: Kirkwood 88F6282_A1
DRAM: 512 MiB
WARNING: Caches not enabled
NAND: 0 MiB
*** Warning - readenv() failed, using default environment
In: serial
Out: serial
Err: serial
Net: egiga0
MV88E1318 PHY initialized on egiga0
Hit any key to stop autoboot: 0
starting USB...
USB0: USB EHCI 1.00
scanning bus 0 for devices... 4 USB Device(s) found
scanning usb for storage devices...
Use USB retry period from the environment: 15 second(s)
Use USB retry period from the environment: 15 second(s)
Device NOT ready
Request Sense returned 02 3A 00
Use USB retry period from the environment: 15 second(s)
Device NOT ready
Request Sense returned 02 3A 00
1 Storage Device(s) found
Reset IDE: ide_preinit failed
Partition Map for USB device 0 -- Partition Type: DOS
Part Start Sector Num Sectors UUID Type
1 2048 60602368 ac0e13c9-01 83
## Unknown partition table type 0
## Unknown partition table type 0
## Unknown partition table type 0
## Unknown partition table type 0
## Unknown partition table type 0
## Unknown partition table type 0
loading envs from usb 0 ...
** File not found /boot/uEnv.txt **
no IDE devices available
running scan_disk ...
Scan device usb
device usb 0:1
1 bytes read in 692 ms (0 Bytes/s)
Found bootable drive on usb 0
loading uImage ...
4985680 bytes read in 976 ms (4.9 MiB/s)
loading uInitrd ...
EHCI timed out on TD - token=0x800d8d80
9713936 bytes read in 6529 ms (1.4 MiB/s)
loading DTB /boot/dts/kirkwood-nsa325.dtb ...
14006 bytes read in 1554 ms (8.8 KiB/s)
## Booting kernel from Legacy Image at 00800000 ...
Image Name: Linux-5.2.9-kirkwood-tld-1
Created: 2020-09-29 17:35:10 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 4985616 Bytes = 4.8 MiB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
Image Name: initramfs-5.2.9-kirkwood-tld-1
Created: 2019-08-25 2:22:50 UTC
Image Type: ARM Linux RAMDisk Image (gzip compressed)
Data Size: 9713872 Bytes = 9.3 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
## Flattened Device Tree blob at 01c00000
Booting using the fdt blob at 0x1c00000
Loading Kernel Image ... OK
Loading Ramdisk to 1f1ca000, end 1fb0d8d0 ... OK
Loading Device Tree to 1f1c3000, end 1f1c96b5 ... OK
Starting kernel ...
Uncompressing Linux... done, booting the kernel.
[ 0.000000][ T0] Booting Linux on physical CPU 0x0
[ 0.000000][ T0] Linux version 5.2.9-kirkwood-tld-1 (root@tldDebian) (gcc version 6.3.0 20170516 (Debian 6.3.0-18+deb9u1)) #1 PREEMPT Sat Aug 17 15:00:56 PDT 2019
[ 0.000000][ T0] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=0005397f
[ 0.000000][ T0] CPU: VIVT data cache, VIVT instruction cache
[ 0.000000][ T0] OF: fdt: Machine model: Synology DS212, DS212p v10, v20, DS213air v10, DS213 v10
[ 0.000000][ T0] Memory policy: Data cache writeback
[ 0.000000][ T0] Built 1 zonelists, mobility grouping on. Total pages: 32512
[ 0.000000][ T0] Kernel command line: console=ttyS0,115200n8
[ 0.000000][ T0] Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
[ 0.000000][ T0] Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
[ 0.000000][ T0] Memory: 114280K/131072K available (9216K kernel code, 868K rwdata, 3400K rodata, 1024K init, 301K bss, 16792K reserved, 0K cma-reserved)
[ 0.000000][ T0] random: get_random_u32 called from cache_alloc_refill+0x38c/0x928 with crng_init=0
[ 0.000000][ T0] rcu: Preemptible hierarchical RCU implementation.
[ 0.000000][ T0] Tasks RCU enabled.
[ 0.000000][ T0] rcu: RCU calculated value of scheduler-enlistment delay is 10 jiffies.
[ 0.000000][ T0] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16
[ 0.000000][ T0] clocksource: orion_clocksource: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 9556302233 ns
[ 0.000007][ T0] sched_clock: 32 bits at 200MHz, resolution 5ns, wraps every 10737418237ns
[ 0.000038][ T0] Switching to timer-based delay loop, resolution 5ns
[ 0.000610][ T0] Console: colour dummy device 80x30
[ 0.000653][ T0] Calibrating delay loop (skipped), value calculated using timer frequency.. 400.00 BogoMIPS (lpj=2000000)
[ 0.000673][ T0] pid_max: default: 32768 minimum: 301
[ 0.000951][ T0] LSM: Security Framework initializing
[ 0.001092][ T0] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.001113][ T0] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.001844][ T0] *** VALIDATE proc ***
[ 0.002074][ T0] *** VALIDATE cgroup1 ***
[ 0.002096][ T0] *** VALIDATE cgroup2 ***
[ 0.002186][ T0] CPU: Testing write buffer coherency: ok
[ 0.003672][ T1] Setting up static identity map for 0x100000 - 0x100058
[ 0.003931][ T1] mvebu-soc-id: MVEBU SoC ID=0x6282, Rev=0x1
[ 0.004179][ T1] rcu: Hierarchical SRCU implementation.
[ 0.006430][ T1] devtmpfs: initialized
[ 0.013457][ T1] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[ 0.013484][ T1] futex hash table entries: 256 (order: -1, 3072 bytes)
[ 0.013699][ T1] xor: measuring software checksum speed
[ 0.110098][ T1] arm4regs : 1806.800 MB/sec
[ 0.210063][ T1] 8regs : 1084.800 MB/sec
[ 0.310060][ T1] 32regs : 1577.200 MB/sec
[ 0.310075][ T1] xor: using function: arm4regs (1806.800 MB/sec)
[ 0.310092][ T1] prandom: seed boundary self test passed
[ 0.312614][ T1] prandom: 100 self tests passed
[ 0.312622][ T1] pinctrl core: initialized pinctrl subsystem
[ 0.313808][ T1] NET: Registered protocol family 16
[ 0.314142][ T1] DMA: preallocated 256 KiB pool for atomic coherent allocations
[ 0.314771][ T1] audit: initializing netlink subsys (disabled)
[ 0.315834][ T14] audit: type=2000 audit(0.310:1): state=initialized audit_enabled=0 res=1
[ 0.315942][ T1] cpuidle: using governor ladder
[ 0.316008][ T1] cpuidle: using governor menu
[ 0.316371][ T1] Feroceon L2: Enabling L2
[ 0.316413][ T1] Feroceon L2: Cache support initialised.
[ 0.320696][ T1] No ATAGs?
[ 2.560044][ C0] random: fast init done
[ 3.878689][ T71] alg: No test for lzo-rle (lzo-rle-generic)
[ 3.878955][ T73] alg: No test for lzo-rle (lzo-rle-scomp)
[ 4.050675][ T1] raid6: int32x8 gen() 208 MB/s
[ 4.220365][ T1] raid6: int32x8 xor() 142 MB/s
[ 4.390291][ T1] raid6: int32x4 gen() 208 MB/s
[ 4.560123][ T1] raid6: int32x4 xor() 137 MB/s
[ 4.730270][ T1] raid6: int32x2 gen() 209 MB/s
[ 4.900199][ T1] raid6: int32x2 xor() 151 MB/s
[ 5.070273][ T1] raid6: int32x1 gen() 156 MB/s
[ 5.240049][ T1] raid6: int32x1 xor() 108 MB/s
[ 5.240056][ T1] raid6: using algorithm int32x2 gen() 209 MB/s
[ 5.240062][ T1] raid6: .... xor() 151 MB/s, rmw enabled
[ 5.240067][ T1] raid6: using intx1 recovery algorithm
[ 5.240298][ T1] vgaarb: loaded
[ 5.240687][ T1] SCSI subsystem initialized
[ 5.241078][ T1] usbcore: registered new interface driver usbfs
[ 5.241123][ T1] usbcore: registered new interface driver hub
[ 5.241186][ T1] usbcore: registered new device driver usb
[ 5.241312][ T1] pps_core: LinuxPPS API ver. 1 registered
[ 5.241320][ T1] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[ 5.241338][ T1] PTP clock support registered
[ 5.242261][ T1] clocksource: Switched to clocksource orion_clocksource
[ 5.870751][ T1] VFS: Disk quotas dquot_6.6.0
[ 5.870827][ T1] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[ 5.877745][ T1] NET: Registered protocol family 2
[ 5.878392][ T1] tcp_listen_portaddr_hash hash table entries: 512 (order: 0, 4096 bytes)
[ 5.878423][ T1] TCP established hash table entries: 1024 (order: 0, 4096 bytes)
[ 5.878443][ T1] TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
[ 5.878461][ T1] TCP: Hash tables configured (established 1024 bind 1024)
[ 5.878535][ T1] UDP hash table entries: 256 (order: 0, 4096 bytes)
[ 5.878558][ T1] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[ 5.878732][ T1] NET: Registered protocol family 1
[ 5.879244][ T1] RPC: Registered named UNIX socket transport module.
[ 5.879255][ T1] RPC: Registered udp transport module.
[ 5.879260][ T1] RPC: Registered tcp transport module.
[ 5.879266][ T1] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 5.879276][ T1] PCI: CLS 0 bytes, default 32
[ 5.879520][ T1] NetWinder Floating Point Emulator V0.97 (double precision)
[ 5.880367][ T1] Initialise system trusted keyrings
[ 5.880406][ T1] Key type blacklist registered
[ 5.880597][ T1] workingset: timestamp_bits=30 max_order=15 bucket_order=0
[ 5.880663][ T1] zbud: loaded
[ 5.881449][ T1] NFS: Registering the id_resolver key type
[ 5.881472][ T1] Key type id_resolver registered
[ 5.881479][ T1] Key type id_legacy registered
[ 5.881492][ T1] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[ 5.881505][ T1] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
[ 5.881712][ T1] jffs2: version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc.
[ 5.881878][ T1] fuse: init (API version 7.31)
[ 5.882171][ T1] orangefs_debugfs_init: called with debug mask: :none: :0:
[ 5.882402][ T1] orangefs_init: module version upstream loaded
[ 5.882413][ T1] SGI XFS with ACLs, security attributes, realtime, scrub, no debug enabled
[ 5.884552][ T1] async_tx: api initialized (async)
[ 5.884569][ T1] Key type asymmetric registered
[ 5.884576][ T1] Asymmetric key parser 'x509' registered
[ 5.884621][ T1] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 246)
[ 5.885614][ T1] kirkwood-pinctrl f1010000.pin-controller: registered pinctrl driver
[ 5.887055][ T1] mvebu-pcie mbus@f1000000:pcie@82000000: PCI host bridge to bus 0000:00
[ 5.887073][ T1] pci_bus 0000:00: root bus resource [bus 00-ff]
[ 5.887083][ T1] pci_bus 0000:00: root bus resource [mem 0xe0000000-0xefffffff]
[ 5.887092][ T1] pci_bus 0000:00: root bus resource [io 0x1000-0xeffff]
[ 5.887229][ T1] pci 0000:00:01.0: [11ab:6282] type 01 class 0x060400
[ 5.887261][ T1] pci 0000:00:01.0: reg 0x38: [mem 0x00000000-0x000007ff pref]
[ 5.887517][ T1] pci 0000:00:02.0: [11ab:6282] type 01 class 0x060400
[ 5.887542][ T1] pci 0000:00:02.0: reg 0x38: [mem 0x00000000-0x000007ff pref]
[ 5.889039][ T1] PCI: bus0: Fast back to back transfers disabled
[ 5.889057][ T1] pci 0000:00:01.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[ 5.889075][ T1] pci 0000:00:02.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[ 5.890604][ T1] PCI: bus1: Fast back to back transfers enabled
[ 5.890622][ T1] pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01
[ 5.892133][ T1] PCI: bus2: Fast back to back transfers enabled
[ 5.892149][ T1] pci_bus 0000:02: busn_res: [bus 02-ff] end is updated to 02
[ 5.892383][ T1] pci 0000:00:01.0: BAR 6: assigned [mem 0xe0000000-0xe00007ff pref]
[ 5.892397][ T1] pci 0000:00:02.0: BAR 6: assigned [mem 0xe0100000-0xe01007ff pref]
[ 5.892408][ T1] pci 0000:00:01.0: PCI bridge to [bus 01]
[ 5.892423][ T1] pci 0000:00:02.0: PCI bridge to [bus 02]
[ 5.892925][ T1] mv_xor f1060800.xor: Marvell shared XOR driver
[ 5.952809][ T1] mv_xor f1060800.xor: Marvell XOR (Registers Mode): ( xor cpy intr )
[ 5.954133][ T1] mv_xor f1060900.xor: Marvell shared XOR driver
[ 6.012852][ T1] mv_xor f1060900.xor: Marvell XOR (Registers Mode): ( xor cpy intr )
[ 6.014409][ T1] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
[ 6.015396][ T1] printk: console [ttyS0] disabled
[ 6.015457][ T1] f1012000.serial: ttyS0 at MMIO 0xf1012000 (irq = 27, base_baud = 12500000) is a 16550A
[ 6.889582][ T1] printk: console [ttyS0] enabled
[ 6.894986][ T1] f1012100.serial: ttyS1 at MMIO 0xf1012100 (irq = 28, base_baud = 12500000) is a 16550A
[ 6.910094][ T1] loop: module loaded
[ 6.914566][ T1] sata_mv f1080000.sata: slots 32 ports 2
[ 6.922118][ T1] scsi host0: sata_mv
[ 6.926477][ T1] scsi host1: sata_mv
[ 6.930532][ T1] ata1: SATA max UDMA/133 irq 34
[ 6.935392][ T1] ata2: SATA max UDMA/133 irq 34
[ 6.941530][ T1] m25p80 spi0.0: found n25q064, expected m25p80
[ 6.947856][ T1] m25p80 spi0.0: n25q064 (8192 Kbytes)
[ 6.953247][ T1] 6 fixed-partitions partitions found on MTD device spi0.0
[ 6.960326][ T1] Creating 6 MTD partitions on "spi0.0":
[ 6.965851][ T1] 0x000000000000-0x000000080000 : "RedBoot"
[ 6.972624][ T1] 0x000000080000-0x000000280000 : "zImage"
[ 6.979189][ T1] 0x000000280000-0x0000003c0000 : "rd.gz"
[ 6.985714][ T1] 0x0000003c0000-0x0000003d0000 : "vendor"
[ 6.992294][ T1] 0x0000003d0000-0x0000003f0000 : "RedBoot config"
[ 6.999569][ T1] 0x0000003f0000-0x000000400000 : "FIS directory"
[ 7.007599][ T1] libphy: Fixed MDIO Bus: probed
[ 7.013022][ T1] libphy: orion_mdio_bus: probed
[ 7.018028][ T1] mdio_bus f1072004.mdio-bus-mii: MDIO device at address 8 is missing.
[ 7.026332][ T1] mdio_bus f1072004.mdio-bus-mii: MDIO device at address 9 is missing.
[ 7.034606][ T1] mv643xx_eth: MV-643xx 10/100/1000 ethernet driver version 1.4
[ 7.042468][ T1] mv643xx_eth_port mv643xx_eth_port.0: DMA mask not set
[ 7.049414][ T1] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 7.056740][ T1] ehci-pci: EHCI PCI platform driver
[ 7.061941][ T1] ehci-orion: EHCI orion driver
[ 7.066841][ T1] orion-ehci f1050000.ehci: EHCI Host Controller
[ 7.073112][ T1] orion-ehci f1050000.ehci: new USB bus registered, assigned bus number 1
[ 7.081634][ T1] orion-ehci f1050000.ehci: irq 32, io mem 0xf1050000
[ 7.112286][ T1] orion-ehci f1050000.ehci: USB 2.0 started, EHCI 1.00
[ 7.119230][ T1] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.02
[ 7.128355][ T1] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 7.136328][ T1] usb usb1: Product: EHCI Host Controller
[ 7.141922][ T1] usb usb1: Manufacturer: Linux 5.2.9-kirkwood-tld-1 ehci_hcd
[ 7.149278][ T1] usb usb1: SerialNumber: f1050000.ehci
[ 7.155172][ T1] hub 1-0:1.0: USB hub found
[ 7.159670][ T1] hub 1-0:1.0: 1 port detected
[ 7.164862][ T1] usbcore: registered new interface driver usb-storage
[ 7.171890][ T1] mousedev: PS/2 mouse device common for all mice
[ 7.178450][ T1] i2c /dev entries driver
[ 7.183891][ T1] rtc-s35390a 0-0030: error resetting chip
[ 7.189983][ T1] rtc-s35390a: probe of 0-0030 failed with error -5
[ 7.197031][ T1] device-mapper: uevent: version 1.0.3
[ 7.202657][ T1] device-mapper: ioctl: 4.40.0-ioctl (2019-01-18) initialised: dm-devel@redhat.com
[ 7.212138][ T1] device-mapper: multipath round-robin: version 1.2.0 loaded
[ 7.219457][ T1] device-mapper: multipath queue-length: version 0.2.0 loaded
[ 7.226842][ T1] device-mapper: multipath service-time: version 0.3.0 loaded
[ 7.234271][ T1] device-mapper: dm-log-userspace: version 1.3.0 loaded
[ 7.241110][ T1] device-mapper: raid: Loading target version 1.14.0
[ 7.248161][ T1] kirkwood-pinctrl f1010000.pin-controller: pin PIN21 already requested by f1080000.sata; cannot claim for gpio-leds-hdd-21-2
[ 7.261140][ T1] kirkwood-pinctrl f1010000.pin-controller: pin-21 (gpio-leds-hdd-21-2) status -22
[ 7.270351][ T112] ata1: SATA link down (SStatus 0 SControl F300)
[ 7.276680][ T1] kirkwood-pinctrl f1010000.pin-controller: could not request pin 21 (PIN21) from group mpp21 on device f1010000.pin-controller
[ 7.289932][ T1] leds-gpio gpio-leds-hdd-21-2: Error applying setting, reverse things back
[ 7.298517][ T1] leds-gpio: probe of gpio-leds-hdd-21-2 failed with error -22
[ 7.306151][ T1] hidraw: raw HID events driver (C) Jiri Kosina
[ 7.312554][ T1] drop_monitor: Initializing network drop monitor service
[ 7.319756][ T1] NET: Registered protocol family 17
[ 7.325143][ T1] Key type dns_resolver registered
[ 7.330665][ T1] registered taskstats version 1
[ 7.335509][ T1] Loading compiled-in X.509 certificates
[ 7.341083][ T1] zswap: loaded using pool lzo/zbud
[ 7.356366][ T1] Key type big_key registered
[ 7.363326][ T1] Key type encrypted registered
[ 7.369779][ T1] hctosys: unable to open rtc device (rtc0)
[ 7.532297][ T15] usb 1-1: new high-speed USB device number 2 using orion-ehci
[ 7.646040][ T114] ata2: SATA link down (SStatus 0 SControl F300)
[ 7.662422][ T1] md: Waiting for all devices to be available before autodetect
[ 7.669933][ T1] md: If you don't use raid, use raid=noautodetect
[ 7.676849][ T1] md: Autodetecting RAID arrays.
[ 7.681662][ T1] md: autorun ...
[ 7.685245][ T1] md: ... autorun DONE.
[ 7.689472][ T1] VFS: Cannot open root device "(null)" or unknown-block(0,0): error -6
[ 7.697730][ T1] Please append a correct "root=" boot option; here are the available partitions:
[ 7.706893][ T1] 1f00 512 mtdblock0
[ 7.706896][ T1] (driver?)
[ 7.714887][ T1] 1f01 2048 mtdblock1
[ 7.714889][ T1] (driver?)
[ 7.722879][ T1] 1f02 1280 mtdblock2
[ 7.722881][ T1] (driver?)
[ 7.730837][ T1] 1f03 64 mtdblock3
[ 7.730838][ T1] (driver?)
[ 7.738846][ T1] 1f04 128 mtdblock4
[ 7.738848][ T1] (driver?)
[ 7.746899][ T1] 1f05 64 mtdblock5
[ 7.746902][ T1] (driver?)
[ 7.754924][ T1] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
[ 7.763922][ T1] CPU: 0 PID: 1 Comm: swapper Not tainted 5.2.9-kirkwood-tld-1 #1
[ 7.771607][ T1] Hardware name: Marvell Kirkwood (Flattened Device Tree)
[ 7.778617][ T1] [<c010f6ac>] (unwind_backtrace) from [<c010bb00>] (show_stack+0x10/0x14)
[ 7.787098][ T1] [<c010bb00>] (show_stack) from [<c0119fa0>] (panic+0xe0/0x30c)
[ 7.794711][ T1] [<c0119fa0>] (panic) from [<c0e01628>] (mount_block_root+0x1bc/0x2a4)
[ 7.802928][ T1] [<c0e01628>] (mount_block_root) from [<c0e017f8>] (mount_root+0xe8/0x154)
[ 7.811490][ T1] [<c0e017f8>] (mount_root) from [<c0e019b0>] (prepare_namespace+0x14c/0x18c)
[ 7.820227][ T1] [<c0e019b0>] (prepare_namespace) from [<c0e011c8>] (kernel_init_freeable+0x270/0x2dc)
[ 7.829841][ T1] [<c0e011c8>] (kernel_init_freeable) from [<c09dcee0>] (kernel_init+0x8/0x10c)
[ 7.838749][ T1] [<c09dcee0>] (kernel_init) from [<c01010e0>] (ret_from_fork+0x14/0x34)
[ 7.847046][ T1] Exception stack(0xc7881fb0 to 0xc7881ff8)
[ 7.852811][ T1] 1fa0: 00000000 00000000 00000000 00000000
[ 7.861724][ T1] 1fc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[ 7.870634][ T1] 1fe0: 00000000 00000000 00000000 00000000 00000013 00000000
[ 7.877974][ T1] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) ]---
Edited 1 time(s). Last edit at 09/29/2020 01:06PM by itangoii.
