Cannot boot root file system from NAND with GoFlex Home

Hello there!

First posting to this group. I recently had a problem with my GoFlex Home base. The unit would function fine but would display "axentraserver: root" when using DLNA on my home LAN. As suggested by many forum posts, it would be better to reflash the base unit with the stock 2.7.1 firmware from Seagate. I did this and hence the problem started...

For the record I was previously able to SSH/SFTP into the base, which has firmware v2.7.1-391.

To debug, I created the serial cable and was able to pull the boot log using Termite and a USB to TTL Serial Cable (Console Cable for Raspberry Pi) from AdaFruit. I tried I receive the following error when using 1) the bare base 2) the base and SATA HDD and 3) trying to reflash with USB stick and SATA HDD in-place:

.
.
.
.
.
Warning Tdm is Powered Off
md: linear personality registered for level -1
md: raid0 personality registered for level 0
md: raid1 personality registered for level 1
raid6: int32x1 91 MB/s
raid6: int32x2 109 MB/s
raid6: int32x4 119 MB/s
raid6: int32x8 94 MB/s
raid6: using algorithm int32x4 (119 MB/s)
md: raid6 personality registered for level 6
md: raid5 personality registered for level 5
md: raid4 personality registered for level 4
raid5: measuring checksumming speed
arm4regs : 1084.400 MB/sec
8regs : 822.000 MB/sec
32regs : 803.200 MB/sec
raid5: using function: arm4regs (1084.400 MB/sec)
device-mapper: ioctl: 4.11.0-ioctl (2006-10-12) initialised: dm-devel@redhat.com
dm_crypt using the OCF package.
usbcore: registered new interface driver usbhid
drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver
TCP cubic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
UBIFS error (pid 1): ubifs_get_sb: cannot open "ubi0:rootfs", error -19
VFS: Cannot open root device "ubi0:rootfs" or unknown-block(0,0)
Please append a correct "root=" boot option; here are the available partitions:
1f00 1024 mtdblock0 (driver?)
1f01 6144 mtdblock1 (driver?)
1f02 254976 mtdblock2 (driver?)
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)


I have tentatively started looking at the uBoot rescue image(?). Any other thoughts would be greatly appreciated

-Chroma

Please post the whole boot log! And the listing of printenv.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

[00]

-- NAS EXPLORER --
_ _ ____ _
| | | | | __ ) ___ ___ | |_
| | | |___| _ \ / _ \ / _ \| __|
| |_| |___| |_) | (_) | (_) | |_
\___/ |____/ \___/ \___/ \__|
** QSI BOARD: NAS-PLUG LE

U-Boot 1.1.4 (Jun 10 2010 - 08:28:13) Marvell version: 3.4.27
QSI NAS version: 1.0.4

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

