DS212 kernel problem (?)

Currently reading
DS212 kernel problem (?)

5
2
NAS
DS212
Operating system
  1. Windows
Hi guys, I've had this question asked on the official forum, but didn't get any answers there. Hoping someone here can help me.

I've reset my DS212 to factory state via the DSM web console and it's never come back up since then (there was no power outage). Boots up with all the proper lights and sounds, but the status light keeps flashing orange. It gets an IP from DHCP server and responds to ping, but no ports are open - I tried telnetting into 22, 23, 80, 443, 5000, 5001, with no response. Synology Assistant won't discover it either.

I've tried the reset button, it beeps once after 4 seconds, if I release and instantly press again for a full reset, it only beeps once, not 3 times, after another 4 seconds.

I tried booting without disks, with blank disks, same story.

I've hooked up to the serial console and here are some logs (I had to truncate it to keep the post under 10k chars, let me know if you need full log and I'll upload it somewhere).

Start up:

=~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2020.05.04 17:50:36 =~=~=~=~=~=~=~=~=~=~=~=
ь
__ __ _ _
| \/ | __ _ _ ____ _____| | |
| |\/| |/ _` | '__\ \ / / _ \ | |
| | | | (_| | | \ V / __/ | |
|_| |_|\__,_|_| \_/ \___|_|_|
_ _ ____ _
| | | | | __ ) ___ ___ | |_
| | | |___| _ \ / _ \ / _ \| __|
| |_| |___| |_) | (_) | (_) | |_
\___/ |____/ \___/ \___/ \__| ** LOADER **
** MARVELL BOARD: Synology Disk Station LE

U-Boot 1.1.4 (Jul 19 2011 - 11:22:59) Marvell version: 3.5.9

U-Boot code: 00600000 -> 0067FFF0 BSS: -> 0068B3D4

Soc: 88F6282 A0CPU running @ 1600Mhz L2 running @ 533Mhz
SysClock = 533Mhz , TClock = 200Mhz

DRAM (DDR3) CAS Latency = 7 tRP = 7 tRAS = 20 tRCD=7
DRAM CS[0] base 0x00000000 size 256MB
DRAM Total size 256MB 16bit width
Addresses 8M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (8M - 7M): Done
Using default environment

[[email protected]] Flash: 4 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: DS212
Fan Status: Not Good
Fan 1: Not Good

Net: egiga0 [PRIME], egiga1
Hit any key to stop autoboot: 3 2 1 0
## Booting image at f8080000 ...
Image Name: Linux-2.6.32.12
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 1552092 Bytes = 1.5 MB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
OK
## Loading Ramdisk Image at f8280000 ...
Image Name: synology_88f6282_212 24922
Image Type: ARM Linux RAMDisk Image (gzip compressed)
Data Size: 1040121 Bytes = 1015.7 kB
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 ([email protected]) (gcc version 4.6.4 (Marvell GCC release 20150204-c4af733b 64K MAXPAGESIZE ALIGN CVE-2015-0235) ) #24922 Tue Apr 23 17:32:06 CST 2019
[ 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: 65024
[ 0.000000] Kernel command line: console=ttyS0,115200 ip=off initrd=0x00800040,4M root=/dev/md0 rw syno_hw_version=DS212v10 ihd_num=2 netif_num=1
[ 0.000000] Synology Hardware Version: DS212v10-j
[ 0.000000] Internal HD num: 2
[ 0.000000] Internal netif num: 1
[ 0.000000] PID hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.000000] Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
[ 0.000000] Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
[ 0.000000] Memory: 256MB = 256MB total
[ 0.000000] Memory: 244992KB available (3652K 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... 1589.24 BogoMIPS (lpj=7946240)
[ 0.240000] Mount-cache hash table entries: 512
[ 0.240000] CPU: Testing write buffer coherency: ok
[ 0.240000] devtmpfs: initialized
[ 0.240000] xor: measuring software checksum speed
[ 0.290000] arm4regs : 1448.800 MB/sec
[ 0.340000] 8regs : 869.200 MB/sec
[ 0.390000] 32regs : 1122.000 MB/sec
[ 0.390000] xor: using function: arm4regs (1448.800 MB/sec)
[ 0.390000] NET: Registered protocol family 16
[ 0.390000] Feroceon L2: Enabling L2
[ 0.390000] Feroceon L2: Cache support initialised, in WT override mode.
:: Loading module synobios[ 48.250000] correction with 0x0f
[ 48.300000] 2020-5-4 8:5:58 UTC
[ 48.310000] synobios: load, major number 201
[ 48.310000] Brand: Synology
[ 48.320000] Model: DS-212
[ 48.320000] This is default settings: set group disks wakeup number to 1, spinup time deno 1
[ 48.330000] synobios cpu_arch proc entry initialized
[ 48.330000] synobios crypto_hw proc entry initialized
[ 48.340000] synobios syno_platform proc entry initialized
[ 48.340000] synobios open /dev/ttyS1 success
... [ OK ]
cat: can't open '/proc/sys/kernel/syno_skip_vender_mac_interfaces': No such file[ 48.560000] eth0: mac address changed
or directory

<a large chunk truncated here>

:: Starting syslogd ... [ OK ]
/etc/rc: line 273: /usr/syno/bin/syno_pstore_collect: not found >>> I think this is where the problem starts
:: Starting scemd
[ 55.180000] eth0: link up, full duplex, speed 1 Gbps
[ 57.990000] eth0: link down
[ 58.000000] eth0: link up, full duplex, speed 1 Gbps
:: Starting services in background
Starting findhostd in flash_rd...
Starting services in flash_rd...
Running /usr/syno/etc/rc.d/J30DisableNCQ.sh...
[ 58.190000] EXT4-fs (md0): barriers disabled
[ 58.200000] EXT4-fs (md0): mounted filesystem with ordered data mode
Running /usr/syno/etc/rc.d/J80ADTFanControl.sh...
:: Loading module usb-storage[ 58.620000] Initializing USB Mass Storage driver...
[ 58.630000] scsi2 : SCSI emulation for USB Mass Storage devices
[ 58.680000] usbcore: registered new interface driver usb-storage
[ 58.680000] USB Mass Storage support registered.
... [ OK ]
============ Date ============
Mon May 4 08:06:08 UTC 2020
================
Mon May 4 08:06:09 2020

Login:

DiskStation login: root
Password:

BusyBox v1.16.1 (2019-04-23 19:48:03 CST) built-in shell (ash)
Enter 'help' for a list of built-in commands.

DiskStation> dir
drwxr-xr-x 2 root root 1024 Apr 1 2019 .
drwxr-xr-x 14 root root 1024 May 4 08:06 ..
-rw-r--r-- 1 root root 1113 Apr 1 2019 .profile
DiskStation> cd ..
DiskStation> dir
drwxr-xr-x 14 root root 1024 May 4 08:06 .
drwxr-xr-x 14 root root 1024 May 4 08:06 ..
-rw-r--r-- 1 root root 0 May 4 08:05 .force_clean_all_disk
lrwxrwxrwx 1 root root 7 Jul 3 2019 bin -> usr/bin
drwxr-xr-x 6 root root 2980 May 4 08:06 dev
drwxr-xr-x 4 root root 1024 May 4 08:06 etc
lrwxrwxrwx 1 root root 3 Jul 3 2019 etc.defaults -> etc
lrwxrwxrwx 1 root root 11 Apr 24 2019 init -> bin/busybox
lrwxrwxrwx 1 root root 7 Jul 3 2019 lib -> usr/lib
lrwxrwxrwx 1 root root 11 Apr 24 2019 linuxrc -> bin/busybox
-rwxr-xr-x 1 root root 17894 Jul 3 2019 linuxrc.syno
drwx------ 2 root root 12288 Jul 3 2019 lost+found
drwxr-xr-x 2 root root 1024 Jul 3 2019 mnt
dr-xr-xr-x 52 root root 0 Jan 1 1970 proc
drwxr-xr-x 2 root root 1024 Apr 1 2019 root
drwxr-xr-x 3 root root 1024 May 4 08:06 run
lrwxrwxrwx 1 root root 8 Jul 3 2019 sbin -> usr/sbin
drwxr-xr-x 11 root root 0 Jan 1 1970 sys
drwxrwxrwt 2 root root 80 May 4 08:06 tmp
drwxr-xr-x 9 root root 1024 Jul 3 2019 usr
drwxr-xr-x 9 root root 1024 May 4 08:05 var
drwxrwxrwx 2 root root 1024 Jul 3 2019 volume1
DiskStation> exit
process '/sbin/getty 115200 con
Mon May 4 08:07:53 2020


I can get it to boot into DSM via tftp and bootm:

tftpboot 0x800000 zImage
bootm 0x800000

That gets me into the DSM and it's fully functional. However, if I restart it, it won't boot back up unless I do the bootm trick again.

I've tried doing a manual upgrade with the same .pat version here, thinking that would re-write the kernel, but that didn't work. It also won't let me downgrade to an earlier version.

So excuse my ignorance, I only have a very vague experience with Linux, but my guess is that the kernel code is corrupt and needs to be re-flashed. Am I correct and is there some easy way of doing that without resoldering the chip?
 

jeyare

Subscriber
1,609
543
here is an advanced help, when your kernel is successfully transferred to memory. Then flash is working.

when the flash needs to be replaced here is a list of similar threads:
link
link
try contact these members

good luck!
 
5
2
NAS
DS212
Operating system
  1. Windows
Thanks jeyare, been through those, so far the only possible reason for my problem that I see is a corrupt flash chip. Still hoping that's not the case as I won't be messing around with replacing it. I won't have any problem resoldering it, but compiling an image and programming the chip is not my forte. Still hoping someone will come up with a software fix, so will let it hang here. Cheers!
 
5
2
NAS
DS212
Operating system
  1. Windows
Does anyone know if the flash gets overwritten during a DSM upgrade? If so, I'm thinking I could boot it into DSM with the old chip on board, switch to a new chip using enggmaug's technique, then run the DSM upgrade to get the new chip written.
 

jeyare

Subscriber
1,609
543
there is another question:
If the cost of the possible success will cover 9-year old DS212 architecture operation to future?
... cost of SOIC clip with USB transceiver, ...
finally it's up to your decision
 

fredbert

Moderator
NAS Support
Subscriber
1,700
692
NAS
DS1520+, DS218+, DS215j
Router
  1. RT2600ac
  2. MR2200ac
Operating system
  1. macOS
Mobile operating system
  1. iOS
Call it another hobby project. I don't even need a NAS, just need to win!
That I recognise!

Entertaining myself t'other day moving an unused early 2000s Sony mini HiFi system into my small office. With a stack of minidisc I slotted in the first one only to get "TOC error" (table of contents read error) ... ok, it's broken and why do I need it, who uses minidisc now?

Shift to much later and jobs not done: it's working after exposing the mechanism and cleaning the laser etc.

But when am I ever going to use minidisc? All my music is on the NAS
 

jeyare

Subscriber
1,609
543
Call it another hobby project. I don't even need a NAS, just need to win!
this attitude is near my own, last week I spent 2 hours with replacement of broken micro switch (On/Off) in my vacuum cleaner. I spent 20 cents for the new switch, re-soldiering time about 2 minutes, but find a way how to disassembly the machine took 1.5 hours :). Finally I saved 250 Eur for the new vacuum cleaner. But the cleaner is just cleaner. New NAS from plus series is different story (docker support, BTRFS, AB4B, ...).

Btw: The NAS disassembly it's peanuts in comparison with the vacuum cleaner.
 
5
2
NAS
DS212
Operating system
  1. Windows
send here some photos pls. And I'll be glad to see new Resources, based on principle when people can help others
Thx
Will do if I get anywhere with it. I've ordered the new flash chip, which should be here early June.
 

Create an account or login to comment

You must be a member in order to leave a comment

Create account

Create an account on our community. It's easy!

Log in

Already have an account? Log in here.

Welcome to SynoForum.com!

SynoForum.com is an unofficial Synology forum for NAS owners and enthusiasts.

Registration is free, easy and fast!

Similar threads

Similar threads

Trending threads

Top