[How-To] Boot Entirely from SATA

This forum is for all other ARMv5 devices

Re: [How-To] Boot Entirely from SATA

Postby WarheadsSE » Mon Mar 12, 2012 2:47 pm

The instructions on how I compiled, patches, my configs, are all present on this forum.
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 mazman2010 » Mon Mar 12, 2012 5:00 pm

$this->bbcode_second_pass_quote('WarheadsSE', 'T')he instructions on how I compiled, patches, my configs, are all present on this forum.


I see the instructions on how to compile a kernel/uboot...but nothing about using them on the SATA boot method. I am guessing that once I get those compiled...I can just simply edit your script to copy the new images to the first partition?
mazman2010
 
Posts: 2
Joined: Mon Mar 12, 2012 2:08 pm

Re: [How-To] Boot Entirely from SATA

Postby WarheadsSE » Mon Mar 12, 2012 5:48 pm

Image



Precisely. There is no magic in my script, and it's fairly self-explanatory.
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 ldi9999 » Sat Mar 17, 2012 3:46 am

I followed the guild and was able to complete successfully. The unit booted normally and I was able to ssh into the box.
However, after I ran "pacman -Syu" and updated system. It won't boot any more. The indicator flashed about 10-15 seconds and then turned off. I was not able to ssh into it anymore. Any idea? Thanks.

Update: I restored original files on rootfs and unit is working now. It seems the problem was on "pacman -Syu" update. I would hold on updating until I got confirmation on what to do. By the way, the line to ignore updating initscripts is in the pacman.conf.

Update2: After restore the original rootfs, the unit was working. I did not do any update. Then I tried install samba. I believe the installation went through some kind of system update as well. So the unit had the same issue "Blinking for 15 seconds and then turned off" after the installation.

Please help! Basically I cannot use the unit at all since I was planning to use samba and minidlna.

Thanks!

