Trying to install rescue system on new GoFlex Net

Hi all!

I just got a new GoFlex Net and I am trying to install debian on a USB stick. Initially I tried running Jeff's script but got the same message as here.
After trying with another USB stick, decided to try the recommendation of running the USB rescue system and then installing the rescue system in the nand, booting from that & then installing debian on the stick.
The USB rescue system booted OK but but when I try to install the rescue system it says that I need to install the newest uboot first. I have already installed ubit davygravy-2012-04-19 and I can't figure out what to try next. Any hints?

the last lines of the install_rescue script are:

Block size 131072, page size 2048, OOB size 64
Dumping data starting at 0x00000000 and ending at 0x00080000...
Connecting to download.doozan.com (50.116.34.13:80)
Connecting to projects.doozan.com (50.116.34.13:80)
valid-uboot.md5      100% |**************************************************************|  1133   0:00:00 ETA
##
## uBoot is not up-to-date
## Please install the newest uBoot and then re-run this installer.
##

when i run the install_uboot_mtd0.sh it says that I have the most recent uBoot!! I then tried commenting out the uboot check in the install_rescue.sh script but that didn't work either yielding the following problem

./install_rescue.sh: line 270: /usr/sbin/flash_eraseall: No such file or directory
ubiformat: mtd2 (nand), size 33554432 bytes (32.0 MiB), 256 eraseblocks of 131072 bytes (128.0 KiB), min. I/O size 2048 bytes
libscan: scanning eraseblock 255 -- 100 % complete  
ubiformat: 62 eraseblocks are supposedly empty
ubiformat: warning!: 194 of 256 eraseblocks contain non-ubifs data
ubiformat: warning!: only 0 of 256 eraseblocks have valid erase counter
ubiformat: erase counter 0 will be used for all eraseblocks
ubiformat: note, arbitrary erase counter value may be specified using -e option
ubiformat: use erase counter 0 for all eraseblocks
ubiformat: flashing eraseblock 220 -- 100 % complete  
ubiformat: formatting eraseblock 255 -- 100 % complete  
# Rescue System installation has completed successfully.

Any insights??



Edited 1 time(s). Last edit at 09/15/2012 04:56PM by alexisazen.

I'm thinking that eraseall has been deprecated.

??

I don't know for sure if that is your problem, but that binary is expected, but not found.

=====================================================

• davy's Github Repo's rescue-dg

Same problem here: netconsole says:

U-Boot 2011.12 (Apr 18 2012 - 23:08:20)

When trying to update uboot:

rescue:/tmp# ./install_uboot_mtd0.sh

!!!!!!  DANGER DANGER DANGER DANGER DANGER DANGER  !!!!!!

If you lose power to your device while running this script,
it could be left in an unusable state.

This script will replace the bootloader on /dev/mtd0.

This installer will only work on the following devices:
 Seagate Dockstar
 Seagate GoFlex Net
 Seagate GoFlex Home
 Pogoplug v1
 Pogoplug Pink (v2)
Do not run this installer on any other device.

By typing ok, you agree to assume all liabilities and risks
associated with running this installer.

If you agree, type 'ok' and press ENTER to continue: ok
# checking for /usr/sbin/nandwrite...
# checking for /usr/sbin/nanddump...
# checking for /usr/sbin/flash_erase...
# checking for /usr/sbin/fw_printenv...
# checking for /etc/fw_env.config...

# Validating existing uBoot...
Block size 131072, page size 2048, OOB size 64
Dumping data starting at 0x00000000 and ending at 0x00080000...
Connecting to jeff.doozan.com (50.116.34.13:80)
Connecting to projects.doozan.com (50.116.34.13:80)
valid-uboot.md5      100% |****************************************************************************************************************|  1133   0:00:00 ETA
## Valid uBoot detected: [goflexnet davygravy-2012-04-19-current]
## The newest uBoot is already installed on mtd0.


You are already running the latest uBoot.
Your current uBoot environment should be reasonable.  However, if you're having
any probems booting, you can reset the environment variables to know good values.
Would you like to reset the uBoot environment? [N/y] n

# uBoot installation has completed successfully.

So latest kernel uboot it is...

Installing rescue system to NAND (actually booted from rescue@USB)

rescue:/tmp# wget http://jeff.doozan.com/debian/rescue/install_rescue.sh
Connecting to jeff.doozan.com (50.116.34.13:80)
Connecting to projects.doozan.com (50.116.34.13:80)
install_rescue.sh    100% |****************************************************************************************************************|  8122   0:00:00 ETA
rescue:/tmp# chmod +x install_rescue.sh
rescue:/tmp# ./install_rescue.sh

This script will install a rescue system on your NAND.
It will OVERWRITE ALL OF THE POGOPLUG FILES.

