[How-To] Boot Entirely from SATA

This forum is for all other ARMv5 devices

Re: [How-To] Boot Entirely from SATA

Postby emax20000 » Wed Apr 24, 2013 8:58 am

Tank you for reply ,
and now I checked and the data is ok, now my device boot up but after a few seconds of loading the LED goes off and does not acquire network address, sometimes the nic flash but the router does not release ip.I have tried to connect in serial but the output is unreadable "@ ÀÀÀ # # #" I've tried different connection speeds including 115200 8N1 and I used an adapter usb / serial. Any idea?
emax20000
 
Posts: 9
Joined: Sun Apr 21, 2013 7:22 pm

Re: [How-To] Boot Entirely from SATA

Postby WarheadsSE » Wed Apr 24, 2013 11:43 am

115200,n,8
Use ONLY a 3.3v TTL/RS232! (NOT A STANDARD 12V!!)
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 emax20000 » Wed Apr 24, 2013 12:37 pm

Hi ,
I have extracted these logs, can help you find what is the problem which does not allow proper start of my Pogoplug?
Dec 31 18:00:17 alarm kernel: [ 0.000000] Linux version 2.6.31.6_SMP_820 (root@ProDev) (gcc version 4.6.0 20110429 (prerelease) (GCC) ) #99 SMP Sun May 29 03:04:43 EDT 2011
Dec 31 18:00:17 alarm kernel: [ 0.000000] CPU: ARMv6-compatible processor [410fb025] revision 5 (ARMv7), cr=00c5387f
Dec 31 18:00:17 alarm kernel: [ 0.000000] CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
Dec 31 18:00:17 alarm kernel: [ 0.000000] Machine: Oxsemi NAS
Dec 31 18:00:17 alarm kernel: [ 0.000000] 1 memory region
Dec 31 18:00:17 alarm kernel: [ 0.000000] Ignoring unrecognised tag 0x00000000
Dec 31 18:00:17 alarm kernel: [ 0.000000] Memory policy: ECC disabled, Data cache writealloc
Dec 31 18:00:18 alarm kernel: [ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 32512
Dec 31 18:00:18 alarm kernel: [ 0.000000] Kernel command line: root=/dev/sda2 console=ttyS0,115200 elevator=cfq mac_adr=0x00,0x30,0xe0,0x00,0x00,0x01 rootwait ubi.mtd=2,512 mem=128M poweroutage=yes
Dec 31 18:00:18 alarm kernel: [ 0.000000] PID hash table entries: 512 (order: 9, 2048 bytes)
Dec 31 18:00:18 alarm kernel: [ 0.000000] Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Dec 31 18:00:18 alarm kernel: [ 0.000000] Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Dec 31 18:00:18 alarm kernel: [ 0.000000] Memory: 128MB = 128MB total
Dec 31 18:00:18 alarm kernel: [ 0.000000] Memory: 125524KB available (3636K code, 296K data, 128K init, 0K highmem)
Dec 31 18:00:18 alarm kernel: [ 0.000000] Hierarchical RCU implementation.
Dec 31 18:00:18 alarm kernel: [ 0.000000] NR_IRQS:96
Dec 31 18:00:18 alarm kernel: [ 0.000000] OX820_RPS_init_irq: interrupts 64 to 96
Dec 31 18:00:18 alarm kernel: [ 0.010000] Console: colour dummy device 80x30
Dec 31 18:00:18 alarm kernel: [ 0.010000] console [ttyS0] enabled
Dec 31 18:00:18 alarm kernel: [ 0.020000] Calibrating delay loop... 279.34 BogoMIPS (lpj=1396736)
Dec 31 18:00:18 alarm kernel: [ 0.260000] Security Framework initialized
Dec 31 18:00:18 alarm kernel: [ 0.260000] Mount-cache hash table entries: 512
Dec 31 18:00:18 alarm kernel: [ 0.270000] CPU: Testing write buffer coherency: ok
Dec 31 18:00:18 alarm kernel: [ 0.270000] Calibrating local timer... 350.00MHz.
Dec 31 18:00:18 alarm kernel: [ 0.340000] CPU1: Booted secondary processor
Dec 31 18:00:18 alarm kernel: [ 0.440000] Calibrating delay loop... 279.34 BogoMIPS (lpj=1396736)
Dec 31 18:00:18 alarm kernel: [ 0.670000] Brought up 2 CPUs
Dec 31 18:00:18 alarm kernel: [ 0.680000] SMP: Total of 2 processors activated (558.69 BogoMIPS).
Dec 31 18:00:18 alarm kernel: [ 0.690000] NET: Registered protocol family 16
Dec 31 18:00:18 alarm kernel: [ 0.690000] Number of DMA channels = 4, version = 4
Dec 31 18:00:18 alarm kernel: [ 0.700000] Reserving a DMA channel for DirectRAID
Dec 31 18:00:18 alarm kernel: [ 0.700000] Allocating 389 SRAM generic DMA descriptors
Dec 31 18:00:18 alarm kernel: [ 1.210000] PCIeA version/deviceID 082510b5
Dec 31 18:00:18 alarm kernel: [ 1.210000] PCIeB version/deviceID 082510b5
Dec 31 18:00:18 alarm kernel: [ 4.240000] ox820_pci_preinit() PCIEB link up timeout (00001814)
Dec 31 18:00:18 alarm kernel: [ 4.240000] ox820_pcie_setup_resources() Enabling PCIe Pre-Emphasis
Dec 31 18:00:18 alarm kernel: [ 4.250000] ox820_pciea_setup_resources() resource c781b2c0
Dec 31 18:00:18 alarm kernel: [ 4.250000] ox820_pciea_setup_resources() io: 0x4be00000 - 0x4befffff
Dec 31 18:00:18 alarm kernel: [ 4.260000] ox820_pciea_setup_resources() non-pre: 0x48000000 - 0x49ffffff
Dec 31 18:00:18 alarm kernel: [ 4.270000] ox820_pciea_setup_resources() pre: 0x4a000000 - 0x4bdfffff
Dec 31 18:00:18 alarm kernel: [ 4.270000] PCI: bus0: Fast back to back transfers disabled
Dec 31 18:00:18 alarm kernel: [ 4.280000] PCI: bus1: Fast back to back transfers enabled
Dec 31 18:00:18 alarm kernel: [ 4.300000] bio: create slab <bio-0> at 0
Dec 31 18:00:18 alarm kernel: [ 4.310000] SCSI subsystem initialized
Dec 31 18:00:18 alarm kernel: [ 4.310000] usbcore: registered new interface driver usbfs
Dec 31 18:00:18 alarm kernel: [ 4.320000] usbcore: registered new interface driver hub
Dec 31 18:00:18 alarm kernel: [ 4.320000] usbcore: registered new device driver usb
Dec 31 18:00:18 alarm kernel: [ 4.360000] NET: Registered protocol family 2
Dec 31 18:00:18 alarm kernel: [ 4.360000] IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
Dec 31 18:00:18 alarm kernel: [ 4.370000] Switched to NOHz mode on CPU #0
Dec 31 18:00:18 alarm kernel: [ 4.370000] TCP established hash table entries: 4096 (order: 3, 32768 bytes)
Dec 31 18:00:18 alarm kernel: [ 4.370000] Switched to NOHz mode on CPU #1
Dec 31 18:00:18 alarm kernel: [ 4.380000] TCP bind hash table entries: 4096 (order: 3, 32768 bytes)
Dec 31 18:00:18 alarm kernel: [ 4.390000] TCP: Hash tables configured (established 4096 bind 4096)
Dec 31 18:00:18 alarm kernel: [ 4.390000] TCP reno registered
Dec 31 18:00:18 alarm kernel: [ 4.400000] NET: Registered protocol family 1
Dec 31 18:00:18 alarm kernel: [ 4.400000] Create fragment cache
Dec 31 18:00:18 alarm kernel: [ 4.410000] fuse init (API version 7.12)
Dec 31 18:00:18 alarm kernel: [ 4.410000] msgmni has been set to 245
Dec 31 18:00:18 alarm kernel: [ 4.420000] alg: No test for stdrng (krng)
Dec 31 18:00:18 alarm kernel: [ 4.420000] io scheduler noop registered
Dec 31 18:00:18 alarm kernel: [ 4.430000] io scheduler anticipatory registered
Dec 31 18:00:18 alarm kernel: [ 4.430000] io scheduler deadline registered
Dec 31 18:00:18 alarm kernel: [ 4.440000] io scheduler cfq registered (default)
Dec 31 18:00:18 alarm kernel: [ 4.460000] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
Dec 31 18:00:18 alarm kernel: [ 4.470000] serial8250: ttyS0 at MMIO 0x44200000 (irq = 55) is a 16550A
Dec 31 18:00:18 alarm kernel: [ 4.480000] brd: module loaded
Dec 31 18:00:18 alarm kernel: [ 4.490000] loop: module loaded
Dec 31 18:00:18 alarm kernel: [ 4.500000] ox820sata: OX820 sata core.
Dec 31 18:00:18 alarm kernel: [ 4.500000] scsi0 : oxnassata
Dec 31 18:00:18 alarm kernel: [ 4.500000] scsi1 : oxnassata
Dec 31 18:00:18 alarm kernel: [ 4.510000] ata1: SATA max UDMA/133 irq 50
Dec 31 18:00:18 alarm kernel: [ 4.510000] ata2: SATA max UDMA/133 irq 50
Dec 31 18:00:18 alarm kernel: [ 5.040000] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Dec 31 18:00:18 alarm kernel: [ 5.040000] ata1.00: ATA-7: Hitachi HDT725025VLA380, V5DOA73A, max UDMA/133
Dec 31 18:00:18 alarm kernel: [ 5.050000] ata1.00: 488281250 sectors, multi 0: LBA48 NCQ (depth 0/32)
Dec 31 18:00:18 alarm kernel: [ 5.060000] ata1.00: configured for UDMA/133
Dec 31 18:00:18 alarm kernel: [ 5.780000] ata2: SATA link down (SStatus 0 SControl 300)
Dec 31 18:00:18 alarm kernel: [ 5.780000] scsi 0:0:0:0: Direct-Access ATA Hitachi HDT72502 V5DO PQ: 0 ANSI: 5
Dec 31 18:00:18 alarm kernel: [ 5.790000] sd 0:0:0:0: [sda] 488281250 512-byte logical blocks: (250 GB/232 GiB)
Dec 31 18:00:18 alarm kernel: [ 5.800000] sd 0:0:0:0: [sda] Write Protect is off
Dec 31 18:00:18 alarm kernel: [ 5.800000] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Dec 31 18:00:18 alarm kernel: [ 5.810000] tun: Universal TUN/TAP device driver, 1.6
Dec 31 18:00:18 alarm kernel: [ 5.810000] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Dec 31 18:00:18 alarm kernel: [ 5.810000] NAND: Page read time 40ms
Dec 31 18:00:18 alarm kernel: [ 5.810000] NAND device: Manufacturer ID: 0xad, Chip ID: 0xf1 (Hynix NAND 128MiB 3,3V 8-bit)
Dec 31 18:00:18 alarm kernel: [ 5.810000] Scanning device for bad blocks
Dec 31 18:00:18 alarm kernel: [ 5.880000] Creating 2 MTD partitions on "NAND 128MiB 3,3V 8-bit":
Dec 31 18:00:18 alarm kernel: [ 5.880000] 0x000000000000-0x000000e00000 : "boot"
Dec 31 18:00:18 alarm kernel: [ 5.890000] sda:
Dec 31 18:00:18 alarm kernel: [ 5.890000] 0x000000e00000-0x000008000000 : "rootfs"
Dec 31 18:00:18 alarm kernel: [ 5.900000] UBI: attaching mtd2 to ubi0
Dec 31 18:00:18 alarm kernel: [ 5.900000] UBI: physical eraseblock size: 131072 bytes (128 KiB)
Dec 31 18:00:18 alarm kernel: [ 5.910000] UBI: logical eraseblock size: 129024 bytes
Dec 31 18:00:18 alarm kernel: [ 5.910000] UBI: smallest flash I/O unit: 2048
Dec 31 18:00:18 alarm kernel: [ 5.920000] UBI: sub-page size: 512
Dec 31 18:00:18 alarm kernel: [ 5.920000] UBI: VID header offset: 512 (aligned 512)
Dec 31 18:00:18 alarm kernel: [ 5.930000] UBI: data offset: 2048
Dec 31 18:00:18 alarm kernel: [ 6.010000] sda1 sda2
Dec 31 18:00:18 alarm kernel: [ 6.350000] UBI: attached mtd2 to ubi0
Dec 31 18:00:18 alarm kernel: [ 6.350000] UBI: MTD device name: "rootfs"
Dec 31 18:00:18 alarm kernel: [ 6.350000] UBI: MTD device size: 114 MiB
Dec 31 18:00:18 alarm kernel: [ 6.360000] UBI: number of good PEBs: 912
Dec 31 18:00:18 alarm kernel: [ 6.360000] UBI: number of bad PEBs: 0
Dec 31 18:00:18 alarm kernel: [ 6.370000] UBI: max. allowed volumes: 128
Dec 31 18:00:18 alarm kernel: [ 6.370000] UBI: wear-leveling threshold: 4096
Dec 31 18:00:18 alarm kernel: [ 6.380000] UBI: number of internal volumes: 1
Dec 31 18:00:18 alarm kernel: [ 6.380000] UBI: number of user volumes: 1
Dec 31 18:00:18 alarm kernel: [ 6.390000] UBI: available PEBs: 0
Dec 31 18:00:18 alarm kernel: [ 6.390000] UBI: total number of reserved PEBs: 912
Dec 31 18:00:18 alarm kernel: [ 6.400000] UBI: number of PEBs reserved for bad PEB handling: 9
Dec 31 18:00:18 alarm kernel: [ 6.400000] UBI: max/mean erase counter: 2/1
Dec 31 18:00:18 alarm kernel: [ 6.410000] UBI: image sequence number: 0
Dec 31 18:00:18 alarm kernel: [ 6.410000] UBI: background thread "ubi_bgt0d" started, PID 304
Dec 31 18:00:18 alarm kernel: [ 6.410000] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Dec 31 18:00:18 alarm kernel: [ 6.410000] oxnas-ehci oxnas-ehci.0: OXNAS EHCI Host Controller
Dec 31 18:00:18 alarm kernel: [ 6.410000] oxnas-ehci oxnas-ehci.0: new USB bus registered, assigned bus number 1
Dec 31 18:00:18 alarm kernel: [ 6.440000] oxnas-ehci oxnas-ehci.0: irq 39, io mem 0x00000000
Dec 31 18:00:18 alarm kernel: [ 6.440000] sd 0:0:0:0: [sda] Attached SCSI disk
Dec 31 18:00:18 alarm kernel: [ 6.460000] oxnas-ehci oxnas-ehci.0: USB 0.0 started, EHCI 1.00
Dec 31 18:00:18 alarm kernel: [ 6.460000] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Dec 31 18:00:18 alarm kernel: [ 6.470000] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Dec 31 18:00:18 alarm kernel: [ 6.470000] usb usb1: Product: OXNAS EHCI Host Controller
Dec 31 18:00:18 alarm kernel: [ 6.480000] usb usb1: Manufacturer: Linux 2.6.31.6_SMP_820 ehci_hcd
Dec 31 18:00:18 alarm kernel: [ 6.490000] usb usb1: SerialNumber: usb
Dec 31 18:00:18 alarm kernel: [ 6.490000] usb usb1: configuration #1 chosen from 1 choice
Dec 31 18:00:18 alarm kernel: [ 6.500000] hub 1-0:1.0: USB hub found
Dec 31 18:00:18 alarm kernel: [ 6.500000] hub 1-0:1.0: 2 ports detected
Dec 31 18:00:18 alarm kernel: [ 6.510000] Initializing USB Mass Storage driver...
Dec 31 18:00:18 alarm kernel: [ 6.510000] usbcore: registered new interface driver usb-storage
Dec 31 18:00:18 alarm kernel: [ 6.520000] USB Mass Storage support registered.
Dec 31 18:00:18 alarm kernel: [ 6.520000] mice: PS/2 mouse device common for all mice
Dec 31 18:00:18 alarm kernel: [ 6.530000] TCP cubic registered
Dec 31 18:00:18 alarm kernel: [ 6.530000] NET: Registered protocol family 10
Dec 31 18:00:18 alarm kernel: [ 6.540000] NET: Registered protocol family 17
Dec 31 18:00:18 alarm kernel: [ 6.540000] RPC: Registered udp transport module.
Dec 31 18:00:18 alarm kernel: [ 6.550000] RPC: Registered tcp transport module.
Dec 31 18:00:18 alarm kernel: [ 6.600000] kjournald starting. Commit interval 5 seconds
Dec 31 18:00:18 alarm kernel: [ 6.600000] EXT3 FS on sda2, internal journal
Dec 31 18:00:18 alarm kernel: [ 6.610000] EXT3-fs: mounted filesystem with writeback data mode.
Dec 31 18:00:18 alarm kernel: [ 6.610000] VFS: Mounted root (ext3 filesystem) on device 8:2.
Dec 31 18:00:18 alarm kernel: [ 6.620000] Freeing init memory: 128K
Dec 31 18:00:18 alarm kernel: [ 6.820000] usb 1-1: new high speed USB device using oxnas-ehci and address 2
Dec 31 18:00:18 alarm kernel: [ 6.970000] usb 1-1: New USB device found, idVendor=05e3, idProduct=0608
Dec 31 18:00:18 alarm kernel: [ 6.970000] usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0
Dec 31 18:00:18 alarm kernel: [ 6.980000] usb 1-1: Product: USB2.0 Hub
Dec 31 18:00:18 alarm kernel: [ 6.990000] usb 1-1: configuration #1 chosen from 1 choice
Dec 31 18:00:18 alarm kernel: [ 6.990000] hub 1-1:1.0: USB hub found
Dec 31 18:00:18 alarm kernel: [ 7.000000] hub 1-1:1.0: 4 ports detected
Dec 31 18:00:18 alarm kernel: [ 10.280000] Probing for Synopsis GMAC, unit 0
Dec 31 18:00:18 alarm kernel: [ 10.290000] eth0: Tuning GMAC 0 RGMII timings
Dec 31 18:00:18 alarm kernel: [ 10.290000] eth0: PHY is Realtek RTL8211D, type 0x001cc914
Dec 31 18:00:18 alarm kernel: [ 10.320000] eth0: GMAC ver = 53, vendor ver = 18 at 0xed400000, IRQ 40
Dec 31 18:00:18 alarm kernel: [ 10.330000] eth0: Found PHY at address 3, type 0x001cc914 -> 10/100/1000
Dec 31 18:00:18 alarm kernel: [ 10.330000] eth0: Ethernet addr: 00:30:e0:00:00:00
Dec 31 18:00:18 alarm kernel: [ 10.350000] probe() eth0: Leon x2 clock
Dec 31 18:00:18 alarm kernel: [ 11.150000] EXT3 FS on sda2, internal journal
Dec 31 18:00:18 alarm kernel: [ 12.440000] Turning off blinking LED.
Dec 31 18:00:18 alarm kernel: [ 12.950000] eth0: PHY is Realtek RTL8211D, type 0x001cc914
Dec 31 18:00:18 alarm kernel: [ 12.960000] CoPro offload is active on eth0
Dec 31 18:00:18 alarm kernel: [ 12.960000] Alloc'ing ARM descs 8192 bytes
Dec 31 18:00:18 alarm kernel: [ 12.970000] Alloc'ing CoPro parameters 36 bytes
Dec 31 18:00:18 alarm kernel: [ 12.970000] gmac gmac.0: firmware: requesting gmac_copro_firmware
Dec 31 18:00:18 alarm kernel: [ 13.020000] CoPro: Programming start address as 0xd000e000
Dec 31 18:00:18 alarm kernel: [ 13.130000] eth0: Resetting GMAC
Dec 31 18:00:18 alarm kernel: [ 13.130000] eth0: GMAC reset complete
Dec 31 18:00:18 alarm kernel: [ 13.140000] eth0: Setting Rx flow control thresholds for LAN port
Dec 31 18:00:18 alarm kernel: [ 13.690000] eth0: PHY is Realtek RTL8211D, type 0x001cc914
Dec 31 18:00:18 alarm kernel: [ 14.190000] eth0: link down
Dec 31 18:00:18 alarm kernel: [ 16.150000] ADDRCONF(NETDEV_UP): eth0: link is not ready
Dec 31 18:00:18 alarm dhcpcd[739]: version 5.6.3 starting
Dec 31 18:00:18 alarm dhcpcd[739]: eth0: waiting for carrier

even with the ethernet cable connected the message is always the same, something seems to hang during boot, the green LED turns off nic of a second and then comes back on fixed while the orange flashes abnormally, with long periods when it is off, I can not figure out if the correct drivers are loaded.
emax20000
 
Posts: 9
Joined: Sun Apr 21, 2013 7:22 pm

Re: [How-To] Boot Entirely from SATA

Postby glombus » Sun Apr 28, 2013 10:14 pm

This post was originally going to be a plea for help, but after serveral days I FINALLY got this working on both my POGOPLUG PRO and POGO-P21.

Posting exactly what I did in case it helps anyone else.

Using a 160GB spindle SATA drive. No enclosure. Power coming from my desktop power supply (I'll get a better long term power source later). These instructions worked to get me a bootable environment on both the PRO and P21. The .nopci worked for both devices even though my PRO has a Mini PCI card.

The drive was sdf on my machine.

Code: Select all
#zero the drive
dd if=/dev/zero of=/dev/sdf

#confirm /dev/sdf has no partitions
sync && fdisk -l

#Download the tarball and verify md5sum.  b09ce58f93c79164c9dae0d62758be6c
#extract to a directory of my choosing on my desktop
tar -xzvf oxnas_sata_boot.tgz

#update disk_create
sed -i 's;#disk=/dev/sdX;disk=/dev/sdf;g' disk_create

#update sym link
ln -sf uImages/uImage.nopci uImage

./disk_create

gnu dd 8.21 does NOT throw an error on my machine

Code: Select all
#I see "Building a new DOS disklabel..." after running this
fdisk -c=dos /dev/sdf

n
p
1
2048
+10M

#Then I make another partition starting at 22529 (the first one ends at 22528) that takes up the remainder of the disk

#write changes to disk
w

#re-run disk create
./disk_create

#format and label
mkfs.ext3 /dev/sdf2 && tune2fs -L "rootfs" /dev/sdf2

#mount, install rootfs, create mac_addr
mount /dev/sdf2 /mnt/random && cd /mnt/random && wget http://archlinuxarm.org/os/ArchLinuxARM-oxnas-latest.tar.gz && tar -xzvf ArchLinuxARM-oxnas-latest.tar.gz && echo "00:25:31:02:B7:8A" > /mnt/random/usr/local/mac_addr

#change dir, sync, unmount
cd / && sync && umount /mnt/random


Then I unplug the SATA cable connecting the drive to my desktop, plug in the SATA cable connecting the device to my P21, and boot up the P21.

I see the LED flash, I can hear the hard drive churn, and after about 8 seconds the LED goes dead. I don't see it getting a DHCP lease. However, I can see the NIC LED flashing. It's alive, but unable to communicate.

I pulled the power on the P21 and mounted the drive again on my desktop

So *this* is what finally got it working it seems.

Code: Select all
mount /dev/sdf2 /mnt/random
dd if=/mnt/random/boot/uImage.nopci of=/dev/sdf1 bs=512
sync
umount /mnt/random


Re-connected it to the P21. Booted. Worked. (yay)

The same drive boots on the Pro too. I haven't tested anything beyond booting and being able to SSH in, but for now, that's all I care about anyway.

Thanks Warhead and everyone for your instructions, time, and comments on this thread. I would never have gotten this going otherwise.

Image
glombus
 
Posts: 4
Joined: Fri Feb 10, 2012 5:06 am

Re: [How-To] Boot Entirely from SATA

Postby emax20000 » Tue Apr 30, 2013 8:46 am

Tank you glombus , now work , the problem was the the uImage , after the dd copy from /boot/uImage the pogoplug is resurrected whaaa.



glombus wrote:This post was originally going to be a plea for help, but after serveral days I FINALLY got this working on both my POGOPLUG PRO and POGO-P21.

Posting exactly what I did in case it helps anyone else.

Using a 160GB spindle SATA drive. No enclosure. Power coming from my desktop power supply (I'll get a better long term power source later). These instructions worked to get me a bootable environment on both the PRO and P21. The .nopci worked for both devices even though my PRO has a Mini PCI card.

The drive was sdf on my machine.

Code: Select all
#zero the drive
dd if=/dev/zero of=/dev/sdf

#confirm /dev/sdf has no partitions
sync && fdisk -l

#Download the tarball and verify md5sum. b09ce58f93c79164c9dae0d62758be6c
#extract to a directory of my choosing on my desktop
tar -xzvf oxnas_sata_boot.tgz

#update disk_create
sed -i 's;#disk=/dev/sdX;disk=/dev/sdf;g' disk_create

#update sym link
ln -sf uImages/uImage.nopci uImage

./disk_create

gnu dd 8.21 does NOT throw an error on my machine

Code: Select all
#I see "Building a new DOS disklabel..." after running this
fdisk -c=dos /dev/sdf

n
p
1
2048
+10M

#Then I make another partition starting at 22529 (the first one ends at 22528) that takes up the remainder of the disk

#write changes to disk
w

#re-run disk create
./disk_create

#format and label
mkfs.ext3 /dev/sdf2 && tune2fs -L "rootfs" /dev/sdf2

#mount, install rootfs, create mac_addr
mount /dev/sdf2 /mnt/random && cd /mnt/random && wget http://archlinuxarm.org/os/ArchLinuxARM-oxnas-latest.tar.gz && tar -xzvf ArchLinuxARM-oxnas-latest.tar.gz && echo "00:25:31:02:B7:8A" > /mnt/random/usr/local/mac_addr

#change dir, sync, unmount
cd / && sync && umount /mnt/random


Then I unplug the SATA cable connecting the drive to my desktop, plug in the SATA cable connecting the device to my P21, and boot up the P21.

I see the LED flash, I can hear the hard drive churn, and after about 8 seconds the LED goes dead. I don't see it getting a DHCP lease. However, I can see the NIC LED flashing. It's alive, but unable to communicate.

I pulled the power on the P21 and mounted the drive again on my desktop

So *this* is what finally got it working it seems.

Code: Select all
mount /dev/sdf2 /mnt/random
dd if=/mnt/random/boot/uImage.nopci of=/dev/sdf1 bs=512
sync
umount /mnt/random


Re-connected it to the P21. Booted. Worked. (yay)

The same drive boots on the Pro too. I haven't tested anything beyond booting and being able to SSH in, but for now, that's all I care about anyway.

Thanks Warhead and everyone for your instructions, time, and comments on this thread. I would never have gotten this going otherwise.

Image
emax20000
 
Posts: 9
Joined: Sun Apr 21, 2013 7:22 pm

Re: [How-To] Boot Entirely from SATA

Postby ianlchen » Mon Jun 10, 2013 12:55 am

Hello,

I tried to download the tarball from http://ppl.ug/r1LnA0CT83U/, but there is nothing to download in the page. Could anyone please post the file? Thanks a lot.
ianlchen
 
Posts: 2
Joined: Mon Jun 10, 2013 12:26 am

Re: [How-To] Boot Entirely from SATA

Postby emax20000 » Mon Jun 10, 2013 9:34 am

emax20000
 
Posts: 9
Joined: Sun Apr 21, 2013 7:22 pm

Re: [How-To] Boot Entirely from SATA

Postby ianlchen » Tue Jun 11, 2013 2:39 am

@emax20000
Thanks a lot! I got the file.
ianlchen
 
Posts: 2
Joined: Mon Jun 10, 2013 12:26 am

Re: [How-To] Boot Entirely from SATA

Postby lijianch » Tue Jun 18, 2013 11:34 pm

I did follow the instruction on my pogoplug pro B02 pink model. I use a direct SATA connection to the PCB and no enclosure involved.

But, the light is solid which is a good sign. No dhcp client dected in my network. Any thought?
lijianch
 
Posts: 5
Joined: Tue Jun 18, 2013 11:29 pm

Re: [How-To] Boot Entirely from SATA

Postby WarheadsSE » Wed Jun 19, 2013 2:18 pm

Hook up a serial, find out.
Core Developer
Remember: Arch Linux ARM is entirely community donation supported!
WarheadsSE
Developer
 
Posts: 6807
Joined: Mon Oct 18, 2010 2:12 pm

PreviousNext

Return to Community Supported

Who is online

Users browsing this forum: No registered users and 3 guests