[ solved ] Unable to copy/delete/move files in file manager or via ftp

December 31st, 2011 Leave a comment Go to comments

Home › Forums › GeeXboX for PC › [ solved ] Unable to copy/delete/move files in file manager or via ftp

This topic has 3 voices, contains 22 replies, and was last updated by  tomlohave 7 days ago.

Viewing 15 posts - 1 through 15 (of 23 total)
Author Posts
Author Posts
December 27, 2011 at 13:49 #2367

hozzdutch

Basically, exactly as it says in the topic.
If I try to copy a file from a USB pen to HD from the file manager, it fails.
If i try and delete a file from USB or HD via the file manager it fails.
If I log into the FTP site and try and copy a file from one HD to another HD, it fails, or delete a file, it fails.

A little bit of background info -

This system used to be a Windows Media Centre PC.
The main drive c: is what I installed Geexbox to.
I have 4 other drives in there that contain my movies. These are the ones that don’t seem to work.
What is now the Geexbox drive (sorry, my linux terminology is non existant) is the only drive I can copy files to so it seems that the other drives have been set to read only.
How do I get about changing this using?

  • This reply was modified 7 days ago by  tomlohave.
December 27, 2011 at 14:59 #2368

tomlohave

that’s because your hardrives are mounted read-only (default)
you can remount them read-write if you want
adding this to /etc/fstab should work

December 27, 2011 at 23:56 #2370

hozzdutch

ok, thanks for that.

From my last post you answered, you probably read that I’m a beginner when it comes to Linux.
I get browse to and nano the fstab file, but I have no idea how to go about adding this drive into it, can you give me some guidance how to do this?
Will remounting wipe the drive or does it stay intact? I don’t know.
Thanks

December 28, 2011 at 02:58 #2374

tomlohave

beginners are welcome ;)
in a console : can you post the result of :
cat /proc/mounts

December 28, 2011 at 07:54 #2381

hozzdutch


rootfs / rootfs rw 0 0
/dev/sdd1 / ext4 rw,relatime,errors=remount-ro,barrier=1,data=ordered 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0
devtmpfs /dev devtmpfs rw,nosuid,relatime,size=1033980k,nr_inodes=220124,mode=755 0 0
tmpfs /dev/shm tmpfs rw,nosuid,nodev,relatime 0 0
devpts /dev/pts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0
tmpfs /run tmpfs rw,nosuid,nodev,relatime,mode=755 0 0
tmpfs /sys/fs/cgroup tmpfs rw,nosuid,nodev,noexec,relatime,mode=755 0 0
cgroup /sys/fs/cgroup/systemd cgroup rw,nosuid,nodev,noexec,relatime,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd 0 0
cgroup /sys/fs/cgroup/cpuset cgroup rw,nosuid,nodev,noexec,relatime,cpuset 0 0
cgroup /sys/fs/cgroup/cpu cgroup rw,nosuid,nodev,noexec,relatime,cpu 0 0
cgroup /sys/fs/cgroup/cpuacct cgroup rw,nosuid,nodev,noexec,relatime,cpuacct 0 0
cgroup /sys/fs/cgroup/memory cgroup rw,nosuid,nodev,noexec,relatime,memory 0 0
cgroup /sys/fs/cgroup/devices cgroup rw,nosuid,nodev,noexec,relatime,devices 0 0
cgroup /sys/fs/cgroup/freezer cgroup rw,nosuid,nodev,noexec,relatime,freezer 0 0
cgroup /sys/fs/cgroup/blkio cgroup rw,nosuid,nodev,noexec,relatime,blkio 0 0
systemd-1 /dev/hugepages autofs rw,relatime,fd=23,pgrp=1,timeout=300,minproto=5,maxproto=5,direct 0 0
systemd-1 /dev/mqueue autofs rw,relatime,fd=24,pgrp=1,timeout=300,minproto=5,maxproto=5,direct 0 0
fusectl /sys/fs/fuse/connections fusectl rw,relatime 0 0
tmpfs /tmp tmpfs rw,relatime 0 0
/dev/sde1 /mnt/SATA40Disk40#540120_Gig_IDE40(0) fuseblk ro,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other,blksize=4096 0 0
/dev/sda1 /mnt/SATA40Disk40#140backup40(0) fuseblk ro,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other,blksize=4096 0 0
/dev/sdb1 /mnt/SATA40Disk40#240Movies40(0) fuseblk ro,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other,blksize=4096 0 0