Soc: 88F6281 A0 (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 128MB
DRAM Total size 128MB 16bit width
Addresses 8M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (8M - 7M): Done
NAND:256 MB
Flash: 0 kB

CPU : Marvell Feroceon (Rev 1)

Streaming disabled
Write allocate disabled


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

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


Reading data from 0x100000 -- 0% complete.
Reading data from 0x10f000 -- 1% complete.
Reading data from 0x11e800 -- 2% complete.
Reading data from 0x12e000 -- 3% complete.
Reading data from 0x13d000 -- 4% complete.
Reading data from 0x14c800 -- 5% complete.
Reading data from 0x15c000 -- 6% complete.
Reading data from 0x16b800 -- 7% complete.
Reading data from 0x17a800 -- 8% complete.
Reading data from 0x18a000 -- 9% complete.
Reading data from 0x199800 -- 10% complete.
Reading data from 0x1a8800 -- 11% complete.
Reading data from 0x1b8000 -- 12% complete.
Reading data from 0x1c7800 -- 13% complete.
Reading data from 0x1d7000 -- 14% complete.
Reading data from 0x1e6000 -- 15% complete.
Reading data from 0x1f5800 -- 16% complete.
Reading data from 0x205000 -- 17% complete.
Reading data from 0x214000 -- 18% complete.
Reading data from 0x223800 -- 19% complete.
Reading data from 0x233000 -- 20% complete.
Reading data from 0x242800 -- 21% complete.
Reading data from 0x251800 -- 22% complete.
Reading data from 0x261000 -- 23% complete.
Reading data from 0x270800 -- 24% complete.
Reading data from 0x27f800 -- 25% complete.
Reading data from 0x28f000 -- 26% complete.
Reading data from 0x29e800 -- 27% complete.
Reading data from 0x2ae000 -- 28% complete.
Reading data from 0x2bd000 -- 29% complete.
Reading data from 0x2cc800 -- 30% complete.
Reading data from 0x2dc000 -- 31% complete.
Reading data from 0x2eb800 -- 32% complete.
Reading data from 0x2fa800 -- 33% complete.
Reading data from 0x30a000 -- 34% complete.
Reading data from 0x319800 -- 35% complete.
Reading data from 0x328800 -- 36% complete.
Reading data from 0x338000 -- 37% complete.
Reading data from 0x347800 -- 38% complete.
Reading data from 0x357000 -- 39% complete.
Reading data from 0x366000 -- 40% complete.
Reading data from 0x375800 -- 41% complete.
Reading data from 0x385000 -- 42% complete.
Reading data from 0x394000 -- 43% complete.
Reading data from 0x3a3800 -- 44% complete.
Reading data from 0x3b3000 -- 45% complete.
Reading data from 0x3c2800 -- 46% complete.
Reading data from 0x3d1800 -- 47% complete.
Reading data from 0x3e1000 -- 48% complete.
Reading data from 0x3f0800 -- 49% complete.
Reading data from 0x3ff800 -- 50% complete.
Reading data from 0x40f000 -- 51% complete.
Reading data from 0x41e800 -- 52% complete.
Reading data from 0x42e000 -- 53% complete.
Reading data from 0x43d000 -- 54% complete.
Reading data from 0x44c800 -- 55% complete.
Reading data from 0x45c000 -- 56% complete.
Reading data from 0x46b800 -- 57% complete.
Reading data from 0x47a800 -- 58% complete.
Reading data from 0x48a000 -- 59% complete.
Reading data from 0x499800 -- 60% complete.
Reading data from 0x4a8800 -- 61% complete.
Reading data from 0x4b8000 -- 62% complete.
Reading data from 0x4c7800 -- 63% complete.
Reading data from 0x4d7000 -- 64% complete.
Reading data from 0x4e6000 -- 65% complete.
Reading data from 0x4f5800 -- 66% complete.
Reading data from 0x505000 -- 67% complete.
Reading data from 0x514000 -- 68% complete.
Reading data from 0x523800 -- 69% complete.
Reading data from 0x533000 -- 70% complete.
Reading data from 0x542800 -- 71% complete.
Reading data from 0x551800 -- 72% complete.
Reading data from 0x561000 -- 73% complete.
Reading data from 0x570800 -- 74% complete.
Reading data from 0x57f800 -- 75% complete.
Reading data from 0x58f000 -- 76% complete.
Reading data from 0x59e800 -- 77% complete.
Reading data from 0x5ae000 -- 78% complete.
Reading data from 0x5bd000 -- 79% complete.
Reading data from 0x5cc800 -- 80% complete.
Reading data from 0x5dc000 -- 81% complete.
Reading data from 0x5eb800 -- 82% complete.
Reading data from 0x5fa800 -- 83% complete.
Reading data from 0x60a000 -- 84% complete.
Reading data from 0x619800 -- 85% complete.
Reading data from 0x628800 -- 86% complete.
Reading data from 0x638000 -- 87% complete.
Reading data from 0x647800 -- 88% complete.
Reading data from 0x657000 -- 89% complete.
Reading data from 0x666000 -- 90% complete.
Reading data from 0x675800 -- 91% complete.
Reading data from 0x685000 -- 92% complete.
Reading data from 0x694000 -- 93% complete.
Reading data from 0x6a3800 -- 94% complete.
Reading data from 0x6b3000 -- 95% complete.
Reading data from 0x6c2800 -- 96% complete.
Reading data from 0x6d1800 -- 97% complete.
Reading data from 0x6e1000 -- 98% complete.
Reading data from 0x6f0800 -- 99% complete.
Reading data from 0x6ff800 -- 100% complete.
6291456 bytes read: OK
## Booting image at 00800000 ...
Image Name: Linux-2.6.22.18
Created: 2010-06-17 5:37:59 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2095148 Bytes = 2 MB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
OK

Starting kernel ...

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

Linux version 2.6.22.18 (ramang@es5x86.axentra.com) (gcc version 4.3.2 (sdk3.2rc1-ct-ng-1.4.1) ) #16 Thu Jun 17 01:37:53 EDT 2010
CPU: ARM926EJ-S [56251311] revision 1 (ARMv5TE), cr=00053977
Machine: Feroceon-KW
Using UBoot passing parameters structure
Memory policy: ECC disabled, Data cache writeback
CPU0: D VIVT write-back cache
CPU0: I cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets
CPU0: D cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets
Built 1 zonelists. Total pages: 32512
Kernel command line: console=ttyS0,115200 ubi.mtd=2,2048 root=ubi0:rootfs rootfstype=ubifs init=/linuxrc
PID hash table entries: 512 (order: 9, 2048 bytes)
Console: colour dummy device 80x30
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Memory: 128MB 0MB 0MB 0MB = 128MB total
Memory: 125568KB available (3844K code, 261K data, 128K init)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
NET: Registered protocol family 16

CPU Interface
-------------
SDRAM_CS0 ....base 00000000, size 128MB
SDRAM_CS1 ....disable
SDRAM_CS2 ....disable
SDRAM_CS3 ....disable
PEX0_MEM ....base e8000000, size 128MB
PEX0_IO ....base f2000000, 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_4.3.4_patch22)-- SHEEVA PLUG Soc: 88F6281 A0 LE

