by rodgoslin » May 9th, '15, 02:11
As a follow up to my previous post, I've re-built the machine as a 32 bit setup, to check whehter this problem was 64 bit only, but the same problem persists. So,, unless things change with the final release, I have no contact with my bulk storage facility.
However, taking another tack, I tried invoking the Control Centre from the command line. Nothing changed, but I had the opportunity to add the password, in the command line, so I at least had an entry in /etc/fstab. But without the password entry. Adding the password to that entry, gave me a viable mount on boot. Doing the same with a Trasporter unit that I have proved a little more difficult, since the "Access Windows (SMB) Shared Drives" could not 'see' the Transporter unit. However, by copying the entry for the Drobo, with the required changes, gave me access to the Transporter, too. A word of advice for anyone trying this. The search for servers oin the "Access Windows (SMB) Drives, etc" finds only the server name, unless I'm missing something.. The mount will always fail, since the mount operation requires the IP address. So before you try it, you have to edit the /etc/hosts file to relate server name to IP address. Then it works. It's not the most elegant of work arounds, and hopefully will be sorted in the final release. But this situation is not something I would have expected in the release candidate. And before someone flames me for these comments. I'm a Production Engineering Desighner, by profession, and despite a number of years as the System Administrator, on a Solaris setup, after the UK decided it no longer wanted to make anything, I have little ability, or interest in writing software.To me the computer is simply a tool, and I expect it to work as well as the tolls that I used to design.