DSM-G600, DNS-3xx and NSA-220 Hack Forum

Unfortunately no one can be told what fun_plug is - you have to see it for yourself.

You are not logged in.

#1 2018-11-09 03:36:49

oliveirahalisson
Member
Registered: 2018-11-05
Posts: 5

DNS 323 blink blue - error U-Boot / Kernel TeraTerm

Hello friends, I searched a lot about this information and it was not a solution.
I'm from Brazil, I'm a DNS323, it always worked very well.
The power supplies from the OK source were running fine, until the moment I saw the blue front led flashing and were no search results by Easy Search - Dlink Utility.
I made the serial cable, but when doing the process http://dns323.kood.org/howto:reflash_from_windows I have a step of I have a DNS-323 that I can not update the firmware, I can upload the images via TerraTerm using kermit (according to the Wiki), however, once it is loaded, it immediately drops with the error message in the title repeated several times.
Is there any way to fix this DNS323?
What is a remote access feature to my equipment, donate some value through paypal so that I can help the subject resolver.
Thank you very much
Regards,
Halisson

Offline

 

#2 2018-11-10 12:09:27

Mijzelf
Member / Developer
Registered: 2008-07-05
Posts: 700

Re: DNS 323 blink blue - error U-Boot / Kernel TeraTerm

it immediately drops with the error message in the title repeated several times.

In the title I see 'DNS 323 blink blue - error U-Boot / Kernel TeraTerm'. What is the exact message you see. Can you post a log?

Offline

 

#3 2018-11-12 05:05:31

oliveirahalisson
Member
Registered: 2018-11-05
Posts: 5

Re: DNS 323 blink blue - error U-Boot / Kernel TeraTerm

Mijzelf, tks to reply.
I really appreciate you wanting to help me, thank you.



** LOADER **
** MARVELL BOARD: RD-88F5182-NAS-2 LE

U-Boot 1.1.1 (Feb 26 2009 - 11:33:03) Marvell version: 1.7.3.003

DRAM CS[0] base 0x00000000   size  64MB
DRAM Total size  64MB
Detect phy 1118
[8192kB@ff800000] Flash:  8 MB
Addresses 20M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (20M - 16M): Done
*** Warning - bad CRC, using default environment


Soc: MV88F5182 Rev 2
CPU: ARM926 (Rev 0) running @ 500Mhz
SysClock = 166Mhz , TClock = 166Mhz


USB 0: host mode
USB 1: host mode
PCI 0: PCI Express Root Complex Interface
PCI 1: Conventional PCI, speed = 33000000
Hit any key to stop autoboot:  0
Marvell>> loadb k
## Ready for binary (kermit) download to 0x00100000 at 115200 bps...
## Total Size      = 0x0016bd5c = 1490268 Bytes
## Start Addr      = 0x00100000
Un-Protect Flash Bank # 1
Erase Kernel from 0xff820000 to 0xff99ffff Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Kernel Size = 1490268
Copy to Flash... done
Protect Flash Bank # 1
Marvell>> loadb r
## Ready for binary (kermit) download to 0x00100000 at 115200 bps...
## Total Size      = 0x00540a6b = 5507691 Bytes
## Start Addr      = 0x00100000
Un-Protect Flash Bank # 1
Erase Ramdisk from 0xff9a0000 to 0xfff7ffff Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted
Erased 1 sectors
Ramdisk Size = 5507691
Copy to Flash... done
Protect Flash Bank # 1
Marvell>> <INTERRUPT>

Power OFF ->
____________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________

Power On


Marvell>>  ** LOADER **
** MARVELL BOARD: RD-88F5182-NAS-2 LE

U-Boot 1.1.1 (Feb 26 2009 - 11:33:03) Marvell version: 1.7.3.003

DRAM CS[0] base 0x00000000   size  64MB
DRAM Total size  64MB
Detect phy 1118
[8192kB@ff800000] Flash:  8 MB
Addresses 20M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (20M - 16M): Done
*** Warning - bad CRC, using default environment