Detected Tclk 200000000 and SysClk 400000000
MV Buttons Device Load
Marvell USB EHCI Host controller #0: c057b600
PEX0 interface detected no Link.
PCI: bus0: Fast back to back transfers enabled
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
NET: Registered protocol family 2
Time: kw_clocksource clocksource has been installed.
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 4096 (order: 3, 32768 bytes)
TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 4096 bind 4096)
TCP reno registered
RTC registered
XOR registered 2 channels
XOR 2nd invalidate WA enabled
cesadev_init(c0011854)
mvCesaInit: sessions=640, queue=64, pSram=f0000000
Warning: TS unit is powered off.
MV Buttons Driver Load
JFFS2 version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
io scheduler noop registered
io scheduler anticipatory registered (default)
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 33) is a 16550A
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
loop: module loaded
Loading Marvell Ethernet Driver:
o Cached descriptors in DRAM
o DRAM SW cache-coherency
o Single RX Queue support - ETH_DEF_RXQ=0
o Single TX Queue support - ETH_DEF_TXQ=0
o TCP segmentation offload enabled
o Receive checksum offload enabled
o Transmit checksum offload enabled
o Network Fast Processing (Routing) supported
o Driver ERROR statistics enabled
o Driver INFO statistics enabled
o Proc tool API enabled
o SKB Reuse supported
o SKB Recycle supported
o Rx descripors: q0=128
o Tx descripors: q0=532
o Loading network interface(s):
o register under eth%d platform
o eth0, ifindex = 1, GbE port = 0

Warning: Giga 1 is Powered Off

mvFpRuleDb (c7da7000): 1024 entries, 4096 bytes
Intel(R) PRO/1000 Network Driver - version 7.3.20-k2-NAPI
Copyright (c) 1999-2006 Intel Corporation.
e100: Intel(R) PRO/100 Network Driver, 3.5.17-k4-NAPI
e100: Copyright(c) 1999-2006 Intel Corporation
Integrated Sata device found
scsi0 : Marvell SCSI to SATA adapter
scsi1 : Marvell SCSI to SATA adapter
NFTL driver: nftlcore.c $Revision: 1.98 $, nftlmount.c $Revision: 1.41 $
NAND device: Manufacturer ID: 0x2c, Chip ID: 0xda (Micron NAND 256MiB 3,3V 8-bit)
Scanning device for bad blocks
Bad eraseblock 63 at 0x007e0000
Using static partition definition
Creating 3 MTD partitions on "nand_mtd":
0x00000000-0x00100000 : "u-boot"
0x00100000-0x00700000 : "uImage"
0x00700000-0x10000000 : "root"
UBI: attaching mtd2 to ubi0
UBI: physical eraseblock size: 131072 bytes (128 KiB)
UBI: logical eraseblock size: 126976 bytes
UBI: smallest flash I/O unit: 2048
UBI: sub-page size: 512
UBI: VID header offset: 2048 (aligned 2048)
UBI: data offset: 4096
UBI: attached mtd2 to ubi0
UBI: MTD device name: "root"
UBI: MTD device size: 249 MiB
UBI: number of good PEBs: 1991
UBI: number of bad PEBs: 1
UBI: max. allowed volumes: 128
UBI: wear-leveling threshold: 4096
UBI: number of internal volumes: 1
UBI: number of user volumes: 0
UBI: available PEBs: 1949
UBI: total number of reserved PEBs: 42
UBI: number of PEBs reserved for bad PEB handling: 38
UBI: max/mean erase counter: 1/1
UBI: background thread "ubi_bgt0d" started, PID 295
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
ehci_marvell ehci_marvell.70059: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
USB Universal Host Controller Interface driver v3.0
usbcore: registered new interface driver usblp
drivers/usb/class/usblp.c: v0.13: USB Printer Device Class driver
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
mice: PS/2 mouse device common for all mice
i2c /dev entries driver
Linux telephony interface: v1.00
Marvell Telephony Driver:

Warning Tdm is Powered Off
md: linear personality registered for level -1
md: raid0 personality registered for level 0
md: raid1 personality registered for level 1
raid6: int32x1 91 MB/s
raid6: int32x2 109 MB/s
raid6: int32x4 119 MB/s
raid6: int32x8 94 MB/s
raid6: using algorithm int32x4 (119 MB/s)
md: raid6 personality registered for level 6
md: raid5 personality registered for level 5
md: raid4 personality registered for level 4
raid5: measuring checksumming speed
arm4regs : 1084.400 MB/sec
8regs : 822.000 MB/sec
32regs : 803.200 MB/sec
raid5: using function: arm4regs (1084.400 MB/sec)
device-mapper: ioctl: 4.11.0-ioctl (2006-10-12) initialised: dm-devel@redhat.com
dm_crypt using the OCF package.
usbcore: registered new interface driver usbhid
drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver
TCP cubic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
UBIFS error (pid 1): ubifs_get_sb: cannot open "ubi0:rootfs", error -19
VFS: Cannot open root device "ubi0:rootfs" or unknown-block(0,0)
Please append a correct "root=" boot option; here are the available partitions:
1f00 1024 mtdblock0 (driver?)
1f01 6144 mtdblock1 (driver?)
1f02 254976 mtdblock2 (driver?)
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)


My apologies!

Sorry - how do I get the listing of printenv?

-Chroma

Chroma,

At serial console

printenv

Do you plan to install latest Debian or just want to run stock kernel from NAND?

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

-- NAS EXPLORER --
_ _ ____ _
| | | | | __ ) ___ ___ | |_
| | | |___| _ \ / _ \ / _ \| __|
| |_| |___| |_) | (_) | (_) | |_
\___/ |____/ \___/ \___/ \__|
** QSI BOARD: NAS-PLUG LE

U-Boot 1.1.4 (Jun 10 2010 - 08:28:13) Marvell version: 3.4.27
QSI NAS version: 1.0.4

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

Soc: 88F6281 A0 (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 128MB
DRAM Total size 128MB 16bit width
Addresses 8M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (8M - 7M): Done
NAND:256 MB
Flash: 0 kB

CPU : Marvell Feroceon (Rev 1)

Streaming disabled
Write allocate disabled


USB 0: host mode
PEX 0: interface detected no Link.
Net: egiga0 [PRIME]
Hit any key to stop autoboot: 0
NAS>> printend
Unknown command 'printend' - try 'help'
NAS>> printenv
baudrate=115200
loads_echo=0
ipaddr=169.254.254.253
serverip=169.254.254.254
rootpath=/mnt/ARM_FS/
netmask=255.255.0.0
run_diag=yes
CASset=min
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;
ethmtu=1500
usb0Mode=host
nandEcc=1bit
netretry=no
rcvrip=169.254.100.100
loadaddr=0x02000000
autoload=no
ethact=egiga0
rtc_mode=active
vm_ver_smt=1.1.0
pcba_sn=JA7A07358
console=console=ttyS0,115200
rtc_tz=PST
ntp_default=pool.ntp.org
smt_tag=10:07:13:02:14:52:54
ethaddr=00:10:75:28:19:FF
explrpk=PGFW-QAKU-WUUC-XJZD
explrsn=NA1Y563N
asm1_tag=10:07:14:03:19:08:02
filesize=33AA2E
bootargs=console=ttyS0,115200 root=/dev/ram0 rw ramdisk=0x01100000,8M install_type=nand
bootargs_root=ubi.mtd=2,2048 root=ubi0:rootfs rootfstype=ubifs init=/linuxrc
console2=console=ttyS0,115200
bootcmd=nand read.e 0x800000 0x100000 0x600000; setenv bootargs $(console2) $(bootargs_root); bootm 0x800000
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
bootdelay=3
disaMvPnp=no
enaAutoRecovery=no
pcieTune=no

Environment size: 1368/131068 bytes
NAS>>

bodhi - Thanks for your help so far, apprecaited! Currently I just want to run stock kernel from NAND and check it's still functioning.

-Chroma

Chroma,

Looks like your rootfs in NAND is still messed up. Did you use this procedure?
http://support.goflexhome.hipserv.com/en/reflash/index.html

This factory reflash is a little flaky,try it again util the LED flashes the correct sequence as desribed in the flashing instrution, if you have not done so already.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

mv-diag passed okay...

-Chroma

It was the factory reflash that got me in this problem to begin with ;) I'll try it again, thanks.

Flaky yes! Worked fine this time - it must have been your virtual presence! Thanks for your help - was unaware of the extensive bootloader commands.

-Chroma

chromaburst Wrote:
-------------------------------------------------------
> Flaky yes! Worked fine this time - it must have
> been your virtual presence!

LOL congrats!

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)