Pogoplug v4 Booting from Sata

This forum is for topics dealing with problems with software specifically in the ARMv5 repo.

Pogoplug v4 Booting from Sata

Postby slick666 » Sun Jan 05, 2014 10:01 pm

After getting things up and running on a spare thumbdrive I'm trying to shift it over to booting off of the Sata drive. Here is what I've done so far.

I partitioned the drive seperately
$this->bbcode_second_pass_code('', '# fdisk -l /dev/sda

Disk /dev/sda: 298.1 GiB, 320072933376 bytes, 625142448 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xc982ec80

Device Boot Start End Blocks Id System
/dev/sda1 2048 566233087 283115520 83 Linux
/dev/sda2 566233088 625142447 29454680 82 Linux swap / Solaris')

I then picked up usinf the instructions from the Pogoplug v4 instructions.

$this->bbcode_second_pass_code('', '# mke2fs -j /dev/sda1
mke2fs 1.42.8 (20-Jun-2013)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
17694720 inodes, 70778880 blocks
3538944 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=0
2160 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872

Allocating group tables: done
Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done

# mkdir alarm
# mount /dev/sda1 alarm
# cd alarm
# wget http://archlinuxarm.org/os/ArchLinuxARM-armv5te-latest.tar.gz
--2014-01-05 14:40:52-- http://archlinuxarm.org/os/ArchLinuxARM-armv5te-latest.tar.gz
Resolving archlinuxarm.org (archlinuxarm.org)... 50.116.36.110
Connecting to archlinuxarm.org (archlinuxarm.org)|50.116.36.110|:80... connected.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: http://os.archlinuxarm.org/os/ArchLinuxARM-armv5te-latest.tar.gz [following]
--2014-01-05 14:40:52-- http://os.archlinuxarm.org/os/ArchLinuxARM-armv5te-latest.tar.gz
Resolving os.archlinuxarm.org (os.archlinuxarm.org)... 128.4.11.201, 67.23.118.182, 54.203.244.41, ...
Connecting to os.archlinuxarm.org (os.archlinuxarm.org)|128.4.11.201|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 163133100 (156M) [application/x-tar]
Saving to: ‘ArchLinuxARM-armv5te-latest.tar.gz’

100%[============================================================================================================>] 163,133,100 715KB/s in 4m 47s

2014-01-05 14:45:39 (556 KB/s) - ‘ArchLinuxARM-armv5te-latest.tar.gz’ saved [163133100/163133100]

# tar -xzvf ArchLinuxARM-armv5te-latest.tar.gz # This will take a long time
./bin
./boot/
...
./var/spool/mail/
./var/games/
# rm ArchLinuxARM-armv5te-latest.tar.gz
# sync
# cd ..
# umount alarm')

This is the point where I stopped. I ran the shutdown command "reboot" and then when my ssh session ended I pull the power, pulled the thumb drive and then plugged it back in. The system lights up and the light stops blinking rapidly after about 8~9 seconds and goes a solid green but I cannot ping the ip address or ssh to the box.

at this point I'm a little stumped. Any ideas or help would be appreciated, thanks.
slick666
 
Posts: 6
Joined: Mon Dec 23, 2013 5:30 am

Re: Pogoplug v4 Booting from Sata

Postby slick666 » Sat Jan 11, 2014 11:25 pm

It took a while but after a number of reboots the system started working. While I was doing some work on the thumbdrive I can't see how that would have effected uboot. The only thought I can think of sitting here now is that I possibly didn't power cycle the unit but simply reboot from the terminal.

I hope this helps someone else.
slick666
 
Posts: 6
Joined: Mon Dec 23, 2013 5:30 am


Return to ARMv5

Who is online

Users browsing this forum: No registered users and 2 guests