Soc: MV88F5182 Rev 2
CPU: ARM926 (Rev 0) running @ 500Mhz
SysClock = 166Mhz , TClock = 166Mhz


USB 0: host mode
USB 1: host mode
PCI 0: PCI Express Root Complex Interface
PCI 1: Conventional PCI, speed = 33000000
Hit any key to stop autoboot:  0
## Booting image at ff820000 ...
   Image Name:   Linux-2.6.12.6-arm1
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1489368 Bytes =  1.4 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
OK
## Loading Ramdisk Image at ff9a0000 ...
   Image Name:   Ramdisk
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    6475114 Bytes =  6.2 MB
   Load Address: 00800000
   Entry Point:  00800000
   Verifying Checksum ... OK

Starting kernel ...

Uncompressing Linux................................................................................................... done, booting the kernel.
Linux version 2.6.12.6-arm1 (tim@SWTEST2) (gcc version 3.3.3) #32 Wed Jun 24 15:19:48 CST 2009
CPU: ARM926EJ-Sid(wb) [41069260] revision 0 (ARMv5TEJ)
CPU0: D VIVT write-back cache
CPU0: I cache: 32768 bytes, associativity 1, 32 byte lines, 1024 sets
CPU0: D cache: 32768 bytes, associativity 1, 32 byte lines, 1024 sets
Machine: MV-88fxx81
Using UBoot passing parameters structure
Sys Clk = 166000000, Tclk = 166000000
Memory policy: ECC disabled, Data cache writeback
Built 1 zonelists
Kernel command line: root=/dev/ram console=ttyS0,115200 :::DB88FXX81:egiga0:none
PID hash table entries: 512 (order: 9, 8192 bytes)
Console: colour dummy device 80x30
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Memory: 64MB 0MB 0MB 0MB = 64MB total
Memory: 55296KB available (2596K code, 463K data, 112K init)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
checking if image is initramfs...it isn't (no cpio magic); looks like an initrd
Freeing initrd memory: 6323K
NET: Registered protocol family 16

  Marvell Development Board (LSP Version 1.7.6_NAS)-- RD-88F5182-NAS-2

Detected Tclk 166000000 and SysClk 166000000
Marvell USB EHCI Host controller #0: c0e49a40
Marvell USB EHCI Host controller #1: c0e49bc0
pexBarOverlapDetect: winNum 2 overlap current 0
mvPexInit:Warning :Bar 2 size is illigal
it will be disabled
please check Pex and CPU windows configuration
PCI: bus0: Fast back to back transfers enabled
PCI: bus1: Fast back to back transfers enabled
SCSI subsystem initialized
usbcore: registered new driver usbfs
usbcore: registered new driver hub
cesadev_init(c0012498)
Fast Floating Point Emulator V0.9 (c) Peter Teichmann.
inotify device minor=63
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
squashfs: version 3.3 (2007/10/31) Phillip Lougher
Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
Initializing Cryptographic API
Serial: 8250/16550 driver $Revision: 1.1.1.1 $ 4 ports, IRQ sharing disabled
ttyS0 at MMIO 0x0 (irq = 3) is a 16550A
io scheduler noop registered
io scheduler deadline registered
RAMDISK driver initialized: 16 RAM disks of 10240K size 1024 blocksize
loop: loaded (max 8 devices)
Marvell Gigabit Ethernet Driver 'egiga':
  o Ethernet descriptors in DRAM
  o DRAM SW cache-coherency
  o Checksum offload enabled
  o Loading network interface 'egiga0'
Intergrated Sata device found
scsi0 : Marvell SCSI to SATA adapter
scsi1 : Marvell SCSI to SATA adapter
  Vendor: SAMSUNG   Model: HD154UI           Rev: 1AG0
  Type:   Direct-Access                      ANSI SCSI revision: 03
