If you hit any problems with this please post back with any error messages.
CRASHPLAN CONNECTING TO BACKUP DESTINATION PC
Hopefully, the PC will now shutdown and/or restart without hanging. Your CIFS mount should be visible and will show the contents when accessed either via a terminal or via the Nautilus GUI file manager. NAS -fstype=cifs,rw,uid=1000,gid=1000 ://192.168.0.32/Volume_1Īutofs should now be running and if the PC is shutdown or restarted this service should start automatically. Open (as root) new file /etc/auto.misc eg.Īdd a line at the end for your mount directory in a similar format to your /etc/fstab file eg: Save the file with Ctrl-o and exit with Ctrl-x. Remove this if you prefer to only see the directory when you enter the path to the mounted directory. The "ghost" option ensures that even unmounted directories are always visible. Note that you can change the mount directory to one of your choice. Open (as root) new file /etc/auto.master eg.Īssuming that you want the mounted directories under /media, add the following line at the end: Save the edited file with Ctrl-o and exit nano with Ctrl-x. This line can then easily be re-enabled if required by editing and removing the "#". "comment-out" your existing CIFS mount(s) by adding a "#" at the start of the relevant line. Open (as root) the existing /etc/fstab file eg. 192.168.0.32/Volume_1/ /media/NAS cifs guest,uid=1000,gid=1000 0 0ĭocJ: I suggest you try the following but I must give the caveat that, as I only use Linux systems, I have no direct experience of Microsoft's SMB or CIFS. # swap was on /dev/sda5 during installation
# /home was on /dev/sda6 during installation # that works even if disks are added and removed. # device this may be used with UUID= as a more robust way to name devices # Use 'blkid' to print the universally unique identifier for a Thanks for your offer, I guess you only needed the last line, but just in case.Īs far as mutual time zone, I'm -5:00 from you I beleive. Gvfs-fuse-daemon on /root/.gvfs type fuse.gvfs-fuse-daemon (rw,nosuid,nodev) Gvfs-fuse-daemon on /home/jlr/.gvfs type fuse.gvfs-fuse-daemon (rw,nosuid,nodev,user=jlr) None on /run/shm type tmpfs (rw,nosuid,nodev) None on /run/lock type tmpfs (rw,noexec,nosuid,nodev,size=5242880) Tmpfs on /run type tmpfs (rw,noexec,nosuid,size=10%,mode=0755) Udev on /dev type devtmpfs (rw,mode=0755)ĭevpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=0620) None on /sys/kernel/security type securityfs (rw) None on /sys/kernel/debug type debugfs (rw) None on /sys/fs/fuse/connections type fusectl (rw) Sysfs on /sys type sysfs (rw,noexec,nosuid,nodev) Proc on /proc type proc (rw,noexec,nosuid,nodev) dev/sda1 on / type ext4 (rw,errors=remount-ro) The ones that start with INFO: task alternate between:
The ones that start with echo 0 all end with: proc/sys/kernel/hung_task_timeout_sec''disables this message. ( 239.650252) ''echo 0 proc/sys/kernel/hung_task_timeout_sec''disables this message. Then there's a bunch of lines with a new one every 120 seconds ( I wont type them all but a few: Speed-dispatcher disabled edit /etc/default/speech-dispatcher *Stopping System V runlevel compatibilityĬhecking for running unattended-upgrades: Starting CrashPlan Engine.Stopping anac(h)ronistic cron *Starting regular background program processing daemon I need to type this from my other computer, but this is what I see on Ubuntu at the top left: I force shut down, and the I can start the computer normally, but if I redo a restart, again, it hangs before shtting down at the black and white screen again I restart the computer and it stops on a black screen with lots of white writing, with an extra line every 120 seconds I edited fstab, then tested the mount but there was no output
0 kommentar(er)