Not sure if this help:
$this->bbcode_second_pass_code('', '
Mar 17 23:09:21 alarm ntpd[967]: set local clock to Sat Mar 17 23:09:21 CDT 2012 (offset 1332043742.039755s)
Mar 17 23:09:22 alarm dhcpcd[932]: eth0: sending IPv6 Router Solicitation
Mar 17 23:09:23 alarm kernel: [ 21.870000] eth0: no IPv6 routers present
Mar 17 23:09:26 alarm dhcpcd[932]: eth0: sending IPv6 Router Solicitation
Mar 17 23:09:26 alarm dhcpcd[932]: eth0: no IPv6 Routers available
Mar 17 23:12:01 alarm udevd[355]: can not find '/lib/udev/rules.d/75-net-description.rules': No such file or directory
Mar 17 23:12:01 alarm udevd[355]: can not find '/lib/udev/rules.d/75-probe_mtd.rules': No such file or directory
Mar 17 23:12:01 alarm udevd[355]: can not find '/lib/udev/rules.d/75-tty-description.rules': No such file or directory
Mar 17 23:12:01 alarm udevd[355]: can not find '/lib/udev/rules.d/78-sound-card.rules': No such file or directory
Mar 17 23:12:01 alarm udevd[355]: can not find '/lib/udev/rules.d/80-drivers.rules': No such file or directory
Mar 17 23:12:01 alarm udevd[355]: can not find '/lib/udev/rules.d/81-arch.rules': No such file or directory
Mar 17 23:12:01 alarm udevd[355]: can not find '/lib/udev/rules.d/95-keyboard-force-release.rules': No such file or directory
Mar 17 23:12:01 alarm udevd[355]: can not find '/lib/udev/rules.d/95-keymap.rules': No such file or directory
Mar 17 23:12:12 alarm init: Trying to re-exec init
Mar 17 23:13:02 alarm udevd[355]: IMPORT{builtin}: 'blkid --offset=$env{ID_CDROM_MEDIA_SESSION_LAST_OFFSET}' unknown /lib/udev/rules.d/60-persistent-storage.rules:70
Mar 17 23:13:02 alarm udevd[355]: IMPORT{builtin}: 'blkid --noraid' unknown /lib/udev/rules.d/60-persistent-storage.rules:73
Mar 17 23:13:02 alarm udevd[355]: IMPORT{builtin}: 'blkid' unknown /lib/udev/rules.d/60-persistent-storage.rules:76
Mar 17 23:13:02 alarm udevd[355]: IMPORT{builtin}: 'usb-db' unknown /lib/udev/rules.d/75-net-description.rules:7
Mar 17 23:13:02 alarm udevd[355]: IMPORT{builtin}: 'pci-db' unknown /lib/udev/rules.d/75-net-description.rules:11
Mar 17 23:13:02 alarm udevd[355]: IMPORT{builtin}: 'kmod load sm_ftl' unknown /lib/udev/rules.d/75-probe_mtd.rules:6
Mar 17 23:13:02 alarm udevd[355]: IMPORT{builtin}: 'usb-db' unknown /lib/udev/rules.d/75-tty-description.rules:7
Mar 17 23:13:02 alarm udevd[355]: IMPORT{builtin}: 'pci-db' unknown /lib/udev/rules.d/75-tty-description.rules:11
Mar 17 23:13:02 alarm udevd[355]: IMPORT{builtin}: 'usb-db' unknown /lib/udev/rules.d/78-sound-card.rules:41
Mar 17 23:13:02 alarm udevd[355]: IMPORT{builtin}: 'pci-db' unknown /lib/udev/rules.d/78-sound-card.rules:44
Mar 17 23:13:02 alarm udevd[355]: IMPORT{builtin}: 'kmod load $env{MODALIAS}' unknown /lib/udev/rules.d/80-drivers.rules:5
Mar 17 23:13:02 alarm udevd[355]: IMPORT{builtin}: 'kmod load tifm_sd' unknown /lib/udev/rules.d/80-drivers.rules:6
Mar 17 23:13:02 alarm udevd[355]: IMPORT{builtin}: 'kmod load tifm_ms' unknown /lib/udev/rules.d/80-drivers.rules:7
Mar 17 23:13:02 alarm udevd[355]: IMPORT{builtin}: 'kmod load ms_block mspro_block' unknown /lib/udev/rules.d/80-drivers.rules:8
Mar 17 23:13:02 alarm udevd[355]: IMPORT{builtin}: 'kmod load i2o_block' unknown /lib/udev/rules.d/80-drivers.rules:9
Mar 17 23:13:02 alarm udevd[355]: IMPORT{builtin}: 'kmod load ppdev' unknown /lib/udev/rules.d/80-drivers.rules:10
Mar 17 23:13:02 alarm udevd[355]: IMPORT{builtin}: 'firmware' unknown /lib/udev/rules.d/50-udev-default.rules:107
Mar 17 23:13:02 alarm udevd[355]: IMPORT{builtin}: 'blkid --offset=$env{ID_CDROM_MEDIA_SESSION_LAST_OFFSET}' unknown /lib/udev/rules.d/60-persistent-storage.rules:70
Mar 17 23:13:02 alarm udevd[355]: IMPORT{builtin}: 'blkid --noraid' unknown /lib/udev/rules.d/60-persistent-storage.rules:73
Mar 17 23:13:02 alarm udevd[355]: IMPORT{builtin}: 'blkid' unknown /lib/udev/rules.d/60-persistent-storage.rules:76
Mar 17 23:13:02 alarm udevd[355]: IMPORT{builtin}: 'usb-db' unknown /lib/udev/rules.d/75-net-description.rules:7
Mar 17 23:13:02 alarm udevd[355]: IMPORT{builtin}: 'pci-db' unknown /lib/udev/rules.d/75-net-description.rules:11
Mar 17 23:13:02 alarm udevd[355]: IMPORT{builtin}: 'kmod load sm_ftl' unknown /lib/udev/rules.d/75-probe_mtd.rules:6
Mar 17 23:13:02 alarm udevd[355]: IMPORT{builtin}: 'usb-db' unknown /lib/udev/rules.d/75-tty-description.rules:7
Mar 17 23:13:02 alarm udevd[355]: IMPORT{builtin}: 'pci-db' unknown /lib/udev/rules.d/75-tty-description.rules:11
Mar 17 23:13:02 alarm udevd[355]: IMPORT{builtin}: 'usb-db' unknown /lib/udev/rules.d/78-sound-card.rules:41
Mar 17 23:13:02 alarm udevd[355]: IMPORT{builtin}: 'pci-db' unknown /lib/udev/rules.d/78-sound-card.rules:44
Mar 17 23:13:02 alarm udevd[355]: IMPORT{builtin}: 'kmod load $env{MODALIAS}' unknown /lib/udev/rules.d/80-drivers.rules:5
Mar 17 23:13:02 alarm udevd[355]: IMPORT{builtin}: 'kmod load tifm_sd' unknown /lib/udev/rules.d/80-drivers.rules:6
Mar 17 23:13:02 alarm udevd[355]: IMPORT{builtin}: 'kmod load tifm_ms' unknown /lib/udev/rules.d/80-drivers.rules:7
Mar 17 23:13:02 alarm udevd[355]: IMPORT{builtin}: 'kmod load ms_block mspro_block' unknown /lib/udev/rules.d/80-drivers.rules:8
Mar 17 23:13:02 alarm udevd[355]: IMPORT{builtin}: 'kmod load i2o_block' unknown /lib/udev/rules.d/80-drivers.rules:9
Mar 17 23:13:02 alarm udevd[355]: IMPORT{builtin}: 'kmod load ppdev' unknown /lib/udev/rules.d/80-drivers.rules:10
Dec 31 18:00:44 alarm udevd[355]: unable to receive ctrl connection: Function not implemented
Dec 31 18:00:44 alarm udevd[355]: unable to receive ctrl connection: Function not implemented
Dec 31 18:00:44 alarm udevd[355]: unable to receive ctrl connection: Function not implemented
Dec 31 18:00:44 alarm udevd[355]: unable to receive ctrl connection: Function not implemented
')
Last edited by WarheadsSE on Mon Mar 19, 2012 3:59 pm, edited 1 time in total.
Reason: CODE TAGS
ldi9999
 
Posts: 59
Joined: Mon Mar 05, 2012 10:31 pm

Re: [How-To] Boot Entirely from SATA

Postby WarheadsSE » Mon Mar 19, 2012 4:00 pm

Sounds like you need to make sure you get an updated rootfs tarball.

Also, to fix the udev problem (massively documented in this forum) `pacman -Sy udev-oxnas`

Look at the /etc/pacman.conf from the latest tarball to prevent it from upgrading initscripts.
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 ldi9999 » Mon Mar 19, 2012 4:06 pm

$this->bbcode_second_pass_quote('WarheadsSE', 'S')ounds like you need to make sure you get an updated rootfs tarball.

Also, to fix the udev problem (massively documented in this forum) `pacman -Sy udev-oxnas`
Do I run it after system update?


Look at the /etc/pacman.conf from the latest tarball to prevent it from upgrading initscripts.

I did. I downloaded it from the link in your 1st post. I verified that the initscripts was igonored in the config file. I also saw the message saying it was ignored while doing the update.

Also, to fix the udev problem (massively documented in this forum) `pacman -Sy udev-oxnas`
Do I run it after system update?
ldi9999
 
Posts: 59
Joined: Mon Mar 05, 2012 10:31 pm

Re: [How-To] Boot Entirely from SATA

Postby WarheadsSE » Mon Mar 19, 2012 4:09 pm

Actually, I would do that first, and it should already be present in the oxnas tarball of late.
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 ldi9999 » Mon Mar 19, 2012 4:16 pm

$this->bbcode_second_pass_quote('WarheadsSE', 'A')ctually, I would do that first, and it should already be present in the oxnas tarball of late.


I'll give it a try tonight. Here is what I was planning to do:
1. Restore the original rootfs & mac_addr.
2. Reboot system and make sure it's in working condition
3. Run "pacman -Sy udev-oxnas"
4. Run "pacman -Syu"
5. Reboot

Please advise if it looks ok. If I still have the same issue, what steps need to be taken? Which log file should I take a look?

Thanks!
ldi9999
 
Posts: 59
Joined: Mon Mar 05, 2012 10:31 pm
Top

Re: [How-To] Boot Entirely from SATA

Postby ldi9999 » Tue Mar 20, 2012 5:16 pm

Update:
"pacman -Sy udev-oxnas" did the trick. It's working now after updates.
Thank you WarheadsSE!

Bad news is, I tried to copy about 300GB of my videos from another HD to the one attached to Pogoplug last night. I think copy was completed but the hard drive is making a very loud noise even without read/write activities. I guess the hard drive is having problem now. This definitely has nothing to do with the software though. Well, I guess I need to contact the manufacturer for warranty. :cry:

One more question. Is there a way to spin down the HD after certain time without using?
ldi9999
 
Posts: 59
Joined: Mon Mar 05, 2012 10:31 pm

Re: [How-To] Boot Entirely from SATA

Postby WarheadsSE » Tue Mar 20, 2012 8:25 pm

look into hdparm
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 8 guests