Bricked my goflex home on ubit v0.6 (solved by peaslaker)

This forum is for Marvell Kirkwood devices such as the GoFlex Home/Net, PogoPlug v1/v2, SheevaPlug, and ZyXEL devices.

Bricked my goflex home on ubit v0.6 (solved by peaslaker)

Postby orange » Sun Feb 13, 2011 7:55 pm

Hi,

I got a new goflex home 2tb and followed the instructions in this link for v0.6 ubit

http://plugboxlinux.org/wiki/index.php5 ... oFlex_Home

- did not use a usb drive
- used the official install
- was able to login to ssh and root access
- at the tar command it gave an error saying usr/man8/soundplex file not found
- I used rm command after tar command as shown in link
- After the reboot command, my goflex is blinking green - no network ip, nothing on port scan.

Any help is appreciated.

I have installed debian on nslu2 in past but i fear this maybe over my novice level. Thanks.
Last edited by orange on Wed Feb 16, 2011 10:53 pm, edited 1 time in total.
orange
 
Posts: 13
Joined: Sun Feb 13, 2011 6:25 pm

Re: Bricked my goflex home on ubit v0.6

Postby peaslaker » Mon Feb 14, 2011 12:08 am

Big message at top saying it was provisional content. UBIT v0.6 not released yet. plugboxlinux.org is the testing site for the version of Arch Linux ARM install that has not released yet.

Probably recoverable because the provisional UBIT v0.6 is one that I am thoroughly testing on the GoFlex Home at the moment, but the problems here are probably more to do with the "official" side of things than UBIT because there are omissions of the necessary stuff for getting SATA working.

Big note also at top of page. GoFlex Home + Official + SATA does not work (yet).

First things first. UBIT installs a netconsole by default. This lets you access U-Boot, which means it is recoverable. Second thing. If you go very far at all, you will not be able to return the GoFlex Home to the normal system unless you took backups of /dev/mtd2 before you got started. Third. If you were using the disk supplied with GoFlex Home, it is formatted as NTFS as standard, which is no good for a Linux install.

You have come to the right place because my GoFlex Home runs Arch Linux ARM install absolutely fine, but you went screaming past every single warning sign possible to get to the place you are now.
peaslaker
 
Posts: 101
Joined: Tue Sep 07, 2010 10:40 pm

Re: Bricked my goflex home on ubit v0.6

Postby peaslaker » Mon Feb 14, 2011 12:13 am

http://Arch Linux ARM.com/index.php5?title=Mo ... ing_netcat

You want to be able to interrupt the U-Boot over a netconsole. The relevant netconsole needs to be on 10.10.10.5, port 6666.

You will need a USB stick to rescue this. Do you have access to a Linux machine or are your other machines Windows?
peaslaker
 
Posts: 101
Joined: Tue Sep 07, 2010 10:40 pm

Re: Bricked my goflex home on ubit v0.6

Postby orange » Mon Feb 14, 2011 4:50 am

Here is netconsole readout with sata hdd attached

U-Boot 2010.09-00037-g4563447 (Feb 10 2011 - 12:49:31)
UBIT v0.6 by Jeff Doozan and Peter Carmichael
(Re)start USB...
USB: Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... 1 USB Device(s) found
scanning bus for storage devices... 0 Storage Device(s) found
Hit any key to stop autoboot: 0
UBIFS error (pid 0): ubifs_get_sb: cannot open "ubi:fast", error -19
Error reading superblock on volume 'ubi:fast'!
UBIFS not mounted, use ubifs mount to mount volume first!
** Block device usb 0 not supported
** Block device usb 0 not supported

** Invalid boot device **

** Invalid boot device **

Reset IDE: Bus 0: OK Bus 1: not available
Device 0: Model: ST32000542AS Firm: CC95 Ser#: 5XW0M877
Type: Hard Disk
Supports 48-bit addressing
Capacity: 1907729.0 MB = 1863.0 GB (-387938128 x 512)
Loading file "/boot/uImage" from ide device 0:1 (hda1)
Failed to mount ext2 filesystem...
** Bad ext2 partition or disk - ide 0:1 **
Loading file "/uInitrd" from ide device 0:1 (hda1)
Failed to mount ext2 filesystem...
** Bad ext2 partition or disk - ide 0:1 **
UBIFS error (pid 0): ubifs_get_sb: cannot open "ubi:preboot", error -19
Error reading superblock on volume 'ubi:preboot'!
UBIFS not mounted, use ubifs mount to mount volume first!
UBIFS error (pid 0): ubifs_get_sb: cannot open "ubi:ramdisk", error -19
Error reading superblock on volume 'ubi:ramdisk'!
UBIFS not mounted, use ubifs mount to mount volume first!
Marvell>>

I will format usb drive in ubuntu ext3 format extract Arch Linux ARM install linux and record netconsole. Will report back.
orange
 
Posts: 13
Joined: Sun Feb 13, 2011 6:25 pm

Re: Bricked my goflex home on ubit v0.6

Postby orange » Mon Feb 14, 2011 7:39 am

How do I build a rescue disk ? Thanks.

I tried usb drive but it keeps saying no boot/uimage, no uninitrd.
orange
 
Posts: 13
Joined: Sun Feb 13, 2011 6:25 pm

Arch Linux ARM install kernel SATA driver not built-in

Postby peaslaker » Mon Feb 14, 2011 9:43 am

To get a UBIT rescue disk, download these items onto the root of a USB disk or USB stick formatted as ext3:

Code: Select all
wget http://jeff.doozan.com/debian/goflex/v0.6/uInitrd
wget http://jeff.doozan.com/debian/goflex/v0.6/v2.6.37/boot.tar.gz

mv boot oldboot
tar -xvzf boot.tar.gz


This should boot. If it doesn't boot it is because of something funny going on with the USB device, in which case you need to interrupt the U-Boot using the netconsole and repeatedly run 'usb start' until the USB stick is identified, following up by running the command 'boot'. The IP address will have changed from your original IP address.

You can leave the GoFlex disk plugged in while you boot from USB.

When you get access to the UBIT prompt, you need to correct the bad untar from the Arch Linux ARM install tarball and you need to provide a kernel that has the SATA driver built in. UBIT provides just such a kernel, but it isn't the Arch Linux ARM install kernel. Arch Linux ARM install updates may kill the boot process until the latest changes filter through.

The GoFlex disk will be on /dev/sda1. At the UBIT prompt:

Code: Select all
#IMPORTANT
# Once you have logged in to the UBIT prompt, unplug the USB stick to protect
# the rescue system from being altered.  The rescue system includes the OE firmware
# to allow reverting to normal GoFlex Home configuration (not recommended).

# WARNING DESTROYS CONTENT OF HARDDRIVE
# If you think it best to start from scratch on the GoFlex disk:
mke2fs -j /dev/sda1


on /dev/sda1 sh
wget http://www.Arch Linux ARM.com/os/2010.12/Plugbox-Linux-2010.12-rootfs.tar.gz
tar -xvzf Plugbox-Linux-2010.12-rootfs.tar.gz
mv boot/uImage boot/olduImage
wget http://jeff.doozan.com/debian/goflex/v0.6/v2.6.37/boot.tar.gz
wget http://jeff.doozan.com/debian/goflex/v0.6/v2.6.37/modules.tar.gz
tar -xvzf boot.tar.gz
tar -xvzf modules.tar.gz

# by the time you get here, you should just have a disk containing the Arch Linux ARM install
# root filesystem and the UBIT kernel.  This is a bootable combination with
# the U-Boot you have installed.

exit  # exits from /dev/sda1
reboot; exit # hopefully reboots into Arch Linux ARM install
peaslaker
 
Posts: 101
Joined: Tue Sep 07, 2010 10:40 pm

Re: Bricked my goflex home on ubit v0.6

Postby orange » Wed Feb 16, 2011 12:24 am

Here is the usb rescue boot

U-Boot 2010.09-00037-g4563447 (Feb 10 2011 - 12:49:31)
UBIT v0.6 by Jeff Doozan and Peter Carmichael
(Re)start USB...
USB: Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... 2 USB Device(s) found
scanning bus for storage devices... 1 Storage Device(s) found
Hit any key to stop autoboot: 0
UBIFS error (pid 0): ubifs_get_sb: cannot open "ubi:fast", error -19
Error reading superblock on volume 'ubi:fast'!
UBIFS not mounted, use ubifs mount to mount volume first!
Loading file "/boot/uImage" from usb device 0:1 (usbda1)
2941544 bytes read
Loading file "/uInitrd" from usb device 0:1 (usbda1)
4000071 bytes read
## Booting kernel from Legacy Image at 00680000 ...
Image Name: Linux-2.6.37-ubit-01715-g1e5cda0
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2941480 Bytes = 2.8 MiB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
Image Name: UBIT-v0.6-00105-gf2d83d5
Image Type: ARM Linux RAMDisk Image (gzip compressed)
Data Size: 4000007 Bytes = 3.8 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK

Starting kernel ...


Kernel readout from netconsole

