dockstar device recognition/permission ??

[chaskito]

So, I have spent some painful days staring into this screen, trying to understand how to get my dockstar running to its full potential as a server. I have checked numerous archives, and googled all I can.
I am able to format and create partitions on the attached "super talent" 4gb thumb drive located in the side slot of my dockstar, but I am unable to go further from there ie. load Arch Linux ARM OS on the flash drive. I am still learning how to use the terminal, but am an eager study, and I apologize for my insufficient knowledge approaching such a project - but this is the way to learn! Here is what I have going on currently:

after successfully SSH'ing into the dockstar I began following Arch Linux ARM official USB installation.
-bash-3.2# killall hbwd
-bash-3.2# cd /tmp
-bash-3.2# wget http://jeff.doozan.com/debian/goflex/v0.6/uInitrd
Connecting to jeff.doozan.com (69.163.187.226:80)
uInitrd 100% |*******************************| 3911k 00:00:00 ETA
-bash-3.2# wget http://jeff.doozan.com/debian/goflex/v0.6/ubit_start
Connecting to jeff.doozan.com (69.163.187.226:80)
ubit_start 100% |*******************************| 2238 --:--:-- ETA
-bash-3.2# ./ubit_start
17218 blocks
Entering UBIT environment
No valid U-Boot environment exists.
You need to reboot once to let U-Boot set its default environment
before the ethaddr setting can be updated, either directly or
with a cached value.
ubit0-6:/# chain_install dockstar
UBIT.CHAIN:dockstar
UBIT.CHAIN:/usr/share/ubit/original/dockstar.kwb writing to 0x380000 of /dev/mtd1
1+0 records in
1+0 records out
UBIT:bl: /usr/share/ubit/original/dockstar.kwb checksum b2d9681ef044e9ab6b058ef442b30b6e -
Erase Total 4 Units
Performing Flash Erase of length 131072 at offset 0x3e0000 done
Writing data to block 28 at offset 0x380000
Writing data to block 29 at offset 0x3a0000
Writing data to block 30 at offset 0x3c0000
Writing data to block 31 at offset 0x3e0000
1+0 records in
1+0 records out
UBIT:bl: u-boot checksum match OK.

Disk /dev/mtdblock0: 1 MB, 1048576 bytes
255 heads, 63 sectors/track, 0 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/mtdblock0 doesn't contain a valid partition table


-bash-3.2# /dev/sda1
-bash: /dev/sda1: Permission denied

How do I get back to the dockstar's original filesystem "bash" after I have entered into the ubit dockstar environment? It seems I enter in deeper, but backing out and in is still a slightly foggy process. I believe I need to access into the partition I have created in order to install the Arch Linux ARM (or debian) OS. Is this correct thinking?

I hope I am just being really stupid. Thank you for your valuable time and knowledge.

[pepedog]

/dec/sda1 is a "device", not a disk
Look for mount in the instruction, and you can cd to the mount
Type mount on it's own just in case it auto mounted

[peaslaker]

$this->bbcode_second_pass_quote('chaskito', 'H')ow do I get back to the dockstar's original filesystem "bash"

[chaskito]

I hope I am posting in the correct area, as I do not wish to go down the thread I started with different issues. Everything was running smoothly, samba and cherokee were up, and I was really stoked about the whole process. Then I rebooted to save, and verify everything. I received an error about a broken pipe (wish I would have saved that) and now I can no longer ssh into dockstar.

ssh root@my.ip.address
ssh: connect to host "my.ip.address port 22: No route to host
My router shows the i.p. I had assigned, but no longer recognizes it as Arch Linux ARM install, as I had labeled. I checked the Arch Linux ARM filesystem on my laptop (linux distro) and it said it is fine. If I remove the thumbdrive and try to SSH then I receive the big "WARNING:REMOTE HOST IDENTIFICATION HAS CHANGED!" prompt and dockstar will flash orange LED. With thumbdrive in LED flashed green for a few seconds then goes out. Sooooo, what is going on here? One other thing. Once Cherokee started running I noted the date was back in 1969. I received an error that it needed to be after 1980. ??? I set the time correctly using the " date MMDDHHMMYYYY" format.

What steps may I take? I have no problem going through the steps to reinstall the os on the flash drive, but without being able to SSH in I can't tell what is going on.

