No cut-paste of file/folder with other HDD partitions

Asked by Navin Talati

I am unable to cut-paste any folder or file to other partition of a separate hdd within the system. Neither it happens vice-e-versa.
I have kept data partitions on separate hdds.
The ubuntu 20.04 freshly installed has the newest version (1:3.36.3-0ubuntu1) of nautilus.
Is/Are some package/s missing to make this facility of transfer (i.e. cut-paste) of data able?
Please guide.
Reards.

Question information

Language:
English Edit question
Status:
Answered
For:
Ubuntu Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:

This question was reopened

Revision history for this message
Manfred Hampl (m-hampl) said :
#1

How do you try the cut/paste action?

with the menu entry edit - cut
with right mouse button end selecting cut from the pop-up
with keyboard short-cuts (like ctrl-x, ctrl-v)
by mouse-drag
or ... ?

Does this action do nothing, or does it copy (and not move), do you get any message, etc.?
Do you have read and write access to the files/directories to move and the directories above?

Details please!

Revision history for this message
Navin Talati (n-m-talati) said :
#2

Now it has started working.
I can cut-paste or copy-paste files and folders from any partition of any hdd to any partition or hdd.
Thanks & regards. Sir.
Navin Talati /02-03-2021

Revision history for this message
Navin Talati (n-m-talati) said :
#3

Again the problem appeared.
I am unable to cut-paste or copy-paste any file or folder from one partition to another of different hdd as described above. Paste remain/show disabled upon right click.
Is there any tweak to activate or deactivate these operation in settings?
How to resolve this issue?

Revision history for this message
Manfred Hampl (m-hampl) said :
#4

Can you create a file on the target drive? (e.g. with a command like "touch /target/directory/path/file.name")
Maybe there was some error that the file system was re-mounted readonly.
In that case a reboot may help.

Are there an messages about disk problems in dmesg?

Revision history for this message
Navin Talati (n-m-talati) said :
#5

 I did Login from Ubuntu 20.04 (a separate HHD) and activity from its Desktop (...say A for reference location)
The Target Folder/Partition/HDD, (- this is 50 GB SSD with Windows 10 OS) – it Desktop (...say B for reference location) folder is selected for performing copy-paste / cut-paste etc.
Upon R-Clicking, :
(a)
1. “New Folder” and “Paste” shows Disabled.
2. “Select All”, “Properties” and “Open in terminal” shows Enabled.
(b)
In “Properties” when I change to “Create and delet files” in all the Three (Owner, Group, Others), it is not allowing or making “New Folder” and “Paste” Enabled. And that change does not persist when I open “Change Permissions for Enclosed Files”. It shows “Read-only” and “Access files” in “Others”
(c)
Have I to do anything in “Local Network Share” ?
(d)
There is no option of creating a file drectly on Desktop (B). - this is because input of actvity is feed through Ubuntu Desktop(A).

When I create some new file on Desktop (A), and try to save it through “Save as” on Desktop (B), it shows intimation/popup/warning saying ....
”Error saving the document: Object not accessible. The object can not e accessed due to insufficient user rights.”

Thus it seems here is some problem related to “Permission” but I don’t know how to reset/resolve it.

Revision history for this message
Manfred Hampl (m-hampl) said :
#6

Repeating my request from above: Are there any messages about disks and file systems in dmesg?

Instead of calling them A and B you had better used the real names (probably something like /dev/sda3) and you better add diagnostic information like
uname -a
lab_release -crid
mount
sudo fdisk -l

Is this a dual boot system with Windows, and the partition where you cannot write is the main partition from your Windows system?
In this case the problem is most probably caused by the Windows hybrid shutdown status. If you have fast startup enabled in your Windows system (which nowadays is the default), shutting down Windows keeps the Windows file systems in an "in use" status and Ubuntu will refuse to mount them in read/write mode.

see e.g. https://askubuntu.com/questions/145902/unable-to-mount-windows-ntfs-filesystem-due-to-hibernation

