Hey Jimmy,
now everything works and I found the source of this misery.
But step by step: Here are my results after I appended the line in fstab you recommended.
Code: Select all
pi@Raspi2HBB:~ $ dmesg | grep mount
[ 2.115018] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
[ 2.138444] devtmpfs: mounted
[ 3.671675] systemd[1]: Starting media-smbFNAS.automount.
[ 3.702997] systemd[1]: Set up automount media-smbFNAS.automount.
[ 3.739522] systemd[1]: Starting Arbitrary Executable File Formats File System Automount Point.
[ 3.759152] systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point.
[ 6.076840] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
[ 10.747545] CIFS VFS: cifs_mount failed w/return code = -101
[ 10.839224] CIFS VFS: cifs_mount failed w/return code = -101
2nd step
Code: Select all
pi@Raspi2HBB:~ $ df -h
Dateisystem Größe Benutzt Verf. Verw% Eingehängt auf
/dev/root 7,2G 4,8G 2,1G 70% /
devtmpfs 412M 0 412M 0% /dev
tmpfs 416M 0 416M 0% /dev/shm
tmpfs 416M 6,0M 410M 2% /run
tmpfs 5,0M 4,0K 5,0M 1% /run/lock
tmpfs 416M 0 416M 0% /sys/fs/cgroup
//192.168.178.1/fritz.nas/ST310005-28AS-01 2,0T 84G 1,9T 5% /media/smbFNAS
/dev/mmcblk0p1 60M 20M 41M 34% /boot
tmpfs 84M 0 84M 0% /run/user/1000
3rd step
Code: Select all
pi@Raspi2HBB:~ $ sudo mount -a
mount error(16): Device or resource busy
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
Code: Select all
pi@Raspi2HBB:~ $ df -h
Dateisystem Größe Benutzt Verf. Verw% Eingehängt auf
/dev/root 7,2G 4,8G 2,1G 70% /
devtmpfs 412M 0 412M 0% /dev
tmpfs 416M 0 416M 0% /dev/shm
tmpfs 416M 6,0M 410M 2% /run
tmpfs 5,0M 4,0K 5,0M 1% /run/lock
tmpfs 416M 0 416M 0% /sys/fs/cgroup
//192.168.178.1/fritz.nas/ST310005-28AS-01 2,0T 84G 1,9T 5% /media/smbFNAS
/dev/mmcblk0p1 60M 20M 41M 34% /boot
tmpfs 84M 0 84M 0% /run/user/1000
I must admit that I first did all what you asked for and copied it - without thinking.
Later I looked into the results and recogniced that the NAS HDD must have been connected because the data regarding that NAS HDD were right!
Then I did a reboot and everything was there where it should be.
But to be honest: I really do not know, what the trick was to make it happen.
Therefore I will remove all the other things which might have been changed and are no longer needed like that rc.local stuff.
Meanwhile I removed the rc.local stuff and it still works.
I asked myself what went wrong and it could be that all my problems were the result of a tiny difference: a result of a copy and paste action from another web page I assume
And you also used the fstab commandline in 2 different syntax
username=123
user=123
Username does not work - at least in fstab, but user does work.
That I found out when I checked my "Ras Pi Master Setup Recipe" from where the hell I got all these problems because at the beginning of easter saturday everything worked fine until I came across this site while I was trying to establish a guest / user share mode. It was late a night when my pi suddenly did not reboot and the next morning I had forgotten what I had exactly changed at last, the changes of my previously working "mount line" in fstab were gone because I forget to use # and deleted that line that had been working before:
https://rasspberrypi.wordpress.com/2012 ... pberry-pi/
There you will find these lines:
2.1 Guest Share
sudo mount -t cifs -o guest //WindowsPC/share1 /mnt/mountfoldername
Tip: If your share has space then run the following command, notice the quotes
sudo mount -t cifs -o guest "//WindowsPC/Share 1" /mnt/mountfoldername
2.2 Password Protected Share
sudo mount -t cifs -o username=yourusername,password=yourpassword //WindowsPC/share1 /mnt/mountfoldername
And I can tell you that you can kill your Ras Pi Installation if fstab content is wrong. At least 3 or 4 times I had to reinstall the whole thing ... and reboot .
Many, many thanks for your constant support the last few days.