Linux version 2.6.37-ubit-01715-g1e5cda0 (root@vmdebian-cli) (gcc version 4.3.5 (Buildroot 2010.11-00087-g1563dfa) ) #1 Mon Feb 7 01:35:47 GMT 2011
CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=00053977
CPU: VIVT data cache, VIVT instruction cache
Machine: Seagate GoFlex Net
Memory policy: ECC disabled, Data cache writeback
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 32512
Kernel command line: console=ttyS0,115200 mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(pogoplug),-(root) root=/dev/sda1 rootdelay=10 netconsole=@10.10.10.6/eth0,@10.10.10.4/
PID hash table entries: 512 (order: -1, 2048 bytes)
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Memory: 128MB = 128MB total
Memory: 119328k/119328k available, 11744k reserved, 0K highmem
Virtual kernel memory layout:
vector : 0xffff0000 - 0xffff1000 ( 4 kB)
fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB)
DMA : 0xffc00000 - 0xffe00000 ( 2 MB)
vmalloc : 0xc8800000 - 0xfe800000 ( 864 MB)
lowmem : 0xc0000000 - 0xc8000000 ( 128 MB)
modules : 0xbf000000 - 0xc0000000 ( 16 MB)
.init : 0xc0008000 - 0xc0031000 ( 164 kB)
.text : 0xc0031000 - 0xc057e9b4 (5431 kB)
.data : 0xc0580000 - 0xc05b88a0 ( 227 kB)
SLUB: Genslabs=13, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
NR_IRQS:114
Console: colour dummy device 80x30
Calibrating delay loop... 1192.75 BogoMIPS (lpj=5963776)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
NET: Registered protocol family 16
Kirkwood: MV88F6281-A1, TCLK=200000000.
Feroceon L2: Cache support initialised.
bio: create slab <bio-0> at 0
vgaarb: loaded
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
Switching to clocksource orion_clocksource
NET: Registered protocol family 2
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
UDP hash table entries: 256 (order: 0, 4096 bytes)
UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
NET: Registered protocol family 1
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
Trying to unpack rootfs image as initramfs...
Freeing initrd memory: 3904K
JFFS2 version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
aufs 2.1-37
msgmni has been set to 240
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 33) is a 16550A
console [ttyS0] enabled
brd: module loaded
loop: module loaded
sata_mv sata_mv.0: version 1.28
sata_mv sata_mv.0: slots 32 ports 2
scsi0 : sata_mv
scsi1 : sata_mv
ata1: SATA max UDMA/133 irq 21
ata2: SATA max UDMA/133 irq 21
ONFI flash detected
ONFI param page 0 valid
NAND device: Manufacturer ID: 0x2c, Chip ID: 0xda (Micron NAND 256MiB 3,3V 8-bit)
Scanning device for bad blocks
Bad eraseblock 617 at 0x000004d20000
4 cmdlinepart partitions found on MTD device orion_nand
Creating 4 MTD partitions on "orion_nand":
0x000000000000-0x000000100000 : "u-boot"
0x000000100000-0x000000500000 : "uImage"
0x000000500000-0x000002500000 : "pogoplug"
0x000002500000-0x000010000000 : "root"
MV-643xx 10/100/1000 ethernet driver version 1.4
mv643xx_eth smi: probed
net eth0: port 0 with MAC address xx:xx:xx:xx:xx:xx
netconsole: local port 6665
netconsole: local IP 10.10.10.6
netconsole: interface 'eth0'
netconsole: remote port 6666
netconsole: remote IP 10.10.10.4
netconsole: remote ethernet address ff:ff:ff:ff:ff:ff
netconsole: device eth0 not up yet, forcing it
ata1: SATA link up 3.0 Gbps (SStatus 123 SControl F300)
ata1.00: ATA-8: ST32000542AS, CC95, max UDMA/133
ata1.00: 3907029168 sectors, multi 0: LBA48 NCQ (depth 31/32)
ata1.00: configured for UDMA/133
scsi 0:0:0:0: Direct-Access ATA ST32000542AS CC95 PQ: 0 ANSI: 5
sd 0:0:0:0: [sda] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: Attached scsi generic sg0 type 0
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sda: sda1
sd 0:0:0:0: [sda] Attached SCSI disk
ata2: SATA link down (SStatus 0 SControl F300)
eth0: link up, 1000 Mb/s, full duplex, flow control disabled
console [netcon0] enabled
netconsole: network logging started
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
orion-ehci orion-ehci.0: Marvell Orion EHCI
orion-ehci orion-ehci.0: new USB bus registered, assigned bus number 1
orion-ehci orion-ehci.0: irq 19, io mem 0xf1050000
orion-ehci orion-ehci.0: USB 2.0 started, EHCI 1.00
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
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
mice: PS/2 mouse device common for all mice
rtc-mv rtc-mv: rtc core: registered rtc-mv as rtc0
i2c /dev entries driver
cpuidle: using governor ladder
cpuidle: using governor menu
mv_xor_shared mv_xor_shared.0: Marvell shared XOR driver
mv_xor_shared mv_xor_shared.1: Marvell shared XOR driver
mv_xor mv_xor.0: Marvell XOR: ( xor cpy )
mv_xor mv_xor.1: Marvell XOR: ( xor fill cpy )
mv_xor mv_xor.2: Marvell XOR: ( xor cpy )
mv_xor mv_xor.3: Marvell XOR: ( xor fill cpy )
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
oprofile: hardware counters not available
oprofile: using timer interrupt.
TCP cubic registered
NET: Registered protocol family 17
lib80211: common routines for IEEE802.11 drivers
Registering the dns_resolver key type
registered taskstats version 1
rtc-mv rtc-mv: setting system clock to 2011-02-15 22:01:44 UTC (1297807304)
Freeing init memory: 164K
usb 1-1: new high speed USB device using orion-ehci and address 2
scsi2 : usb-storage 1-1:1.0
scsi 2:0:0:0: Direct-Access HP v125w 0.00 PQ: 0 ANSI: 2
sd 2:0:0:0: [sdb] 7892040 512-byte logical blocks: (4.04 GB/3.76 GiB)
sd 2:0:0:0: Attached scsi generic sg1 type 0
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
sshd (786): /proc/786/oom_adj is deprecated, please use /proc/786/oom_score_adj instead.