Attached scsi generic sg0 at scsi0, channel 0, id 0, lun 0,  type 0
physmap flash device: 800000 at ff800000
phys_mapped_flash: Found 1 x16 devices at 0x0 in 8-bit bank
Amd/Fujitsu Extended Query Table at 0x0040
number of CFI chips: 1
cfi_cmdset_0002: Disabling erase-suspend-program due to code brokenness.
cmdlinepart partition parsing not available
RedBoot partition parsing not available
Using physmap partition definition
Creating 5 MTD partitions on "phys_mapped_flash":
0x00000000-0x00010000 : "MTD1"
0x00010000-0x00020000 : "MTD2"
0x00020000-0x001a0000 : "Linux Kernel"
0x001a0000-0x007d0000 : "File System"
0x007d0000-0x00800000 : "u-boot"
ehci_platform ehci_platform.20865: EHCI Host Controller
ehci_platform ehci_platform.20865: new USB bus registered, assigned bus number 1
ehci_platform ehci_platform.20865: irq 17, io mem 0x00000000
ehci_platform ehci_platform.20865: park 0
ehci_platform ehci_platform.20865: USB 0.0 initialized, EHCI 1.00, driver 10 Dec 2004
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
ehci_platform ehci_platform.86401: EHCI Host Controller
ehci_platform ehci_platform.86401: new USB bus registered, assigned bus number 2
ehci_platform ehci_platform.86401: irq 12, io mem 0x00000000
ehci_platform ehci_platform.86401: park 0
ehci_platform ehci_platform.86401: USB 0.0 initialized, EHCI 1.00, driver 10 Dec 2004
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 1 port detected
mice: PS/2 mouse device common for all mice
md: linear personality registered as nr 1
md: raid0 personality registered as nr 2
md: raid1 personality registered as nr 3
md: md driver 0.90.1 MAX_MD_DEVS=256, MD_SB_DISKS=27
device-mapper: 4.4.0-ioctl (2005-01-12) initialised: dm-devel@redhat.com
NET: Registered protocol family 2
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP established hash table entries: 4096 (order: 3, 32768 bytes)
TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 4096 bind 4096)
NET: Registered protocol family 1
NET: Registered protocol family 17
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
RAMDISK: Compressed image found at block 0
EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended
VFS: Mounted root (ext2 filesystem).
Freeing init memory: 112K
init started:  BusyBox v1.00-pre1 (2009.05.07-06:36+0000) multi-call binary
init started:  BusyBox v1.00-pre1 (2009.05.07-06:36+0000) multi-call binary
Starting pid 219, console /dev/ttyS0: '/etc/rc.sh'
** Mounting /etc/fstab
umount: proc: not mounted
umount: proc: not mounted
umount: /image.cfs: not mounted
umount: /image.cfs: not mounted
Check MTD block device V2.05.12102008
        MTDC: Mount MTD1 done.
        MTDC: Mount MTD2 done.
        Error: mtd1 /sys/mtd1/smb.default size = 1128.
        Error: mtd2 /sys/mtd2/smb.default size = 0.
Bad inode number on dev mtdblock1: 65535 is out of range
rm: unable to stat `/sys/mtd2/': Input/output error
rm: unable to stat `/sys/mtd2/': Input/output error
rm: unable to stat `/sys/mtd2/': Input/output error
rm: unable to stat `/sys/mtd2/': Input/output error
rm: unable to stat `/sys/mtd2/': Input/output error
rm: unable to stat `/sys/mtd2/': Input/output error
rm: unable to stat `/sys/mtd2/': Input/output error
rm: unable to stat `/sys/mtd2/': Input/output error
rm: unable to stat `/sys/mtd2/': Input/output error
rm: unable to stat `/sys/mtd2/': Input/output error
rm: unable to stat `/sys/mtd2/': Input/output error
rm: unable to stat `/sys/mtd2/': Input/output error
rm: unable to stat `/sys/mtd2/': Input/output error
rm: unable to stat `/sys/mtd2/': Input/output error
        MTDC: Backup files from MTD1 to MTD2.
