Hi Group. Let me start by saying that if I have posted this in the wrong location, please advise and I will delete and repost. I assumed this best fit my question.
I am brand new to the Linux system. I have a very tangential understanding so please bear with me on this.
I have an external hard drive by WD called MyCloud. It appears that sometimes when power gets cut off that problems occur with ownership as I use windows 8 and although I can see all the files on the drive, I do not have 'permission' to write to the disc.
With help from some others on a MyCloud forum, we determined that all of my files have somehow been made 'Read Only' (RO).
So it was suggested to do an unmount (umount) and then an e2fsck.
I assume one is to unmount the files and one to remount hopefully as read AND write.

*Heres the problem. I cant umount because some processed are 'busy'
I tried 'umount /dev/sda4 --force' but that didnt work.

So I entered 'lsof |grep sda4' and it showed (3) processes, all of which have the same PID#.
*Note, I have rebooted several times. each time the PID number for these 3 process changes, but still seems to be the same 3 processes.

Currently the processes are '5233' but as I said, that PID seems to change with each reboot. Of the 3 processes, one seems to be a cwd, rtd, and a txt process, all with the same 5233 PID#.

So I tried several ways to kill the 5233. I tried ''kill 5233, 'kill -15 5233', 'kill -9 5233'. No matter what I do, the 3 processes keep showing up in 'lsof |grep sda4'

After doing some more research, I tried to locate possible parent programs keeping 5233 from dieing with 'ps -Al'

I dont know for sure what im doing but in that list, I find the PID 5233 and the PPID (Parent PID??) I found a '2'.
So I tried everything I could to kill the 2 then the 5233 and nothing worked.

Please bear with this bull in a china shop regarding Linux programming. Can you help?

Floundering around will show you many things - some of which are interesting. Just stay away from --force and kill till you know what you are attempting to do. The system will protect itself most of the time (like here), but sometimes you'll do real damage.

My understanding is that mycloud is a NAS - how is it connected ?. Hopefully to your router. From a terminal enter this and post the output

1 members found this post helpful.

Hi syg,
Yes, I believe the mycloud is NAS. On my system, the mycloud is connected via ethernet cable to a network switch then by ethernet cable to my ATT Uverse router. Thank you for the advice about '--force'. I had actually tried that on advice from another group but it didnt work. I will be sure not to try it again.
The connection is shown here:
https://support.wdc.com/knowledgebas....aspx?ID=15086

I have backup, but its 2tb in 2 shoeboxes on cdrw, dvdrw and bd. Hoping I can get this thing writeable but if not, I have backup.

Here are 2 overlapping screenshots of 'df -hT'

Attached Thumbnails

   

And here is a screenshot of 'lsblk -f'

Attached Thumbnails

 

Can't help with the killing of the processes, but something to try for the not being able to unmount, try a umount -l /whatever/mount

1 members found this post helpful.

Hi Timothy,
It says "not found"

Are you doing -"ell" or -"capital eye"?

Should be -"ell" lazy umount. It's the cousin of --force that makes force look like a little child asking "please sir, might you unmount?"

1 members found this post helpful.

OK, that answers some q's but raises others. Those displays imply you are logged into the mycloud - say via ssh. Is that correct ?.
Do you have access to the mycloud GUI user interface from your Win8 system ?. If so the best way to do this is to disable NFS from the Win8 UI, then ssh in and do the fsck. Much cleaner and simpler.
Then go back to Win8 and re-enable NFS.

Note I have no experience with mycloud.

1 members found this post helpful.

Hi Timothy,
I copied the command from your posting.

Attached Thumbnails

 

Hi syg,
I access the MyCloud via a downloaded program called puTTY after enabling SSH via the MyCloud dashboard (MyCloud-control panel).
I did not know about GUI. *(note) I was using Windows 10, but the infernal 'Automated Updates' (which I had no way of stopping) frustrated me to no end. Even causing my computer to crash with the dreaded blue screen on several occasions, so I voluntarily went back to Win 8 (pro).

How do I disable NSF and utilize the GUI user interface? I'll Google it to start understanding how it works. (I'm good at googling)
Thank you

No, we are talking about the same thing - the dashboard. It should have a "Shares" option where you can turn NFS off. Then just use putty to get in and run the fsck.

You would replace /whatever/mount with whatever mount you're trying to unmount.

Apparently on this MyCloud, I do not have the dashboard option of turning on or off the NFS. Please bear with me as I am very very novice.
I checked and according to what I read on the WD website regarding the NFS, with my version of firmware and it being a single bay device (?), there is no option to turn NFS off or on in the dashboard itself.
From what I have gathered in troubleshooting this problem,after entering 'mount' I find that these things need to be umounted before the e2fsk can be done:
umount /DataVolume
umount /CacheVolume
umount /nfs/Public
umount /nfs/Media
umount /nfs/Username

But when I try to enter those commands, I get a message saying it is 'busy'
So when I run a 'dmesg | grep mount' I find that there are 3 processes running. these 3 processes have the same PID#. I have done a couple re-boots and each time those 3 processes' PID#'s change but the processes themselves seem to be the same.
Hence the 'kill'ing I was trying to do. I tried to kill those PID's but it didnt work.

Let me reiderate, from what I understand, the main problem here is that the sda4 is mounted as ro (read only). Im kind of have a grasp on that concept. Hence the necessity to umount and run the esfsk.

If this isn't making good sense I apologize, thanks for bearing with me.

Here is my output from 'mount'

Attached Thumbnails

         

Here is the output of 'dmesg | grep mount'

Attached Thumbnails