The line net eth0: port 0 with MAC address xx:xx:xx:xx:xx:xx gives a mac address (it gave a real alpha numeric- I changed it to xxx for posting) that is different than the mac id on the bottom of seagate go flex.

The line netconsole: remote ethernet address ff:ff:ff:ff:ff:ff (did not give alpha-numeric - Its unchanged by me)

When I ssh using putty or linux ssh, I get access denied.

Ubit prompt never started. Do I need to have the ubit_start on the usb drive.

What I am doing wrong ? TIA.
orange
 
Posts: 13
Joined: Sun Feb 13, 2011 6:25 pm

Re: Bricked my goflex home on ubit v0.6

Postby peaslaker » Wed Feb 16, 2011 1:34 am

/proc/786/oom_adj is deprecated, please use /proc/786/oom_score_adj instead


This line indicates that the ssh server has started up. It comes from the rather primitive version of ssh implemented in the UBIT ramdisk when it generates the ssh keys. There should be two lines like this. As long as you don't have any signs of a kernel panic after this point, the ssh server is up and running. It can take 10-20 seconds to generate the keys after the kernel has started, so be patient.

These keys will change every time you boot the ramdisk from a USB stick, so you may have to delete out of date credentials from the Ubuntu system you are accessing the system from.

Code: Select all
ssh-keygen -R 192.168.1.2 (or whatever your device ip id)


The MAC address was overridden when you replaced the U-Boot. You can put it back later, but it doesn't stop you logging in.

The ff:ff:ff:ff:ff:ff on the netconsole is entirely normal. Doesn't matter.

The login credentials for the default UBIT install are userid "root" and password "root".

If you set up a netconsole on 10.10.10.2 while the system boots UBIT, it will tell you the IP address. Test the IP address using ping. No response means the wrong IP address. You can also look at your router logs to find the IP address given out by DHCP.

If it pings and you see:

/proc/786/oom_adj is deprecated, please use /proc/786/oom_score_adj instead
/proc/786/oom_adj is deprecated, please use /proc/786/oom_score_adj instead

you should be good to login.
peaslaker
 
Posts: 101
Joined: Tue Sep 07, 2010 10:40 pm

Re: Bricked my goflex home on ubit v0.6

Postby orange » Wed Feb 16, 2011 10:53 pm

Thanks for your help. I got my goflex home running Arch Linux ARM install linux.
I was using seagate login for root, ssh was geeting denied. root and root worked.

You are a genius, thanks for your input. I now have a fully functional Arch Linux ARM install, otherwise I would have a door stop. :mrgreen:
orange
 
Posts: 13
Joined: Sun Feb 13, 2011 6:25 pm

Re: Bricked my goflex home on ubit v0.6 (solved by peaslaker

Postby peaslaker » Wed Feb 16, 2011 10:58 pm

Ah, but you followed my instructions to generate the doorstop... Honestly, the next generation is looking very very good for reliability and simplicity. The development version of Arch Linux ARM install is moving ahead with full support for the GoFlex Home and I've been putting in a lot of work to make it simpler to get the install and rescue features running.

Sorry you got caught in the middle. Glad we've got you sorted... for now.
peaslaker
 
Posts: 101
Joined: Tue Sep 07, 2010 10:40 pm

Next

Return to Marvell Kirkwood

Who is online

Users browsing this forum: No registered users and 2 guests