cp: Write Error: No space left on device
cp: Write Error: No space left on device
cp: Write Error: No space left on device
cp: Write Error: No space left on device
cp: Write Error: No space left on device
cp: Write Error: No space left on device
cp: Write Error: No space left on device
cp: Write Error: No space left on device
cp: Write Error: No space left on device
check file  =/mtd1/mdadm.conf error
mtd file error
cp: Write Error: No space left on device
cp: Write Error: No space left on device
cp: Write Error: No space left on device
cp: Write Error: No space left on device
cp: Write Error: No space left on device
cp: Write Error: No space left on device
cp: Write Error: No space left on device
cp: Write Error: No space left on device
cp: Write Error: No space left on device
** copy mtd1 files
cp: /sys/mtd1/firmwareupdate: No such file or directory
cp: /sys/mtd1/codepage: No such file or directory
cp: /sys/mtd1/upnp_serialnum.conf: No such file or directory
cp: /sys/mtd1/onedisk: No such file or directory
cp: /sys/mtd1/MountError: No such file or directory
cp: /sys/mtd1/web_NToR1: No such file or directory
cp: /sys/mtd1/dsk_mapping: No such file or directory
rm: cannot remove `/sys/mtd1/udhcpd.leases': No such file or directory
mv: /sys/mtd1/firmwareupdate: No such file or directory
mv: /sys/mtd1/restore: No such file or directory
mv: /sys/mtd1/format_ok: No such file or directory
mv: /sys/mtd1/pls_sync: No such file or directory
mv: /sys/mtd1/pls_chmod_a2: No such file or directory
mv: /sys/mtd1/pls_chmod_b2: No such file or directory
mv: /sys/mtd1/spare_dsk: No such file or directory
mv: /sys/mtd1/std_raid1: No such file or directory
mv: /sys/mtd1/old_prescan_version: No such file or directory
cp: /sys/mtd1/ez-ipupdate.cache: No such file or directory
cp: /sys/mtd1/ftpgroup: No such file or directory
** link lib **
** link web **
** link /usr/bin **
** link /usr/sbin **
SCSI device sda: 2930277168 512-byte hdwr sectors (1500302 MB)
SCSI device sda: drive cache: write back
SCSI device sda: 2930277168 512-byte hdwr sectors (1500302 MB)
SCSI device sda: drive cache: write back
sda: sda1 sda2 sda4
Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
usbcore: registered new driver usblp
drivers/usb/class/usblp.c: v0.13: USB Printer Device Class driver
** link /usr/local/LPRng **
cp: /sys/crfs/default/server-key-nopassword.pem: No such file or directory
    mode:         16384
-o  offset:       0
-f  frequency:    0
    maxerror:     16384000
    esterror:     16384000
    status:       64 ( UNSYNC )
-p  timeconstant: 2
    precision:    1
    tolerance:    33554432
-t  tick:         9960
    time.tv_sec:  1541980738
    time.tv_usec: 136849
    return value: 5 (clock not synchronized)
<rtc>: getRTC time= 18/11/11 23:58:58
<fan script start>
** set loopback interface
read mac from /dev/mtdblock4
Stop fan
MAC = 34:08:04:93:D6:65
egiga0: mac address changed
** Activate Gigabit Interface
Set fan to low speed
** execute rc.init.sh
SIOCDELRT: No such process
*****8192.168.0.32
info, udhcpc (v0.9.9-pre) started
[write_ssl start]
[ write_ssl ]now ip = 0.0.0.0,7
ip is different ,return
get IP = [NONE SET]
debug, Sending discover...
debug, Sending discover...
debug, Sending discover...
info, No lease, forking to background.
------------>ifconfig egiga0 192.168.0.32
[write_ssl start]
[ write_ssl ]now ip = 0.0.0.0,7
ip is different ,return
get IP = [NONE SET]
[write_ssl start]
[ write_ssl ]now ip = 192.168.0.32,12
Setting hostname .... DNS-323
*** Starting fdisk...
fdisk /dev/sda p 1

The number of cylinders for this disk is set to 182401.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
   (e.g., DOS FDISK, OS/2 FDISK)
partitions = 4, sys_ind = 0x82
exit status 0
success
Setting up swapspace version 1, size = 542830592 bytes
Adding 530104k swap on /dev/sda1.  Priority:-1 extents:1
copy default cacert
cp: /sys/crfs/default/server-key-nopassword.pem: No such file or directory
CP_SSL_MTD1
cp: unable to open `/mnt/HD_a2/.systemfile/.': No such file or directory
cp: unable to open `/mnt/HD_a2/.systemfile/.': No such file or directory
cp: unable to open `/mnt/HD_a2/.systemfile/.': No such file or directory
cp: unable to open `/mnt/HD_a2/.systemfile/.': No such file or directory
cp: /web/server-key-nopassword.pem: No such file or directory

Offline

 

#4 2018-11-13 13:06:36

Mijzelf
Member / Developer
Registered: 2008-07-05
Posts: 700

Re: DNS 323 blink blue - error U-Boot / Kernel TeraTerm

That doesn't look well. I think your flash somehow got damaged, and now it's in read-only mode, or something like that.

Code:

Erase Kernel from 0xff820000 to 0xff99ffff Can't erase unknown flash type - aborted
Erased 1 sectors
Can't erase unknown flash type - aborted

This kind of flash has to be erased before it can be written. Erasing failed, and so writing failed.

There are two small partition on flash which contain user settings, MTD1 and MTD2. In the bootlog you can see they are corrupted, and unwritable. This causes the boot to fail.

Code:

Check MTD block device V2.05.12102008
        MTDC: Mount MTD1 done.
        MTDC: Mount MTD2 done.
        Error: mtd1 /sys/mtd1/smb.default size = 1128.
        Error: mtd2 /sys/mtd2/smb.default size = 0.
Bad inode number on dev mtdblock1: 65535 is out of range
rm: unable to stat `/sys/mtd2/': Input/output error

