Debian on GoFlex Home
Posted by fly
|
fly
Re: Debian on GoFlex Home June 13, 2012 09:20AM |
Here we go:
serverip is the IP of my Desktop-Linux-machine, ipaddr is the IP of the GF's booted rescue-system. Triple checked that
ethact=egiga0 bootdelay=3 baudrate=115200 mainlineLinux=yes console=ttyS0,115200 led_init=green blinking led_exit=green off led_error=orange blinking mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data) mtdids=nand0=orion_nand partition=nand0,2 stdin=serial stdout=serial stderr=serial rescue_installed=0 rescue_set_bootargs=setenv bootargs console=$console ubi.mtd=2 root=ubi0:rootfs ro rootfstype=ubifs $mtdparts $rescue_custom_params rescue_bootcmd=if test $rescue_installed -eq 1; then run rescue_set_bootargs; nand read.e 0x800000 0x100000 0x400000; bootm 0x800000; else run pogo_bootcmd; fi pogo_bootcmd=if fsload uboot-original-mtd0.kwb; then go 0x800200; fi force_rescue=0 force_rescue_bootcmd=if test $force_rescue -eq 1 || ext2load usb 0:1 0x1700000 /rescueme 1 || fatload usb 0:1 0x1700000 /rescueme.txt 1; then run rescue_bootcmd; fi ubifs_mtd=3 ubifs_set_bootargs=setenv bootargs console=$console ubi.mtd=$ubifs_mtd root=ubi0:rootfs rootfstype=ubifs $mtdparts $ubifs_custom_params ubifs_bootcmd=run ubifs_set_bootargs; if ubi part data && ubifsmount rootfs && ubifsload 0x800000 /boot/uImage && ubifsload 0x1100000 /boot/uInitrd; then bootm 0x800000 0x1100000; fi usb_scan=usb_scan_done=0;for scan in $usb_scan_list; do run usb_scan_$scan; if test $usb_scan_done -eq 0 && ext2load usb $usb 0x800000 /boot/uImage 1; then usb_scan_done=1; echo "Found bootable drive on usb $usb"; setenv usb_device $usb; setenv usb_root /dev/$dev; fi; done usb_scan_list=1 2 3 4 usb_scan_1=usb=0:1 dev=sda1 usb_scan_2=usb=1:1 dev=sdb1 usb_scan_3=usb=2:1 dev=sdc1 usb_scan_4=usb=3:1 dev=sdd1 usb_init=run usb_scan usb_device=0:1 usb_root=/dev/sda1 usb_rootfstype=ext2 usb_rootdelay=10 usb_set_bootargs=setenv bootargs console=$console root=$usb_root rootdelay=$usb_rootdelay rootfstype=$usb_rootfstype $mtdparts $usb_custom_params usb_bootcmd=run usb_init; run usb_set_bootargs; run usb_boot usb_boot=mw 0x800000 0 1; ext2load usb $usb_device 0x800000 /boot/uImage; if ext2load usb $usb_device 0x1100000 /boot/uInitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi bootcmd=usb start; run force_rescue_bootcmd; run ubifs_bootcmd; run usb_bootcmd; usb stop; run rescue_bootcmd; run pogo_bootcmd; reset arcNumber=3089 serverip=192.168.178.24 ethaddr=00:10:75:29:0B:98 ipaddr=192.168.178.39 if_netconsole=ping $serverip start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version; preboot=run if_netconsole start_netconsole
serverip is the IP of my Desktop-Linux-machine, ipaddr is the IP of the GF's booted rescue-system. Triple checked that
|
Re: Debian on GoFlex Home June 13, 2012 05:27PM |
Registered: 13 years ago Posts: 78 |
fly Wrote:
-------------------------------------------------------
> I use a Linux machine (Ubuntu 11.04), and when I
> do nc -l -u -p 6666, i get:
>
> look if it works...)
Yes it is a hint. I use netcat-openbsd and the correct arguments to get it to work is "--klu 6666". So try:
nc -klu 6666
And make sure that your are rapidly, repeatably hitting the enter key when you see the boot count down.
-------------------------------------------------------
> I use a Linux machine (Ubuntu 11.04), and when I
> do nc -l -u -p 6666, i get:
>
> This is nc from the netcat-openbsd package. An > alternative nc is available > in the netcat-traditional package. > usage: nc [-46DdhklnrStUuvzC] [-i interval] [-P > proxy_username] [-p source_port] > [-s source_ip_address] [-T ToS] [-w timeout] > [-X proxy_protocol] > [-x proxy_address[:port]] [hostname] [port[s]] >> Maybe this is a hint? (Don't know how it should
> look if it works...)
Yes it is a hint. I use netcat-openbsd and the correct arguments to get it to work is "--klu 6666". So try:
nc -klu 6666
And make sure that your are rapidly, repeatably hitting the enter key when you see the boot count down.
|
fly
Re: Debian on GoFlex Home June 13, 2012 05:48PM |
I got it. Worked either via nc -klu 6666 (or -lu, without k), or with SvOlli's little GTK tool (http://forum.doozan.com/read.php?3,14,2511#msg-2511).
I'm sorry, I believe it didn't work first because there was some socat-job running in the background.
I now get this output:
And in the countdown at the beginning, I can stop autoboot.
I think we can now continue with davygravy's instructions? xD
I'm sorry, I believe it didn't work first because there was some socat-job running in the background.
I now get this output:
U-Boot 2011.12 (Apr 18 2012 - 23:08:20)
Seagate GoFlexNet
arm-none-linux-gnueabi-gcc (Sourcery G++ Lite 2009q3-67) 4.4.1
GNU ld (Sourcery G++ Lite 2009q3-67) 2.19.51.20090709
Hit any key to stop autoboot: 0
(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
Loading file "/rescueme" from usb device 0:1 (usbda1)
** File not found /rescueme
reading /rescueme.txt
** Unable to read "/rescueme.txt" from usb 0:1 **
Creating 1 MTD partitions on "nand0":
0x000002500000-0x000010000000 : "mtd=3"
UBI: attaching mtd1 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 error: validate_ec_hdr: bad VID header offset 2048, expected 512
UBI error: validate_ec_hdr: bad EC header
UBI error: ubi_io_read_ec_hdr: validation failed for PEB 0
UBI error: ubi_init: cannot attach mtd1
UBI error: ubi_init: UBI error: cannot initialize UBI, error -22
UBI init error 22
Loading file "/boot/uImage" from usb device 0:1 (usbda1)
1 bytes read
Found bootable drive on usb 0:1
Loading file "/boot/uImage" from usb device 0:1 (usbda1)
3627880 bytes read
Loading file "/boot/uInitrd" from usb device 0:1 (usbda1)
** File not found /boot/uInitrd
## Booting kernel from Legacy Image at 00800000 ...
Image Name: Linux-3.3.2-kirkwide
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 3627816 Bytes = 3.5 MiB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK
Starting kernel ...
And in the countdown at the beginning, I can stop autoboot.
I think we can now continue with davygravy's instructions? xD
Quote
davygravy
> Ok, so what now? How can I fix the (supposedly)
> broken uBoot, and make the GFH boot from USB flash
> drive?
You'll need to make sure (A) your U-Boot is the correct (updated version) and (B) its env variables are set correctly.
|
Re: Debian on GoFlex Home June 13, 2012 07:35PM |
Registered: 12 years ago Posts: 501 |
Yeppers, that all looks fine. Now you can see what is going on at boot-time, and also control/influence it.
It is my guess that your Debian image (from when you first installed, and it sounds like it failed) is not viable. I'm looking to see if I have a Debian tarball ... I think it is here: http://ppl.ug/CbFkPNovNkI/ this is actually the support tarball for the Zyxel NSA320, which contains a bunch of stuff (uboot, directions/hints, rootfs tarball)... don't use the uboot, just the rootfs tarball... see the directions on how to copy it onto a flash drive... it should boot straight away..., and it is standard debian (except for the kernel, which supports the GoFlex Net/Home).
=====================================================
It is my guess that your Debian image (from when you first installed, and it sounds like it failed) is not viable. I'm looking to see if I have a Debian tarball ... I think it is here: http://ppl.ug/CbFkPNovNkI/ this is actually the support tarball for the Zyxel NSA320, which contains a bunch of stuff (uboot, directions/hints, rootfs tarball)... don't use the uboot, just the rootfs tarball... see the directions on how to copy it onto a flash drive... it should boot straight away..., and it is standard debian (except for the kernel, which supports the GoFlex Net/Home).
=====================================================
- davy's Github Repo's rescue-dg
|
fly
Re: Debian on GoFlex Home June 14, 2012 04:35PM |
YEAH! Your debian really booted nice. Seems to work so far, I could even mount the SATA drive.
But I won't get, why this debian booted, and not my backup-image, which I made from my Dockstar-usbdrive-debian? o_O There, it was always working, but it did work on the GF for the first three times...
-> Hmm, ok, maybe it was because I changed the ArcNumber of the GF from *dockstar* to *goflex*...
So, I have nothing to do concerning the uBoot? Or on the serial-observed boot? I mean, the PlugOS alone still doesn't boot anymore (only orange LED flashing forever and ever), don't know if this is bad, at least rescue-os and debian are both booting from USB.
And I what about "Setup rootfs label to ensure booting from correct USB or HDD drive"? I'm afraid to try this only on trial-and-error, thats to say just to boot with usb-debian AND SATA-data-drive connected; don't want to break anything...
But I won't get, why this debian booted, and not my backup-image, which I made from my Dockstar-usbdrive-debian? o_O There, it was always working, but it did work on the GF for the first three times...
-> Hmm, ok, maybe it was because I changed the ArcNumber of the GF from *dockstar* to *goflex*...
So, I have nothing to do concerning the uBoot? Or on the serial-observed boot? I mean, the PlugOS alone still doesn't boot anymore (only orange LED flashing forever and ever), don't know if this is bad, at least rescue-os and debian are both booting from USB.
And I what about "Setup rootfs label to ensure booting from correct USB or HDD drive"? I'm afraid to try this only on trial-and-error, thats to say just to boot with usb-debian AND SATA-data-drive connected; don't want to break anything...
|
Re: Debian on GoFlex Home June 14, 2012 06:00PM |
Registered: 12 years ago Posts: 501 |
fly Wrote:
-------------------------------------------------------
> YEAH! Your debian really booted nice. Seems to
> work so far, I could even mount the SATA drive.
Great to hear...
> But I won't get, why this debian booted, and not
> my backup-image, which I made from my
> Dockstar-usbdrive-debian?
That might have something to do with how you made a backup of it...
>There, it was always
> working, but it did work on the GF for the first
> three times...
> -> Hmm, ok, maybe it was because I changed the
> ArcNumber of the GF from *dockstar* to
> *goflex*...
>
> So, I have nothing to do concerning the uBoot? Or
> on the serial-observed boot? I mean, the PlugOS
> alone still doesn't boot anymore (only orange LED
> flashing forever and ever), don't know if this is
> bad, at least rescue-os and debian are both
> booting from USB.
As far as I know, It won't boot the PlugOS for anyone... mine doesn't either, though TBH, I have no need for it.
> And I what about "Setup rootfs label to ensure
> booting from correct USB or HDD drive"? I'm afraid
> to try this only on trial-and-error, thats to say
> just to boot with usb-debian AND SATA-data-drive
> connected; don't want to break anything...
There are some writeup on how to do this. I'm thinking that Vlad wrote it up, but I can't remember for sure.
=====================================================
-------------------------------------------------------
> YEAH! Your debian really booted nice. Seems to
> work so far, I could even mount the SATA drive.
Great to hear...
> But I won't get, why this debian booted, and not
> my backup-image, which I made from my
> Dockstar-usbdrive-debian?
That might have something to do with how you made a backup of it...
>There, it was always
> working, but it did work on the GF for the first
> three times...
> -> Hmm, ok, maybe it was because I changed the
> ArcNumber of the GF from *dockstar* to
> *goflex*...
>
> So, I have nothing to do concerning the uBoot? Or
> on the serial-observed boot? I mean, the PlugOS
> alone still doesn't boot anymore (only orange LED
> flashing forever and ever), don't know if this is
> bad, at least rescue-os and debian are both
> booting from USB.
As far as I know, It won't boot the PlugOS for anyone... mine doesn't either, though TBH, I have no need for it.
> And I what about "Setup rootfs label to ensure
> booting from correct USB or HDD drive"? I'm afraid
> to try this only on trial-and-error, thats to say
> just to boot with usb-debian AND SATA-data-drive
> connected; don't want to break anything...
There are some writeup on how to do this. I'm thinking that Vlad wrote it up, but I can't remember for sure.
=====================================================
- davy's Github Repo's rescue-dg
|
Re: Debian on GoFlex Home June 14, 2012 11:24PM |
Admin Registered: 13 years ago Posts: 18,542 |
fly Wrote:
-------------------------------------------------------
> And I what about "Setup rootfs label to ensure
> booting from correct USB or HDD drive"? I'm afraid
> to try this only on trial-and-error, thats to say
> just to boot with usb-debian AND SATA-data-drive
> connected; don't want to break anything...
Here you go, tried and true method:
http://forum.doozan.com/read.php?3,8044,8152#msg-8152
But as always, turn on netconsole first so you can revert any typing mistake :-)
-------------------------------------------------------
> And I what about "Setup rootfs label to ensure
> booting from correct USB or HDD drive"? I'm afraid
> to try this only on trial-and-error, thats to say
> just to boot with usb-debian AND SATA-data-drive
> connected; don't want to break anything...
Here you go, tried and true method:
http://forum.doozan.com/read.php?3,8044,8152#msg-8152
But as always, turn on netconsole first so you can revert any typing mistake :-)
|
fly
Re: Debian on GoFlex Home June 16, 2012 10:05AM |
I backuped my Dockstar-debianusbstick as full systembackup via dd...
I think it just doesn't work anymore because of the arcnumber.
Ok, if PlugOS isn't needed, fine :)
---
and not # fw_setenv usb_init "usb start; setenv usb_root LABEL=rootfs", right?
And about typing mistakes; I'm not sure what I should watch for on the netconsole, if I do the above rootfs-hack, and what I can do with nc->ctrl+J input-prompt (don't understand the commands shown by "help")
---
By the way, this is the nc-output, if I boot from the debian-usbdrive:
---
And, another question: Is it dangerous, if I turn down the GF just by pushing the power-button in the back (when it's still running)?
And can I protect it anyhow of short power-blackouts? (Because I think this crashed my Dockstar..)
I think it just doesn't work anymore because of the arcnumber.
Ok, if PlugOS isn't needed, fine :)
---
root@debian-kirkwood-wide:~# fw_printenv usb_init usb_init=run usb_scan-> so I have to do # fw_setenv usb_init "run usb_scan; setenv usb_root LABEL=rootfs"
and not # fw_setenv usb_init "usb start; setenv usb_root LABEL=rootfs", right?
And about typing mistakes; I'm not sure what I should watch for on the netconsole, if I do the above rootfs-hack, and what I can do with nc->ctrl+J input-prompt (don't understand the commands shown by "help")
---
By the way, this is the nc-output, if I boot from the debian-usbdrive:
U-Boot 2011.12 (Apr 18 2012 - 23:08:20)
Seagate GoFlexNet
arm-none-linux-gnueabi-gcc (Sourcery G++ Lite 2009q3-67) 4.4.1
GNU ld (Sourcery G++ Lite 2009q3-67) 2.19.51.20090709
Hit any key to stop autoboot: 0
(Re)start USB...
USB: Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices...
USB device not accepting new address (error=22)
2 USB Device(s) found
scanning bus for storage devices... 0 Storage Device(s) found
** Block device usb 0 not supported
** Invalid boot device **
Creating 1 MTD partitions on "nand0":
0x000002500000-0x000010000000 : "mtd=3"
UBI: attaching mtd1 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 error: validate_ec_hdr: bad VID header offset 2048, expected 512
UBI error: validate_ec_hdr: bad EC header
UBI error: ubi_io_read_ec_hdr: validation failed for PEB 0
UBI error: ubi_init: cannot attach mtd1
UBI error: ubi_init: UBI error: cannot initialize UBI, error -22
UBI init error 22
** Block device usb 0 not supported
** Block device usb 1 not supported
** Block device usb 2 not supported
** Block device usb 3 not supported
** Block device usb 0 not supported
** Block device usb 0 not supported
Wrong Image Format for bootm command
ERROR: can't get kernel image!
stopping USB..
### JFFS2 loading 'uboot-original-mtd0.kwb' to 0x800000
Scanning JFFS2 FS: read_nand_cached: error reading nand off 0xb5e600 size 8192 bytes
read_nand_cached: error reading nand off 0xb5e200 size 8192 bytes
read_nand_cached: error reading nand off 0xb60200 size 8192 bytes
read_nand_cached: error reading nand off 0xb62200 size 8192 bytes
read_nand_cached: error reading nand off 0xb64200 size 8192 bytes
read_nand_cached: error reading nand off 0xb66200 size 8192 bytes
read_nand_cached: error reading nand off 0xb68200 size 8192 bytes
read_nand_cached: error reading nand off 0xb6a200 size 8192 bytes
read_nand_cached: error reading nand off 0xb6c200 size 8192 bytes
read_nand_cached: error reading nand off 0xb6e200 size 8192 bytes
read_nand_cached: error reading nand off 0xb70200 size 8192 bytes
read_nand_cached: error reading nand off 0xb72200 size 8192 bytes
read_nand_cached: error reading nand off 0xb74200 size 8192 bytes
read_nand_cached: error reading nand off 0xb76200 size 8192 bytes
read_nand_cached: error reading nand off 0xb78200 size 8192 bytes
read_nand_cached: error reading nand off 0xb7a200 size 8192 bytes
read_nand_cached: error reading nand off 0xb7c200 size 8192 bytes
read_nand_cached: error reading nand off 0xb7e200 size 8192 bytes
read_nand_cached: error reading nand off 0xb9ee00 size 8192 bytes
read_nand_cached: error reading nand off 0xb9e400 size 8192 bytes
read_nand_cached: error reading nand off 0xba0400 size 8192 bytes
read_nand_cached: error reading nand off 0xba2400 size 8192 bytes
read_nand_cached: error reading nand off 0xba4400 size 8192 bytes
read_nand_cached: error reading nand off 0xba6400 size 8192 bytes
read_nand_cached: error reading nand off 0xba8400 size 8192 bytes
read_nand_cached: error reading nand off 0xbaa400 size 8192 bytes
read_nand_cached: error reading nand off 0xbac400 size 8192 bytes
read_nand_cached: error reading nand off 0xbae400 size 8192 bytes
read_nand_cached: error reading nand off 0xbb0400 size 8192 bytes
read_nand_cached: error reading nand off 0xbb2400 size 8192 bytes
read_nand_cached: error reading nand off 0xbb4400 size 8192 bytes
read_nand_cached: error reading nand off 0xbb6400 size 8192 bytes
read_nand_cached: error reading nand off 0xbb8400 size 8192 bytes
read_nand_cached: error reading nand off 0xbba400 size 8192 bytes
read_nand_cached: error reading nand off 0xbbc400 size 8192 bytes
read_nand_cached: error reading nand off 0xbbe400 size 8192 byte done.
find_inode failed for name=uboot-original-mtd0.kwb
load: Failed to find inode
### JFFS2 LOAD ERROR<0> for uboot-original-mtd0.kwb!
### JFFS2 loading 'uboot-original-mtd0.kwb' to 0x800000
Scanning JFFS2 FS: read_nand_cached: error reading nand off 0xb5e600 size 8192 bytes
read_nand_cached: error reading nand off 0xb5e200 size 8192 bytes
read_nand_cached: error reading nand off 0xb60200 size 8192 bytes
read_nand_cached: error reading nand off 0xb62200 size 8192 bytes
read_nand_cached: error reading nand off 0xb64200 size 8192 bytes
read_nand_cached: error reading nand off 0xb66200 size 8192 bytes
read_nand_cached: error reading nand off 0xb68200 size 8192 bytes
read_nand_cached: error reading nand off 0xb6a200 size 8192 bytes
read_nand_cached: error reading nand off 0xb6c200 size 8192 bytes
read_nand_cached: error reading nand off 0xb6e200 size 8192 bytes
read_nand_cached: error reading nand off 0xb70200 size 8192 bytes
read_nand_cached: error reading nand off 0xb72200 size 8192 bytes
read_nand_cached: error reading nand off 0xb74200 size 8192 bytes
read_nand_cached: error reading nand off 0xb76200 size 8192 bytes
read_nand_cached: error reading nand off 0xb78200 size 8192 bytes
read_nand_cached: error reading nand off 0xb7a200 size 8192 bytes
read_nand_cached: error reading nand off 0xb7c200 size 8192 bytes
read_nand_cached: error reading nand off 0xb7e200 size 8192 bytes
read_nand_cached: error reading nand off 0xb9ee00 size 8192 bytes
read_nand_cached: error reading nand off 0xb9e400 size 8192 bytes
read_nand_cached: error reading nand off 0xba0400 size 8192 bytes
read_nand_cached: error reading nand off 0xba2400 size 8192 bytes
read_nand_cached: error reading nand off 0xba4400 size 8192 bytes
read_nand_cached: error reading nand off 0xba6400 size 8192 bytes
read_nand_cached: error reading nand off 0xba8400 size 8192 bytes
read_nand_cached: error reading nand off 0xbaa400 size 8192 bytes
read_nand_cached: error reading nand off 0xbac400 size 8192 bytes
read_nand_cached: error reading nand off 0xbae400 size 8192 bytes
read_nand_cached: error reading nand off 0xbb0400 size 8192 bytes
read_nand_cached: error reading nand off 0xbb2400 size 8192 bytes
read_nand_cached: error reading nand off 0xbb4400 size 8192 bytes
read_nand_cached: error reading nand off 0xbb6400 size 8192 bytes
read_nand_cached: error reading nand off 0xbb8400 size 8192 bytes
read_nand_cached: error reading nand off 0xbba400 size 8192 bytes
read_nand_cached: error reading nand off 0xbbc400 size 8192 bytes
read_nand_cached: error reading nand off 0xbbe400 size 8192 byte done.
find_inode failed for name=uboot-original-mtd0.kwb
load: Failed to find inode
### JFFS2 LOAD ERROR<0> for uboot-original-mtd0.kwb!
resetting ...
U-Boot 2011.12 (Apr 18 2012 - 23:08:20)
Seagate GoFlexNet
arm-none-linux-gnueabi-gcc (Sourcery G++ Lite 2009q3-67) 4.4.1
GNU ld (Sourcery G++ Lite 2009q3-67) 2.19.51.20090709
Hit any key to stop autoboot: 0
(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
Loading file "/rescueme" from usb device 0:1 (usbda1)
** File not found /rescueme
reading /rescueme.txt
** Unable to read "/rescueme.txt" from usb 0:1 **
Creating 1 MTD partitions on "nand0":
0x000002500000-0x000010000000 : "mtd=3"
UBI: attaching mtd1 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 error: validate_ec_hdr: bad VID header offset 2048, expected 512
UBI error: validate_ec_hdr: bad EC header
UBI error: ubi_io_read_ec_hdr: validation failed for PEB 0
UBI error: ubi_init: cannot attach mtd1
UBI error: ubi_init: UBI error: cannot initialize UBI, error -22
UBI init error 22
Loading file "/boot/uImage" from usb device 0:1 (usbda1)
1 bytes read
Found bootable drive on usb 0:1
Loading file "/boot/uImage" from usb device 0:1 (usbda1)
2279256 bytes read
Loading file "/boot/uInitrd" from usb device 0:1 (usbda1)
7004538 bytes read
## Booting kernel from Legacy Image at 00800000 ...
Image Name: Linux-3.3.2
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2279192 Bytes = 2.2 MiB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
Image Name: initramfs-3.3.2-kirkwood-dg
Image Type: ARM Linux RAMDisk Image (gzip compressed)
Data Size: 7004474 Bytes = 6.7 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK
Starting kernel ...
It boots nice after all that, but I'm just curious: Does that mean it tries to boot from nand-sector mtd0? Is that the broken PlugOS there or what?
---
And, another question: Is it dangerous, if I turn down the GF just by pushing the power-button in the back (when it's still running)?
And can I protect it anyhow of short power-blackouts? (Because I think this crashed my Dockstar..)
|
Re: Debian on GoFlex Home June 16, 2012 03:08PM |
Admin Registered: 13 years ago Posts: 18,542 |
fly Wrote:
-------------------------------------------------------
> root@debian-kirkwood-wide:~# fw_printenv usb_init
> usb_init=run usb_scan
>
> -> so I have to do # fw_setenv usb_init "run
> usb_scan; setenv usb_root LABEL=rootfs"
> and not # fw_setenv usb_init "usb start; setenv
> usb_root LABEL=rootfs", right?
Right, that should do it.
> It boots nice after all that, but I'm just
> curious: Does that mean it tries to boot from
> nand-sector mtd0? Is that the broken PlugOS there
> or what?
>
Davy should answer this.
>
> And, another question: Is it dangerous, if I turn
> down the GF just by pushing the power-button in
> the back (when it's still running)?
> And can I protect it anyhow of short
> power-blackouts? (Because I think this crashed my
> Dockstar..)
It will corrupt the file systems. Likewise in power outage. If you're using Ext2, then most likely you will have problem booting again, so you will need to take the USB stick to another Linux box and run e2fsck to fix the errors. If you're using Ext3, then when the file system error recovery will kick in and booting will be a little longer but eventualy it will boot. I boot most my boxes from a USB stick (so that I can swap HDD or remove them), and Ext3 will wear out the flash drive significantly comapring to Ext2, so I use Ext2. And to minimize the power outage problem, I move all the log files to /tmp, and use Ext3 for the HDDs.
If your boot drive is HDD, then use Ext3. It will be great, no worry about power outage. But you also need to set the UBoot env for rootfstype to ext3:
# fw_setenv usb_rootfstype ext3
-------------------------------------------------------
> root@debian-kirkwood-wide:~# fw_printenv usb_init
> usb_init=run usb_scan
>
> -> so I have to do # fw_setenv usb_init "run
> usb_scan; setenv usb_root LABEL=rootfs"
> and not # fw_setenv usb_init "usb start; setenv
> usb_root LABEL=rootfs", right?
Right, that should do it.
> It boots nice after all that, but I'm just
> curious: Does that mean it tries to boot from
> nand-sector mtd0? Is that the broken PlugOS there
> or what?
>
Davy should answer this.
>
> And, another question: Is it dangerous, if I turn
> down the GF just by pushing the power-button in
> the back (when it's still running)?
> And can I protect it anyhow of short
> power-blackouts? (Because I think this crashed my
> Dockstar..)
It will corrupt the file systems. Likewise in power outage. If you're using Ext2, then most likely you will have problem booting again, so you will need to take the USB stick to another Linux box and run e2fsck to fix the errors. If you're using Ext3, then when the file system error recovery will kick in and booting will be a little longer but eventualy it will boot. I boot most my boxes from a USB stick (so that I can swap HDD or remove them), and Ext3 will wear out the flash drive significantly comapring to Ext2, so I use Ext2. And to minimize the power outage problem, I move all the log files to /tmp, and use Ext3 for the HDDs.
If your boot drive is HDD, then use Ext3. It will be great, no worry about power outage. But you also need to set the UBoot env for rootfstype to ext3:
# fw_setenv usb_rootfstype ext3
|
fly
Re: Debian on GoFlex Home June 17, 2012 03:09PM |
Okay, after rootfs-hack, it boots correct with usbdrive and satadrive connected.
---
bodhi Wrote:
> It will corrupt the file systems. Likewise in
> power outage. If you're using Ext2, then most
> likely you will have problem booting again, so you
> will need to take the USB stick to another Linux
> box and run e2fsck to fix the errors. If you're
> using Ext3, then when the file system error
> recovery will kick in and booting will be a little
> longer but eventualy it will boot. I boot most my
> boxes from a USB stick (so that I can swap HDD or
> remove them), and Ext3 will wear out the flash
> drive significantly comapring to Ext2, so I use
> Ext2. And to minimize the power outage problem, I
> move all the log files to /tmp, and use Ext3 for
> the HDDs.
>
> If your boot drive is HDD, then use Ext3. It will
> be great, no worry about power outage. But you
> also need to set the UBoot env for rootfstype to
> ext3:
> # fw_setenv usb_rootfstype ext3
No, I boot from a USB thumb-drive, and use the sata-drive as a file-drive. Thumbdrive is formatted as ext2, and satadrive also; I heard that it's faster than ext3.
---
Fyi, nc shows now during boot into debian (even though it boots up correct):
---
bodhi Wrote:
> It will corrupt the file systems. Likewise in
> power outage. If you're using Ext2, then most
> likely you will have problem booting again, so you
> will need to take the USB stick to another Linux
> box and run e2fsck to fix the errors. If you're
> using Ext3, then when the file system error
> recovery will kick in and booting will be a little
> longer but eventualy it will boot. I boot most my
> boxes from a USB stick (so that I can swap HDD or
> remove them), and Ext3 will wear out the flash
> drive significantly comapring to Ext2, so I use
> Ext2. And to minimize the power outage problem, I
> move all the log files to /tmp, and use Ext3 for
> the HDDs.
>
> If your boot drive is HDD, then use Ext3. It will
> be great, no worry about power outage. But you
> also need to set the UBoot env for rootfstype to
> ext3:
> # fw_setenv usb_rootfstype ext3
No, I boot from a USB thumb-drive, and use the sata-drive as a file-drive. Thumbdrive is formatted as ext2, and satadrive also; I heard that it's faster than ext3.
---
Fyi, nc shows now during boot into debian (even though it boots up correct):
U-Boot 2011.12 (Apr 18 2012 - 23:08:20)
Seagate GoFlexNet
arm-none-linux-gnueabi-gcc (Sourcery G++ Lite 2009q3-67) 4.4.1
GNU ld (Sourcery G++ Lite 2009q3-67) 2.19.51.20090709
Hit any key to stop autoboot: 0
(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
Loading file "/rescueme" from usb device 0:1 (usbda1)
** File not found /rescueme
reading /rescueme.txt
** Unable to read "/rescueme.txt" from usb 0:1 **
Creating 1 MTD partitions on "nand0":
0x000002500000-0x000010000000 : "mtd=3"
UBI: attaching mtd1 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 error: validate_ec_hdr: bad VID header offset 2048, expected 512
UBI error: validate_ec_hdr: bad EC header
UBI error: ubi_io_read_ec_hdr: validation failed for PEB 0
UBI error: ubi_init: cannot attach mtd1
UBI error: ubi_init: UBI error: cannot initialize UBI, error -22
UBI init error 22
Loading file "/boot/uImage" from usb device 0:1 (usbda1)
1 bytes read
Found bootable drive on usb 0:1
Loading file "/boot/uImage" from usb device 0:1 (usbda1)
2279256 bytes read
Loading file "/boot/uInitrd" from usb device 0:1 (usbda1)
7004538 bytes read
## Booting kernel from Legacy Image at 00800000 ...
Image Name: Linux-3.3.2
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2279192 Bytes = 2.2 MiB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
Image Name: initramfs-3.3.2-kirkwood-dg
Image Type: ARM Linux RAMDisk Image (gzip compressed)
Data Size: 7004474 Bytes = 6.7 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK
Starting kernel ...
No idea what that means xD
|
Re: Debian on GoFlex Home June 17, 2012 04:14PM |
Registered: 12 years ago Posts: 501 |
I think that for large file operations, ext2 may be faster than ext3, since ext2 doesn't have to worry about journaling... but that is only consequential for large file stuff. Ext2 has the unfortunate lack of journaling, so if there is a bump to the head (ie. power outage, problem), getting stuff back up and running takes much more time.
=====================================================
=====================================================
- davy's Github Repo's rescue-dg
|
Re: Debian on GoFlex Home June 18, 2012 12:20AM |
Admin Registered: 13 years ago Posts: 18,542 |
Agree with Davy, for sure large files Ext2 will be faster. However, for HDD I think it's really not that much of a factor anyway. IMO the benefit of avoiding corruption during power outage would outweight the speed increase, if one lives in area that power outage occurs from time to time. I recalled Varkey said he has his boot drive format as Ext3, and never had problem (and he has frequent power outage where he lives).
|
fly
Re: Debian on GoFlex Home June 18, 2012 04:08PM |
So the speed increase is not much. Okay, then I think I'd prefere reliability, and format the data-drive as ext3. Even though I use it mostly for big files (online-videorecorder movies and series).
Has anyone of you a solution about using one of the LEDs as networktraffic-indicator? I only find this for Arch Linux versions, but not for debian...
Anyway, I want to thank you guys really really much for patiently helping me to get this whole stuff going, your're awesome! : D
Has anyone of you a solution about using one of the LEDs as networktraffic-indicator? I only find this for Arch Linux versions, but not for debian...
Anyway, I want to thank you guys really really much for patiently helping me to get this whole stuff going, your're awesome! : D
|
Re: Debian on GoFlex Home June 18, 2012 05:40PM |
Admin Registered: 13 years ago Posts: 18,542 |
|
fly
Re: Debian on GoFlex Home June 18, 2012 06:57PM |
Ok, so this is the Arch version:
And pretty much the same for debian: http://forum.doozan.com/read.php?2,4638,4645
But I don't know half of those commands, and it's mixed with firewall stuff; I think I don't need any of the above iptables settings changed so far...Besides, I do everything about firewall directly in the router.
I'm not sure if I got that right: With that, the LED will flash according to the downstream? So, as an example, if there's a 0.5 MB/s dl, it flashes 60 HZ, and fullspeed 1.2 MB/s, it flashes 120 Hz? Pretty sure I read somewhere else that that's possible
Or does it just flash if traffic, and not flash if not?
#Set up orange LED to blink on incoming TCP traffic iptables -A INPUT -p tcp -j LED --led-trigger-id tcpin --led-delay 100 echo netfilter-tcpin > /sys/class/leds/dockstar\:orange\:misc/trigger(source)
And pretty much the same for debian: http://forum.doozan.com/read.php?2,4638,4645
But I don't know half of those commands, and it's mixed with firewall stuff; I think I don't need any of the above iptables settings changed so far...Besides, I do everything about firewall directly in the router.
I'm not sure if I got that right: With that, the LED will flash according to the downstream? So, as an example, if there's a 0.5 MB/s dl, it flashes 60 HZ, and fullspeed 1.2 MB/s, it flashes 120 Hz? Pretty sure I read somewhere else that that's possible
Or does it just flash if traffic, and not flash if not?
|
Re: Debian on GoFlex Home June 19, 2012 10:18PM |
Admin Registered: 13 years ago Posts: 18,542 |
Sorry, I've searched for Debian-equivalent packages for netfilter-tcpin, but no success. Package iptables is available in Debian wheezy. TBH, I don't understand the real meaning of the echo command, either :-) Will take a look at the debian thread to see if it'd shed any light.
Anybody who is more familiar with iptables/netfilter, please post!
Anybody who is more familiar with iptables/netfilter, please post!
|
maihoaomv
Re: Debian on GoFlex Home July 04, 2012 02:56PM |
|
Re: Debian on GoFlex Home August 25, 2012 12:09PM |
Registered: 12 years ago Posts: 501 |
fly Wrote:
-------------------------------------------------------
> Ok, so this is the Arch version:
>
> =18&t=289](source)[/url]
>
> And pretty much the same for debian:
> [url]http://forum.doozan.com/read.php?2,4638,4645[/url]
>
> But I don't know half of those commands, and it's
> mixed with firewall stuff; I think I don't need
> any of the above iptables settings changed so
> far...Besides, I do everything about firewall
> directly in the router.
>
> I'm not sure if I got that right: With that, the
> LED will flash according to the downstream? So, as
> an example, if there's a 0.5 MB/s dl, it flashes
> 60 HZ, and fullspeed 1.2 MB/s, it flashes 120 Hz?
> Pretty sure I read somewhere else that that's
> possible
> Or does it just flash if traffic, and not flash if
> not?
One caveat is to make sure that you have a later version of iptables. In v1.4.8 this is not supported...
[code]
root@AirDisk2:/etc# iptables -A INPUT -p tcp -j LED --led-trigger-id tcpin --led-delay 100
iptables v1.4.8: unknown option `--led-trigger-id'
Try `iptables -h' or 'iptables --help' for more information.
[/code]
I installed v1.4.14 from here:
[url]http://cdn.debian.net/debian/pool/main/i/iptables/[/url]
and it works fine now again.
=====================================================
[list]
[*][url=https://github.com/davygravy/]davy's Github Repo's [/url]rescue-dg
[/list]
-------------------------------------------------------
> Ok, so this is the Arch version:
>
> #Set up orange LED to blink on incoming TCP > traffic > iptables -A INPUT -p tcp -j LED --led-trigger-id > tcpin --led-delay 100 > echo netfilter-tcpin > > /sys/class/leds/dockstar\:orange\:misc/trigger >> [url=http://archlinuxarm.org/forum/viewtopic.php?f
> =18&t=289](source)[/url]
>
> And pretty much the same for debian:
> [url]http://forum.doozan.com/read.php?2,4638,4645[/url]
>
> But I don't know half of those commands, and it's
> mixed with firewall stuff; I think I don't need
> any of the above iptables settings changed so
> far...Besides, I do everything about firewall
> directly in the router.
>
> I'm not sure if I got that right: With that, the
> LED will flash according to the downstream? So, as
> an example, if there's a 0.5 MB/s dl, it flashes
> 60 HZ, and fullspeed 1.2 MB/s, it flashes 120 Hz?
> Pretty sure I read somewhere else that that's
> possible
> Or does it just flash if traffic, and not flash if
> not?
One caveat is to make sure that you have a later version of iptables. In v1.4.8 this is not supported...
[code]
root@AirDisk2:/etc# iptables -A INPUT -p tcp -j LED --led-trigger-id tcpin --led-delay 100
iptables v1.4.8: unknown option `--led-trigger-id'
Try `iptables -h' or 'iptables --help' for more information.
[/code]
I installed v1.4.14 from here:
[url]http://cdn.debian.net/debian/pool/main/i/iptables/[/url]
and it works fine now again.
=====================================================
[list]
[*][url=https://github.com/davygravy/]davy's Github Repo's [/url]rescue-dg
[/list]