This script will replace the kernel on on mtd1 and the rootfs on mtd2.

This installer will only work on a Seagate Dockstar or Pogoplug Pink.
Do not run this installer on any other device.

By typing ok, you agree to assume all liabilities and risks
associated with running this installer.

If you agree, type 'ok' and press ENTER to continue: ok
# checking for /usr/sbin/nandwrite...
# checking for /usr/sbin/nanddump...
# checking for /usr/sbin/ubiformat...
# checking for /usr/sbin/flash_eraseall...
# checking for /usr/sbin/fw_printenv...
# checking for /etc/fw_env.config...
## Verifying new uBoot...
Block size 131072, page size 2048, OOB size 64
Dumping data starting at 0x00000000 and ending at 0x00080000...
Connecting to download.doozan.com (50.116.34.13:80)
Connecting to projects.doozan.com (50.116.34.13:80)
valid-uboot.md5      100% |****************************************************************************************************************|  1133   0:00:00 ETA
##
## uBoot is not up-to-date
## Please install the newest uBoot and then re-run this installer.
##

So i commented those rm-commands out which deleted the dumps and compared:

rescue:/tmp# md5sum uboot-mtd0-dump
fc870ab151ac6c369d094de36318d6a5  uboot-mtd0-dump

rescue:/tmp# cat valid-uboot.md5
b2d9681ef044e9ab6b058ef442b30b6e dockstar original
5cbbbca7693c5939836349bbd7f270e8 goflexnet original
9b940e0b3b5a523f8b50ef0fa50af97f goflexhome original
c7b77a049725096d83db958f39b2c0c3 pinkpogo original
7e454d6b669ddadf3e97a2bf562653fa pogov1 original
3a6f82e07f89e569d721f1f8b25096c2 dockstar jeff-2010-08-07
76a3ff87a2a2df5ab129319c6cf14089 dockstar jeff-2010-08-23
21196b4c6bf2f7ef94b9ddf7d44f5272 dockstar jeff-2010-08-24
447561d59678984205324463d003311f dockstar jeff-2010-08-25
7acb243fb8c3f131f1a165b3dc64faaf dockstar jeff-2010-08-30
ebd566de30c6521e65fb1255415c037f dockstar jeff-2010-10-23
ebd566de30c6521e65fb1255415c037f pogov1 jeff-2010-10-23
2774216e13c4e46bb7e554b9a3eb1dfb goflexnet jeff-2010-10-23
0eb4684426a96efd12574c1ea9b52b6f pinkpogo jeff-2010-10-23
e18a2c7e308c249bc16f55bbaad31f50 dockstar davygravy-2012-02-12-current
e18a2c7e308c249bc16f55bbaad31f50 pogov1 davygravy-2012-02-12-current
e84a5fd0a0205bb79aed07c3c6fbd145 pinkpogo davygravy-2012-02-20-current
77ce1df732843774e5257b615ba8a9db goflexnet davygravy-2012-04-19-current
77ce1df732843774e5257b615ba8a9db goflexhome davygravy-2012-04-19-current

Which just gives me the clue that there is a MD5 mismatch... Ideas?

Basically the command

$NANDDUMP -no -l 0x80000 -f /tmp/uboot-mtd0-dump /dev/mtd0

gives sometimes another MD5sum than

$NANDDUMP --noecc --omitoob -l 0x80000 -f /tmp/uboot-mtd0-dump /dev/mtd0

which is used in the install_uboot_mtd0.sh

But anyway, after omitting that, I get to the same error like above, that "flash_eraseall" is not existent. Which is just wrong.

Writing data to block 26 at offset 0x340000
Writing data to block 27 at offset 0x360000
./install_rescue.sh: line 271: /usr/sbin/flash_eraseall: No such file or directory
ubiformat: mtd2 (nand), size 33554432 bytes (32.0 MiB), 256 eraseblocks of 131072 bytes (128.0 KiB), min. I/O size 2048 bytes
libscan: scanning eraseblock 255 -- 100 % complete
ubiformat: 256 eraseblocks have valid erase counter, mean value is 0
ubiformat: flashing eraseblock 220 -- 100 % complete
ubiformat: formatting eraseblock 255 -- 100 % complete
# Rescue System installation has completed successfully.

If I download it manually:

rescue:/tmp# wget http://download.doozan.com/uboot/flash_eraseall
Connecting to download.doozan.com (50.116.34.13:80)
flash_eraseall       100% |*******************************| 11648   0:00:00 ETA

rescue:/tmp# chmod +x flash_eraseall

rescue:/tmp# ./flash_eraseall
-sh: ./flash_eraseall: No such file or directory

rescue:/tmp# md5sum flash_eraseall
309da0690d9ad7079f6d16310d655ff9  flash_eraseall

