Quantcast
Channel: Linux Device Hacking
Viewing all articles
Browse latest Browse all 3178

Cannot boot root file system from NAND with GoFlex Home (1 reply)

$
0
0
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

Viewing all articles
Browse latest Browse all 3178

Trending Articles