thanks in advance!

$this->bbcode_second_pass_quote('chaskito', 'I') hope I am posting in the correct area, as I do not wish to go down the thread I started with different issues. Everything was running smoothly, samba and cherokee were up, and I was really stoked about the whole process. Then I rebooted to save, and verify everything. I received an error about a broken pipe (wish I would have saved that) and now I can no longer ssh into dockstar.

ssh root@my.ip.address
ssh: connect to host "my.ip.address port 22: No route to host

[chaskito]

thanks again for your help in this matter - I am learning slowly. I have typed in the commands as instructed in the "Monitoring UBIT boot using netcat" wiki.

:~$ ssh-keygen -R <my i.p.>
/home/user/.ssh/known_hosts updated.
Original contents retained as /home/user/.ssh/known_hosts.old
:~$ ssh root@<my.ip>
ssh: connect to host <my.ip> port 22: No route to host
:~$ sudo ifconfig eth0:0 10.10.10.5
[sudo] password for user:
:~$ sudo ifconfig eth0:1 10.10.10.4
:~$ sudo ifconfig eth0:2 10.10.10.2
:~$ nc -lu 10.10.10.5 6666

...and so on as instructed. There is no response after I type in any of the commands. Is this what is supposed to happen? I thought perhaps I would learn something. Yet, I am sure I am typing something in wrong, such as the 10.10.10.x is just an example, and I need to either connect my dockstar in directly to my computer, or enter in unique ip's to the command line for kernel monitoring, etc. I am stumped at this point. Is it possible I can pull my usb flash drive and configure it through my linux laptop, then plug it back in and let it load? I am unfamiliar with netcat, even after some in depth studying of the literature provided online,detailing its valuable uses.

Thanks!

[peaslaker]

The netcat stuff will only work if the UBIT U-Boot is installed correctly... which it should be.

If there is any doubt, start up without any USB device plugged in which you have reported as starting the original Pogoplug system. Log into the original Pogoplug system (probably chain booted). RUn the commands to access the UBIT prompt again and run 'uboot_identify'... this will tell you what U-Boot you have installed. If it tells you something about a U-Boot in /usr/share/ubit/firmware/dockstar-xxxxxxxxxxxxxx.md5 then the UBIT U-Boot is installed and netcat does work.

netcat only shows results during reboot.

[chaskito]

Thank you very much "peaslaker" I am very grateful for your assistance on this matter - - I was able to get into the uboot environment, but after running the command "uboot_identify" all that I learned was "The existing firmware cannot be identified.." shall I try to update the firmware some other way? When I successfully installed pogo OS, I did not log into the uboot environment to update the mtd0 directory and complete the installation on the usb. Is it possible that I took some sort of shortcut that screwed my installation? It is just nice to be able to get into the dockstar, and not keep getting the "No route to host" message.

Also, then I run the command "uboot_uptodate" I am given the response "The existing firmware cannot be identified, so no update has been performed."

Thanks again, I am crossing my fingers that there is still hope yet for my potential server.

cheers-

[chaskito]

Well, after reloading everything as described in the wiki I have my little server running. I am still having trouble getting the "transmission" app. to install correctly, continues to tell me it is a corrupt file, but I have read issues published by others throughout the forums.

One of my only issues is getting my other OS (windows 7) to be able to "see" the server, but I have more hunting to do before I beg for more advice. For now I am very satisfied.

Thanks for everyone's help. I look forward to learning more as I further understand the capability of my little "linux box"

-

[peaslaker]

$this->bbcode_second_pass_quote('chaskito', 'T')hank you very much "peaslaker" I am very grateful for your assistance on this matter - - I was able to get into the uboot environment, but after running the command "uboot_identify" all that I learned was "The existing firmware cannot be identified.." shall I try to update the firmware some other way? When I successfully installed pogo OS, I did not log into the uboot environment to update the mtd0 directory and complete the installation on the usb. Is it possible that I took some sort of shortcut that screwed my installation? It is just nice to be able to get into the dockstar, and not keep getting the "No route to host" message.

Also, then I run the command "uboot_uptodate" I am given the response "The existing firmware cannot be identified, so no update has been performed."

Thanks again, I am crossing my fingers that there is still hope yet for my potential server.

cheers-