December 28, 2011 at 07:56 #2382

hozzdutch

I’m guessing a seasoned pro such as yourself has already picked out my read only drives at the bottom there - SDE1, SDA1 and SDB1

December 28, 2011 at 09:25 #2386

Koumi

OK, I’m not pro, but i’we done it by myself and it works:
edit /etc/fstab with vi to this:

/dev/sde1 /mnt/SATA40Disk40#540120_Gig_IDE40(0) ntfs rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other 0 0
/dev/sda1 /mnt/SATA40Disk40#140backup40(0) ntfs rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other 0 0
/dev/sdb1 /mnt/SATA40Disk40#240Movies40(0) ntfs rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other 0 0

But now, how do I force all removable devices to mount rw every time?

December 28, 2011 at 12:14 #2387

tomlohave

right you found it

for removable device :
can you test this : connect to a shell then execute :
systemctl stop automountd.service
plug your device, does it appaears under xbmc ?

December 28, 2011 at 12:20 #2388

hozzdutch

thanks Koumi, that appeared to work, but now after reboot it keeps entering emergency mode.
If I press control-D it then gives me the same message - Welcome to emergency mode. I tried another reboot but I can’t get out of this.
If I enter the root password, I tried to edit the fstab file again in case a change there made this happen but i can’t save it because it seems this drive has now changed to read only as well.

Whats’ going on here?

December 28, 2011 at 12:41 #2389

tomlohave

dmesg ?

December 28, 2011 at 12:48 #2390

Koumi

@Hozzdutch
Yes, that happens when one of the drives failed to mount by the line in fstab. First of all, delete all info in the fstab and leave it blank as it was. Reboot and you should be back to normal. Then go to shell and start again. After you modify your fstab again, execute mount -a to see, whether everything worked good. If it tells you to unmount: umount /dev/sda1 or like that. If no error appear during mount -a, you are ready to reboot. But it will give you some error now. Something like bad filesystem type or superblock. That means that one of the atributes in fstab are wrong. Maybe some drives are not ntfs, but vfat or something like that. Post me error message from the mount -a
Thx
@tomlohave:
no, it wont automount after i executed your command. What does it mean?

  • This reply was modified 10 days ago by  Koumi.
December 28, 2011 at 13:16 #2392

hozzdutch

as easy as that sounds Koumi, i can’t edit the fstab…it’s changed to read only - I can’t save the changes i make to it :-(

December 28, 2011 at 13:39 #2393

tomlohave

ypu use persistent, right

edit the file casper-rw (under windows use explore2fs), locate file fstab in directory and remove it
Else boot without persistent
or delete casper-rw

December 28, 2011 at 13:44 #2394

Koumi

didn’t happened to me, but it should not be a big deal.
i erased it by entering root emergency console and:
cat > /etc/fstab

[press ctrl + c]
If it say its read only, remount root filesystem to rw with:
mount /dev/sdd1 -o remount,rw

but it seems quite weird to me. In the emergency console you are root, so you shall have all permitions to / and /etc/ . We changed permitions to sda1, sdb1, sde1. Your geexbox is on sdd1, so no change should be done.

Anyway, if it doesnt work, post cat /proc/mounts and error from mount -a (both executed in the emer. console.)
Thanx

PS: But if Tomlohave say something different you should listen to him. I’m just guy who got it to work, he is an expert…

  • This reply was modified 10 days ago by  Koumi.
  • This reply was modified 10 days ago by  Koumi.
  • This reply was modified 10 days ago by  Koumi.
December 28, 2011 at 15:44 #2399

tomlohave

hey, i’m not an expert. Removing persistent is “maybe” the easiest solution.
All advices are good ;)

Viewing 15 posts - 1 through 15 (of 23 total)

You must be logged in to reply to this topic.