Revision history for this message
Navin Talati (n-m-talati) said :
#7

Sir,

1,
Your prediction mentioned in #6 stands right.i.e. ".............In this case the problem is most probably caused by the Windows hybrid shutdown status. If you have fast startup enabled in your Windows system (which nowadays is the default), shutting down Windows keeps the Windows file systems in an "in use" status and Ubuntu will refuse to mount them in read/write mode....."

As per reference: https://www.asus.com/support/FAQ/1045548/, I disabled the "Fast Startup" from my Windows 10 hdd, and now I can easily transfer my files from Ubuntu HDD partitions to Windows 10 hdd partitions.

2.
On applying stuff "dmesg" in terminal, it gives very very large output but due to my limitations of computer knowledge, I am unable to understand. some lines in RED colour appears but what it implies,,,? --that I am not understanding.

3.
You are right that Instead of calling them A and B , I should better use the real names of partitions and HDDs. That I will brief out as condensed information and will refer as that in future. Presently my A and B matter is resolved by disabling the "Fast Startup" from my Windows 10 hdd.

4.
Terminal output of your suggested ( i.e. 1. uname -a, 2. lab_release -crid, 3. mount, & 4. sudo fdisk -l ) stuffs is as under:

------------------ OUT PUT--------------------
navin@linux:~$ uname -a
Linux linux 5.8.0-50-generic #56~20.04.1-Ubuntu SMP Mon Apr 12 21:46:35 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
navin@linux:~$ lab_release -crid

Command 'lab_release' not found, did you mean:

  command 'lsb_release' from deb lsb-release (11.1.0ubuntu2)

Try: sudo apt install <deb name>

navin@linux:~$ lsb_release -crid
Distributor ID: Ubuntu
Description: Ubuntu 20.04.2 LTS
Release: 20.04
Codename: focal
navin@linux:~$ sudo fdisk -l
[sudo] password for navin:
Disk /dev/loop0: 187.3 MiB, 196116480 bytes, 383040 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/loop1: 184.7 MiB, 193011712 bytes, 376976 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/loop2: 9.8 MiB, 9519104 bytes, 18592 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/loop3: 9.9 MiB, 9531392 bytes, 18616 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/loop4: 99.22 MiB, 104030208 bytes, 203184 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/loop5: 99.15 MiB, 103964672 bytes, 203056 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/loop6: 55.48 MiB, 58159104 bytes, 113592 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/loop7: 55.46 MiB, 58142720 bytes, 113560 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/sda: 232.91 GiB, 250059350016 bytes, 488397168 sectors
Disk model: ST3250823NS
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x7a8b72ea

Device Boot Start End Sectors Size Id Type
/dev/sda1 * 2048 5859327 5857280 2.8G 83 Linux
/dev/sda2 5859328 279295999 273436672 130.4G 83 Linux
/dev/sda3 279296000 292968447 13672448 6.5G 82 Linux swap / Solaris
/dev/sda4 292970494 488396799 195426306 93.2G 5 Extended
/dev/sda5 292970496 488396799 195426304 93.2G 83 Linux

Disk /dev/sdc: 223.58 GiB, 240057409536 bytes, 468862128 sectors
Disk model: ADATA SU650
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x2ec7c2f7

Device Boot Start End Sectors Size Id Type
/dev/sdc1 * 2048 1026047 1024000 500M 7 HPFS/NTFS/exFAT
/dev/sdc2 1026048 467168004 466141957 222.3G 7 HPFS/NTFS/exFAT
/dev/sdc3 467169280 468856831 1687552 824M 27 Hidden NTFS WinRE

Disk /dev/sdb: 232.91 GiB, 250059350016 bytes, 488397168 sectors
Disk model: ST3250310CS
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xb146d0a1

