[How-To] Boot Entirely from SATA

This forum is for all other ARMv5 devices

Re: [How-To] Boot Entirely from SATA

Postby WarheadsSE » Sun Dec 23, 2012 4:20 pm

disk_create was made such that if there are no links to the parts, it will skip them. So, you can:
- change out the stage1 link
- remove uboot link
- remove kernel link
- run script and only change stage1
Core Developer
Remember: Arch Linux ARM is entirely community donation supported!
WarheadsSE
Developer
 
Posts: 6807
Joined: Mon Oct 18, 2010 2:12 pm

Re: [How-To] Boot Entirely from SATA

Postby shv » Sun Dec 23, 2012 6:12 pm

Does it mean that I can write stage1 any time even the drive is already partitioned?
So I have written the the right 850 stage1 file again and again but never got more than 700MHz! It seams that previously written stage1 content isn't changed anymore.

I executed the command directly and still get just 700MHz.

$this->bbcode_second_pass_code('', 'dd if=stage1.wrapped850 of=sda bs=512 seek=34
14+1 Datensätze ein
14+1 Datensätze aus
7576 Bytes (7,6 kB) kopiert, 0,0854193 s, 88,7 kB/s
')
$this->bbcode_second_pass_code('', 'Stage-1 Bootloader Mon Nov 14 22:15:13 EST 2011
Attempting to set PLLA to 700MHz ...
plla_ctrl0 : 0x0000000A
plla_ctrl1 : 0x000E0000
plla_ctrl2 : 0x001B01A0
plla_ctrl3 : 0x00000016
PLLA Set

Setup memory, testing
Reading disk 0, Image 0
Sector : 0x0000009A
Hdr len: 0x0001FB34
Hdr CRC: 0x2229BDCD
OK
')
Debian @ Pogoplug Pro (actively used)
Debian @ Pogoplug E02
shv
 
Posts: 38
Joined: Fri Dec 21, 2012 6:35 am

Re: [How-To] Boot Entirely from SATA

Postby karog » Sun Dec 23, 2012 6:37 pm

of (out file) should be /dev/sda, not just sda. You just wrote it to a file named sda in your current directory.

And yes you can write it without reformatting.
karog
 
Posts: 304
Joined: Thu Jan 05, 2012 7:55 pm

Re: [How-To] Boot Entirely from SATA

Postby shv » Sun Dec 23, 2012 7:22 pm

Thanks for your comment. Now my Pogo is running at 850MHz.

Using the file stage1.wrapped800 I just get 750 MHz instead of 800 MHz CPU clock. The other stage1 files are working as expected.
Last edited by shv on Mon Dec 24, 2012 3:19 pm, edited 1 time in total.
Debian @ Pogoplug Pro (actively used)
Debian @ Pogoplug E02
shv
 
Posts: 38
Joined: Fri Dec 21, 2012 6:35 am

Re: [How-To] Boot Entirely from SATA

Postby wxtofly » Mon Dec 24, 2012 7:39 pm

$this->bbcode_second_pass_quote('s09g06', 'I')s anyone else having issues updating the system after setting up boot from SATA drive.

Also I could not get the system to boot from SATA drive for the longest time. I recently realized that I had to update the uImage in the downloaded root file system with the uImage in the initial .tar download. After replacing the uImage the system boots correctly and I am able to ssh in, but if I try to install any package, the system asks me to update pacman and a bunch of other system packages. I am not able to correctly update these and this always results in a broken system. I would appreciate if someone could help me with this.


This concerns me. When I installed arch to a usb from slightly older source, I had a very hard time with upgrading because several important things had changed. I found the answers in generic upgrade forums, not here.

I have not been sucessful with an sata boot. My concern is that the december 2011 kernel is before all the upgrades, and the "latest" distribution is after the changes. Could that be why I can't get the sata to boot? Do I need to populate it with an old distribution first, to go with the old kernel rather than with "latest"?

Also, there was no direct response to the question as to whether the sdx1 partition needs to be marked bootable. Does it?

Also, the disk_create script that I downloaded does not have skip=2048 for the kernel install. Is it needed, or is that taken care of by writing to sdx1?

Thanks for all this great information!
TJ
wxtofly
 
Posts: 17
Joined: Mon Dec 24, 2012 3:27 am

Re: [How-To] Boot Entirely from SATA

Postby karog » Tue Dec 25, 2012 1:46 am

$this->bbcode_second_pass_quote('wxtofly', '
')Also, there was no direct response to the question as to whether the sdx1 partition needs to be marked bootable. Does it?

No, it does not.
$this->bbcode_second_pass_quote('wxtofly', '
')Also, the disk_create script that I downloaded does not have skip=2048 for the kernel install. Is it needed, or is that taken care of by writing to sdx1?

Not needed, taken care of by sdx1.
karog
 
Posts: 304
Joined: Thu Jan 05, 2012 7:55 pm
Top

Re: [How-To] Boot Entirely from SATA

Postby wxtofly » Tue Dec 25, 2012 6:55 am

With mostly luck I got back access to my V3
Once I got the original CE stuff back and then ran oxnas-install.sh, now I can boot from the SATA drive directly.

THIS was not done without touching NAND however! Did I miss something somewhere that said that the new u-boot and kernel were prerequisites?

I am a bit concerned that dmesg has all this in it:
$this->bbcode_second_pass_code('', '
[ 101.220000] uncorrectable error :
[ 101.220000] uncorrectable error :
[ 101.230000] end_request: I/O error, dev mtdblock0, sector 2048
[ 101.230000] Buffer I/O error on device mtdblock0, logical block 256
[ 101.320000] uncorrectable error :
[ 101.330000] uncorrectable error :
[ 101.330000] end_request: I/O error, dev mtdblock0, sector 768
[ 101.330000] Buffer I/O error on device mtdblock0, logical block 96
[ 101.340000] uncorrectable error :
[ 101.350000] uncorrectable error :
[ 101.350000] end_request: I/O error, dev mtdblock0, sector 512
[ 101.350000] Buffer I/O error on device mtdblock0, logical block 64
[ 101.390000] uncorrectable error :
[ 101.390000] uncorrectable error :
[ 101.390000] end_request: I/O error, dev mtdblock1, sector 2048
[ 101.390000] Buffer I/O error on device mtdblock1, logical block 256
[ 101.420000] uncorrectable error :
[ 101.420000] uncorrectable error :
[ 101.430000] end_request: I/O error, dev mtdblock1, sector 512
[ 101.430000] Buffer I/O error on device mtdblock1, logical block 64
[ 265.130000] uncorrectable error :
[ 265.130000] uncorrectable error :
[ 265.140000] end_request: I/O error, dev mtdblock0, sector 2048
[ 265.140000] Buffer I/O error on device mtdblock0, logical block 256
[ 265.230000] uncorrectable error :
[ 265.240000] uncorrectable error :
[ 265.240000] end_request: I/O error, dev mtdblock0, sector 768
[ 265.240000] Buffer I/O error on device mtdblock0, logical block 96
[ 265.250000] uncorrectable error :
[ 265.260000] uncorrectable error :
[ 265.260000] end_request: I/O error, dev mtdblock0, sector 512
[ 265.260000] Buffer I/O error on device mtdblock0, logical block 64
[ 265.300000] uncorrectable error :
[ 265.300000] uncorrectable error :
[ 265.300000] end_request: I/O error, dev mtdblock1, sector 2048
[ 265.300000] Buffer I/O error on device mtdblock1, logical block 256
[ 265.330000] uncorrectable error :
[ 265.330000] uncorrectable error :
[ 265.340000] end_request: I/O error, dev mtdblock1, sector 512
[ 265.340000] Buffer I/O error on device mtdblock1, logical block 64
')

Is it a problem?

TJ
wxtofly
 
Posts: 17
Joined: Mon Dec 24, 2012 3:27 am

Re: [How-To] Boot Entirely from SATA

Postby Socaltom » Thu Dec 27, 2012 1:09 am

Since I'm avoiding taking down the christmas decorations, I decided to try out the SATA boot system with a spare drive I acquired last week. My normal configuration is still booting from NAND, but if I understand correctly, the boot entirely from SATA method should still work.
I followed all the instructions in the first post, but got no boot, the drive led flashed a couple of times, then nothing happened.
Daemon.log had this which I thought was odd since my ip range is 192.168.10.1XXX
$this->bbcode_second_pass_code('', 'ec 31 18:00:15 alarm-oxnas dhcpcd[909]: eth0: waiting for carrier
Dec 31 18:00:15 alarm-oxnas dhcpcd[909]: eth0: carrier acquired
Dec 31 18:00:15 alarm-oxnas dhcpcd[909]: eth0: sending IPv6 Router Solicitation
Dec 31 18:00:15 alarm-oxnas dhcpcd[909]: eth0: sendmsg: Cannot assign requested$
Dec 31 18:00:15 alarm-oxnas dhcpcd[909]: eth0: broadcasting for a lease
Dec 31 18:00:17 alarm-oxnas dhcpcd[909]: eth0: offered 192.168.11.27 from 192.1$
Dec 31 18:00:17 alarm-oxnas dhcpcd[909]: eth0: acknowledged 192.168.11.27 from $
Dec 31 18:00:18 alarm-oxnas dhcpcd[909]: eth0: checking for 192.168.11.27
Dec 31 18:00:19 alarm-oxnas dhcpcd[909]: eth0: sending IPv6 Router Solicitation
Dec 31 18:00:23 alarm-oxnas dhcpcd[909]: eth0: leased 192.168.11.27 for 86400 s$
')

What could be causing this?
Tom
used to be owned by me
Pink Pogo V2, Black Pogo V3, Zyxel NAS 325 v1,
used to be Adminstrator for
Goflex net, Black V3, Black V2
Now I have a couple of raspberry pi ( 3+ and 4)
Socaltom
 
Posts: 571
Joined: Thu Apr 07, 2011 2:21 pm
Location: The left side

Re: [How-To] Boot Entirely from SATA

Postby dasepsilon » Sat Dec 29, 2012 1:12 pm

hi, i'm sorry to ask, i was not able to boot from sata, can anyone help?
i've bricked my pogoplug classic (=pro internally) it by writing some wrong version,
now following the first post gives me a blinking-for-5-seconds-led and then
the led turns off, and thats it. it does not show up in dhcp or whatever.
while using disk_create i also do not get an error upon first usage-- but i do not
understand how to correct this? i tried to rewrite just the kernel, but to no
avail. unluckily i do not have a serial connection, so no logs :(
(i had hoped to find some logs under /var/log, but the only the wtmp file gets touched).
can anyone help me out?
dasepsilon
 
Posts: 1
Joined: Sat Dec 29, 2012 1:06 pm

Re: [How-To] Boot Entirely from SATA

Postby Socaltom » Sun Dec 30, 2012 3:28 am

I got an almost new Pogo Pro in the mail today. Activated it, all works fine through my.pogoplug.com

Set up my sata drive per the instructions,
When the drive in in the dock ( rosewill eSata external case), the drive LED flickers a few times, then comes on for a few seconds, the Pogo LED never comes on. Review of the logs finds that it boots fine, but doesn't get a proper IP.

When I run a cable direct from the drive ( no dock) ( with power), I get the flickering green LED for a little bit on the pogo, then it goes out, but it seems to have the same failure, no proper IP address.mount
$this->bbcode_second_pass_code('', 'Dec 31 18:00:26 alarm kernel: [ 20.320000] Probing for Synopsis GMAC, unit 0
Dec 31 18:00:26 alarm kernel: [ 20.320000] eth0: Tuning GMAC 0 RGMII timings
Dec 31 18:00:26 alarm kernel: [ 20.330000] eth0: PHY is Realtek RTL8211D, type 0x001cc914
Dec 31 18:00:26 alarm kernel: [ 20.340000] eth0: GMAC ver = 53, vendor ver = 18 at 0xed400000, IRQ 40
Dec 31 18:00:26 alarm kernel: [ 20.340000] eth0: Found PHY at address 3, type 0x001cc914 -> 10/100/1000
Dec 31 18:00:26 alarm kernel: [ 20.350000] eth0: Ethernet addr: 00:30:e0:00:00:00
Dec 31 18:00:26 alarm kernel: [ 20.360000] probe() eth0: Leon x2 clock
Dec 31 18:00:26 alarm kernel: [ 20.940000] EXT3 FS on sda1, internal journal
Dec 31 18:00:26 alarm kernel: [ 21.450000] Turning off blinking LED.
Dec 31 18:00:26 alarm kernel: [ 21.620000] eth0: PHY is Realtek RTL8211D, type 0x001cc914
Dec 31 18:00:26 alarm kernel: [ 21.630000] CoPro offload is active on eth0
Dec 31 18:00:26 alarm kernel: [ 21.630000] Alloc'ing ARM descs 8192 bytes
Dec 31 18:00:26 alarm kernel: [ 21.640000] Alloc'ing CoPro parameters 36 bytes
Dec 31 18:00:26 alarm kernel: [ 21.640000] gmac gmac.0: firmware: requesting gmac_copro_firmware
Dec 31 18:00:26 alarm kernel: [ 21.660000] CoPro: Programming start address as 0xd000e000
Dec 31 18:00:26 alarm kernel: [ 21.760000] eth0: Resetting GMAC
Dec 31 18:00:26 alarm kernel: [ 21.770000] eth0: GMAC reset complete
Dec 31 18:00:26 alarm kernel: [ 21.770000] eth0: Setting Rx flow control thresholds for LAN port
Dec 31 18:00:26 alarm kernel: [ 22.330000] eth0: PHY is Realtek RTL8211D, type 0x001cc914
Dec 31 18:00:26 alarm kernel: [ 22.830000] eth0: link down
Dec 31 18:00:26 alarm kernel: [ 24.790000] ADDRCONF(NETDEV_UP): eth0: link is not ready
Dec 31 18:00:26 alarm kernel: [ 26.330000] eth0: link up, 1000Mbps, full-duplex, not using pause, lpa 0xC1E1
Dec 31 18:00:26 alarm kernel: [ 26.330000] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Dec 31 18:00:26 alarm dhcpcd[675]: version 5.5.6 starting
Dec 31 18:00:26 alarm dhcpcd[675]: eth0: sending IPv6 Router Solicitation
Dec 31 18:00:26 alarm dhcpcd[675]: eth0: sendmsg: Cannot assign requested address
Dec 31 18:00:26 alarm dhcpcd[675]: eth0: broadcasting for a lease
Dec 31 18:00:29 alarm dhcpcd[675]: eth0: offered 192.168.11.38 from 192.168.11.1
Dec 31 18:00:29 alarm dhcpcd[675]: eth0: acknowledged 192.168.11.38 from 192.168.11.1
Dec 31 18:00:29 alarm dhcpcd[675]: eth0: checking for 192.168.11.38
Dec 31 18:00:30 alarm dhcpcd[675]: eth0: sending IPv6 Router Solicitation
Dec 31 18:00:34 alarm dhcpcd[675]: eth0: leased 192.168.11.38 for 86400 seconds
Dec 31 18:00:35 alarm dhcpcd[675]: forked to background, child pid 702
Dec 31 18:00:35 alarm dhcpcd[702]: eth0: sending IPv6 Router Solicitation
Dec 31 18:00:35 alarm /usr/sbin/crond[717]: (CRON) STARTUP (1.4.8)
Dec 31 18:00:35 alarm /usr/sbin/crond[717]: (CRON) INFO (Syslog will be used instead of sendmail.): No such file or directory
Dec 31 18:00:35 alarm /usr/sbin/crond[717]: (CRON) INFO (running with inotify support)
Dec 31 18:00:36 alarm kernel: [ 36.620000] eth0: no IPv6 routers present
Jun 14 18:27:51 alarm ntpd[737]: set local clock to Thu Jun 14 18:27:51 CDT 2012 (offset 1339716435.027559s)
Jun 14 18:27:54 alarm dhcpcd[702]: eth0: sending IPv6 Router Solicitation
')

FYI, my router is 192.168.10.X, not 11.X so I don't get that. Any suggestions?
used to be owned by me
Pink Pogo V2, Black Pogo V3, Zyxel NAS 325 v1,
used to be Adminstrator for
Goflex net, Black V3, Black V2
Now I have a couple of raspberry pi ( 3+ and 4)
Socaltom
 
Posts: 571
Joined: Thu Apr 07, 2011 2:21 pm
Location: The left side

PreviousNext

Return to Community Supported

Who is online

Users browsing this forum: No registered users and 8 guests