Funnily on my second old dockstar (not new goflex) which is running squeeze correct, i get:

root@slut:~# ./flash_eraseall
./flash_eraseall: no MTD device specified
Try `./flash_eraseall --help' for more information.

Any ideas?

rescue:/tmp# uname -a
Linux rescue 3.3.2-kirkwide #1 Fri Jun 8 14:39:32 CDT 2012 armv5tel GNU/Linux

Edited 1 time(s). Last edit at 09/19/2012 06:23AM by Gr3yh0und.

... be very careful here... updates and changes to mtd-utils have resulted to some new command structures...

=====================================================

• davy's Github Repo's rescue-dg

davygravy Wrote:
-------------------------------------------------------
> ... be very careful here... updates and changes to
> mtd-utils have resulted to some new command
> structures...


Haven't done anything what the script wouldn't have... But I am just wondering why THIS binary (flash_eraseall) is not working on THIS device. i.e. it is executed on another dockstar with same architecture/hw. So where is the difference?

Even when i get the actual mtd-utils debian squeeze package, the same binary is supplied
(md5 = 309da0690d9ad7079f6d16310d655ff9)



Edited 1 time(s). Last edit at 09/20/2012 11:37AM by Gr3yh0und.

Got it working. Resolution:

Download the NSA320 tar.gz from davey from here: http://forum.doozan.com/read.php?2,7806,7806,quote=1
Unpack it to USB and, oh wonder, flash_eraseall is working. Now the V2 Version of Jeff is running, which is sufficient for my uses...

Hi Gr3yh0und,

if I understand correctly, your resolution is to boot from davygray's NSA320's USB and then do the install of the rescue in the nand.

If could just confirm that my understanding is correct, I would be grateful.

Hey alexisazen,

Yes you are right. Booting the NSA320's root filesystem from USB and doing the whole NAND install process which leads to a working JEFF V2 Rescue system. After that i booted into rescue and did the USB wheezy install, which also ran fine. I will make a blog post this weekend about the whole procedure.

Cheers

Following your lead, I booted the davy's NSA320 from USB, installed rescue in NAND and now I am trying to install debian in a USB stick. Many thanks for your input!

Sadly, my debian installation fails in the same fashion as here. Can I just use my debian installation from a working dockstar? (I mean to just dd the image of the dockstar USB stick to a new stick and try booting goflex net from there).

Gr3yh0und Wrote:
-------------------------------------------------------
> I will make a blog post this weekend about the whole
> procedure.

Cool, where did you post it, I'd like to take a look at that, since I ran into probs with my goflex net?

Hey there,
sorry for delay. It's missing partitioning and rescueing, will add that when I have more time to play with it again...
http://morschi.com/2012/10/05/seagate-goflex-net-debian/

Cheers

I am attempting to install Debian on my friend's GoFlex Net and uBoot has already been updated and boots from USB with no issue.

Yet I got the "FATAL: Kernel Too Old" during Jeff's script which Google Search pointed me to try booting this USB stick and then install rescue system on MTD and then do install Debian install booted on rescue system;.

Yet install_rescue.sh tells me first my uBoot is bad even though it's definitely the latest and even bypassing that it tells me flash_eraseall is not found even though I obviously see it in ls and tried downloading it.

Also I tried running the NSA320 USB Stick but it just seems to boot with an endless green light for minutes on end.

alexisazen Wrote:
-------------------------------------------------------
> Following your lead, I booted the davy's NSA320
> from USB, installed rescue in NAND and now I am
> trying to install debian in a USB stick.
>
> Sadly, my debian installation fails in the same
> fashion as
>
> here.

dito

Wheezy is still formally in "Testing" designation, is it not? It is discouraging that there are still so many bumps in the road, but I guess that is why they call it "Testing"...

=====================================================

• davy's Github Repo's rescue-dg

Bumps are useful to learn...and some people including you have helped us learn quite a lot!!
shufb take a look at tuxuser message here. It helped me so I guess it might do the trick for you too.

Hello!

Maybe someone can help me please?

I'm trying tto follo Gr3yh0und's tutorial (http://morschi.com/2012/10/05/seagate-goflex-net-debian/) but I got stuck at the recursive problem where the install to flash script claims my UBoot being to old, while UBoot- Update keeps saying it was up to doate. I wanted to try the NSA320 workaround, but I don't really now how to use the files in that tar. So i just used dd for copying the included image file to my bootable partition on the USB drive.
After that myGoFlex Net showed a flashign green LED as if it was working, but when the LED stops flashing i just can't connect to the device using ssh.

Also this solution seems so old.

Is there any way to get this working?

Thank You!

Get the latest rootfs from here:
http://forum.doozan.com/read.php?2,12096

Put this on USB stick, boot with it and let us know the status.

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