mount -t cifs -s -o username=family,password=*****,dir_mode=0777,file_mode=0777,iocharset=utf8 //192.168.80.129/F /mnt/device/75In fact, at the time when getting the mount failures, the drive is actually mounted successfully to a different mount point and I can see its content.

I googled the mount problem, and found some hints to possible kernel failure. dmesg shows the following error:

I unplugged the network drive, deleted the device from the device tree, rebooted the machine, and plugged back the network drive.After this the Orbiter behavior changed as follows:Video files: the data grid shows the video files as expected (see img1.jpg).Audio files: the data grid is empty (see img2.jpg). Only after I click on the "AB" button, it populates as expected (see img3.jpg)... (continued in next post)

... (continued from previous post)Image files: the data grid shows flickr and the local drive (see img4.jpg) but the files for the network drive don't show up.When searching for a file from the external drive it shows up (see img5.jpg) and the actual image displays when selecting a search result, but I cannot get the data grid to show the image files (I tried clicking arbitrarily on the letter buttons, e.g. on the "AB" button as I did for the audio files but the data grid still doesn't show the images from the external drive.

...cifs_read_super: get root inode failedcifs_read_super: get root inode failed...The reason I was getting the messages above (and all the other mount failures) was due to the samba service.These messages were swamping all terminals, and freezing the Orbiter (it wouldn't redraw and appear completely black).I stopped the service from starting at reboot by doing: