General NAS-Central Forums

Welcome to the NAS community
It is currently Sat Dec 16, 2017 10:35 pm

All times are UTC




Post new topic Reply to topic  [ 16 posts ]  Go to page 1, 2  Next
Author Message
 Post subject: ix2-dl no boot
PostPosted: Thu Nov 09, 2017 7:26 am 
Offline

Joined: Thu Nov 09, 2017 7:21 am
Posts: 10
Hi, I have a trouble, help please:
Code:
Reading data from 0x3ff800 -- 100% complete.
 3145728 bytes read: OK
## Booting image at 02000000 ...
Bad Magic Number
Marvell>> usb start
(Re)start USB...
USB:   scanning bus for devices... 2 USB Device(s) found
Waiting for storage device(s) to settle before scanning...
1 Storage Device(s) found
Marvell>> load usb 0:1 0x800000 /images/zImage
Unknown command 'load' - try 'help'
Marvell>> fatload usb 0:1 0x800000 /images/zImage
Unknown command 'fatload' - try 'help'
Marvell>> fatload usb 0:1 0x800000 /images/zImage
reading /images/zImage
...............................................................................................................................................................................................................................................................................................

2943504 bytes read
Marvell>> fatload usb 0:1 0x1100000 /images/initrd
reading /images/initrd
....................................................................................................................................................................................................................................................................................

2834433 bytes read
Marvell>> bootm 0x1100000 0x80000
## Booting image at 01100000 ...
   Image Name:
   Created:      2013-04-08  17:29:27 UTC
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    2834369 Bytes =  2.7 MB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
Wrong Image Type for bootm command
Marvell>> bootm 0x800000 0x1100000
## Booting image at 00800000 ...
   Image Name:   Linux-2.6.31.8
   Created:      2013-03-12  21:25:40 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2943440 Bytes =  2.8 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
OK
## Loading Ramdisk Image at 01100000 ...
   Image Name:
   Created:      2013-04-08  17:29:27 UTC
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    2834369 Bytes =  2.7 MB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK

Starting kernel ...

Linux version 2.6.31.8 (soho@bsoho142.iomegacorp.com) (gcc version 4.3.2 (Sourcery G++ Lite 2008q3-72) ) Tue Mar 12 17:25:32 EDT 2013 v0.0.9 Tue Mar 12 17:25:32 EDT 2013
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: 64960
Kernel command line: console=ttyS0,115200 ubi.mtd=2 root=ubi0:rootfsU rootfstype=ubifs mv_net_config=(00:11:88:0f:62:81,0:1:2:3),mtu=1500 mv_phone_config=dev[0]:fxs,dev[1]:fxo
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: 243712KB available (5480K code, 371K data, 140K init, 0K highmem)
Hierarchical RCU implementation.
NR_IRQS:128
Console: colour dummy device 80x30
Calibrating delay loop... 1589.24 BogoMIPS (lpj=7946240)
Security Framework initialized
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
xor: measuring software checksum speed
   arm4regs  :  1446.000 MB/sec
   8regs     :  1096.000 MB/sec
   32regs    :  1070.800 MB/sec
xor: using function: arm4regs (1446.000 MB/sec)
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 ....base e8000000, size 128MB
PEX1_IO ....base f2100000, size   1MB
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_patch25)-- DB-88F6282A-BP  Soc: 88F6282 A1 LE

 Detected Tclk 200000000 and SysClk 533333333
MV Buttons Device Load
Marvell USB EHCI Host controller #0: c8040740
PEX0 interface detected no Link.
PEX1 interface detected no Link.
PCI: bus0: Fast back to back transfers enabled
PCI: bus1: Fast back to back transfers enabled
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
raid6: int32x1    122 MB/s
raid6: int32x2    146 MB/s
raid6: int32x4    159 MB/s
raid6: int32x8    124 MB/s
raid6: using algorithm int32x4 (159 MB/s)
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
Trying to unpack rootfs image as initramfs...
rootfs image is not initramfs (no cpio magic); looks like an initrd
Freeing initrd memory: 2768K
rtc mv_rtc: rtc core: registered kw-rtc as rtc0
RTC registered
XOR registered 4 channels
XOR 2nd invalidate WA enabled
cesadev_init(c000edd4)
mvCesaInit: sessions=640, queue=64, pSram=f0000000
MV Buttons Driver Load
VFS: Disk quotas dquot_6.5.2
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
squashfs: version 4.0 (2009/01/31) Phillip Lougher
Registering unionfs 2.5.11 (for 2.6.31.14)
Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
JFFS2 version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
SGI XFS with ACLs, security attributes, large block/inode numbers, no debug enabled
SGI XFS Quota Management subsystem
msgmni has been set to 481
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)
alg: No test for hmac(digest_null) (hmac(digest_null-generic))
async_tx: api initialized (sync-only)
Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253)
io scheduler noop registered
io scheduler anticipatory registered (default)
Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
serial8250.0: ttyS0 at MMIO 0xf1012100 (irq = 34) 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
scsi0 : Marvell SCSI to SATA adapter
scsi1 : Marvell SCSI to SATA adapter
Loading Marvell Ethernet Driver:
  o Cached descriptors in DRAM
  o DRAM SW cache-coherency
  o 2 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 Proc tool API enabled
  o Rx descripors: q0=256
  o Tx descripors: q0=532
  o Loading network interface(s):
     o register under mv88fx_eth platform
     o eth0, ifindex = 2, GbE port = 0

Warning: Giga 1 is Powered Off