Device Boot Start End Sectors Size Id Type
/dev/sdb1 * 2048 206847 204800 100M 7 HPFS/NTFS/exFAT
/dev/sdb2 206848 488394751 488187904 232.8G 7 HPFS/NTFS/exFAT

Disk /dev/sde: 931.53 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: ST31000528AS
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x000333ba

Device Boot Start End Sectors Size Id Type
/dev/sde1 * 2048 5855231 5853184 2.8G 83 Linux
/dev/sde2 97652734 1953503999 1855851266 885G f W95 Ext'd (LBA)
/dev/sde3 5855232 74215423 68360192 32.6G 83 Linux
/dev/sde4 74215424 97650687 23435264 11.2G 82 Linux swap / Solaris
/dev/sde5 409593303 1228795784 819202482 390.6G 7 HPFS/NTFS/exFAT
/dev/sde6 1228795848 1953503999 724708152 345.6G 7 HPFS/NTFS/exFAT
/dev/sde7 97652736 409591807 311939072 148.8G 7 HPFS/NTFS/exFAT

Partition table entries are not in disk order.

Disk /dev/sdd: 931.53 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: ST1000DM003-9YN1
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0x9e309e30

Device Boot Start End Sectors Size Id Type
/dev/sdd1 * 63 512007614 512007552 244.1G 7 HPFS/NTFS/exFAT
/dev/sdd2 512007615 1953503999 1441496385 687.4G f W95 Ext'd (LBA)
/dev/sdd5 512007678 1843201709 1331194032 634.8G 7 HPFS/NTFS/exFAT
/dev/sdd6 1843201773 1953503999 110302227 52.6G 7 HPFS/NTFS/exFAT

Partition 1 does not start on physical sector boundary.
Partition 2 does not start on physical sector boundary.
Partition 5 does not start on physical sector boundary.
Partition 6 does not start on physical sector boundary.

Disk /dev/loop8: 238.71 MiB, 250290176 bytes, 488848 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/loop9: 238.76 MiB, 250343424 bytes, 488952 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/loop10: 162.89 MiB, 170778624 bytes, 333552 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/loop11: 218.102 MiB, 229629952 bytes, 448496 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/loop12: 140 KiB, 143360 bytes, 280 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/loop13: 64.79 MiB, 67915776 bytes, 132648 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/loop14: 65.1 MiB, 68259840 bytes, 133320 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/loop15: 260.73 MiB, 273375232 bytes, 533936 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/loop16: 621.57 MiB, 651747328 bytes, 1272944 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/loop17: 621.58 MiB, 651755520 bytes, 1272960 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/loop18: 101.48 MiB, 106397696 bytes, 207808 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/loop19: 290.53 MiB, 304631808 bytes, 594984 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/loop20: 89.17 MiB, 93495296 bytes, 182608 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/loop21: 111.54 MiB, 116944896 bytes, 228408 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/loop22: 51.4 MiB, 53522432 bytes, 104536 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/loop23: 32.28 MiB, 33841152 bytes, 66096 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/loop24: 32.28 MiB, 33841152 bytes, 66096 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/loop25: 132.72 MiB, 139145216 bytes, 271768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/loop26: 132.81 MiB, 139243520 bytes, 271960 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/loop27: 295.32 MiB, 309661696 bytes, 604808 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/loop28: 71.16 MiB, 74616832 bytes, 145736 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/loop29: 303.8 MiB, 317796352 bytes, 620696 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/loop30: 337.44 MiB, 353816576 bytes, 691048 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/loop31: 337.72 MiB, 354107392 bytes, 691616 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
navin@linux:~$
---------------- END ----------------------
Here following is the RED Coloured lines stating that some partitions do not start on physical sector boundary. These are as under:

Partition 1 does not start on physical sector boundary.
Partition 2 does not start on physical sector boundary.
Partition 5 does not start on physical sector boundary.
Partition 6 does not start on physical sector boundary.

But I am unable to understand what it implies...!

This is for your kind information and for further guidance.

