Seagate Dockstar Discussion and Tutorial Thread

Gaurish said:
just remove the echo

PHP: 
#!/bin/bash 

WGET="/usr/bin/wget"

$WGET -q --tries=10 --timeout=5 [url=http://www.google.com]Google[/url] -O /tmp/index.google &> /dev/null 

if [ ! -s /tmp/index.google ];

then 

          pon nokia

else 

          echo "yes" 

fi

Yes, DDNS Client for DynDNS inbuilt into my Router. you can there DynDNS.com - Support -- Update Clients -- Linux / Unix Clients

I normally use inbuilt FTP Ability in OS. I think Windows Explorer too has basic FTP. so you don't really need any client.
Click to expand...
thanks let me remove the echo and try it

i have installed ddclient , generated the config file

but still not able to connect

am troubleshooting it still

regarding the ftp client i wanted to know which ftp server you have on debian

is it proftpd ??

i have samba installed

added my external drive in fstab for autoboot

dockstar is working beautifully as a NAS
 
kuduku said:
thanks let me remove the echo and try it

i have installed ddclient , generated the config file

but still not able to connect

am troubleshooting it still
Click to expand...

Try ddclient -force. if it fails check your log on what went wrong

regarding the ftp client i wanted to know which ftp server you have on debian

is it proftpd ??
Click to expand...

you seems to be confused with FTP client and FTP server:P for FTP server, I use vsftpd because its lightweight and fast
 
dinjo said:
Anyone used it with built in torrent client ? i.e without turning on the pc
Click to expand...
LOL crawl back to the cave you came from! :P

The entire crowd has just been doing that! The dock supports a bt client and can be accessed by the PC.
 
dinjo said:
Anyone used it with built in torrent client ? i.e without turning on the pc
Click to expand...

there is no built in client

I am using transmission with GUI

and others are using rtorrent also

depends on your taste

and please check back all the pages in the thread

they have all your queries answered

--- Updated Post - Automerged ---

@Gaurish thanks got my bash script working

i am still working on ddclient config file

that has not woked out still
 
The problem of not booting into Debian after a power fail is still there. Sometimes repairing the filesystem with e2fsck works but not always.

Anyone found a solution?
 
Don't know whether the UBIFS is corrupted or not.

Can anybody help me to run netconsole / netcat on windows?

--- Updated Post - Automerged ---

I'm running the following command (my dockstar IP is 192.168.2.6)

C:\nc>nc

Cmd line: nc -lup 192.168.2.6 6666
Click to expand...
it just gives me a blinking cursor on the next line and no output even on rebooting the dockstar.

I've configured the Dockstar as

fw_setenv serverip 192.168.2.2

fw_setenv ipaddr 192.168.2.6

fw_setenv if_netconsole 'ping $serverip'

fw_setenv start_netconsole 'setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version;'

fw_setenv preboot 'run if_netconsole start_netconsole'
Click to expand...

Does everything looks O.K?

--- Updated Post - Automerged ---

Firewall is diabled BTW.

--- Updated Post - Automerged ---

O.K guys got it working.

--- Updated Post - Automerged ---

I got the following output from netcat:

U-Boot 2010.06-00695-gbd23130-dirty (Aug 30 2010 - 23:04:56)

Marvell-Dockstar/Pogoplug by Jeff Doozan

Hit any key to stop autoboot: 0

(Re)start USB...

USB: Register 10011 NbrPorts 1

USB EHCI 1.00

scanning bus for devices... 3 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: attached mtd1 to ubi0

UBI: MTD device name: "mtd=3"

UBI: MTD device size: 219 MiB

UBI: number of good PEBs: 1751

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: 1730

UBI: total number of reserved PEBs: 21

UBI: number of PEBs reserved for bad PEB handling: 17

UBI: max/mean erase counter: 1/1

UBIFS error (pid 0): ubifs_get_sb: cannot open "ubi:rootfs", error -19

Error reading superblock on volume 'ubi:rootfs'!

(Re)start USB...

USB: Register 10011 NbrPorts 1

USB EHCI 1.00

scanning bus for devices... 3 USB Device(s) found

scanning bus for storage devices... 0 Storage Device(s) found

** 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..

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

4194304 bytes read: OK

## Booting kernel from Legacy Image at 00800000 ...

Image Name: Linux-2.6.32.18-dockstar

Image Type: ARM Linux Kernel Image (uncompressed)

Data Size: 3175992 Bytes = 3 MiB

Load Address: 00008000

Entry Point: 00008000

Verifying Checksum ... OK

Loading Kernel Image ... OK

OK

Starting kernel ...
Click to expand...

Any help?

--- Updated Post - Automerged ---

Need some help with un-bricking the dockstar. Will buy the CA-42 cable tomorrow. Pls suggest steps to unbrick the dockstar with windows.
 
archat68 said:
The problem of not booting into Debian after a power fail is still there. Sometimes repairing the filesystem with e2fsck works but not always.

Anyone found a solution?
Click to expand...
Had it happen here too.

My solution, I keep a zipped backup of the whole root (280mb) on a separate partition. If it fails AND fsck doesnt fix it, I just delete contents of root partition and restore from backup.
 
Happenning for me too, thought it was fine but happening again.

But fsck always works.

If the filesystem is corrupt it will not boot at all, whereas if it boots the recovery system in case of a filesystem issue, you could have configured it to do an fsck and reboot.
 
varkey said:
Happenning for me too, thought it was fine but happening again.

But fsck always works.

If the filesystem is corrupt it will not boot at all, whereas if it boots the recovery system in case of a filesystem issue, you could have configured it to do an fsck and reboot.
Click to expand...
Nope, had an issue where fsck fixed issues but it still wouldnt boot. Luckily my habit of making backups saved me :)
 