tun: Universal TUN/TAP device driver, 1.6
tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
mvSFlashInit ERROR: Unknown SPI flash device!
ERROR: sflash_probe - Failed to initialize the SFlash.Using Hamming 1-bit ECC for NAND device
NAND device: Manufacturer ID: 0xec, Chip ID: 0xd3 (Samsung NAND 1GiB 3,3V 8-bit)
Scanning device for bad blocks
Bad eraseblock 3405 at 0x00001a9a0000
Bad eraseblock 4890 at 0x000026340000
Bad eraseblock 5928 at 0x00002e500000
Using static partition definition
Creating 3 MTD partitions on "nand_mtd":
0x000000000000-0x000000100000 : "u-boot"
0x000000100000-0x000000300000 : "uImage"
0x000000300000-0x000040000000 : "root"
UBI: attaching mtd2 to ubi0
UBI: physical eraseblock size:   131072 bytes (128 KiB)
UBI: logical eraseblock size:    129024 bytes
UBI: smallest flash I/O unit:    2048
UBI: sub-page size:              512
UBI: VID header offset:          512 (aligned 512)
UBI: data offset:                2048
UBI: attached mtd2 to ubi0
UBI: MTD device name:            "root"
UBI: MTD device size:            1021 MiB
UBI: number of good PEBs:        8165
UBI: number of bad PEBs:         3
UBI: max. allowed volumes:       128
UBI: wear-leveling threshold:    4096
UBI: number of internal volumes: 1
UBI: number of user volumes:     1
UBI: available PEBs:             40
UBI: total number of reserved PEBs: 8125
UBI: number of PEBs reserved for bad PEB handling: 81
UBI: max/mean erase counter: 2/1
UBI: image sequence number: 0
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
UBI: background thread "ubi_bgt0d" started, PID 480
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
adt7473 0-002e: adt7473 chip found
iBoard_model 2
md: linear personality registered for level -1
md: raid0 personality registered for level 0
md: raid1 personality registered for level 1
md: raid10 personality registered for level 10
md: raid6 personality registered for level 6
md: raid5 personality registered for level 5
md: raid4 personality registered for level 4
device-mapper: uevent: version 1.0.3
device-mapper: ioctl: 4.15.0-ioctl (2009-04-01) initialised: dm-devel@redhat.com
dm_crypt using the OCF package.
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 17
NET: Registered protocol family 5
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
rtc mv_rtc: setting system clock to 2056-08-19 01:55:30 UTC (2733875730)
md: Waiting for all devices to be available before autodetect
md: If you don't use raid, use raid=noautodetect
md: Autodetecting RAID arrays.
md: Scanned 0 and added 0 devices.
md: autorun ...
md: ... autorun DONE.
UBIFS error (pid 1): ubifs_get_sb: cannot open "ubi0:rootfsU", error -19
VFS: Cannot open root device "ubi0:rootfsU" or unknown-block(0,0)
Please append a correct "root=" boot option; here are the available partitions:
1f00            1024 mtdblock0 (driver?)
1f01            2048 mtdblock1 (driver?)
1f02         1045504 mtdblock2 (driver?)
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
Backtrace:
[<c014fe10>] (dump_backtrace+0x0/0x114) from [<c0038ee4>] (dump_stack+0x18/0x1c)
 r7:00008000 r6:c8077000 r5:c0026808 r4:c05b85d0
[<c0038ecc>] (dump_stack+0x0/0x1c) from [<c0038f34>] (panic+0x4c/0x114)
[<c0038ee8>] (panic+0x0/0x114) from [<c0008f9c>] (mount_block_root+0x1e0/0x220)
 r3:00000000 r2:20000013 r1:c8021f78 r0:c00e78bc
[<c0008dbc>] (mount_block_root+0x0/0x220) from [<c0009170>] (prepare_namespace+0x98/0x1cc)
 r8:00000000 r7:00000000 r6:00000000 r5:c0026808 r4:c0026818
[<c00090d8>] (prepare_namespace+0x0/0x1cc) from [<c0008494>] (kernel_init+0xdc/0x110)
 r5:00000000 r4:c05b7900
[<c00083b8>] (kernel_init+0x0/0x110) from [<c017e018>] (do_exit+0x0/0x5b4)
 r5:00000000 r4:00000000


Top
 Profile  
 
 Post subject: Re: ix2-dl no boot
PostPosted: Thu Nov 09, 2017 8:04 pm 
Offline

Joined: Mon Jun 16, 2008 10:45 am
Posts: 6091
Can you give some context?


Top
 Profile  
 
 Post subject: Re: ix2-dl no boot
PostPosted: Fri Nov 10, 2017 4:17 am 
Offline

Joined: Thu Nov 09, 2017 7:21 am
Posts: 10
Mijzelf wrote:
Can you give some context?

After unsuccessful update firmware, device don't booting. I was try to recover it, but it don't flash from usb, so i try to boot from command line.


Top
 Profile  
 
 Post subject: Re: ix2-dl no boot
PostPosted: Fri Nov 10, 2017 8:27 am 
Offline

Joined: Mon Jun 16, 2008 10:45 am
Posts: 6091
The box worked before the failed firmware update, I guess?

It doesn't boot now because it can't mount the right ubi partition on flash. That is strange for 2 reasons:
  • the UBI subsystem log doesn't show anything strange, so I would expect the ubi partition to be healthy.
  • You provided an initrd. Why doesn't it use that?
Where does this kernel&initrd come from?
Can you post the output of 'printenv'? Maybe another command line should be used.


Top
 Profile  
 
 Post subject: Re: ix2-dl no boot
PostPosted: Fri Nov 10, 2017 10:57 am 
Offline

Joined: Thu Nov 09, 2017 7:21 am
Posts: 10
Mijzelf wrote:
The box worked before the failed firmware update, I guess?