Regards.
Navin Talati /26-04-2021

Revision history for this message
Manfred Hampl (m-hampl) said :
#8

1. Sorry for my typo error. You have correctly identified that the command should have been lsb_release.

2. The warnings "Partition xy does not start on physical sector boundary." are not blocking usage of the disk.
They are a warning that the layout is not optimal which might slow down disk access a little bit.
In case that you want to correct this: changing this requires a complete restructuring of the disk layout including backup and restore of all data.
Just do a web search for that message and you will get lots of hits.

Revision history for this message
Navin Talati (n-m-talati) said :
#9

Sir,
Again the same/similar problem is arised.

My one hdd contains Ubuntu 20.04 LTS as OS and the second hdd contains Windows 10 as OS. Since years I was able to move my files and folders between different HDDs. It is normal that booting the system in UBUNTU avails this facility and we can view and transfer any files or folders from from Ubuntu to Windows sides or from one HDD to another HDD whatever OS it contains, or may be simply Data HDD wirthout any OS.

Now, the present problem is raised after installing the Windows 10 as OS as a replacement of previously used Windows 7. Upon disabling Fast/Quick Start in Windows 10, the matter was resolved, but again the same issue happens. Fast/Quick Start in Windows 10 is still disabled.

I am a computer's non-technical, so may not be able to even represent the question/problem in an appropriate terms, but what happens is "am nerrating as under:

(1).
From Ubuntu hdd side, I can CUT or COPY any file or folder but CAN NOT PASTE on Windows 10 hdd side
(i.e. I mean PASTE remain Disabled on Win-10 side).
(2).
From Windows 10 hdd side, I can only COPY any file or folder and PASTE on Ubuntu hdd side, but can not CUT from Windows 10 hdd side (i.e. I mean CUT remains Disabled on Win-10 side).

I did lots of surfing along with my knowledge-limitation, and also tried the tweaks and tricks etc, but could not succeed...!

I need your valuable help so that I can achieve the previous situation - i.e. which was before installing Windows 10.

Regards.

Revision history for this message
Manfred Hampl (m-hampl) said :
#10

For diagnostic purposes you should try finding out whether the "windows hdd" (which one is it?) is mounted in read-only mode, and if yes, why this is the case.

What is the output of the commands

mount
dmesg | grep -E sd[bcde]

Revision history for this message
Launchpad Janitor (janitor) said :
#11

This question was expired because it remained in the 'Needs information' state without activity for the last 15 days.

Revision history for this message
Navin Talati (n-m-talati) said :
#12

Sir,
Sorry for delay in providing needed information. The problem still persists. Required and requested information is as under with the references;

Ref:#10

1.
There are TWO hard drives as under:

sda = 250 GB HDD ---> Ubuntu 20.04 LTS
Partitions are: [ (sda1 /boot 3 GB) + (sda2 / 140 GB) + sda3 swap 7 GB) + sda4 extended partition as sda5 100 GB) ]

sdb = 240 GB SSD ---> Windows 10

Normally system is operated through Ubuntu 20.04 LTS (so it is identified as “sda”)

2.
How can I find that "windows hdd" (i.e. sdb) is mounted in read-only mode? AND How to get it mounted

Using “Disks” app, I can see that all the partitions of sda shows “Mounted at” at respective type of partition. But all the partitions of sdb (i.e. of Windows 10 ssd) shows “Not Mounted”. I think this may be the culprit, but I do not know how to make them “Mounted”?

Actually I afraid to make any change in “Disks” app whether it may disturb my whole system. So without proper guidance, it is difficul for me to change somthing!

3.
The OUTPUT of the commands “mount” and “dmesg | grep -E sd[bcde]” are as under:

