[How-To] Boot Entirely from SATA

[WarheadsSE]

viewtopic.php?f=29&t=2453

[benni]

I read the hole thread you posted, but don't get it.
The Kernel is on the hdd and works with Archlinux 2012.05

Do I have to use your patch (in the running system) to write the newer Kernel to hdd (have to edit the script) and then copy the latest Archlinux to sdX2 ??
or can i edit the script from the first post to directly write the new kernel to hdd?

I try to understand!
Thanks for helping

[WarheadsSE]

If using Pure SATA boot:
- replace /usr/lib/modules/2.6.31_SMP_820
- dd uImage to sda1 *direct dd, no filesystem*

If using NAND kernel:
- run the script.

[bharath]

Any one have recommendation for a good enclosure with eSATA port that one can use to hold a boot drive. I have a Rosewill RX-358 V2 and I dont think that gets recognized. I dont have serial cable yet so not sure what the reason is. Any recommendations are greatly appreciated.

[0123456789]

I am not sure if you want an enclosed enclosure or not. I had a similar issue with a different rosewell enclosure, which I documented on page 3 of this thread. Below is what my post said.

This enclosure did NOT work:
BAD eSATA Dock:
Rosewill RX-DUS100
http://www.newegg.com/Product/Product.a ... 6817182197

Echoing what warhead said, this enclosure DOES work:
GOOD eSATA Dock:
Thermaltake BlacX ST0005U
http://www.newegg.com/Product/Product.a ... 6817153071



$this->bbcode_second_pass_quote('bharath', 'A')ny one have recommendation for a good enclosure with eSATA port that one can use to hold a boot drive. I have a Rosewill RX-358 V2 and I dont think that gets recognized. I dont have serial cable yet so not sure what the reason is. Any recommendations are greatly appreciated.

[bharath]

I was looking for an enclosed enclosure. I know the Vantec Nexstar NST-360SU is known to work. I was wondering if that is the only enclosure known to work.

[0123456789]

Update: Got the latest rootfs to work but still see the issue with the strange control chars.
Update: Control chars are console color settings from ls alias 'ls --color'.

Setup:
POGO-B01
SATA HD boot
nopci uImage

Issue:
On the ArchLinuxARM-oxnas-latest.tar.gz rootfs with the uImage from update-oxnas.tar.gz. Some of files/directories have funny control characters in the names.

For example.
# ls -d /etc | od -c
0000000 033 [ 0 m 033 [ 0 1 ; 3 4 m / e t c
0000020 033 [ 0 m \n
0000025

I would expect to see something like:
# ls -d /etc | od -c
0000000 / e t c \n
0000005

DUH:
So I looked up \033[0m and found it is the linux console colors. Then I realized that ls was aliased to ls --color. Unaliasing ls gives me the desired behavior. Move along, nothing to see here

I guess I should have done
# \ls -d /etc | od -c (to ensure I wasn't using an alias)

$this->bbcode_second_pass_quote('WarheadsSE', 'I')f using Pure SATA boot:
- replace /usr/lib/modules/2.6.31_SMP_820
- dd uImage to sda1 *direct dd, no filesystem*

If using NAND kernel:
- run the script.

[bharath]

I have a BlacX Duet docking station connected to the pogo over esata. During the startup it detects the drive but fails to boot. Apart from that it only detects ~128G of my 250G SATA drive. Any suggestions

$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 : 0x0000009ANo FIS received

Hdr len: 0xA1A2A3A4
Hdr CRC: 0xB1B2B3B4
read failed
Reading disk 0, Image 1
Sector : 0x0000DF78No FIS received

Hdr len: 0xA1A2A3A4
Hdr CRC: 0xB1B2B3B4
read failed
Reading disk 1, Image 0
Sector : 0x0000009A
Hdr len: 0xA1A2A3A4
Hdr CRC: 0xB1B2B3B4
read failed
Reading disk 1, Image 1
Sector : 0x0000DF78
Hdr len: 0xA1A2A3A4
Hdr CRC: 0xB1B2B3B4
read failed
Reading disk 0, Image 0
Sector : 0x0000009A
Hdr len: 0x0001FB34
Hdr CRC: 0x2229BDCD
OK
Initialising disks
SATA PHY not ready for device 1
Detecting SATA busses:
Bus 0: Found first device OK
Device 0: Model: ST3250820AS Firm: 3.AAE Ser#: 9QE2DDPK
Type: Hard Disk
Capacity: 131071.9 MB = 127.9 GB (268435455 x 512)
Device 1: not available
Failed to read valid environment from disk, using built-in default
')

I was wondering if it is impossible to boot of the BlacX duet or is there something that can be done to make it boot as it definitely seems to recognize the drives.

[bharath]

Ok the disk boots if connected directly, I am wondering if anyone had luck with the Vantec NexStar3 NST-380SU3-BK http://www.vantecusa.com/en/product/view_detail/479.

[bharath]

Just wanted to let others know that the Vantec NexStar CX NST-300SU-BK http://www.vantecusa.com/en/product/view_detail/374 also works as an enclosure that one can boot from.