Can't Read Second Drive Since Last Update. (Not (Solved))

[Stephen]

On 14-09-03 11:36 PM, Stephen wrote:
> On 14-09-03 08:52 PM, Francis (Grizzly) Smit wrote:
>> On 04/09/14 05:14, Stephen wrote:
>>> I updated my Ubuntu 12.04 this morning.
>>>
>>> Then I tried to copy files from my main drive to the second drive in 
>>> the
>>> box.
>>>
>>> I got this error;
>>> Error splicing file: Input/output error
>>>
>>> Then I couldn't even read from my second drive.
>>>
>>> I got suspicious because, it was just after an update, and I never had
>>> any trouble with the drive before.
>>>
>>> I checked both drives a couple of days ago and they were functioning
>>> fine. The second drive is formated NTFS, but I don't have windows on my
>>> system, except in a virtual box.
>>>
>>> I restarted my system and then I could read from the second drive so 
>>> I tried
>>> gksudo nautilus.
>>>
>>> I could read the second drive so I tried to copy files from my main 
>>> hard
>>> drive and I got these messages in the terminal after I exited nautilus;
>>>
>>> Initializing nautilus-gdu extension
>>> Shutting down nautilus-gdu extension
>>> Error loading document: Error opening file: Permission denied
>>> Error loading document: Error opening file: Permission denied
>>> Error loading document: Error opening file: Permission denied
>>>
>>> ** (nautilus:2823): WARNING **: Could not inhibit power management:
>>> GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name
>>> "org.gnome.SessionManager" does not exist
>>>
>>> ** (nautilus:2823): WARNING **: Could not inhibit power management:
>>> GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name
>>> "org.gnome.SessionManager" does not exist
>>>
>>> ** (nautilus:2823): WARNING **: Could not inhibit power management:
>>> GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name
>>> "org.gnome.SessionManager" does not exist
>>>
>>> I restarted my system and am coping all the information from my second
>>> drive to an External 1 terrabyte drive.
>>>
>>>
>> My recommendation open a terminal and use "sudo -i" to become root 
>> then try looking a5t the drive, it sounds like the owner is set to 
>> something diff from your user try "ls -l <path to files>" or just "ls 
>> -l <path to drive>" if the user and group are wrong try
>> chown -R <your user>.<your group> <path to drive>
>>
>> hope that helps
>>
>>
>>
> Thank you Francis.
>
> When I got the listing it said the stephen stephen then the file entry 
> for that spot, but it still didn't work When I did the chown -R 
> stephen.stephen then I could copy files to and from the drive.
>
> I have complete control of the drive.
>
> Thanks a lot;
> Stephen
>
After a couple of minutes it stoped copping from the main drive and gave 
me the message of no permission to write, but in the mean time it had 
already written a directory with several files in it.

I didn't have this problem until I updated to the new kernal for Ubuntu 
12.04 lts.

I considered upgrading to 14.04 but I have the old AMD graphics card, 
and have the driver locked so it won't update.

If I switch to Ubuntu 14.04 an I going to have the same problem with the 
graphics accelerator.

Thanks in advance;
Stephen.