------------O U T P U T -----------------
navin@linux:~$ mount
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
udev on /dev type devtmpfs (rw,nosuid,noexec,relatime,size=6973136k,nr_inodes=1743284,mode=755,inode64)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,nodev,noexec,relatime,size=1407152k,mode=755,inode64)
/dev/sda2 on / type ext4 (rw,relatime,errors=remount-ro)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev,inode64)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k,inode64)
tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755,inode64)
cgroup2 on /sys/fs/cgroup/unified type cgroup2 (rw,nosuid,nodev,noexec,relatime,nsdelegate)
cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,name=systemd)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
none on /sys/fs/bpf type bpf (rw,nosuid,nodev,noexec,relatime,mode=700)
cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio)
cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory)
cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls,net_prio)
cgroup on /sys/fs/cgroup/rdma type cgroup (rw,nosuid,nodev,noexec,relatime,rdma)
cgroup on /sys/fs/cgroup/hugetlb type cgroup (rw,nosuid,nodev,noexec,relatime,hugetlb)
cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event)
cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,relatime,pids)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=28,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=17201)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime,pagesize=2M)
debugfs on /sys/kernel/debug type debugfs (rw,nosuid,nodev,noexec,relatime)
mqueue on /dev/mqueue type mqueue (rw,nosuid,nodev,noexec,relatime)
tracefs on /sys/kernel/tracing type tracefs (rw,nosuid,nodev,noexec,relatime)
fusectl on /sys/fs/fuse/connections type fusectl (rw,nosuid,nodev,noexec,relatime)
configfs on /sys/kernel/config type configfs (rw,nosuid,nodev,noexec,relatime)
/var/lib/snapd/snaps/blender_460.snap on /snap/blender/460 type squashfs (ro,nodev,relatime,x-gdu.hide)
/var/lib/snapd/snaps/brave_124.snap on /snap/brave/124 type squashfs (ro,nodev,relatime,x-gdu.hide)
/var/lib/snapd/snaps/blender_206.snap on /snap/blender/206 type squashfs (ro,nodev,relatime,x-gdu.hide)
/var/lib/snapd/snaps/canonical-livepatch_102.snap on /snap/canonical-livepatch/102 type squashfs (ro,nodev,relatime,x-gdu.hide)
/var/lib/snapd/snaps/canonical-livepatch_104.snap on /snap/canonical-livepatch/104 type squashfs (ro,nodev,relatime,x-gdu.hide)
/var/lib/snapd/snaps/core_11420.snap on /snap/core/11420 type squashfs (ro,nodev,relatime,x-gdu.hide)
/var/lib/snapd/snaps/core_11316.snap on /snap/core/11316 type squashfs (ro,nodev,relatime,x-gdu.hide)
/var/lib/snapd/snaps/core18_2074.snap on /snap/core18/2074 type squashfs (ro,nodev,relatime,x-gdu.hide)
/var/lib/snapd/snaps/core20_1026.snap on /snap/core20/1026 type squashfs (ro,nodev,relatime,x-gdu.hide)
/var/lib/snapd/snaps/core20_1081.snap on /snap/core20/1081 type squashfs (ro,nodev,relatime,x-gdu.hide)
/var/lib/snapd/snaps/ffmpeg_1286.snap on /snap/ffmpeg/1286 type squashfs (ro,nodev,relatime,x-gdu.hide)
/var/lib/snapd/snaps/fwupd_3305.snap on /snap/fwupd/3305 type squashfs (ro,nodev,relatime,x-gdu.hide)
/var/lib/snapd/snaps/fwupd_3142.snap on /snap/fwupd/3142 type squashfs (ro,nodev,relatime,x-gdu.hide)
/var/lib/snapd/snaps/gimp_367.snap on /snap/gimp/367 type squashfs (ro,nodev,relatime,x-gdu.hide)
/var/lib/snapd/snaps/gimp_372.snap on /snap/gimp/372 type squashfs (ro,nodev,relatime,x-gdu.hide)
/var/lib/snapd/snaps/gnome-3-28-1804_161.snap on /snap/gnome-3-28-1804/161 type squashfs (ro,nodev,relatime,x-gdu.hide)
/var/lib/snapd/snaps/gnome-3-28-1804_145.snap on /snap/gnome-3-28-1804/145 type squashfs (ro,nodev,relatime,x-gdu.hide)
/var/lib/snapd/snaps/gnome-3-34-1804_66.snap on /snap/gnome-3-34-1804/66 type squashfs (ro,nodev,relatime,x-gdu.hide)
/var/lib/snapd/snaps/gtk2-common-themes_13.snap on /snap/gtk2-common-themes/13 type squashfs (ro,nodev,relatime,x-gdu.hide)
/var/lib/snapd/snaps/gnome-3-38-2004_39.snap on /snap/gnome-3-38-2004/39 type squashfs (ro,nodev,relatime,x-gdu.hide)
/var/lib/snapd/snaps/gtk-common-themes_1515.snap on /snap/gtk-common-themes/1515 type squashfs (ro,nodev,relatime,x-gdu.hide)
/var/lib/snapd/snaps/gnome-3-34-1804_72.snap on /snap/gnome-3-34-1804/72 type squashfs (ro,nodev,relatime,x-gdu.hide)
/var/lib/snapd/snaps/p7zip-desktop_220.snap on /snap/p7zip-desktop/220 type squashfs (ro,nodev,relatime,x-gdu.hide)
/var/lib/snapd/snaps/libreoffice_223.snap on /snap/libreoffice/223 type squashfs (ro,nodev,relatime,x-gdu.hide)
/var/lib/snapd/snaps/kde-frameworks-5-core18_32.snap on /snap/kde-frameworks-5-core18/32 type squashfs (ro,nodev,relatime,x-gdu.hide)
/var/lib/snapd/snaps/libreoffice_225.snap on /snap/libreoffice/225 type squashfs (ro,nodev,relatime,x-gdu.hide)
/var/lib/snapd/snaps/gtk-common-themes_1514.snap on /snap/gtk-common-themes/1514 type squashfs (ro,nodev,relatime,x-gdu.hide)
/var/lib/snapd/snaps/qucs-spice_4.snap on /snap/qucs-spice/4 type squashfs (ro,nodev,relatime,x-gdu.hide)
/var/lib/snapd/snaps/photogimp_141.snap on /snap/photogimp/141 type squashfs (ro,nodev,relatime,x-gdu.hide)
/var/lib/snapd/snaps/simplescreenrecorder-brlin_69.snap on /snap/simplescreenrecorder-brlin/69 type squashfs (ro,nodev,relatime,x-gdu.hide)
/var/lib/snapd/snaps/snap-store_547.snap on /snap/snap-store/547 type squashfs (ro,nodev,relatime,x-gdu.hide)
/var/lib/snapd/snaps/snap-store_542.snap on /snap/snap-store/542 type squashfs (ro,nodev,relatime,x-gdu.hide)
/var/lib/snapd/snaps/snapd_12398.snap on /snap/snapd/12398 type squashfs (ro,nodev,relatime,x-gdu.hide)
/var/lib/snapd/snaps/snapd_12704.snap on /snap/snapd/12704 type squashfs (ro,nodev,relatime,x-gdu.hide)
/var/lib/snapd/snaps/sweethome3d-homedesign_13.snap on /snap/sweethome3d-homedesign/13 type squashfs (ro,nodev,relatime,x-gdu.hide)
/var/lib/snapd/snaps/vlc_2288.snap on /snap/vlc/2288 type squashfs (ro,nodev,relatime,x-gdu.hide)
/var/lib/snapd/snaps/sweethome3d-homedesign_12.snap on /snap/sweethome3d-homedesign/12 type squashfs (ro,nodev,relatime,x-gdu.hide)
/var/lib/snapd/snaps/vlc_2344.snap on /snap/vlc/2344 type squashfs (ro,nodev,relatime,x-gdu.hide)
/var/lib/snapd/snaps/walc_19.snap on /snap/walc/19 type squashfs (ro,nodev,relatime,x-gdu.hide)
/var/lib/snapd/snaps/walc_17.snap on /snap/walc/17 type squashfs (ro,nodev,relatime,x-gdu.hide)
/var/lib/snapd/snaps/wine-platform-5-stable_16.snap on /snap/wine-platform-5-stable/16 type squashfs (ro,nodev,relatime,x-gdu.hide)
/var/lib/snapd/snaps/zoom-client_152.snap on /snap/zoom-client/152 type squashfs (ro,nodev,relatime,x-gdu.hide)
/var/lib/snapd/snaps/wine-platform-runtime_232.snap on /snap/wine-platform-runtime/232 type squashfs (ro,nodev,relatime,x-gdu.hide)
/var/lib/snapd/snaps/wine-platform-runtime_231.snap on /snap/wine-platform-runtime/231 type squashfs (ro,nodev,relatime,x-gdu.hide)
/var/lib/snapd/snaps/zoom-client_153.snap on /snap/zoom-client/153 type squashfs (ro,nodev,relatime,x-gdu.hide)
/dev/sda5 on /home type ext4 (rw,relatime)
/dev/sda1 on /boot type ext4 (rw,relatime)
tmpfs on /run/snapd/ns type tmpfs (rw,nosuid,nodev,noexec,relatime,size=1407152k,mode=755,inode64)
nsfs on /run/snapd/ns/canonical-livepatch.mnt type nsfs (rw)
/var/lib/snapd/snaps/core18_2128.snap on /snap/core18/2128 type squashfs (ro,nodev,relatime,x-gdu.hide)
/var/lib/snapd/snaps/brave_125.snap on /snap/brave/125 type squashfs (ro,nodev,relatime,x-gdu.hide)
tmpfs on /run/user/1000 type tmpfs (rw,nosuid,nodev,relatime,size=1407148k,mode=700,uid=1000,gid=1000,inode64)
gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)
/dev/fuse on /run/user/1000/doc type fuse (rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)
nsfs on /run/snapd/ns/snap-store.mnt type nsfs (rw)
nsfs on /run/snapd/ns/brave.mnt type nsfs (rw)
navin@linux:~$ dmesg | grep -E sd[bcde]
[ 2.621649] sd 4:0:0:0: [sdb] 468862128 512-byte logical blocks: (240 GB/224 GiB)
[ 2.621665] sd 4:0:0:0: [sdb] Write Protect is off
[ 2.621667] sd 4:0:0:0: [sdb] Mode Sense: 00 3a 00 00
[ 2.621687] sd 4:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 2.643035] sdb: sdb1 sdb2 sdb3
[ 2.643938] sd 4:0:0:0: [sdb] Attached SCSI disk
navin@linux:~$

---------------E N D --------------

Regards.

Revision history for this message
Manfred Hampl (m-hampl) said :
#13

Your last output does not fit to the previous ones.
In comment #7 you have five disks, but now there are only two.
I am sorry, but I do not understand what you are doing and so I cannot help.

Revision history for this message
Navin Talati (n-m-talati) said :
#14

Sir,

To make the machine's configuration simple, I removed all other data hdds and has kept only TWO hard drives bearing operating systems. Then updated the grub. After that I have obtained the output as per #12

My question regarding "No cut-paste of file/folder with other HDD partitions" is mainly between these TWO existing hard drives only. With other hard drives it happens, so it is removed - just to make a simple system and shell keep it till the problem solves.

So please help me.

Regards.

Revision history for this message
Manfred Hampl (m-hampl) said :
#15

In the output in comment #12 the partitions on the sdb disk are not mounted at all.
They need to be mounted to be accessible.
Have you ever read https://help.ubuntu.com/community/MountingWindowsPartitions ?

Can you help with this problem?

Provide an answer of your own, or ask Navin Talati for more information if necessary.

To post a message you must log in.