Trouble with SAMBA + udevil

[fox1986]

This is what I have done so far:

- Installed ArchLinux on my Pogoplug E02
- OS is on USB Flashdrive and booted with echo "LABEL=ROOTFS / ext3 rw,noatime 0 1" >> /etc/fstab


This is what I wanna do:

- Install SAMBA so I can access my attached NTFS Harddsik within the network
- Combine SAMBA with udevil, so that attached devices are automatically mounted and provided by SAMBA
- When I switch of Pogoplug, and swith it on again, I want the plug to boot and mount all attached device and make them accesible via SAMBA again.

I know how to setup Samba, however I have no idea how to combine udevil with samba. Samba requires a smb.conf
with explicit information about each device and its path. But of course device and path change every time a new device
is attached

My second problem is that, since I installed udevil and activated tell him to automount on boot, my pogoplug fails to boot. I have to unplug my harddisk and reboot again. Whatever I do, once i reboot the device, everything seems to fail, while everything is running perfect as long as i reboot. Is that normal?

[moonman]

Attach your bootable flash to the bqck bottom usb port. Is your ntfs drive over 2tb?

[fox1986]

Ok I gave up on udevil since It seems to fail mounting my usb-harddisc. Once I removed the harddisc and the udevil service I can boot into archlinux again.

The phenomenom I have is:
Everytime I mount a device and start SAMBA, everything is fine. I can see the device in Windows and Linux and acces its data. But one I do a reboot or plug the system of, I cant access via ssh anymore and the pogoplug does not appear on my router-clientlist anymore. Only after removing the harddisk and boot with the system-usb, I can access again.

What do I do wrong? Everything went fine, but one reboot or restart of the plug destroys everything?

@moonman: no I tried a 1TB NTFS and a 4GB EXT3 so far. Same bad result. Does it change anything to plug it on the backside?

[WarheadsSE]

1) enable netconsole per the advanced tab, and get us some debug output
2) is the ntfs drive configured with a GPT partition table?
3) what is the order of disk detection in the kernel log, if it makes it that far.

[fox1986]

I plugged the usb-stick with ArchLinux now on the lower usb-slot on the back (its my 4th usb-stick now and this one actually is the only one that boots correctly).

I followed the guide here:
http://blog.qnology.com/2013/03/tutoria ... linux.html

I think the problem is the correct boot order of the two devices, since I can mount and access them via Samba
without problems, it just collapses on reboots.

My fstab looks like this:

LABEL=ROOTFS / ext3 rw,noatime 0 1
UUID=F474B7AA74B76DCC /media/wd ntfs-3g

ROOTFS is the USB-Stick running archLinux.
The UUID Entry is the one of my WD-Harddisk NTFS formatted.

Is there any way to tell that the ROOTFS schould boot first (since the OS is on there, and the Harddisk second?)

[grayman4hire]

Why do so many people insist on using ntfs drives with their pogoplug?

Just follow the tutorial and use ext3 and keep thing simple. I left out ntfs (and udevil) instructions intentionally.

[fox1986]

$this->bbcode_second_pass_quote('grayman4hire', 'W')hy do so many people insist on using ntfs drives with their pogoplug?

Just follow the tutorial and use ext3 and keep thing simple. I left out ntfs (and udevil) instructions intentionally.

$this->bbcode_second_pass_quote('fox1986', '')$this->bbcode_second_pass_quote('grayman4hire', 'W')hy do so many people insist on using ntfs drives with their pogoplug?

Just follow the tutorial and use ext3 and keep thing simple. I left out ntfs (and udevil) instructions intentionally.

[WarheadsSE]

With this in mind, I really want to see your boot log so that we can sort out exactly what is happening.