Desecrator said:
LOL crawl back to the cave you came from! :P

The entire crowd has just been doing that! The dock supports a bt client and can be accessed by the PC.
Click to expand...

d\Is it easy enough to setup i'm looking for torrent client nothing else not interested in Wireless stuff if other alternatives
 
but there has to be a better and more fail-proof method for stopping this. hapened to me the first couple of times i tried booting off usb on the tonidoplug. incase of an improper shutdown, like power outage, it would just refuse to boot off the usb hdd and hang in b/w. i had an externally powered usb hdd attached to the plug... then i changed the hdd's power mgmt from auto to manual, realising that if the uboot doesnt engage with the usb hdd in under 8 secs, it fails or hangs to boot. setting power mode to manual ensred the hdd powered up alongside the plug and the handshaking process has been running without an issue since...
 
Hey guys. Need some help tpo unbrick the Dockstar. i got the CA-42 cable - attached it to Dockstar and I can see the Dockstar booting using Putty.

But which guide to follow to restore the bootloader?

Plls help.

--- Updated Post - Automerged ---

When i'm using the serial cable and putty , i'm getting the following output:

U-Boot 2010.06-00695-gbd23130-dirty (Aug 30 2010 - 23:04:56)

Marvell-Dockstar/Pogoplug by Jeff Doozan

SoC: Kirkwood 88F6281_A0

DRAM: 128 MiB

NAND: 256 MiB

In: serial

Out: serial

Err: serial

Net: egiga0

88E1116 Initialized on egiga0

Using egiga0 device

ping failed; host 192.168.2.3 is not alive

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... 0 Storage Device(s) found

** Block device usb 0 not supported

** Block device usb 0 not supported

Wrong Image Format for bootm command

ERROR: can't get kernel image!

resetting ...
Click to expand...

And this runs in a loop.
 
Gaurish said:
Hey, Can you upload that somewhere like dropbox? so we can have a backup?
Click to expand...
Errr...much quicker to just copy your own root directory to another location.

This should work:
1. Go to your root directory >cd /
2. >tar -zclvpf /<backup-drive>/fullbackup.tar.gz --exclude=proc --exclude=sys --exclude=dev/pts .

That should do it :)
 
Download Putty. Connect the serial cable to the computer and verify that the drivers get installed. You get a CD with that. Use it. Go to device manager to verify. Didnt get installed on Win 7 64 bit so I made an XP VM and connected the USB to that. More on that later if you can't install the drivers.

Then check this link out: Seagate Dockstar: Add an accessible serial port « Your Warranty Is Void.com

Buy the cable from eBay. The cable which I got had the wires Black = GND, Blue = Rx and White = Tx. Now follow the instructions from the link above. It's quite simple. The only tough part is the fact that the wires take a lot of time to get wrapped around the tiny pins. :)

Update: Oops just noticed that you have already attached the serial cable.. I think you should install the uBoot again. Better wait for varkey and also post it on Jeff's forum: http://forum.doozan.com/
 
Back
Top