It doesn't boot now because it can't mount the right ubi partition on flash. That is strange for 2 reasons:
  • the UBI subsystem log doesn't show anything strange, so I would expect the ubi partition to be healthy.
  • You provided an initrd. Why doesn't it use that?
Where does this kernel&initrd come from?
Can you post the output of 'printenv'? Maybe another command line should be used.


How can I use initrd? ;)
it come from ix2-ng-4.1.206.33777.exe(recover flash maker)
Code:
         __  __                      _ _
        |  \/  | __ _ _ ____   _____| | |
        | |\/| |/ _` | '__\ \ / / _ \ | |
        | |  | | (_| | |   \ V /  __/ | |
        |_|  |_|\__,_|_|    \_/ \___|_|_|
 _   _     ____              _
| | | |   | __ )  ___   ___ | |_
| | | |___|  _ \ / _ \ / _ \| __|
| |_| |___| |_) | (_) | (_) | |_
 \___/    |____/ \___/ \___/ \__|  ** ix2-nand ** ** uboot_ver:0.0.8 **

 ** MARVELL BOARD: DB-88F6282A-BP LE

U-Boot 1.1.4 (Oct 28 2011 - 15:19:29) Marvell version: 3.6.1 - EMC

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

Soc: 88F6282 A1 CPU 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
NAND:1024 MB
Found ADT7473, program PWM1 ... OK
Flash:  0 kB

Marvell Serial ATA Adapter
Integrated Sata device found
[0 1 0]: Enable DMA mode (6)
  Device 1 @ 0 1:
Model: WDC WD20EFRX-68AX9N0                     Firm: 80.00A80 Ser#:      WD-WMC300579804
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 1907729.0 MB = 1863.0 GB (-387938128 x 512)


CPU : Marvell Feroceon (Rev 1)
Could not found correct kernel
Found initrd at 0x400000

Streaming disabled
Write allocate disabled


USB 0: host mode
PEX 0: interface detected no Link.
PEX 1: interface detected no Link.
Net:   egiga0 [PRIME]
Hit any key to stop autoboot:  0

NAND read: device 0 offset 0x100000, size 0x300000

Reading data from 0x3ff800 -- 100% complete.
 3145728 bytes read: OK
## Booting image at 02000000 ...
Bad Magic Number
Marvell>> printenv
baudrate=115200
loads_echo=0
rootpath=/srv/ubuntu
netmask=255.255.255.0
run_diag=yes
MALLOC_len=1
ethprime=egiga0
bootargs_end=:::DB88FXX81:eth0:none
image_name=uImage
standalone=fsload 0x2000000 $(image_name);setenv bootargs $(console) root=/dev/mtdblock0 rw ip=$(ipaddr):$(serverip)$(bootargs_end) $(mvPhoneConfig); bootm 0x2000000;
lcd0_enable=0
lcd0_params=640x480-16@60
ethmtu=1500
mvPhoneConfig=mv_phone_config=dev[0]:fxs,dev[1]:fxo
mvNetConfig=mv_net_config=(00:11:88:0f:62:81,0:1:2:3),mtu=1500
usb0Mode=host
yuk_ethaddr=00:00:00:EE:51:81
nandEcc=1bit
netretry=no
rcvrip=169.254.100.100
loadaddr=0x02000000
autoload=no
ethact=egiga0
kernel_size=0x300000
loadzimage=nand read.e 0x40000 $(kernel_start) $(kernel_size)
loadinitrd=nand read.e 0x900000 $(initrd_start) $(initrd_size)
bootargs_root=root=/dev/ram0
mk_mtdparts=setenv mtdparts mtdparts=nand_mtd:0x80000@0(uboot),0x20000@0xa0000(env),0x20000@0xc0000(env2),$(kernel_size)@$(kernel_start)(uImage),$(initrd_size)@$(initrd_start)(initrd),0x3f800000@0x800000(boot),1024m@0x0(flash)
initrdimage=mfginitrd
ipaddr=192.168.1.2
mfgmodel=ix2
preroot_ver=0.0.2
kernel_start=0x100000
uboot_ver=0.0.8
fw_ver=3.3.2.18857
serial_number=5563Y01011G23000255J0C1
ethaddr=00:D0:B8:20:E3:85
serialNo=LXAC320069
modelname=35888
serialno=1,01T9a0NK6chSMJQMZ3FvoF9JTi69Zoq7Pbwps03LsFScAl4yTTkad2RClWIjzqR1yK,LXAC320069,
runintime=10800
ftpserver=192.168.43.4
testfile=100M
mfgtest_state=system_tested_ok
pre_path=IX2/1.0.3/download_runin.sh
pre_path_conf=IX2/1.0.3/download_runin.conf
pre_serverip=192.168.32.4
pre_user=ixxrunin
pre_passwd=123
pre_dirzi=IX2/1.0.3
serverip=192.168.32.4
initrd_size=0x400000
mtdparts=mtdparts=nand_mtd:0x80000@0(uboot),0x20000@0xa0000(env),0x20000@0xc0000(env2),0x300000@0x100000(uImage),0x400000@0x400000(initrd),0x3f800000@0x800000(boot),1024m@0x0(flash)
image_multi=yes
bootcmd=setenv bootargs $(console) ubi.mtd=2 root=ubi0:rootfsU rootfstype=ubifs $(mvNetConfig) $(mvPhoneConfig) $(lcd0_bootargs); nand read.e $(loadaddr) 0x100000 0x300000; bootm $(loadaddr);
console=console=ttyS0,115200
filesize=2CEA10
stdin=serial
stdout=serial
stderr=serial
mainlineLinux=no
enaMonExt=no
enaCpuStream=no
enaWrAllo=no
pexMode=RC
disL2Cache=no
setL2CacheWT=yes
disL2Prefetch=yes
enaICPref=yes
enaDCPref=yes
sata_dma_mode=yes
netbsd_en=no
vxworks_en=no
initrd_start=0x400000
bootdelay=3
disaMvPnp=no
enaAutoRecovery=yes
pcieTune=no
pcieTune1=no
bootargs=console=ttyS0,115200 ubi.mtd=2 root=ubi0:rootfsU rootfstype=ubifs mv_net_config=(00:11:88:0f:62:81,0:1:2:3),mtu=1500 mv_phone_config=dev[0]:fxs,dev[1]:fxo

Environment size: 2572/131067 bytes
Marvell>>


Top
 Profile  
 
 Post subject: Re: ix2-dl no boot
PostPosted: Sat Nov 11, 2017 9:06 am 
Offline

Joined: Mon Jun 16, 2008 10:45 am
Posts: 6091
igorO wrote:
it come from ix2-ng-4.1.206.33777.exe(recover flash maker)
An ix2-ng is not an ix2-dl. Although I would expect them to share the same kernel and initrd, it can be different. And it seems to be different, as there might be no driver for the NAND flash
Quote:
Code:
1f00 1024 mtdblock0 (driver?)
1f01 2048 mtdblock1 (driver?)
1f02 1045504 mtdblock2 (driver?)
An ng has 1MiB NOR flash, while the dl has 1GiB NAND flash. (Wiki). So a ng kernel doesn't need to have the NAND drivers included.

Was your failed firmware update done using the same usb stick? Or was it an automatical webinterface update?


Top
 Profile  
 
 Post subject: Re: ix2-dl no boot
PostPosted: Sat Nov 11, 2017 9:58 am 
Offline

Joined: Thu Nov 09, 2017 7:21 am
Posts: 10
Mijzelf wrote:
igorO wrote:
it come from ix2-ng-4.1.206.33777.exe(recover flash maker)
An ix2-ng is not an ix2-dl. Although I would expect them to share the same kernel and initrd, it can be different. And it seems to be different, as there might be no driver for the NAND flash
Quote:
Code:
1f00 1024 mtdblock0 (driver?)
1f01 2048 mtdblock1 (driver?)
1f02 1045504 mtdblock2 (driver?)
An ng has 1MiB NOR flash, while the dl has 1GiB NAND flash. (Wiki). So a ng kernel doesn't need to have the NAND drivers included.

Was your failed firmware update done using the same usb stick? Or was it an automatical webinterface update?


I use the USB for update. On box written IX-DL, but at the sticker written ix2-ng.
Where I can find firmware for my device?


Top
 Profile  
 
 Post subject: Re: ix2-dl no boot
PostPosted: Sun Nov 12, 2017 6:42 pm 
Offline

Joined: Mon Jun 16, 2008 10:45 am
Posts: 6091
Quote:
Where I can find firmware for my device?

At download.lenovo.com. But it seems to offer 1 version for both the dl and the ng. I extracted the package, and it seems to contain only a single kernel. So probably there is only one kernel, and are your problems caused by a damaged ubi, although there are no complaints in your bootlog.
Maybe you can turn your box in an ng, by changing the u-boot environment. Reading your environment it reads it's kernel from nand, doesn't use an initrd, and uses ubi:rootfsU as rootfs.
The ng loads a kernel and initrd from harddisk, and use the initrd as rootfs. The initrd assembles the raidarray and mount it. I guess on the dl the ubi partition is responsible for that.
I think I can provide a dump of an ng u-boot, but you'll have to be patient, as I won't be near my ng for a week.


Top
 Profile  
 
 Post subject: Re: ix2-dl no boot
PostPosted: Mon Nov 13, 2017 7:12 am 
Offline

Joined: Thu Nov 09, 2017 7:21 am
Posts: 10
Mijzelf wrote:
Quote:
Where I can find firmware for my device?

At download.lenovo.com. But it seems to offer 1 version for both the dl and the ng. I extracted the package, and it seems to contain only a single kernel. So probably there is only one kernel, and are your problems caused by a damaged ubi, although there are no complaints in your bootlog.
Maybe you can turn your box in an ng, by changing the u-boot environment. Reading your environment it reads it's kernel from nand, doesn't use an initrd, and uses ubi:rootfsU as rootfs.
The ng loads a kernel and initrd from harddisk, and use the initrd as rootfs. The initrd assembles the raidarray and mount it. I guess on the dl the ubi partition is responsible for that.
I think I can provide a dump of an ng u-boot, but you'll have to be patient, as I won't be near my ng for a week.

Thank you!) I'l wait


Top
 Profile  
 
 Post subject: Re: ix2-dl no boot
PostPosted: Mon Nov 13, 2017 7:15 am 
Offline

Joined: Thu Nov 09, 2017 7:21 am
Posts: 10
Mijzelf wrote:
Quote:
Where I can find firmware for my device?

At download.lenovo.com. But it seems to offer 1 version for both the dl and the ng. I extracted the package, and it seems to contain only a single kernel. So probably there is only one kernel, and are your problems caused by a damaged ubi, although there are no complaints in your bootlog.
Maybe you can turn your box in an ng, by changing the u-boot environment. Reading your environment it reads it's kernel from nand, doesn't use an initrd, and uses ubi:rootfsU as rootfs.

Actually, what I should change in env?


Top
 Profile  
 
 Post subject: Re: ix2-dl no boot
PostPosted: Tue Nov 21, 2017 11:48 am 
Offline

Joined: Mon Jun 16, 2008 10:45 am
Posts: 6091
I dumped it in the Wiki

The command which is executed on boot is bootcmd:
Code:
bootcmd=ide reset; ide read 0x40000 0x800 0x1800; ide read 0x900000 0x2000 0x2000; setenv bootargs $(console) $(bootargs_root) $(bootargs_mtd) $(bootargs_end); bootm 0x40000 0x900000;run bootcmd2
As you can see it reads kernel&initrd from disk. Further it pulls some other variables, like console and bootargs_root. So make sure they are valid too.
At the end of the line it runs bootm. If that fails bootcmd2 is executed, which basically tries the other disk.

Because the kernel&initrd have to be on disk now, you have to prepare the disk this way.


Top
 Profile  
 
 Post subject: Re: ix2-dl no boot
PostPosted: Tue Nov 21, 2017 12:11 pm 
Offline

Joined: Thu Nov 09, 2017 7:21 am
Posts: 10
wow!
thank you!
now i have a way to recover my box!!!


Top
 Profile  
 
 Post subject: Re: ix2-dl no boot
PostPosted: Tue Nov 21, 2017 1:35 pm 
Offline

Joined: Thu Nov 09, 2017 7:21 am
Posts: 10
over trouble (

Code:
Starting kernel ...

Linux version 2.6.31.8 (soho@bsoho165.iomegacorp.com) (gcc version 4.7.2 (crosstool-NG 1.20.0) ) Fri Mar 25 09:21:23 EDT 2016 v0.0.9 Fri Mar 25 09:21:23 EDT 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: 64960
Kernel command line: console=ttyS0,115200 root=/dev/ram0 mtdparts=nand_mtd:0x80000@0(uboot),0x20000@0xa0000(env),0x20000@0xc0000(env2),0x300000@0x100000,0x400000@0x400000(initrd),0x3f800000@0x800000(boot),1024m@0x0(flash) :::DB88FXX81:eth0:none
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: 244352KB available (4592K code, 365K data, 136K init, 0K highmem)
Hierarchical RCU implementation.
NR_IRQS:128
Console: colour dummy device 80x30
Calibrating delay loop... 1589.24 BogoMIPS (lpj=7946240)
Security Framework initialized
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
xor: measuring software checksum speed
   arm4regs  :  1447.200 MB/sec
   8regs     :   867.200 MB/sec
   32regs    :  1086.800 MB/sec
xor: using function: arm4regs (1447.200 MB/sec)
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 ....base e8000000, size 128MB
PEX1_IO ....base f2100000, size   1MB
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_patch25)-- DB-88F6282A-BP  Soc: 88F6282 A1 LE

 Detected Tclk 200000000 and SysClk 533333333
MV Buttons Device Load
Marvell USB EHCI Host controller #0: c8040740
PEX0 interface detected no Link.
PEX1 interface detected no Link.
PCI: bus0: Fast back to back transfers enabled
PCI: bus1: Fast back to back transfers enabled
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
raid6: int32x1    125 MB/s
raid6: int32x2    157 MB/s
raid6: int32x4    162 MB/s
raid6: int32x8    159 MB/s
raid6: using algorithm int32x4 (162 MB/s)
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
Trying to unpack rootfs image as initramfs...
rootfs image is not initramfs (no cpio magic); looks like an initrd
Freeing initrd memory: 2912K
rtc mv_rtc: rtc core: registered kw-rtc as rtc0
RTC registered
XOR registered 4 channels
XOR 2nd invalidate WA enabled
cesadev_init(c000ed58)
mvCesaInit: sessions=640, queue=64, pSram=f0000000
MV Buttons Driver Load
VFS: Disk quotas dquot_6.5.2
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
squashfs: version 4.0 (2009/01/31) Phillip Lougher
Registering unionfs 2.5.11 (for 2.6.31.14)
Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
msgmni has been set to 483
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)
alg: No test for hmac(digest_null) (hmac(digest_null-generic))
async_tx: api initialized (sync-only)
Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253)
io scheduler noop registered
io scheduler anticipatory registered (default)
Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
serial8250.0: ttyS0 at MMIO 0xf1012100 (irq = 34) 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
scsi0 : Marvell SCSI to SATA adapter
scsi1 : Marvell SCSI to SATA adapter
scsi 1:0:0:0: Direct-Access     WDC      WD20EFRX-68AX9N0 80.0 PQ: 0 ANSI: 5
sd 1:0:0:0: [sda] Sector size 0 reported, assuming 512.
sd 1:0:0:0: [sda] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB)
sd 1:0:0:0: [sda] 0-byte physical blocks
sd 1:0:0:0: Attached scsi generic sg0 type 0
sd 1:0:0:0: [sda] Write Protect is off
Loading Marvell Ethernet Driver:
  o Cached descriptors in DRAM
  o DRAM SW cache-coherency
  o 2 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 Proc tool API enabled
  o Rx descripors: q0=256
  o Tx descripors: q0=532
  o Loading network interface(s):
     o register under mv88fx_eth platform
     o eth0, ifindex = 2, GbE port = 0

Warning: Giga 1 is Powered Off

tun: Universal TUN/TAP device driver, 1.6
tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
sd 1:0:0:0: [sda] Write cache: enabled, read cache: enabled, supports DPO and FUA
sd 1:0:0:0: [sda] Sector size 0 reported, assuming 512.
mvSFlashInit ERROR: Unknown SPI flash device!
ERROR: sflash_probe - Failed to initialize the SFlash.Using Hamming 1-bit ECC for NAND device
NAND flash model -> K9K8G08U0D.
NAND device: Manufacturer ID: 0xec, Chip ID: 0xd3 (Samsung NAND 1GiB 3,3V 8-bit)
Scanning device for bad blocks
Bad eraseblock 3405 at 0x00001a9a0000
Bad eraseblock 4890 at 0x000026340000
Bad eraseblock 5928 at 0x00002e500000
7 cmdlinepart partitions found on MTD device nand_mtd
Using command line partition definition
Creating 7 MTD partitions on "nand_mtd":
0x000000000000-0x000000080000 : "uboot"
0x0000000a0000-0x0000000c0000 : "env"
 sda:
0x0000000c0000-0x0000000e0000 : "env2"
0x000000100000-0x000000400000 : "Partition_003"
0x000000400000-0x000000800000 : "initrd"
0x000000800000-0x000040000000 : "boot"
0x000000000000-0x000040000000 : "flash"
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
ehci_marvell ehci_marvell.70059: irq 19, io base 0xf1050100
 sda1
sd 1:0:0:0: [sda] Sector size 0 reported, assuming 512.
sd 1:0:0:0: [sda] Attached SCSI disk
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
adt7473 0-002e: adt7473 chip found
iBoard_model 2
md: linear personality registered for level -1
md: raid0 personality registered for level 0
md: raid1 personality registered for level 1
md: raid10 personality registered for level 10
md: raid6 personality registered for level 6
md: raid5 personality registered for level 5
md: raid4 personality registered for level 4
device-mapper: uevent: version 1.0.3
device-mapper: ioctl: 4.15.0-ioctl (2009-04-01) initialised: dm-devel@redhat.com
dm_crypt using the OCF package.
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 17
NET: Registered protocol family 5
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
rtc mv_rtc: setting system clock to 2013-01-12 08:11:51 UTC (1357978311)
md: Waiting for all devices to be available before autodetect
md: If you don't use raid, use raid=noautodetect
md: Autodetecting RAID arrays.
md: Scanned 0 and added 0 devices.
md: autorun ...
md: ... autorun DONE.
RAMDISK: bzip2 image found at block 0
usb 1-1: new high speed USB device using ehci_marvell and address 2
usb 1-1: configuration #1 chosen from 1 choice
scsi2 : SCSI emulation for USB Mass Storage devices
VFS: Mounted root (ext2 filesystem) on device 1:0.
Looking for shell in cmdline: console=ttyS0,115200 root=/dev/ram0 mtdparts=nand_mtd:0x80000@0(uboot),0x20000@0xa0000(env),0x20000@0xc0000(env2),0x300000@0x100000,0x400000@0x400000(initrd),0x3f800000@0x800000(boot),1024m@0x0(flash) :::DB88FXX81:eth0:none
Make node for mtd devices
HDD /dev/sda detected
cat: can't open '/sys/class/block/sdb/removable': No such file or directory
FLASH based system detected
Create fw_env.config in /etc
Model name is ix2-ng
UBI: attaching mtd5 to ubi0
UBI: physical eraseblock size:   131072 bytes (128 KiB)
UBI: logical eraseblock size:    129024 bytes
UBI: smallest flash I/O unit:    2048
UBI: sub-page size:              512
UBI: VID header offset:          512 (aligned 512)
UBI: data offset:                2048
UBI: attached mtd5 to ubi0
UBI: MTD device name:            "boot"
UBI: MTD device size:            1016 MiB
UBI: number of good PEBs:        8125
UBI: number of bad PEBs:         3
UBI: max. allowed volumes:       128
UBI: wear-leveling threshold:    4096
UBI: number of internal volumes: 1
UBI: number of user volumes:     1
UBI: available PEBs:             0
UBI: total number of reserved PEBs: 8125
UBI: number of PEBs reserved for bad PEB handling: 81
UBI: max/mean erase counter: 2/1
UBI: image sequence number: 0
UBI: background thread "ubi_bgt0d" started, PID 623
UBI device number 0, total 8125 LEBs (1048320000 bytes, 999.8 MiB), available 0 LEBs (0 bytes), LEB size 129024 bytes (126.0 KiB)
UUID_1 = 8a49d597:c931a9d9:968e663a:8e60d376, size = 41943041
mdadm: No devices to examine
cat: can't open '/sys/class/block///size': No such file or directory
Valid Disk 1 in md0: /dev/sda1
Valid Disk 2 in md0:
USB Device node is /dev/sdb1
Checking to see the if the reset button is pressed or not
scsi 2:0:0:0: Direct-Access     SanDisk  Ultra Fit        1.00 PQ: 0 ANSI: 6
sd 2:0:0:0: Attached scsi generic sg1 type 0
sd 2:0:0:0: [sdb] 30031872 512-byte logical blocks: (15.3 GB/14.3 GiB)
sd 2:0:0:0: [sdb] Write Protect is off
sd 2:0:0:0: [sdb] Assuming drive cache: write through
sd 2:0:0:0: [sdb] Assuming drive cache: write through
 sdb: sdb1
sd 2:0:0:0: [sdb] Assuming drive cache: write through
sd 2:0:0:0: [sdb] Attached SCSI removable disk
Checking for valid image on system
UBIFS: recovery needed
UBIFS: recovery completed
UBIFS: mounted UBI device 0, volume 0, name "boot"
UBIFS: file system size:   1035159552 bytes (1010898 KiB, 987 MiB, 8023 LEBs)
UBIFS: journal size:       33546240 bytes (32760 KiB, 31 MiB, 260 LEBs)
UBIFS: media format:       w4/r0 (latest is w4/r0)
UBIFS: default compressor: lzo
UBIFS: reserved for root:  4952683 bytes (4836 KiB)
md: md0 stopped.
mdadm: stopped /dev/md0
md: md0 stopped.
md: bind<sda1>
raid1: raid set md0 active with 1 out of 2 mirrors
md0: detected capacity change from 0 to 21457928192
mdadm: /dev/md0 has been started with 1 drive (out of 2).
 md0: unknown partition table
  1 logical volume(s) in volume group "md0_vg" now active
Mount BFDlv to /mnt/boot on ix2-ng NAND
e2fsck 1.42.5 (29-Jul-2012)
ext2fs_check_if_mount: Can't check if filesystem is mounted due to missing mtab file while determining whether /dev/md0_vg/BFDlv is mounted.
/dev/md0_vg/BFDlv was not cleanly unmounted, check forced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information

          15 inodes used (0.01%, out of 262144)
           1 non-contiguous file (6.7%)
           0 non-contiguous directories (0.0%)
             # of inodes with ind/dind/tind blocks: 3/2/0
      152417 blocks used (14.54%, out of 1048576)
           0 bad blocks
           1 large file

           3 regular files
           3 directories
           0 character device files
           0 block device files
           0 fifos
           0 links
           0 symbolic links (0 fast symbolic links)
           0 sockets
------------
           6 files
Copy dev node to /sysroot/dev
Found Valid EMC Image in disk...
Mounting apps image...
Mounting config image...
Check config filesystem
attempt to access beyond end of device
loop0: rw=0, want=573456, limit=455088
EXT2-fs error (device loop0): ext2_get_inode: unable to read inode block - inode=12882, block=286727
Remounting filesystem read-only
attempt to access beyond end of device
loop0: rw=0, want=573456, limit=455088
EXT2-fs error (device loop0): ext2_get_inode: unable to read inode block - inode=12882, block=286727
Remounting filesystem read-only
attempt to access beyond end of device
loop0: rw=0, want=573456, limit=455088
EXT2-fs error (device loop0): ext2_get_inode: unable to read inode block - inode=12882, block=286727
Remounting filesystem read-only
attempt to access beyond end of device
loop0: rw=0, want=573456, limit=455088
EXT2-fs error (device loop0): ext2_get_inode: unable to read inode block - inode=12882, block=286727
Remounting filesystem read-only
attempt to access beyond end of device
loop0: rw=0, want=573456, limit=455088
EXT2-fs error (device loop0): ext2_get_inode: unable to read inode block - inode=12882, block=286727
Remounting filesystem read-only
attempt to access beyond end of device
loop0: rw=0, want=573456, limit=455088
EXT2-fs error (device loop0): ext2_get_inode: unable to read inode block - inode=12882, block=286727
Remounting filesystem read-only
attempt to access beyond end of device
loop0: rw=0, want=573456, limit=455088
EXT2-fs error (device loop0): ext2_get_inode: unable to read inode block - inode=12882, block=286727
Remounting filesystem read-only
attempt to access beyond end of device
loop0: rw=0, want=573456, limit=455088
EXT2-fs error (device loop0): ext2_get_inode: unable to read inode block - inode=12882, block=286727
Remounting filesystem read-only
e2fsck 1.42.5 (29-Jul-2012)
ext2fs_check_if_mount: Can't check if filesystem is mounted due to missing mtab file while determinattempt to access beyond end of device
ing whether /devloop0: rw=0, want=704606, limit=455088
/loop1 is mounteEXT2-fs error (device loop0): ext2_get_inode: d.
e2fsck: Invaunable to read inode block - inode=16144, block=352302lid argument whi
le trying to opeRemounting filesystem read-only
n /dev/loop1
mounionfs: error accessing lower directory '/sysroot/mnt/apps/etc' (error -5)
unt: mounting /dunionfs: read_super: error while parsing options (err = -5)
ev/loop1 on sysroot/mnt/etc failattempt to access beyond end of device
ed: Invalid arguloop0: rw=0, want=868446, limit=455088
ment
mount: mouEXT2-fs error (device loop0): ext2_get_inode: nting none on /sunable to read inode block - inode=19817, block=434222ysroot/etc faile
d: Input/output Remounting filesystem read-only
error
rm: can'tattempt to access beyond end of device
 remove '/sysrooloop0: rw=0, want=868446, limit=455088
t/boot/System.maEXT2-fs error (device loop0): ext2_get_inode: p-*': No such fiunable to read inode block - inode=19817, block=434222le or directory

Copying System.Remounting filesystem read-only
map...
mount: mounting /dev/loop2 on sysroot/oem failed: Invalid argument
No need to create fw_env.config
Create fw_env.config in /etc
Constructing root filesystem...
attempt to access beyond end of device
loop0: rw=0, want=491536, limit=455088
EXT2-fs error (device loop0): ext2_get_inode: unable to read inode block - inode=11043, block=245767
Remounting filesystem read-only
cp: can't stat 'attempt to access beyond end of device
/sysroot/mnt/apploop0: rw=0, want=999440, limit=455088
s/ram/lib/ld-2.7EXT2-fs error (device loop0): ext2_get_inode: .so': Input/outpunable to read inode block - inode=22450, block=499719ut error

Remounting filesystem read-only
cp: can't stat 'attempt to access beyond end of device
/sysroot/mnt/apploop0: rw=0, want=1032208, limit=455088
s/ram/lib/libselEXT2-fs error (device loop0): ext2_get_inode: inux.so.1': Inpuunable to read inode block - inode=23187, block=516103t/output error

Remounting filesystem read-only
cp: can't stat '/sysroot/mnt/apps/ram/lib/libdl-2.7.so': Input/output error
attempt to access beyond end of device
loop0: rw=0, want=868446, limit=455088
EXT2-fs error (device loop0): ext2_get_inode: unable to read inode block - inode=19817, block=434222
Remounting filesystem read-only
attempt to access beyond end of device
loop0: rw=0, want=540764, limit=455088
EXT2-fs error (device loop0): ext2_get_inode: unable to read inode block - inode=12456, block=270381
Remounting filesystem read-only
attempt to access beyond end of device
loop0: rw=0, want=573456, limit=455088
EXT2-fs error (device loop0): ext2_get_inode: unable to read inode block - inode=12882, block=286727
Remounting filesystem read-only
/linuxrc: attempt to access beyond end of device
line 77: echo: Iloop0: rw=0, want=540764, limit=455088
nput/output erroEXT2-fs error (device loop0): ext2_get_inode: r
unable to read inode block - inode=12456, block=270381
Remounting filesystem read-only
attempt to access beyond end of device
loop0: rw=0, want=573456, limit=455088
EXT2-fs error (device loop0): ext2_get_inode: unable to read inode block - inode=12882, block=286727
Remounting filesystem read-only
/linuxrc: attempt to access beyond end of device
line 78: ln: Inploop0: rw=0, want=573456, limit=455088
EXT2-fs error (device loop0): ext2_get_inode:
                                              unable to read inode block - inode=12882, block=286727
Remounting filesystem read-only
/linuxrc: attempt to access beyond end of device
line 80: /usr/loloop0: rw=0, want=540764, limit=455088
cal/cfg/initrd_bEXT2-fs error (device loop0): ext2_get_inode: ootstrap.sh: Inpunable to read inode block - inode=12456, block=270381ut/output error

Remounting filesystem read-only
attempt to access beyond end of device
loop0: rw=0, want=573456, limit=455088
EXT2-fs error (device loop0): ext2_get_inode: unable to read inode block - inode=12882, block=286727
Remounting filesystem read-only
/linuxrc: attempt to access beyond end of device
line 82: mount: loop0: rw=0, want=540764, limit=455088
Input/output errEXT2-fs error (device loop0): ext2_get_inode: or
unable to read inode block - inode=12456, block=270381
Remounting filesystem read-only
/linuxrc: attempt to access beyond end of device
line 87: /bin/grloop0: rw=0, want=540764, limit=455088
ep: Input/outputEXT2-fs error (device loop0): ext2_get_inode:  error
unable to read inode block - inode=12456, block=270381
Remounting filesystem read-only
attempt to access beyond end of device
loop0: rw=0, want=573456, limit=455088
EXT2-fs error (device loop0): ext2_get_inode: unable to read inode block - inode=12882, block=286727
Remounting filesystem read-only
/linuxrc: line 97: echo: Input/output erroattempt to access beyond end of device
r
loop0: rw=0, want=573456, limit=455088
EXT2-fs error (device loop0): ext2_get_inode: unable to read inode block - inode=12882, block=286727
Remounting filesystem read-only
attempt to access beyond end of device
loop0: rw=0, want=540764, limit=455088
EXT2-fs error (device loop0): ext2_get_inode: unable to read inode block - inode=12456, block=270381
Remounting filesystem read-only
attempt to access beyond end of device
loop0: rw=0, want=573456, limit=455088
EXT2-fs error (device loop0): ext2_get_inode: unable to read inode block - inode=12882, block=286727
Remounting filesystem read-only
/linuxrc: line 101: uname: Input/output error
sh: 3.8.6: unknown operand
Freeing init memory: 136K
attempt to access beyond end of device
loop0: rw=0, want=917598, limit=455088
EXT2-fs error (device loop0): ext2_get_inode: unable to read inode block - inode=20921, block=458798
Remounting filesystem read-only
attempt to access beyond end of device
loop0: rw=0, want=540764, limit=455088
EXT2-fs error (device loop0): ext2_get_inode: unable to read inode block - inode=12456, block=270381
Remounting filesystem read-only
attempt to access beyond end of device
loop0: rw=0, want=540764, limit=455088
EXT2-fs error (device loop0): ext2_get_inode: unable to read inode block - inode=12456, block=270381
Remounting filesystem read-only
Kernel panic - not syncing: No init found.  Try passing init= option to kernel.
Backtrace:
[<c0130760>] (dump_backtrace+0x0/0x10c) from [<c0130884>] (dump_stack+0x18/0x1c)
 r6:00000000 r5:c0024468 r4:c04d73d8 r3:80000013
[<c013086c>] (dump_stack+0x0/0x1c) from [<c015a9f4>] (panic+0x48/0x108)
[<c015a9ac>] (panic+0x0/0x108) from [<c012cd50>] (init_post+0xd8/0x100)
 r3:c8019c40 r2:0000000d r1:c0bd9000 r0:c00d7b3f
[<c012cc78>] (init_post+0x0/0x100) from [<c0008a80>] (kernel_init+0xe4/0x10c)
 r4:c0024468 r3:c800f798
[<c000899c>] (kernel_init+0x0/0x10c) from [<c015d78c>] (do_exit+0x0/0x5b0)
 r5:00000000 r4:00000000


Top
 Profile  
 
 Post subject: Re: ix2-dl no boot
PostPosted: Wed Nov 22, 2017 4:40 am 
Offline

Joined: Thu Nov 09, 2017 7:21 am
Posts: 10
I win it!
Thanks to Mijzelf !


Top
 Profile  
 
 Post subject: Re: ix2-dl no boot
PostPosted: Wed Nov 22, 2017 9:16 am 
Offline

Joined: Mon Jun 16, 2008 10:45 am
Posts: 6091
Great!

You don't give much information, as usual, so let me guess. You had to keep the reset button pressed while booting?


Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 16 posts ]  Go to page 1, 2  Next

All times are UTC


Who is online

Users browsing this forum: No registered users and 5 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
Powered by phpBB® Forum Software © phpBB Group