I tried your script as-is but it didn't work. It wouldn't capture ifconfig's exit status of 1. I don't know why. I could clearly see the exit status was 1 when testing it in my bash shell. I experimented with a few variations and wound up rewriting the test a bit differently, but it works. Here's my rc.local: echo none > /sys/class/leds/dockstar\:orange\:miscby kraqh3d - Debian
Hey bastel, thanks. I like your rc.local script. I'm definitely going to use it. I worked around this by modifying 75-persistent-net-generator.rules, commenting out the line that executes write_net_rules. But I prefer to leave the base debian installation as un-altered as possible.by kraqh3d - Debian
I;m curious about the conversion from ext2 to ext3 of the root file system as I've been considering this... Was it as simple as running "tune2fs -j /dev/sda1" and updating /etc/fstab ? Or were some other steps ? (Other than remounting the filesystem read-only before creating the journal.) Some old instructions found online about converting the root file system included aby kraqh3d - Debian
The usb_scan "function" runs through all the usb ports in a fixed order (until it can e2load /boot/uImage) and assigns that disk a device id based on the it's port. This is then device is passed to the kernel as the root parameter. The problem is that when the kernel boots, it can identify the devices in a different order, making the kernel load the root file system from the wronby kraqh3d - Debian
I went through all these gyrations a while back, and detailed the process in this thread. http://forum.doozan.com/read.php?2,3910 Jump to the second page, and look for a message from me that says "Done!" at the top. It has everything you need. I've not changed anything in my setup since then. To summarize the thread, I create a udev rule to auto-mount any hot-plug'by kraqh3d - Debian
I know this is after the fact, but could you not simply have changed the U-boot "bootargs" environment variable to set "root=LABEL=rootfs" instead of "root=$usb_root"? That parameter should be passed to the initrd to locate using the udev symlink "/dev/disk/by-label/rootfs". (Looking at your U-bit output, you would to set root in set_bootargs line, whby kraqh3d - Debian
Your card likely has a corrupted filesystem. It's best to keep a backup image. While waiting for your CA42 cable, try this. It can't hurt... Boot up a computer with a linux live distro. It doesn't matter which. I prefer aptosid. But ubuntu will work just fine. Open a command window, and "sudo su -" to get root access. Connect your usb card reader, wait a minute,by kraqh3d - Debian
@thi You're coming up with eth1 because udev previsouly wrote an automatic rule that forces eth0 to match the mac address of your "working" dockstar. When you boot that same stick on another dockstar, that rule fails, so it adds a second rule for eth1. You can simply clone the usb stick and remove the udev rule file: "/etc/udev/rules.d/70-persistent-net.rules". Whenby kraqh3d - Debian
Thanks for the info. I'm going to wipe the swap partition and replace it with a swap file. And I am intimately aware of the autoclean issue... As it turned out, I was an Xbmc developer back from it's inception, when it only ran on the Xbox. If you look through the old svn commit logs, you'll find that I made change that defaulted the "cleanonupdate" option to falsby kraqh3d - Debian
How's the swap file working? I've noticed that swap is mounted by /etc/fstab from a direct device path, in my case /dev/sda2. The root partition is loaded from a symlink /dev/root that points to the boot device, which is not always /dev/sda1. (I'm not sure where this symlink is created. I think possibly by the uboot scripts.) The problem with this is that swap is only loadedby kraqh3d - Debian
I'm sorry but I don't. Another option would be to contact someone else with one, and ask them to image their bootup partition for you.by kraqh3d - Debian
Done! Below is my updated udev rule. It adds a device symlink of /dev/usb-storage/%E{name} where %E{name} is either the label or the device name if there's no label. (The SYMLINK directive is very particular. I found you can't just append it to any rule. I had to look at the base rules in /lib/udev/rules.d and compare. After wasting a lot of time on this, I decided it was just eby kraqh3d - Debian
Yes thats part of my plan as blkid provides all the information necessary to mount the filesystem. And by using very specific /dev symlinks for the usb found storage devices, I can generalize the script for use on some other linux boxes of mine. I'm also considering adding support for blacklist file that could be used to explicitly prevent a particular device from being mounted (by UUID orby kraqh3d - Debian
I don't have a GoFlex. I assume a blinking orange LED is bad? If so, and you're sure its not booted, then I think you have two choices... 1) build a console cable and change the arcNumber, or 2) build a custom kernel (or find one) and put it on your usb stick from another linux box.by kraqh3d - Debian
I have an idea how to address the boot up issue. I'm going to experiment with having that rule file also add some unique symlinks under /dev with the intention that a start up script can later go through them all and pmount them. It won't even matter if the script runs again because pmount will skip anything already mounted. I also need to verify if all mounted file systems are unmouby kraqh3d - Debian
I don't know about the GoFlex specifically but if it has a Pogoplug linux environment, and you can boot into that, you should be able to change the arcNumber from there. Both fw_printenv and fw_setenv should be available in /usr/bin. The u-boot installer puts them there.by kraqh3d - Debian
You can force udev to reload the rules after a change with "udevadm control --reload-rules". You can also log what udev sees with "udevadm monitor". You can additionally see all the attributes with "udevadm monitor --property". It's a lot of output. Hmmm. That should be mostly correct. I'm not using that rule. I've changed rules a few times sby kraqh3d - Debian
That rule change doesn't address the startup problem. It just passes the filesystem type to pmount, so it doesnt test every supported filesystem in succession until it finds the correct one (where ntfs is last in the list looking at the source.) I'm using it, though without that extra check for a blank filesystem type.by kraqh3d - Debian
I was looking at pmount's source, and it needed to have been built with blkid support to autodetect like mount. I'm not sure why it doesn't work. It could be that the debian packaged one wasnt.... But this doesn't matter. Udev can also pass the filesystem type since we're detecting the label with the blkid command line tool. Try this udev rule file. The filesystby kraqh3d - Debian
Ah, so you're using busybox-syslogd. Nice. I think I'm going to run it. It's kind of a pain not to have any logging. I wouldn't use usbmount. It has fixed mount points which are rather annoying. I want to know exactly where the filesystem is mounted. Why are you so concerned about pmount trying a bunch of filesystems in succession? It's not going to breakby kraqh3d - Debian
I don't have any logging enabled; no syslogd, klogd, logrotate, etc. I'm trying to keep my dockstar as slim as possible. I've been considering using busybox-syslogd though because its a bit harder to diagnose problems without a log. I see the note in the man page. Are you seeing messages about it trying to mount a bunch of different file systems in succession? Try adding --tby kraqh3d - Debian
Sorry I'm not following. Clearly a 15GB swap partition is silly, so use the 1GB partition for swap . The install script requires that partition1 is where debian boots from, and partition2 is swap.by kraqh3d - Debian
You might still be able to find it. It defaults with an IP address in the 169.254 range. See this: http://ahsoftware.de/dockstar/by kraqh3d - Debian
No, it's just to make sure you know what you're doing. The man page says --lazy, but when you try that you get this: root@debian:~# pumount --lazy WARNING: Lazy unmount are likely to jeopardize data integrity on removable devices. If that's what you really want, run pumount with --yes-I-really-want-lazy-unmount Aborting.by kraqh3d - Debian
The install leaves the Pogoplug Linux environment intact. The only thing it over writes is the u-boot. It installs a new one that will chain load the original u-boot if it can't find the debian root file system (which is on USB.) The u-boot, Pogoplug Linux, and the original u-boot are all on the NAND. If Pogoplug Linux isn't loading, then I can only presume you did something bad toby kraqh3d - Debian
The boot up thing will likely require a shell script. The standard udev rules that create the devices work. I can see them in /dev/disks/by-uuid and /dev/disks/by-label, etc. I may work up a shell script to go through them and mount them. Ah! Your unmount problem should be fixed by using the lazy unmount option. Pumount's lazy option is "--yes-I-really-want-lazy-unmount".by kraqh3d - Debian
I think it's "dpkg-reconfigure locale" or something like that. Google that as a starting point.by kraqh3d - Debian
Yeah... I had not rebooted my Dockstar since I set it up. I assumed that the uboot would always enumerate the rootfs stick as /dev/sda. I was wrong. I discovered that yesterday when I was updating my udev rules to use the file system label if present. This is my new udev rule. It uses blkid to get the label, and then it mounts it with the label as the mount point, or the device name if tby kraqh3d - Debian
It's hard to tell what's wrong if you can't watch the boot up. But all is not lost. Power it up without your debian stick, and it'll boot back into Pogoplug Linux. I'm pretty sure you can use fw_printenv and fw_setenv from Pogoplug Linux, so you should be able to set up network console like this thread: http://forum.doozan.com/read.php?3,14,14. Watching the boot seqby kraqh3d - Debian
Copy it on another linux system with dd. Pop it in your original but don't mount it. Also pop in a second larger one. Use dd to make a full image of the device (it'll copy both partitions, assuming you have the swap partition) to the new device, with dd if=/dev/sdb of=/dev/sdc. Just be damn sure you know which stick is which device so you don't copy the wrong way, overwriting yby kraqh3d - Debian