Code:

      MTDC: Backup files from MTD1 to MTD2.
cp: Write Error: No space left on device

I'm sorry, I don't know how to revive your box.

Offline

 

#5 2019-04-16 00:03:31

oliveirahalisson
Member
Registered: 2018-11-05
Posts: 5

Re: DNS 323 blink blue - error U-Boot / Kernel TeraTerm

HI Mijzelf

Thank you for your help,
I have a friend who was able to evaluate a problem on another 320 DNS and believed to be the problem of my NAS. I made the purchase of IC En29lv640b (flash memory), however our device is DNS323 rev C (different from the other) and despite getting the new part, we do not have the file to write, when trying to back up the information, several pins presented errors and badblocks while reading.
I have the new part but I do not know the file to put in, do you have any tips?

Offline

 

#6 2019-04-19 23:14:17

Mijzelf
Member / Developer
Registered: 2008-07-05
Posts: 700

Re: DNS 323 blink blue - error U-Boot / Kernel TeraTerm

According to the bootlog you showed, u-boot on the original flash is still alive. So if you copy the flash to the first error, you should have a working bootloader. Then you can flash a firmware upgrade file: http://dns323.kood.org/howto:reflash_from_windows

Offline

 

#7 2019-04-22 03:14:57

oliveirahalisson
Member
Registered: 2018-11-05
Posts: 5

Re: DNS 323 blink blue - error U-Boot / Kernel TeraTerm

Hi Mijzelf ,

According to the bootlog you showed, the u-boot in the original flash is still active. So if you copy the flash to the first error, you should have a working bootloader. You can then update a firmware update file: http://dns323.kood.org/howto:reflash_from_windows


Thanks for your help one more time. I can not make eeprom copy, it presents me with lots of badblocks. When putting the new eeprom, I do not have any file including the bootloader. you would have these file (s)? I can make a donation via paypal for your help, because my box is dead.

Offline

 

#8 2019-04-23 12:34:06

Mijzelf
Member / Developer
Registered: 2008-07-05
Posts: 700

Re: DNS 323 blink blue - error U-Boot / Kernel TeraTerm

I'm sorry, I don't have any files. And I don't have a 323 either. And I saw I'm mistaken. The bootloader is not in the first part of the flash, but in the last 192KiB: http://dns323.kood.org/information:firm … ry_access. Does that help?

Offline

 

Board footer

Powered by PunBB
© Copyright 2002–2010 PunBB