NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
ReadyNAS OS6 sur les modèles Legacy
17 Topics
READYNAS RN102 OS6 bloque apres upgrade firmware 6.10.6=>6.10.7
Bonjour, le NAS ne redemarre plus depuis la mise à jour du dernier firmware. connecté en serie j'ai les infos ci dessous : je vois 2 erreurs : [ 3.431061] Initramfs unpacking failed: unexpected EOF [ 4.434078] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) les essais usb recovery ou bootmenu osreinstall ou factory reset ne donnent rien merci d'avance pour vos conseils ---- General initialization - Version: 1.0.0 High speed PHY - Version: 2.1.4 (COM-PHY-V20) Update PEX Device ID 0x6710 High speed PHY - Ended Successfully 0001 DDR3 Training Sequence - Ver 5.7.1 DDR3 Training Sequence - Run without PBS. DDR3 Training Sequence - Ended Successfully BootROM: Image checksum verification PASSED __ __ _ _ | \/ | __ _ _ ____ _____| | | | |\/| |/ _` | '__\ \ / / _ \ | | | | | | (_| | | \ V / __/ | | |_| |_|\__,_|_| \_/ \___|_|_| _ _ ____ _ | | | | | __ ) ___ ___ | |_ | | | |___| _ \ / _ \ / _ \| __| | |_| |___| |_) | (_) | (_) | |_ \___/ |____/ \___/ \___/ \__| ** LOADER ** U-Boot 2011.12-gec25d27-dirty (Oct 26 2015 - 16:53:05) Marvell version: v2011.12 2014_T2.0p1 06/23/2015 ReadyNAS-102 V2.0 Board: DB-88F6710-BP SoC: MV6710 A1 CPU: Marvell PJ4B v7 UP (Rev 1) LE CPU @ 1200 [MHz] L2 @ 600 [MHz] TClock @ 200 [MHz] DDR @ 600 [MHz] DDR 16Bit Width, FastPath Memory Access DRAM: 512 MiB Map: Code: 0x1feef000:0x1ff9ef34 BSS: 0x1ffef0a0 Stack: 0x1f9eeef8 Heap: 0x1f9ef000:0x1feef000 NAND: (ID 0xf1ad) 128 MiB MMC: MRVL_MMC: 0 Bad block table found at page 65472, version 0x01 Bad block table found at page 65408, version 0x01 nand_read_bbt: Bad block at 0x000000060000 nand_read_bbt: Bad block at 0x000006bc0000 Initialize and scan all PCI interfaces PEX unit.port(active IF[-first bus]): ------------------------------------------ PEX 0: Root Complex Interface, Detected Link X1, GEN 2.0 PEX 1: Root Complex Interface, Detected Link X1, GEN 2.0 FPU not initialized USB 0: Host Mode USB 1: Host Mode Shutting down unused interfaces: GBE0 SDIO AUDIO TDM Modules/Interfaces Detected: RGMII1 Phy PEX0 (Lane 0) PEX1 (Lane 1) SATA0 (Lane 2) SATA1 (Lane 3) Net: , egiga1 [PRIME] Power On! FDT loaded successfully Saving Environment to NAND... Erasing Nand... Writing to Nand... done Enter Bootmenu... Bootmenu : NORMAL Bootmenu : FACTORY_DEFAULT Bootmenu : OS_REINSTALL Bootmenu : TECH_SUPPORT Bootmenu : VOL_RO Hit any key to stop autoboot: 0 NAND read: device 0 offset 0x200000, size 0x400000 4194304 bytes read: OK NAND read: device 0 offset 0x800000, size 0x400000 4194304 bytes read: OK ## Booting kernel from Legacy Image at 02000000 ... Image Name: Linux-4.4.218.armada.1 Created: 2021-11-07 15:34:15 UTC Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 3475392 Bytes = 3.3 MiB Load Address: 00008000 Entry Point: 00008000 Verifying Checksum ... OK ## Loading init Ramdisk from Legacy Image at 03000000 ... Image Name: initramfs Created: 2022-02-09 18:28:00 UTC Image Type: ARM Linux RAMDisk Image (lzma compressed) Data Size: 3426307 Bytes = 3.3 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 01000000 Booting using the fdt blob at 0x01000000 Loading Kernel Image ... OK Loading Ramdisk to 1f6aa000, end 1f9ee803 ... OK Using Device Tree in place at 01000000, end 01006617 Updating device tree successful Starting kernel ... [ 3.431061] Initramfs unpacking failed: unexpected EOF [ 3.812759] rtc-isl12057 0-0068: _isl12057_rtc_read_time: oscillator failure bit set, continuing anyway [ 3.824611] rtc-isl12057 0-0068: _isl12057_rtc_read_time: oscillator failure bit set, continuing anyway [ 3.836033] rtc-isl12057 0-0068: _isl12057_rtc_read_time: oscillator failure bit set, continuing anyway [ 3.846962] rtc-isl12057 0-0068: _isl12057_rtc_read_time: oscillator failure bit set, continuing anyway [ 3.902588] rtc-isl12057 0-0068: _isl12057_rtc_read_time: oscillator failure bit set, continuing anyway [ 4.350300] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) [ 4.358609] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.4.218.armada.1 #1 [ 4.365428] Hardware name: Marvell Armada 370/XP (Device Tree) [ 4.371325] [<c0015158>] (unwind_backtrace) from [<c00115ec>] (show_stack+0x10/0x18) [ 4.379114] [<c00115ec>] (show_stack) from [<c038667c>] (dump_stack+0x84/0xa8) [ 4.386386] [<c038667c>] (dump_stack) from [<c009bf04>] (panic+0x9c/0x210) [ 4.393310] [<c009bf04>] (panic) from [<c091a228>] (mount_block_root+0x24c/0x29c) [ 4.400835] [<c091a228>] (mount_block_root) from [<c091a410>] (prepare_namespace+0x128/0x188) [ 4.409404] [<c091a410>] (prepare_namespace) from [<c0919e78>] (kernel_init_freeable+0x210/0x260) [ 4.418332] [<c0919e78>] (kernel_init_freeable) from [<c06c5c2c>] (kernel_init+0x8/0xe8) [ 4.426466] [<c06c5c2c>] (kernel_init) from [<c000ec20>] (ret_from_fork+0x14/0x34) [ 4.434078] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)Solved2.7KViews1like5CommentsRecuperation d'un readynas duo
Bonjour voila je viens de recuperer un readynasduo il demarre mais a premiere vu il et vide pas de firmware comment en remetre un quelle et la manoeuvre a faire Raidrar me donne sa Modele : Readynasduo nas 17-cf-2 Statut aucun disqe detecter "logique il y en a pas " Micrologiciel (firmware) il mais rien c'est blanc Disques comme quoi je peut en mettre 2 mais ca je le savez :) Merci3.6KViews1like9Comments