Dzisiaj jest 7 lip 2020, 20:32

Strefa czasowa UTC+1godz. [letni]




Nowy temat Odpowiedz w temacie  [ Posty: 26 ]  Przejdź na stronę 1, 2  Następna
Autor Wiadomość
 Tytuł: Nsa310 - uszkodzony firmware / jak naprawić?
Post: 15 maja 2016, 12:56 
Offline
Użytkownik

Rejestracja: 6 cze 2012, 15:35
Posty: 46
Witam
Podczas aktualizacji firmware z 4.70 AKF2 do AKF3 brakło w bloku prądu. Obecnie mój NSA310 nie startuje, zasoby nie są widoczne w sieci i miga na zielono dioda SYS. Możecie coś pomóc w tym temacie?
dzieki


Na górę
 Wyświetl profil  
Odpowiedz z cytatem  
 Tytuł: Re: Nsa310 - uszkodzony firmware / jak naprawić?
Post: 15 maja 2016, 15:18 
Offline
Użytkownik

Rejestracja: 6 maja 2010, 21:55
Posty: 533
Pomożemy. Załatw kabelek serwisowy i daj znać.


Na górę
 Wyświetl profil  
Odpowiedz z cytatem  
 Tytuł: Re: Nsa310 - uszkodzony firmware / jak naprawić?
Post: 17 maja 2019, 00:58 
Offline
Użytkownik

Rejestracja: 29 sty 2018, 13:04
Posty: 5
Przepraszam że się podczepiam pod temat, ale czy jest gdzieś może na forum opisany pewny sposób powrotu do OFW? obecnie od biedy w moim NAS siedzi OpenWrt, ale wolałbym wrócić do OFW :), tylko że teraz już chyba przez moją niewiedzę może być marnie z partycjami mtd..


Na górę
 Wyświetl profil  
Odpowiedz z cytatem  
 Tytuł: Re: Nsa310 - uszkodzony firmware / jak naprawić?
Post: 17 maja 2019, 16:24 
Offline
Administrator
Awatar użytkownika

Rejestracja: 10 kwie 2010, 00:28
Posty: 13694
Lokalizacja: Warszawa
Sprawdzałem takie kombinacje: http://martin.topholm.eu/blog/2013/work ... el-nsa310/ ?

_________________
http://eko.one.pl - prawie wszystko o OpenWrt


Na górę
 Wyświetl profil  
Odpowiedz z cytatem  
 Tytuł: Re: Nsa310 - uszkodzony firmware / jak naprawić?
Post: 17 maja 2019, 16:38 
Offline
Administrator
Awatar użytkownika

Rejestracja: 10 kwie 2010, 00:28
Posty: 13694
Lokalizacja: Warszawa
Revocery usb jest na ftp ftp://ftp.zyxel.it/guide/nas/

_________________
http://eko.one.pl - prawie wszystko o OpenWrt


Na górę
 Wyświetl profil  
Odpowiedz z cytatem  
 Tytuł: Re: Nsa310 - uszkodzony firmware / jak naprawić?
Post: 17 maja 2019, 17:18 
Offline
Użytkownik

Rejestracja: 29 sty 2018, 13:04
Posty: 5
Dzięki Cezary :)
Jak tylko wyprowadzę UART na zewnątrz NAS-a będę testował dalej bo tak to próbowałem tej instrukcji
ftp://ftp.zyxel.it/guide/nas/nsa320_recovery_firmware.pdf (brak komunikacji PC-NAS) oraz próbowałem zapisać ponownie własne kopie partycji mtd. Na ten moment co bym nie robił kończyło się na..

Cytuj:
Uncompressing Linux............................ done, booting the kernel.


Ostatnio zmieniony 25 maja 2019, 16:49 przez IceG, łącznie zmieniany 2 razy

Na górę
 Wyświetl profil  
Odpowiedz z cytatem  
 Tytuł: Re: Nsa310 - uszkodzony firmware / jak naprawić?
Post: 17 maja 2019, 18:18 
Offline
Administrator
Awatar użytkownika

Rejestracja: 10 kwie 2010, 00:28
Posty: 13694
Lokalizacja: Warszawa
To też może świadczyć o braku odpowiednich zmiennych środowiskowych uboota.

_________________
http://eko.one.pl - prawie wszystko o OpenWrt


Na górę
 Wyświetl profil  
Odpowiedz z cytatem  
 Tytuł: Re: Nsa310 - uszkodzony firmware / jak naprawić?
Post: 25 maja 2019, 17:05 
Offline
Użytkownik

Rejestracja: 29 sty 2018, 13:04
Posty: 5
Rozumiem, że te operacje

Cytuj:
Flashing using Upgrade-Key

Prepare a FAT formatted USB key with force_flash.zip.

Add Zyxel firmware binary to the USB key - rename it to ras.bin.

Boot the device in TDC mode and log in with the recovered password.

Insert the USB key, determine the mount point, and add a symlink:

USB=`mount | sed -n '/e-data/{s/.*sdb1 on \([^ ]*\) .*/\1/;p;}'`
ln -s $USB /mnt/parnerkey

Execute the upgrade script:

cd /mnt/parnerkey
sh usb_key_func.sh.2



mam wykonać uruchamiając Debiana z pena?

Chyba nie uda mi się przywrócić OFW.. mam zrzuconą kopie wszystkich partycji.. zapisane ustawienia env.. a to dalej zawsze wisi na..

Uncompressing Linux............................ done, booting the kernel.


Znowu przy wgrywaniu za pomocą u-boota nie wiem jak uzyskać plik DATA_1004.yaffs2.

Patrząc po instrukcji nsa320-recovery-firmware samo wrzucenie DATA_1000 powinno się kończyć

Cytuj:
After bootup, Press “Enter” after you see this message “Please press Enter to
activate this console.”


a to dalej stoi na bootowaniu.. i nie ma mowy o komunikacie z wciśnięciem Enter.

Ktoś wie może co jest z tym nie tak..? może ja coś źle wrzucam.. ktoś może pamięta jak reanimował Swojego ZyXEL-a?


Na górę
 Wyświetl profil  
Odpowiedz z cytatem  
 Tytuł: Re: Nsa310 - uszkodzony firmware / jak naprawić?
Post: 26 gru 2019, 20:07 
Offline
Użytkownik

Rejestracja: 5 mar 2012, 10:41
Posty: 72
Witajcie.
Proszę Was o pomoc. Problem polega na tym, iż nie mogę się połączyć poprzez www z NSA 310. NAS Starter Utility go nie widzi. Adres IP po przeskanowaniu mam. Po włączeniu dysku mruga kontrolka SYS i świeci HDD po chwili zaczyna piszczeć co sekundę.
Chciałem przywrócić oprogramowanie ale nie do końca rozumiem instrukcję: ftp://ftp.zyxel.it/guide/nas/nsa320_rec ... rmware.pdf



Po połączeniu RS-232 pokazuje:


| \/ | __ _ _ ____ _____| | |
| |\/| |/ _` | '__\ \ / / _ \ | |
| | | | (_| | | \ V / __/ | |
|_| |_|\__,_|_| \_/ \___|_|_|
_ _ ____ _
| | | | | __ ) ___ ___ | |_
| | | |___| _ \ / _ \ / _ \| __|
| |_| |___| |_) | (_) | (_) | |_
\___/ |____/ \___/ \___/ \__|
** MARVELL BOARD: RD-88F6281A LE

U-Boot 1.1.4 (Feb 22 2011 - 10:31:35) Marvell version: 3.4.19

U-Boot code: 00600000 -> 0067FFF0 BSS: -> 006CFEE0

Soc: 88F6281 A1 (DDR2)
CPU running @ 1200Mhz L2 running @ 400Mhz
SysClock = 400Mhz , TClock = 200Mhz

DRAM CAS Latency = 5 tRP = 5 tRAS = 18 tRCD=6
DRAM CS[0] base 0x00000000 size 256MB
DRAM Total size 256MB 16bit width
Addresses 10M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (10M - 7M): Done
NAND:128 MB
Flash: 0 kB

CPU : Marvell Feroceon (Rev 1)
Kernel address is 0xc80000.

Streaming disabled
Write allocate disabled

Module 0 is RGMII
Module 1 is TDM

USB 0: host mode
PEX 0: PCI Express Root Complex Interface
PEX interface detected Link X1
Net: egiga0, egiga1 [PRIME]
Hit any key to stop autoboot: 0

NAND read: device 0 offset 0xc80000, size 0xa00000

Reading data from 0x167f800 -- 100% complete.
10485760 bytes read: OK
## Booting image at 02000000 ...
Image Name: Linux-2.6.31.8
Created: 2016-03-11 9:35:37 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 5696716 Bytes = 5.4 MB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
OK

Starting kernel ...

Uncompressing Linux............................................................................................................................................................................................................................................................................ done, booting the kernel.
Linux version 2.6.31.8 (root@BuildMachine) (gcc version 4.3.2 (sdk3.3-ct-ng-1.4.1) ) #2 Fri Mar 11 17:35:20 CST 2016
CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=00053977
CPU: VIVT data cache, VIVT instruction cache
Machine: Feroceon-KW
Using UBoot passing parameters structure
Memory policy: ECC disabled, Data cache writeback
Built 1 zonelists in Zone order, mobility grouping off. Total pages: 65024
Kernel command line: console=ttyS0,115200 mtdparts=nand_mtd:0x100000(uboot),0x80000(uboot_env),0x80000(key_store),0x80000(info),0xA00000(etc),0xA00000(kernel_1),0x2FC0000(rootfs1),0xA00000(kernel_2),0x2FC0000(rootfs2) root=/dev/nfs rw init=/init
PID hash table entries: 1024 (order: 10, 4096 bytes)
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Memory: 256MB = 256MB total
Memory: 244992KB available (5304K code, 300K data, 2804K init, 0K highmem)
Hierarchical RCU implementation.
NR_IRQS:128
Console: colour dummy device 80x30
Calibrating delay loop... 1199.30 BogoMIPS (lpj=5996544)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
NET: Registered protocol family 16
Feroceon L2: Enabling L2
Feroceon L2: Cache support initialised.

CPU Interface
-------------
SDRAM_CS0 ....base 00000000, size 256MB
SDRAM_CS1 ....disable
SDRAM_CS2 ....disable
SDRAM_CS3 ....disable
PEX0_MEM ....base e0000000, size 128MB
PEX0_IO ....base f2000000, size 1MB
PEX1_MEM ....no such
PEX1_IO ....no such
INTER_REGS ....base f1000000, size 1MB
NFLASH_CS ....base fa000000, size 2MB
SPI_CS ....base f4000000, size 16MB
BOOT_ROM_CS ....no such
DEV_BOOTCS ....no such
CRYPT_ENG ....base f0000000, size 2MB

Marvell Development Board (LSP Version KW_LSP_5.1.3_patch18)-- RD-88F6281A Soc: 88F6281 A1 LE

Detected Tclk 200000000 and SysClk 400000000
Marvell USB EHCI Host controller #0: c8040740
PEX0 interface detected Link X1
pci 0000:00:01.0: PME# supported from D0 D1 D2 D3hot D3cold
pci 0000:00:01.0: PME# disabled
PCI: bus0: Fast back to back transfers disabled
mvPexLocalBusNumSet: ERR. Invalid PEX interface 1
bio: create slab <bio-0> at 0
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
cfg80211: Calling CRDA to update world regulatory domain
NET: Registered protocol family 2
IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
TCP established hash table entries: 8192 (order: 4, 65536 bytes)
TCP bind hash table entries: 8192 (order: 3, 32768 bytes)
TCP: Hash tables configured (established 8192 bind 8192)
TCP reno registered
NET: Registered protocol family 1
RTC has been updated!!!
rtc mv_rtc: rtc core: registered kw-rtc as rtc0
RTC registered
cpufreq: Init kirkwood cpufreq driver
XOR registered 4 channels
XOR 2nd invalidate WA enabled
mvCesaInit: sessions=640, queue=64, pSram=f0000000
Warning: TS unit is powered off.
gpio_dev = fd00000
LED_SET_CTL_IOC_NUM= 6702
High gpio polarity = 50
High gpio polarity = 70
Enable Interrupt
mv88f6281_wdt: Watchdog Timer timeout = 8 sec.
mv88f6281_wdt: HW Watchdog timeout = 15 sec.
VFS: Disk quotas dquot_6.5.2
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
JFFS2 version 2.2. (NAND) &#169; 2001-2006 Red Hat, Inc.
fuse init (API version 7.12)
SGI XFS with security attributes, large block/inode numbers, no debug enabled
SGI XFS Quota Management subsystem
msgmni has been set to 478
alg: No test for cipher_null (cipher_null-generic)
alg: No test for ecb(cipher_null) (ecb-cipher_null)
alg: No test for digest_null (digest_null-generic)
alg: No test for compress_null (compress_null-generic)
alg: No test for stdrng (krng)
Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
io scheduler noop registered
io scheduler cfq registered (default)
Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 33) is a 16550A
console [ttyS0] enabled
brd: module loaded
loop: module loaded
Integrated Sata device found
IRQ 21/mvSata: IRQF_DISABLED is not guaranteed on shared IRQs
Wake up disk0......
Wake up disk1......
scsi0 : Marvell SCSI to SATA adapter
scsi1 : Marvell SCSI to SATA adapter
scsi 0:0:0:0: Direct-Access Seagate ST1000DM003-1SB1 CC41 PQ: 0 ANSI: 5
EnablePowerSaving
PowerSavingTime = 15
sd 0:0:0:0: [sda] Sector size 0 reported, assuming 512.
sd 0:0:0:0: [sda] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB)
sd 0:0:0:0: [sda] 0-byte physical blocks
sd 0:0:0:0: Attached scsi generic sg0 type 0
Loading Marvell Ethernet Driver:
o Cached descriptors in DRAM
o DRAM SW cache-coherency
o 0 Giga ports supported
o Single RX Queue support - ETH_DEF_RXQ=0
o Single TX Queue support - ETH_DEF_TXQ=0
o TCP segmentation offload (TSO) supported
o Large Receive offload (LRO) supported
o Receive checksum offload supported
o Transmit checksum offload supported
o Network Fast Processing (Routing) supported - (Disabled)
o Driver ERROR statistics enabled
o Proc tool API enabled
o SKB Reuse supported - (Disabled)
o SKB Recycle supported - (Disabled)
o Rx descripors: q0=128
o Tx descripors: q0=532
o Loading network interface(s):

mvFpRuleDb (c8d42000): 2048 entries, 8192 bytes
Counter=0, opIdx=6, overhead=16
Counter=1, opIdx=2, overhead=0
Counter=2, opIdx=1, overhead=18
Counter=3, opIdx=2, overhead=0
sd 0:0:0:0: [sda] Write Protect is off
NAND device: Manufacturer ID: 0xec, Chip ID: 0xf1 (Samsung NAND 128MiB 3,3V 8-bit)
Scanning device for bad blocks
Bad eraseblock 690 at 0x000005640000
9 cmdlinepart partitions found on MTD device nand_mtd
Using command line partition definition
Creating 9 MTD partitions on "nand_mtd":
0x000000000000-0x000000100000 : "uboot"
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, supports DPO and FUA
sd 0:0:0:0: [sda] Sector size 0 reported, assuming 512.
0x000000100000-0x000000180000 : "uboot_env"
0x000000180000-0x000000200000 : "key_store"
sda:
0x000000200000-0x000000280000 : "info"
0x000000280000-0x000000c80000 : "etc"
0x000000c80000-0x000001680000 : "kernel_1"
0x000001680000-0x000004640000 : "rootfs1"
0x000004640000-0x000005040000 : "kernel_2"
0x000005040000-0x000008000000 : "rootfs2"
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci_marvell ehci_marvell.70059: Marvell Orion EHCI
ehci_marvell ehci_marvell.70059: new USB bus registered, assigned bus number 1
sda1
sd 0:0:0:0: [sda] Sector size 0 reported, assuming 512.
sd 0:0:0:0: [sda] Attached SCSI disk
ehci_marvell ehci_marvell.70059: irq 19, io base 0xf1050100
ehci_marvell ehci_marvell.70059: USB 2.0 started, EHCI 1.00
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
uhci_hcd: USB Universal Host Controller Interface driver
usbcore: registered new interface driver usblp
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
usbcore: registered new interface driver ums-datafab
usbcore: registered new interface driver ums-freecom
usbcore: registered new interface driver ums-jumpshot
usbcore: registered new interface driver ums-sddr09
usbcore: registered new interface driver ums-sddr55
usbcore: registered new interface driver ums-usbat
mice: PS/2 mouse device common for all mice
i2c /dev entries driver
hwmon-vid: Unknown VRM version of your CPU
lm85 0-002e: Starting monitoring
md: linear personality registered for level -1
md: raid0 personality registered for level 0
md: raid1 personality registered for level 1
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
mmc0: mvsdio driver initialized, lacking card detect (fall back to polling)
usbcore: registered new interface driver hiddev
usbcore: registered new interface driver usbhid
usbhid: v2.6:USB HID core driver
TCP cubic registered
NET: Registered protocol family 10
lo: Disabled Privacy Extensions
Mobile IPv6
IPv6 over IPv4 tunneling driver
sit0: Disabled Privacy Extensions
ip6tnl0: Disabled Privacy Extensions
NET: Registered protocol family 17
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
rtc mv_rtc: setting system clock to 2000-01-01 01:25:59 UTC (946689959)
Freeing init memory: 2804K
*** Stage 1: Setup system and device drivers ***
usb 1-1: new high speed USB device using ehci_marvell and address 2
In hub_port_init, and number is 0, retry 0, port 1 .....
usb 1-1: configuration #1 chosen from 1 choice
hub 1-1:1.0: USB hub found
hub 1-1:1.0: 4 ports detected
r8168 Gigabit Ethernet driver 8.023.00-NAPI loaded
r8168 0000:00:01.0: no MSI. Back to INTx.
Set LED ...
eth%d: RTL8168B/8111B at 0xd0900000, 00:00:00:00:00:30, IRQ 9
r8168: This product is covered by one or more of the following patents: US5,307,459, US5,434,872, US5,732,094, US6,570,884, US6,115,776, and US6,327,625.
r8168 Copyright (C) 2011 Realtek NIC software team <nicfae@realtek.com>
This program comes with ABSOLUTELY NO WARRANTY; for details, please see <http://www.gnu.org/licenses/>.
This is free software, and you are welcome to redistribute it under certain conditions; see <http://www.gnu.org/licenses/>.
r8168: egiga0: link down
ADDRCONF(NETDEV_UP): egiga0: link is not ready
*** Stage 2: Prepare the root file system ***
Mount system partition...
yaffs: dev is 32505862 name is "mtdblock6" ro
yaffs: passed flags ""
lsFrownzyxel/mnt/nand/sysdisk.img.gz: No such file or directory
NAND Flash Corrupt...
Starting Pure-FTPd ...
/etc/init.d/rcS: line 212Frownbin/pure-ftpd.official: not found
1 second...
2 second...
r8168: egiga0: link up
ADDRCONF(NETDEV_CHANGE): egiga0: link becomes ready
r8168: egiga0: link up
3 second...
4 second...
5 second...
6 second...
7 second...
8 second...
9 second...
10 second...
sda
checking sda
Trying to mount /dev/sda1
mount: unknown filesystem type 'ntfs'
Fail to mount /dev/sda1
the sys-root image /dev/mtdblock6 is currupt !!
Dual images are currupt !!!
Starting Pure-FTPd ...
/etc/init.d/rcS: line 212Frownbin/pure-ftpd.official: not found
1 second...
2 second...
3 second...
4 second...
5 second...
6 second...
7 second...
8 second...
9 second...
10 second...
sda
checking sda
Trying to mount /dev/sda1
mount: unknown filesystem type 'ntfs'
Fail to mount /dev/sda1
bz time = 1f
bz status = 3
start buzzer

Please press Enter to activate this console.


BusyBox v1.17.2 (2016-03-11 17:11:16 CST) built-in shell (ash)
Enter 'help' for a list of built-in commands.


Na górę
 Wyświetl profil  
Odpowiedz z cytatem  
 Tytuł: Re: Nsa310 - uszkodzony firmware / jak naprawić?
Post: 26 gru 2019, 21:07 
Offline
Administrator
Awatar użytkownika

Rejestracja: 10 kwie 2010, 00:28
Posty: 13694
Lokalizacja: Warszawa
Masz jakiś ntfs na podłączonym dysku do zyxela. Zmień system plików na dysku.

_________________
http://eko.one.pl - prawie wszystko o OpenWrt


Na górę
 Wyświetl profil  
Odpowiedz z cytatem  
 Tytuł: Re: Nsa310 - uszkodzony firmware / jak naprawić?
Post: 1 mar 2020, 18:34 
Offline
Użytkownik

Rejestracja: 5 mar 2012, 10:41
Posty: 72
Zmieniłem na exFAT i nic.


Na górę
 Wyświetl profil  
Odpowiedz z cytatem  
 Tytuł: Re: Nsa310 - uszkodzony firmware / jak naprawić?
Post: 1 mar 2020, 18:36 
Offline
Administrator
Awatar użytkownika

Rejestracja: 10 kwie 2010, 00:28
Posty: 13694
Lokalizacja: Warszawa
Linux będzie raczej oczekiwał ext2/3/4 a nie exfat...

_________________
http://eko.one.pl - prawie wszystko o OpenWrt


Na górę
 Wyświetl profil  
Odpowiedz z cytatem  
 Tytuł: Re: Nsa310 - uszkodzony firmware / jak naprawić?
Post: 13 maja 2020, 11:49 
Offline
Użytkownik

Rejestracja: 17 lis 2011, 10:51
Posty: 323
Po wykonaniu poniższych niestety nie startuje, świecą wszystkie diody i nie zwraca nic w konsoli. Jestem coś w stanie zrobić?

Cytuj:
open: No such file or directory
open: No such file or directory


U-Boot 2018.03 (Jun 27 2018 - 06:41:13 +0000)
ZyXEL NSA310 1-Bay Power Media Server

SoC: Kirkwood 88F6281_A1
DRAM: 256 MiB
WARNING: Caches not enabled
NAND: 128 MiB
MMC:
Loading Environment from NAND... OK
In: serial
Out: serial
Err: serial
Net: egiga0
PHY reset timed out
MV88E1318 PHY initialized on egiga0
Hit any key to stop autoboot: 0
NSA310> usdb reset
Unknown command 'usdb' - try 'help'
NSA310> usb reset
resetting USB...
USB0: USB EHCI 1.00
scanning bus 0 for devices... 3 USB Device(s) found
scanning usb for storage devices... 1 Storage Device(s) found
NSA310> print ethaddr
ethaddr=50:67:F0:69:2A:CC
NSA310> fatload usb 0 0x2000000 nsa310.bin
14548992 bytes read in 1089 ms (12.7 MiB/s)
NSA310> nand erase.part ubi

NAND erase.part: device 0 offset 0x140000, size 0x7ec0000
Skipping bad block at 0x02860000
Erasing at 0x7fe0000 -- 100% complete.
OK
NSA310> nand write 0x2000000 ubi 0x600000

NAND write: device 0 offset 0x140000, size 0x600000
6291456 bytes written: OK
NSA310> nand scrub 0x0 0x80000

NAND scrub: device 0 offset 0x0, size 0x80000
Warning: scrub option will erase all factory set bad blocks!
There is no reliable way to recover them.
Use this command only for testing purposes if you
are sure of what you are doing!

Really scrub this NAND flash? <y/N>
y
Erasing at 0x60000 -- 100% complete.
OK
NSA310> reset
resetting ...



Na górę
 Wyświetl profil  
Odpowiedz z cytatem  
 Tytuł: Re: Nsa310 - uszkodzony firmware / jak naprawić?
Post: 13 maja 2020, 12:06 
Offline
Administrator
Awatar użytkownika

Rejestracja: 10 kwie 2010, 00:28
Posty: 13694
Lokalizacja: Warszawa
W jakim celu zrobiłeś nand scrub? Po co w ogóle?

Użyj kwboot, zobacz czy się uda wgrać nowy bootloader

_________________
http://eko.one.pl - prawie wszystko o OpenWrt


Na górę
 Wyświetl profil  
Odpowiedz z cytatem  
 Tytuł: Re: Nsa310 - uszkodzony firmware / jak naprawić?
Post: 13 maja 2020, 12:15 
Offline
Użytkownik

Rejestracja: 17 lis 2011, 10:51
Posty: 323
https://forum.doozan.com/read.php?3,7852 - według tej instrukcji korzystając z pliku http://downloads.openwrt.org/releases/1 ... u-boot.kwb ?


Na górę
 Wyświetl profil  
Odpowiedz z cytatem  
 Tytuł: Re: Nsa310 - uszkodzony firmware / jak naprawić?
Post: 13 maja 2020, 12:42 
Offline
Administrator
Awatar użytkownika

Rejestracja: 10 kwie 2010, 00:28
Posty: 13694
Lokalizacja: Warszawa
Instrukcja tak, ale wgraj ten plik: https://downloads.openwrt.org/snapshots ... u-boot.kwb

_________________
http://eko.one.pl - prawie wszystko o OpenWrt


Na górę
 Wyświetl profil  
Odpowiedz z cytatem  
 Tytuł: Re: Nsa310 - uszkodzony firmware / jak naprawić?
Post: 13 maja 2020, 15:22 
Offline
Użytkownik

Rejestracja: 17 lis 2011, 10:51
Posty: 323
@obsy dzięki. kwboot postawił go na nogi, ale po wykonaniu coś nie startuje:

Cytuj:
NSA310> usb reset
resetting USB...
USB0: USB EHCI 1.00
scanning bus 0 for devices... 3 USB Device(s) found
scanning usb for storage devices... 1 Storage Device(s) found
NSA310> fatload usb 0 0x2000000 nsa310.bin
14548992 bytes read in 1066 ms (13 MiB/s)
NSA310> nand erase.part ubi

NAND erase.part: device 0 offset 0x140000, size 0x7ec0000
Skipping bad block at 0x02860000
Erasing at 0x7fe0000 -- 100% complete.
OK
NSA310> nand write 0x2000000 ubi 0x600000

NAND write: device 0 offset 0x140000, size 0x600000
6291456 bytes written: OK
NSA310> reset
resetting ...


U-Boot 2020.04 (May 11 2020 - 14:49:04 +0000)
ZyXEL NSA310 1-Bay Power Media Server

SoC: Kirkwood 88F6281_A1
DRAM: 256 MiB
NAND: 128 MiB
MMC:
Loading Environment from NAND... OK
In: serial
Out: serial
Err: serial
Net: egiga0
PHY reset timed out
MV88E1318 PHY initialized on egiga0
Hit any key to stop autoboot: 0
ubi0: attaching mtd3
ubi0: scanning is finished
ubi0: volume 2 ("rootfs_data") re-sized from 9 to 881 LEBs
ubi0: attached mtd3 (name "ubi", size 126 MiB)
ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 129024 bytes
ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 512
ubi0: VID header offset: 512 (aligned 512), data offset: 2048
ubi0: good PEBs: 1013, bad PEBs: 1, corrupted PEBs: 0
ubi0: user volume: 3, internal volumes: 1, max. volumes count: 128
ubi0: max/mean erase counter: 1/0, WL threshold: 4096, image sequence number: 1922118826
ubi0: available PEBs: 0, total reserved PEBs: 1013, PEBs reserved for bad PEB handling: 19
No size specified -> Using max size (2193408)
Read 2193408 bytes from volume kernel to 00800000
## Booting kernel from Legacy Image at 00800000 ...
Image Name: ARM OpenWrt Linux-4.14.179
Created: 2020-05-08 18:35:50 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2081586 Bytes = 2 MiB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
Loading Kernel Image

Starting kernel ...

[ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] Linux version 4.14.179 (cezary@eko.one.pl) (gcc version 7.5.0 (OpenWrt GCC 7.5.0 r11006-3b6f079d8d)) #0 Fri May 8 18:35:50 2020
[ 0.000000] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=0005397f
[ 0.000000] CPU: VIVT data cache, VIVT instruction cache
[ 0.000000] OF: fdt: Machine model: ZyXEL NSA310b
[ 0.000000] Memory policy: Data cache writeback
[ 0.000000] random: get_random_bytes called from 0xc0700980 with crng_init=0
[ 0.000000] Built 1 zonelists, mobility grouping on. Total pages: 65024
[ 0.000000] Kernel command line: console=ttyS0,115200
[ 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: 252208K/262144K available (4807K kernel code, 163K rwdata, 728K rodata, 1024K init, 208K bss, 9936K reserved, 0K cma-reserved)
[ 0.000000] Virtual kernel memory layout:
[ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB)
[ 0.000000] fixmap : 0xffc00000 - 0xfff00000 (3072 kB)
[ 0.000000] vmalloc : 0xd0800000 - 0xff800000 ( 752 MB)
[ 0.000000] lowmem : 0xc0000000 - 0xd0000000 ( 256 MB)
[ 0.000000] modules : 0xbf000000 - 0xc0000000 ( 16 MB)
[ 0.000000] .text : 0xc0008000 - 0xc05b1cd0 (5800 kB)
[ 0.000000] .init : 0xc0700000 - 0xc0800000 (1024 kB)
[ 0.000000] .data : 0xc0800000 - 0xc0828c20 ( 164 kB)
[ 0.000000] .bss : 0xc0828c20 - 0xc085d004 ( 209 kB)
[ 0.000000] SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[ 0.000000] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16
[ 0.000000] clocksource: orion_clocksource: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 9556302233 ns
[ 0.000008] sched_clock: 32 bits at 200MHz, resolution 5ns, wraps every 10737418237ns
[ 0.000038] Switching to timer-based delay loop, resolution 5ns
[ 0.000119] Calibrating delay loop (skipped), value calculated using timer frequency.. 400.00 BogoMIPS (lpj=2000000)
[ 0.000142] pid_max: default: 32768 minimum: 301
[ 0.000273] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.000294] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.000826] CPU: Testing write buffer coherency: ok
[ 0.001576] Setting up static identity map for 0x100000 - 0x10003c
[ 0.001843] mvebu-soc-id: MVEBU SoC ID=0x6281, Rev=0x3
[ 0.005276] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[ 0.005302] futex hash table entries: 256 (order: -1, 3072 bytes)
[ 0.005386] pinctrl core: initialized pinctrl subsystem
[ 0.006412] NET: Registered protocol family 16
[ 0.006754] DMA: preallocated 256 KiB pool for atomic coherent allocations
[ 0.007670] cpuidle: using governor ladder
[ 0.008026] Feroceon L2: Enabling L2
[ 0.008070] Feroceon L2: Cache support initialised.
[ 0.011879] No ATAGs?
[ 0.027791] SCSI subsystem initialized
[ 0.028455] usbcore: registered new interface driver usbfs
[ 0.028511] usbcore: registered new interface driver hub
[ 0.028567] usbcore: registered new device driver usb
[ 0.030438] clocksource: Switched to clocksource orion_clocksource
[ 0.031215] NET: Registered protocol family 2
[ 0.031793] TCP established hash table entries: 2048 (order: 1, 8192 bytes)
[ 0.031827] TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
[ 0.031856] TCP: Hash tables configured (established 2048 bind 2048)
[ 0.031932] UDP hash table entries: 256 (order: 0, 4096 bytes)
[ 0.031954] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[ 0.032085] NET: Registered protocol family 1
[ 0.033178] Crashlog allocated RAM at address 0x3f00000
[ 0.034914] workingset: timestamp_bits=30 max_order=16 bucket_order=0
[ 0.039119] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[ 0.039133] jffs2: version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) (c) 2001-2006 Red Hat, Inc.
[ 0.046686] io scheduler noop registered
[ 0.046700] io scheduler deadline registered (default)
[ 0.047868] kirkwood-pinctrl f1010000.pin-controller: registered pinctrl driver
[ 0.049292] mvebu-pcie mbus@f1000000:pcie@82000000: PCI host bridge to bus 0000:00
[ 0.049312] pci_bus 0000:00: root bus resource [io 0x1000-0xfffff]
[ 0.049323] pci_bus 0000:00: root bus resource [mem 0xe0000000-0xefffffff]
[ 0.049334] pci_bus 0000:00: root bus resource [bus 00-ff]
[ 0.049562] PCI: bus0: Fast back to back transfers disabled
[ 0.049577] pci 0000:00:01.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[ 0.050000] PCI: bus1: Fast back to back transfers disabled
[ 0.050051] pci 0000:00:01.0: BAR 8: assigned [mem 0xe0000000-0xe00fffff]
[ 0.050065] pci 0000:00:01.0: BAR 7: assigned [io 0x10000-0x10fff]
[ 0.050082] pci 0000:01:00.0: BAR 6: assigned [mem 0xe0000000-0xe000ffff pref]
[ 0.050097] pci 0000:01:00.0: BAR 4: assigned [mem 0xe0010000-0xe0013fff 64bit pref]
[ 0.050118] pci 0000:01:00.0: BAR 2: assigned [mem 0xe0014000-0xe0014fff 64bit pref]
[ 0.050137] pci 0000:01:00.0: BAR 0: assigned [io 0x10000-0x100ff]
[ 0.050151] pci 0000:00:01.0: PCI bridge to [bus 01]
[ 0.050162] pci 0000:00:01.0: bridge window [io 0x10000-0x10fff]
[ 0.050175] pci 0000:00:01.0: bridge window [mem 0xe0000000-0xe00fffff]
[ 0.050656] Serial: 8250/16550 driver, 16 ports, IRQ sharing enabled
[ 0.052413] console [ttyS0] disabled
[ 0.052480] f1012000.serial: ttyS0 at MMIO 0xf1012000 (irq = 26, base_baud = 12500000) is a 16550A
[ 0.566624] console [ttyS0] enabled
[ 0.571170] sata_mv f1080000.sata: slots 32 ports 2
[ 0.579394] scsi host0: sata_mv
[ 0.583071] scsi host1: sata_mv
[ 0.586368] ata1: SATA max UDMA/133 irq 32
[ 0.590515] ata2: SATA max UDMA/133 irq 32
[ 0.595085] nand: device found, Manufacturer ID: 0xec, Chip ID: 0xf1
[ 0.601490] nand: Samsung NAND 128MiB 3,3V 8-bit
[ 0.606131] nand: 128 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
[ 0.613756] Scanning device for bad blocks
[ 0.648757] Bad eraseblock 323 at 0x000002860000
[ 0.720258] 3 fixed-partitions partitions found on MTD device orion_nand
[ 0.727003] Creating 3 MTD partitions on "orion_nand":
[ 0.732179] 0x000000000000-0x0000000c0000 : "uboot"
[ 0.737613] 0x0000000c0000-0x000000140000 : "uboot_env"
[ 0.743360] 0x000000140000-0x000008000000 : "ubi"
[ 0.749469] libphy: Fixed MDIO Bus: probed
[ 0.753825] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 0.760377] ehci-pci: EHCI PCI platform driver
[ 0.764899] ehci-orion: EHCI orion driver
[ 0.769081] orion-ehci f1050000.ehci: EHCI Host Controller
[ 0.774636] orion-ehci f1050000.ehci: new USB bus registered, assigned bus number 1
[ 0.782469] orion-ehci f1050000.ehci: irq 30, io mem 0xf1050000
[ 0.810459] orion-ehci f1050000.ehci: USB 2.0 started, EHCI 1.00
[ 0.817048] hub 1-0:1.0: USB hub found
[ 0.821040] hub 1-0:1.0: 1 port detected
[ 0.825406] usbcore: registered new interface driver usb-storage
[ 0.831819] rtc-mv f1010300.rtc: rtc core: registered f1010300.rtc as rtc0
[ 0.838794] i2c /dev entries driver
[ 0.843403] orion_wdt: Initial timeout 21 sec
[ 0.854136] marvell-cesa f1030000.crypto: CESA device successfully registered
[ 0.862170] NET: Registered protocol family 10
[ 0.868193] Segment Routing with IPv6
[ 0.871969] NET: Registered protocol family 17
[ 0.876463] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this.
[ 0.889496] 8021q: 802.1Q VLAN Support v1.8
[ 0.896479] UBI: auto-attach mtd2
[ 0.899817] ubi0: attaching mtd2
[ 1.077142] ubi0: scanning is finished
[ 1.092526] ubi0: attached mtd2 (name "ubi", size 126 MiB)
[ 1.098090] ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 129024 bytes
[ 1.105016] ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 512
[ 1.111756] ubi0: VID header offset: 512 (aligned 512), data offset: 2048
[ 1.118570] ubi0: good PEBs: 1013, bad PEBs: 1, corrupted PEBs: 0
[ 1.124710] ubi0: user volume: 3, internal volumes: 1, max. volumes count: 128
[ 1.131980] ubi0: max/mean erase counter: 1/0, WL threshold: 4096, image sequence number: 1922118826
[ 1.141169] ubi0: available PEBs: 0, total reserved PEBs: 1013, PEBs reserved for bad PEB handling: 19
[ 1.151154] block ubiblock0_1: created from ubi0:1(rootfs)
[ 1.156668] ubiblock: device ubiblock0_1 (rootfs) set to be root filesystem
[ 1.163871] rtc-mv f1010300.rtc: setting system clock to 2020-05-13 13:19:51 UTC (1589375991)
[ 1.172864] ata1: SATA link down (SStatus 0 SControl F300)
[ 1.178567] ubi0: background thread "ubi_bgt0d" started, PID 451
[ 1.240456] usb 1-1: new high-speed USB device number 2 using orion-ehci
[ 1.442595] hub 1-1:1.0: USB hub found
[ 1.446732] hub 1-1:1.0: 4 ports detected
[ 1.512189] ata2: SATA link down (SStatus 0 SControl F300)
[ 1.521163] squashfs: SQUASHFS error: unable to read id index table
[ 1.527566] List of all partitions:
[ 1.531101] 1f00 768 mtdblock0
[ 1.531106] (driver?)
[ 1.537672] 1f01 512 mtdblock1
[ 1.537675] (driver?)
[ 1.544257] 1f02 129792 mtdblock2
[ 1.544260] (driver?)
[ 1.550836] fe00 11592 ubiblock0_1
[ 1.550839] (driver?)
[ 1.557576] No filesystem could mount root, tried:
[ 1.557579] ext3
[ 1.562495] ext2
[ 1.564430] ext4
[ 1.566357] squashfs
[ 1.568284]
[ 1.572073] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(254,0)
[ 1.581338] Rebooting in 1 seconds..


NSA310> printenv
baudrate=115200
bootcmd=run setenv bootargs; ubi part ubi; ubi read 0x800000 kernel; bootm 0x800000
bootdelay=3
console=console=ttyS0,115200
ethact=egiga0
ethaddr=50:67:F0:69:2A:CC
ipaddr=192.168.1.1
mtdids=nand0=orion_nand
mtdparts=mtdparts=orion_nand:0x00c0000(uboot),0x80000(uboot_env),0x7ec0000(ubi)
serverip=192.168.1.2
stderr=serial
stdin=serial
stdout=serial

Environment size: 367/131068 bytes


Na górę
 Wyświetl profil  
Odpowiedz z cytatem  
 Tytuł: Re: Nsa310 - uszkodzony firmware / jak naprawić?
Post: 13 maja 2020, 15:37 
Offline
Administrator
Awatar użytkownika

Rejestracja: 10 kwie 2010, 00:28
Posty: 13694
Lokalizacja: Warszawa
Nie wgrał ci sie obraz do końca. Możliwe że to przez ten scrub, bo pozbyłeś się w ten sposób oznaczenia błędnych sektorów (jeszcze raz: po co to zrobiłeś w ogóle?).
Spróbuj jeszcze raz wgrać, nie zapomnij o nand erase partycji ubi.

_________________
http://eko.one.pl - prawie wszystko o OpenWrt


Na górę
 Wyświetl profil  
Odpowiedz z cytatem  
 Tytuł: Re: Nsa310 - uszkodzony firmware / jak naprawić?
Post: 13 maja 2020, 16:02 
Offline
Użytkownik

Rejestracja: 17 lis 2011, 10:51
Posty: 323
Zrobiłem to z automatu, bo pamiętam miałem jakiś problem ostatnim razem z wgraniem i wystartowaniem openwrt.. https://openrouter.info/forum/viewtopic ... 414#p46414

Wgrałem factory ze strony głównej, które jest mniejsze (~4MB vs ~14MB) i zdaje się poszło:

Cytuj:
U-Boot 2020.04 (May 11 2020 - 14:49:04 +0000)
ZyXEL NSA310 1-Bay Power Media Server

SoC: Kirkwood 88F6281_A1
DRAM: 256 MiB
NAND: 128 MiB
MMC:
Loading Environment from NAND... OK
In: serial
Out: serial
Err: serial
Net: egiga0
PHY reset timed out
MV88E1318 PHY initialized on egiga0
Hit any key to stop autoboot: 0
## Error: "setenv" not defined
ubi0: attaching mtd3
ubi0: scanning is finished
ubi0: volume 2 ("rootfs_data") re-sized from 9 to 959 LEBs
ubi0: attached mtd3 (name "ubi", size 126 MiB)
ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 129024 bytes
ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 512
ubi0: VID header offset: 512 (aligned 512), data offset: 2048
ubi0: good PEBs: 1013, bad PEBs: 1, corrupted PEBs: 0
ubi0: user volume: 3, internal volumes: 1, max. volumes count: 128
ubi0: max/mean erase counter: 1/0, WL threshold: 4096, image sequence number: 522944975
ubi0: available PEBs: 0, total reserved PEBs: 1013, PEBs reserved for bad PEB handling: 19
No size specified -> Using max size (2193408)
Read 2193408 bytes from volume kernel to 00800000
## Booting kernel from Legacy Image at 00800000 ...
Image Name: ARM OpenWrt Linux-4.14.171
Created: 2020-02-27 21:05:12 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2080770 Bytes = 2 MiB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
Loading Kernel Image

Starting kernel ...

[ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] Linux version 4.14.171 (builder@buildhost) (gcc version 7.5.0 (OpenWrt GCC 7.5.0 r10947-65030d81f3)) #0 Thu Feb 27 21:05:12 2020
[ 0.000000] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=0005397f
[ 0.000000] CPU: VIVT data cache, VIVT instruction cache
[ 0.000000] OF: fdt: Machine model: ZyXEL NSA310b
[ 0.000000] Memory policy: Data cache writeback
[ 0.000000] random: get_random_bytes called from 0xc0700980 with crng_init=0
[ 0.000000] Built 1 zonelists, mobility grouping on. Total pages: 65024
[ 0.000000] Kernel command line: console=ttyS0,115200
[ 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: 252212K/262144K available (4804K kernel code, 162K rwdata, 728K rodata, 1024K init, 208K bss, 9932K reserved, 0K cma-reserved)
[ 0.000000] Virtual kernel memory layout:
[ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB)
[ 0.000000] fixmap : 0xffc00000 - 0xfff00000 (3072 kB)
[ 0.000000] vmalloc : 0xd0800000 - 0xff800000 ( 752 MB)
[ 0.000000] lowmem : 0xc0000000 - 0xd0000000 ( 256 MB)
[ 0.000000] modules : 0xbf000000 - 0xc0000000 ( 16 MB)
[ 0.000000] .text : 0xc0008000 - 0xc05b1250 (5797 kB)
[ 0.000000] .init : 0xc0700000 - 0xc0800000 (1024 kB)
[ 0.000000] .data : 0xc0800000 - 0xc0828ba0 ( 163 kB)
[ 0.000000] .bss : 0xc0828ba0 - 0xc085cf84 ( 209 kB)
[ 0.000000] SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[ 0.000000] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16
[ 0.000000] clocksource: orion_clocksource: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 9556302233 ns
[ 0.000009] sched_clock: 32 bits at 200MHz, resolution 5ns, wraps every 10737418237ns
[ 0.000040] Switching to timer-based delay loop, resolution 5ns
[ 0.000123] Calibrating delay loop (skipped), value calculated using timer frequency.. 400.00 BogoMIPS (lpj=2000000)
[ 0.000148] pid_max: default: 32768 minimum: 301
[ 0.000286] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.000307] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.000846] CPU: Testing write buffer coherency: ok
[ 0.001590] Setting up static identity map for 0x100000 - 0x10003c
[ 0.001857] mvebu-soc-id: MVEBU SoC ID=0x6281, Rev=0x3
[ 0.005542] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[ 0.005568] futex hash table entries: 256 (order: -1, 3072 bytes)
[ 0.005654] pinctrl core: initialized pinctrl subsystem
[ 0.006686] NET: Registered protocol family 16
[ 0.007027] DMA: preallocated 256 KiB pool for atomic coherent allocations
[ 0.007977] cpuidle: using governor ladder
[ 0.008331] Feroceon L2: Enabling L2
[ 0.008374] Feroceon L2: Cache support initialised.
[ 0.012208] No ATAGs?
[ 0.028124] SCSI subsystem initialized
[ 0.028789] usbcore: registered new interface driver usbfs
[ 0.028846] usbcore: registered new interface driver hub
[ 0.028901] usbcore: registered new device driver usb
[ 0.030760] clocksource: Switched to clocksource orion_clocksource
[ 0.031543] NET: Registered protocol family 2
[ 0.032120] TCP established hash table entries: 2048 (order: 1, 8192 bytes)
[ 0.032154] TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
[ 0.032183] TCP: Hash tables configured (established 2048 bind 2048)
[ 0.032259] UDP hash table entries: 256 (order: 0, 4096 bytes)
[ 0.032281] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[ 0.032412] NET: Registered protocol family 1
[ 0.033517] Crashlog allocated RAM at address 0x3f00000
[ 0.035257] workingset: timestamp_bits=30 max_order=16 bucket_order=0
[ 0.039486] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[ 0.039499] jffs2: version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) (c) 2001-2006 Red Hat, Inc.
[ 0.047048] io scheduler noop registered
[ 0.047062] io scheduler deadline registered (default)
[ 0.048237] kirkwood-pinctrl f1010000.pin-controller: registered pinctrl driver
[ 0.049669] mvebu-pcie mbus@f1000000:pcie@82000000: PCI host bridge to bus 0000:00
[ 0.049689] pci_bus 0000:00: root bus resource [io 0x1000-0xfffff]
[ 0.049700] pci_bus 0000:00: root bus resource [mem 0xe0000000-0xefffffff]
[ 0.049711] pci_bus 0000:00: root bus resource [bus 00-ff]
[ 0.049941] PCI: bus0: Fast back to back transfers disabled
[ 0.049956] pci 0000:00:01.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[ 0.050380] PCI: bus1: Fast back to back transfers disabled
[ 0.050431] pci 0000:00:01.0: BAR 8: assigned [mem 0xe0000000-0xe00fffff]
[ 0.050445] pci 0000:00:01.0: BAR 7: assigned [io 0x10000-0x10fff]
[ 0.050462] pci 0000:01:00.0: BAR 6: assigned [mem 0xe0000000-0xe000ffff pref]
[ 0.050476] pci 0000:01:00.0: BAR 4: assigned [mem 0xe0010000-0xe0013fff 64bit pref]
[ 0.050497] pci 0000:01:00.0: BAR 2: assigned [mem 0xe0014000-0xe0014fff 64bit pref]
[ 0.050516] pci 0000:01:00.0: BAR 0: assigned [io 0x10000-0x100ff]
[ 0.050530] pci 0000:00:01.0: PCI bridge to [bus 01]
[ 0.050541] pci 0000:00:01.0: bridge window [io 0x10000-0x10fff]
[ 0.050555] pci 0000:00:01.0: bridge window [mem 0xe0000000-0xe00fffff]
[ 0.051040] Serial: 8250/16550 driver, 16 ports, IRQ sharing enabled
[ 0.052813] console [ttyS0] disabled
[ 0.052881] f1012000.serial: ttyS0 at MMIO 0xf1012000 (irq = 26, base_baud = 12500000) is a 16550A
[ 0.567103] console [ttyS0] enabled
[ 0.571652] sata_mv f1080000.sata: slots 32 ports 2
[ 0.579867] scsi host0: sata_mv
[ 0.583536] scsi host1: sata_mv
[ 0.586831] ata1: SATA max UDMA/133 irq 32
[ 0.590974] ata2: SATA max UDMA/133 irq 32
[ 0.595550] nand: device found, Manufacturer ID: 0xec, Chip ID: 0xf1
[ 0.601960] nand: Samsung NAND 128MiB 3,3V 8-bit
[ 0.606601] nand: 128 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
[ 0.614226] Scanning device for bad blocks
[ 0.649232] Bad eraseblock 323 at 0x000002860000
[ 0.720744] 3 fixed-partitions partitions found on MTD device orion_nand
[ 0.727491] Creating 3 MTD partitions on "orion_nand":
[ 0.732666] 0x000000000000-0x0000000c0000 : "uboot"
[ 0.738100] 0x0000000c0000-0x000000140000 : "uboot_env"
[ 0.743845] 0x000000140000-0x000008000000 : "ubi"
[ 0.749959] libphy: Fixed MDIO Bus: probed
[ 0.754313] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 0.760892] ehci-pci: EHCI PCI platform driver
[ 0.765403] ehci-orion: EHCI orion driver
[ 0.769587] orion-ehci f1050000.ehci: EHCI Host Controller
[ 0.775141] orion-ehci f1050000.ehci: new USB bus registered, assigned bus number 1
[ 0.782974] orion-ehci f1050000.ehci: irq 30, io mem 0xf1050000
[ 0.810780] orion-ehci f1050000.ehci: USB 2.0 started, EHCI 1.00
[ 0.817367] hub 1-0:1.0: USB hub found
[ 0.821362] hub 1-0:1.0: 1 port detected
[ 0.825739] usbcore: registered new interface driver usb-storage
[ 0.832161] rtc-mv f1010300.rtc: rtc core: registered f1010300.rtc as rtc0
[ 0.839135] i2c /dev entries driver
[ 0.843752] orion_wdt: Initial timeout 21 sec
[ 0.854505] marvell-cesa f1030000.crypto: CESA device successfully registered
[ 0.862549] NET: Registered protocol family 10
[ 0.868576] Segment Routing with IPv6
[ 0.872349] NET: Registered protocol family 17
[ 0.876846] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this.
[ 0.889870] 8021q: 802.1Q VLAN Support v1.8
[ 0.896836] UBI: auto-attach mtd2
[ 0.900175] ubi0: attaching mtd2
[ 1.077631] ubi0: scanning is finished
[ 1.093036] ubi0: attached mtd2 (name "ubi", size 126 MiB)
[ 1.098595] ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 129024 bytes
[ 1.105520] ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 512
[ 1.112260] ubi0: VID header offset: 512 (aligned 512), data offset: 2048
[ 1.119074] ubi0: good PEBs: 1013, bad PEBs: 1, corrupted PEBs: 0
[ 1.125215] ubi0: user volume: 3, internal volumes: 1, max. volumes count: 128
[ 1.132484] ubi0: max/mean erase counter: 1/0, WL threshold: 4096, image sequence number: 522944975
[ 1.141586] ubi0: available PEBs: 0, total reserved PEBs: 1013, PEBs reserved for bad PEB handling: 19
[ 1.151579] block ubiblock0_1: created from ubi0:1(rootfs)
[ 1.157094] ubiblock: device ubiblock0_1 (rootfs) set to be root filesystem
[ 1.164299] rtc-mv f1010300.rtc: setting system clock to 2020-05-13 14:01:24 UTC (1589378484)
[ 1.173385] ubi0: background thread "ubi_bgt0d" started, PID 451
[ 1.240777] usb 1-1: new high-speed USB device number 2 using orion-ehci
[ 1.340787] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl F300)
[ 1.349512] ata1.00: ATA-9: WDC WD20EFRX-68EUZN0, 82.00A82, max UDMA/133
[ 1.356266] ata1.00: 3907029168 sectors, multi 0: LBA48 NCQ (depth 31/32)
[ 1.365620] ata1.00: configured for UDMA/133
[ 1.370222] scsi 0:0:0:0: Direct-Access ATA WDC WD20EFRX-68E 0A82 PQ: 0 ANSI: 5
[ 1.379470] sd 0:0:0:0: [sda] 3907029168 512-byte logical blocks: (2.00 TB/1.82 TiB)
[ 1.387285] sd 0:0:0:0: [sda] 4096-byte physical blocks
[ 1.392989] sd 0:0:0:0: [sda] Write Protect is off
[ 1.397941] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 1.442842] hub 1-1:1.0: USB hub found
[ 1.446984] hub 1-1:1.0: 4 ports detected
[ 1.701829] random: fast init done
[ 1.725503] ata2: SATA link down (SStatus 0 SControl F300)
[ 1.770773] usb 1-1.3: new high-speed USB device number 3 using orion-ehci
[ 1.922203] sda: sda1 sda2 sda3
[ 1.926811] sd 0:0:0:0: [sda] Attached SCSI disk
[ 1.933050] usb-storage 1-1.3:1.0: USB Mass Storage device detected
[ 1.943332] VFS: Mounted root (squashfs filesystem) readonly on device 254:0.
[ 1.953443] Freeing unused kernel memory: 1024K
[ 1.958432] scsi host2: usb-storage 1-1.3:1.0
[ 2.266956] init: Console is alive
[ 2.270524] init: - watchdog -
[ 2.406662] kmodloader: loading kernel modules from /etc/modules-boot.d/*
[ 2.473343] kmodloader: done loading kernel modules from /etc/modules-boot.d/*
[ 2.490956] init: - preinit -
[ 2.993512] random: jshn: uninitialized urandom read (4 bytes read)
[ 3.028631] random: jshn: uninitialized urandom read (4 bytes read)
[ 3.042456] scsi 2:0:0:0: Direct-Access Ut163 USB2FlashStorage 0.00 PQ: 0 ANSI: 2
[ 3.051555] random: procd: uninitialized urandom read (4 bytes read)
[ 3.059655] sd 2:0:0:0: [sdb] 1007616 512-byte logical blocks: (516 MB/492 MiB)
[ 3.076005] sd 2:0:0:0: [sdb] Write Protect is off
[ 3.082305] sd 2:0:0:0: [sdb] Asking for cache data failed
[ 3.087828] sd 2:0:0:0: [sdb] Assuming drive cache: write through
[ 3.230960] sdb: sdb1
[ 3.237018] sd 2:0:0:0: [sdb] Attached SCSI removable disk
Press the [f] key and hit [enter] to enter failsafe mode
Press the [1], [2], [3] or [4] key and hit [enter] to select the debug level
[ 6.571636] UBIFS (ubi0:2): default file-system created
[ 6.603537] UBIFS (ubi0:2): background thread "ubifs_bgt0_2" started, PID 570
[ 6.665515] UBIFS (ubi0:2): UBIFS: mounted UBI device 0, volume 2, name "rootfs_data"
[ 6.673416] UBIFS (ubi0:2): LEB size: 129024 bytes (126 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
[ 6.683395] UBIFS (ubi0:2): FS size: 122314752 bytes (116 MiB, 948 LEBs), journal size 6064128 bytes (5 MiB, 47 LEBs)
[ 6.694064] UBIFS (ubi0:2): reserved for root: 4952683 bytes (4836 KiB)
[ 6.700708] UBIFS (ubi0:2): media format: w4/r0 (latest is w5/r0), UUID B518BC5D-2F15-4701-B37C-8F535DACA1A6, small LPT model
[ 6.713614] mount_root: overlay filesystem has not been fully initialized yet
[ 6.721113] mount_root: switching to ubifs overlay
[ 6.737036] urandom-seed: Seed file not found (/etc/urandom.seed)
[ 6.781290] procd: - early -
[ 6.784251] procd: - watchdog -
[ 7.405015] procd: - watchdog -
[ 7.408382] procd: - ubus -
[ 7.490344] urandom_read: 3 callbacks suppressed
[ 7.490351] random: ubusd: uninitialized urandom read (4 bytes read)
[ 7.503178] random: ubusd: uninitialized urandom read (4 bytes read)
[ 7.509874] random: ubusd: uninitialized urandom read (4 bytes read)
[ 7.517235] procd: - init -
Please press Enter to activate this console.
[ 7.881312] kmodloader: loading kernel modules from /etc/modules.d/*
[ 7.904428] ip6_tables: (C) 2000-2006 Netfilter Core Team
[ 7.922775] ip_tables: (C) 2000-2006 Netfilter Core Team
[ 7.943093] hwmon_vid: Unknown VRM version of your CPU
[ 7.948731] lm85 0-002e: Starting monitoring
[ 7.965038] nf_conntrack version 0.5.0 (4096 buckets, 16384 max)
[ 8.014523] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
[ 8.020156] pci 0000:00:01.0: enabling device (0140 -> 0143)
[ 8.025902] r8169 0000:01:00.0: enabling device (0140 -> 0143)
[ 8.032590] r8169 0000:01:00.0 eth0: RTL8168d/8111d at 0xd0b83000, 00:00:00:00:00:30, XID 083000c0 IRQ 36
[ 8.042245] r8169 0000:01:00.0 eth0: jumbo features [frames: 9200 bytes, tx checksumming: ko]
[ 8.101443] urngd: v1.0.2 started.
[ 8.186766] xt_time: kernel timezone is -0000
[ 8.206547] PPP generic driver version 2.4.2
[ 8.221453] NET: Registered protocol family 24
[ 8.231916] kmodloader: done loading kernel modules from /etc/modules.d/*
[ 8.313725] random: crng init done
[ 8.317148] random: 1 urandom warning(s) missed due to ratelimiting
[ 15.530890] r8169 0000:01:00.0 eth0: link down
[ 15.541228] br-lan: port 1(eth0) entered blocking state
[ 15.546482] br-lan: port 1(eth0) entered disabled state
[ 15.551996] device eth0 entered promiscuous mode
[ 15.579337] IPv6: ADDRCONF(NETDEV_UP): br-lan: link is not ready


Na górę
 Wyświetl profil  
Odpowiedz z cytatem  
 Tytuł: Re: Nsa310 - uszkodzony firmware / jak naprawić?
Post: 13 maja 2020, 16:04 
Offline
Administrator
Awatar użytkownika

Rejestracja: 10 kwie 2010, 00:28
Posty: 13694
Lokalizacja: Warszawa
Ja napisałem - dalej możesz mieć uszkodzone bloki z których wywaliłeś oznaczenie że są błędne...

_________________
http://eko.one.pl - prawie wszystko o OpenWrt


Na górę
 Wyświetl profil  
Odpowiedz z cytatem  
Wyświetl posty nie starsze niż:  Sortuj wg  
Nowy temat Odpowiedz w temacie  [ Posty: 26 ]  Przejdź na stronę 1, 2  Następna

Strefa czasowa UTC+1godz. [letni]


Kto jest online

Użytkownicy przeglądający to forum: Obecnie na forum nie ma żadnego zarejestrowanego użytkownika i 0 gości


Nie możesz tworzyć nowych tematów
Nie możesz odpowiadać w tematach
Nie możesz zmieniać swoich postów
Nie możesz usuwać swoich postów

Szukaj:
Przejdź do:  
designed by digi-led.pl
...Copyright © 2010-2013, Ekipa openrouter.info