Print

[NewIT_Marcus]

OK, belatedly, some quite basic stuff:

The eSATA slot is /dev/sda

The mini-SD card device is /dev/sdc

When there are no USB devices connected to the Guruplug, the first device connected (in either slot) becomes /dev/sdd. A second USB device becomes /dev/sde.

I haven't tested all possible combinations of having devices dis/connected, but this should be a start. On the Sheevaplug the (full size) SD card is /dev/mmcblk0 (and partitions are /dev/mmcblk0p1 and /dev/mmcblk0p2; on the Guruplug it's more conventional.

[rmentjens]

Hey Markus.

Im not trying to be a wiseguy. (in fact i am very confused)

but df -h tells me:

sheevaplug-debian:~# df -h
Filesystem            Size  Used Avail Use% Mounted on
tmpfs                 251M     0  251M   0% /lib/init/rw
udev                   10M  724K  9.3M   8% /dev
tmpfs                 251M  4.0K  251M   1% /dev/shm
rootfs                463M  205M  258M  45% /
tmpfs                 251M     0  251M   0% /var/cache/apt
/dev/sdb1             7.5G   32K  7.5G   1% /media/usb0
sheevaplug-debian:~#


where my uSD card is /dev/sdb1

[NewIT_Marcus]

Thanks for the info. Only time will tell what is predictable and stable with regard to device assignments.

[varkey]

I noticed that if I connect my eSata disk after the Guruplug has booted, the disk is assigned /dev/sdc whereas if I connect the disk before switching on the device its assigned /dev/sda

[punaniac]

I have recently upgraded to kernel 2.6.34.

Now the µSD card always comes up as /dev/sdb, while the eSATA drive always gets assigned /dev/sdc. It doesn't matter if the eSATA drive is connected on boot or hot-plugged. I'm not using an initrd, though, which could probably change this behaviour.

best regards,
Andreas

[mola]

I have recently upgraded to kernel 2.6.34.

Now the µSD card always comes up as /dev/sdb, while the eSATA drive always gets assigned /dev/sdc. It doesn't matter if the eSATA drive is connected on boot or hot-plugged. I'm not using an initrd, though, which could probably change this behaviour.

Hi,

same here with Kernel 2.6.33.2. Behaviour changed when I started to boot from a uSDHC card.
Booting from NAND: eSata=sda / uSDHC=sdc
Booting from uSDHC: eSata=sdc / uSDHC=sdb

Have not changed anything else, i.e. still running the same system, have just copied things to the uSDHC card and changed environment to boot from there.

Best
mola