Linux can't read and write, but windows canCannot mount second 1TB harddrive in Linux, works fine in Windows 8.1How to mount sdb directly or using LVM partitions on sda?Can't write on recently created EXT4 partitionCan't mount anywhere but to /mntIs it possible to mount ~/.ipfs folder to an external drive?Use external drive as a folder in nginxHow to auto-mount HDD within encrypted /home partition/directory?Mounting a 4tb lvm in Centos 7 keeps saying not enough space on deviceDifferent EFIs and Windows dual bootingWrong fs type, bad option, bad superblock on /dev/sdX

Giving a career talk in my old university, how prominently should I tell students my salary?

Plausibility of Mushroom Buildings

Which classes are needed to have access to every spell in the PHB?

Power Strip for Europe

Does an unused member variable take up memory?

What materials can be used to make a humanoid skin warm?

Can the alpha, lambda values of a glmnet object output determine whether ridge or Lasso?

From an axiomatic set theoric approach why can we take uncountable unions?

Shifting between bemols and diesis in the key signature

Is it possible that a question has only two answers?

How do electrons receive energy when a body is heated?

When a wind turbine does not produce enough electricity how does the power company compensate for the loss?

Are all players supposed to be able to see each others' character sheets?

Called into a meeting and told we are being made redundant (laid off) and "not to share outside". Can I tell my partner?

What would be the most expensive material to an intergalactic society?

I reported the illegal activity of my boss to his boss. My boss found out. Now I am being punished. What should I do?

PTIJ: Why does only a Shor Tam ask at the Seder, and not a Shor Mu'ad?

Recommendation letter by significant other if you worked with them professionally?

Has a sovereign Communist government ever run, and conceded loss, on a fair election?

Why restrict private health insurance?

For which categories of spectra is there an explicit description of the fibrant objects via lifting properties?

After `ssh` without `-X` to a machine, is it possible to change `$DISPLAY` to make it work like `ssh -X`?

Why do we say ‘pairwise disjoint’, rather than ‘disjoint’?

When Schnorr signatures are part of Bitcoin will it be possible validate each block with only one signature validation?



Linux can't read and write, but windows can


Cannot mount second 1TB harddrive in Linux, works fine in Windows 8.1How to mount sdb directly or using LVM partitions on sda?Can't write on recently created EXT4 partitionCan't mount anywhere but to /mntIs it possible to mount ~/.ipfs folder to an external drive?Use external drive as a folder in nginxHow to auto-mount HDD within encrypted /home partition/directory?Mounting a 4tb lvm in Centos 7 keeps saying not enough space on deviceDifferent EFIs and Windows dual bootingWrong fs type, bad option, bad superblock on /dev/sdX













0















I have a hard drive with a lot of back up files, that were created by PhotoRec. When mounting it with a windows computer I can read all the files perfectly fine. Under linux I get an error when trying to look at the folder that contains all my backups. The rest of the hard drive is perfectly readable but when I try to ls the backup folder I get



ls: reading directory .: Input/output error



In Dolphin I just see a blank directory. I have tried letting arch auto mount and I have tried manually mounting it with -t ntfs-3g option (only flag used). A strange thing I notice is that if I manually mount it with the 3g option then all permissions are -rwxrwxrwx but if I let it be automatically mounted I have permissions -rw------- 1 steven steven (some have 2, but not many. The directories show d as they should). These are the same for every file and directory on the system.



I don't understand why I can't see these files under Linux, but can under Windows. I even booted up SystemRescueCD again to see if it recognized it, but it couldn't even see the files (even though it was what had originally written the files in the first place). What is so weird to me is that I can read everything on the hard drive except that one folder. It has the exact same permissions as everything else in the hard drive.



Additional info:



This is a fresh install of Arch. As of today.



[steven@serenity ~]$ uname -a
Linux serenity 3.16.1-1-ARCH #1 SMP PREEMPT Thu Aug 14 07:40:19 CEST 2014 x86_64 GNU/Linux



(auto mounted)



[steven@serenity ~]$ sudo fdisk -l

Disk /dev/sdb: 596.2 GiB, 640135028736 bytes, 1250263728 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
Disklabel type: dos
Disk identifier: 0x1549f232

Device Boot Start End Sectors Size Id Type
/dev/sdb1 * 63 1250258159 1250258097 596.2G 7 HPFS/NTFS/exFAT









share|improve this question
















bumped to the homepage by Community 1 hour ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.















  • You say you can't see anything in the directory, but also give permissions for "every file and directory" in it - I'm not sure how those fit together. Could you clarify what you can and can't see, and what is happening with each way of mounting?

    – Michael Homer
    Aug 31 '14 at 23:14











  • @MichaelHomer sorry, I'll clear this up in the OP. It is only a single folder that this error is happening on the hard drive.

    – Steven Walton
    Aug 31 '14 at 23:49











  • did you try running chkdsk from windows?

    – pqnet
    Sep 1 '14 at 7:48















0















I have a hard drive with a lot of back up files, that were created by PhotoRec. When mounting it with a windows computer I can read all the files perfectly fine. Under linux I get an error when trying to look at the folder that contains all my backups. The rest of the hard drive is perfectly readable but when I try to ls the backup folder I get



ls: reading directory .: Input/output error



In Dolphin I just see a blank directory. I have tried letting arch auto mount and I have tried manually mounting it with -t ntfs-3g option (only flag used). A strange thing I notice is that if I manually mount it with the 3g option then all permissions are -rwxrwxrwx but if I let it be automatically mounted I have permissions -rw------- 1 steven steven (some have 2, but not many. The directories show d as they should). These are the same for every file and directory on the system.



I don't understand why I can't see these files under Linux, but can under Windows. I even booted up SystemRescueCD again to see if it recognized it, but it couldn't even see the files (even though it was what had originally written the files in the first place). What is so weird to me is that I can read everything on the hard drive except that one folder. It has the exact same permissions as everything else in the hard drive.



Additional info:



This is a fresh install of Arch. As of today.



[steven@serenity ~]$ uname -a
Linux serenity 3.16.1-1-ARCH #1 SMP PREEMPT Thu Aug 14 07:40:19 CEST 2014 x86_64 GNU/Linux



(auto mounted)



[steven@serenity ~]$ sudo fdisk -l

Disk /dev/sdb: 596.2 GiB, 640135028736 bytes, 1250263728 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
Disklabel type: dos
Disk identifier: 0x1549f232

Device Boot Start End Sectors Size Id Type
/dev/sdb1 * 63 1250258159 1250258097 596.2G 7 HPFS/NTFS/exFAT









share|improve this question
















bumped to the homepage by Community 1 hour ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.















  • You say you can't see anything in the directory, but also give permissions for "every file and directory" in it - I'm not sure how those fit together. Could you clarify what you can and can't see, and what is happening with each way of mounting?

    – Michael Homer
    Aug 31 '14 at 23:14











  • @MichaelHomer sorry, I'll clear this up in the OP. It is only a single folder that this error is happening on the hard drive.

    – Steven Walton
    Aug 31 '14 at 23:49











  • did you try running chkdsk from windows?

    – pqnet
    Sep 1 '14 at 7:48













0












0








0








I have a hard drive with a lot of back up files, that were created by PhotoRec. When mounting it with a windows computer I can read all the files perfectly fine. Under linux I get an error when trying to look at the folder that contains all my backups. The rest of the hard drive is perfectly readable but when I try to ls the backup folder I get



ls: reading directory .: Input/output error



In Dolphin I just see a blank directory. I have tried letting arch auto mount and I have tried manually mounting it with -t ntfs-3g option (only flag used). A strange thing I notice is that if I manually mount it with the 3g option then all permissions are -rwxrwxrwx but if I let it be automatically mounted I have permissions -rw------- 1 steven steven (some have 2, but not many. The directories show d as they should). These are the same for every file and directory on the system.



I don't understand why I can't see these files under Linux, but can under Windows. I even booted up SystemRescueCD again to see if it recognized it, but it couldn't even see the files (even though it was what had originally written the files in the first place). What is so weird to me is that I can read everything on the hard drive except that one folder. It has the exact same permissions as everything else in the hard drive.



Additional info:



This is a fresh install of Arch. As of today.



[steven@serenity ~]$ uname -a
Linux serenity 3.16.1-1-ARCH #1 SMP PREEMPT Thu Aug 14 07:40:19 CEST 2014 x86_64 GNU/Linux



(auto mounted)



[steven@serenity ~]$ sudo fdisk -l

Disk /dev/sdb: 596.2 GiB, 640135028736 bytes, 1250263728 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
Disklabel type: dos
Disk identifier: 0x1549f232

Device Boot Start End Sectors Size Id Type
/dev/sdb1 * 63 1250258159 1250258097 596.2G 7 HPFS/NTFS/exFAT









share|improve this question
















I have a hard drive with a lot of back up files, that were created by PhotoRec. When mounting it with a windows computer I can read all the files perfectly fine. Under linux I get an error when trying to look at the folder that contains all my backups. The rest of the hard drive is perfectly readable but when I try to ls the backup folder I get



ls: reading directory .: Input/output error



In Dolphin I just see a blank directory. I have tried letting arch auto mount and I have tried manually mounting it with -t ntfs-3g option (only flag used). A strange thing I notice is that if I manually mount it with the 3g option then all permissions are -rwxrwxrwx but if I let it be automatically mounted I have permissions -rw------- 1 steven steven (some have 2, but not many. The directories show d as they should). These are the same for every file and directory on the system.



I don't understand why I can't see these files under Linux, but can under Windows. I even booted up SystemRescueCD again to see if it recognized it, but it couldn't even see the files (even though it was what had originally written the files in the first place). What is so weird to me is that I can read everything on the hard drive except that one folder. It has the exact same permissions as everything else in the hard drive.



Additional info:



This is a fresh install of Arch. As of today.



[steven@serenity ~]$ uname -a
Linux serenity 3.16.1-1-ARCH #1 SMP PREEMPT Thu Aug 14 07:40:19 CEST 2014 x86_64 GNU/Linux



(auto mounted)



[steven@serenity ~]$ sudo fdisk -l

Disk /dev/sdb: 596.2 GiB, 640135028736 bytes, 1250263728 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
Disklabel type: dos
Disk identifier: 0x1549f232

Device Boot Start End Sectors Size Id Type
/dev/sdb1 * 63 1250258159 1250258097 596.2G 7 HPFS/NTFS/exFAT






arch-linux mount ls






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Sep 1 '14 at 2:26









Ramesh

23.8k34104186




23.8k34104186










asked Aug 31 '14 at 22:50









Steven WaltonSteven Walton

398112




398112





bumped to the homepage by Community 1 hour ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.







bumped to the homepage by Community 1 hour ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.














  • You say you can't see anything in the directory, but also give permissions for "every file and directory" in it - I'm not sure how those fit together. Could you clarify what you can and can't see, and what is happening with each way of mounting?

    – Michael Homer
    Aug 31 '14 at 23:14











  • @MichaelHomer sorry, I'll clear this up in the OP. It is only a single folder that this error is happening on the hard drive.

    – Steven Walton
    Aug 31 '14 at 23:49











  • did you try running chkdsk from windows?

    – pqnet
    Sep 1 '14 at 7:48

















  • You say you can't see anything in the directory, but also give permissions for "every file and directory" in it - I'm not sure how those fit together. Could you clarify what you can and can't see, and what is happening with each way of mounting?

    – Michael Homer
    Aug 31 '14 at 23:14











  • @MichaelHomer sorry, I'll clear this up in the OP. It is only a single folder that this error is happening on the hard drive.

    – Steven Walton
    Aug 31 '14 at 23:49











  • did you try running chkdsk from windows?

    – pqnet
    Sep 1 '14 at 7:48
















You say you can't see anything in the directory, but also give permissions for "every file and directory" in it - I'm not sure how those fit together. Could you clarify what you can and can't see, and what is happening with each way of mounting?

– Michael Homer
Aug 31 '14 at 23:14





You say you can't see anything in the directory, but also give permissions for "every file and directory" in it - I'm not sure how those fit together. Could you clarify what you can and can't see, and what is happening with each way of mounting?

– Michael Homer
Aug 31 '14 at 23:14













@MichaelHomer sorry, I'll clear this up in the OP. It is only a single folder that this error is happening on the hard drive.

– Steven Walton
Aug 31 '14 at 23:49





@MichaelHomer sorry, I'll clear this up in the OP. It is only a single folder that this error is happening on the hard drive.

– Steven Walton
Aug 31 '14 at 23:49













did you try running chkdsk from windows?

– pqnet
Sep 1 '14 at 7:48





did you try running chkdsk from windows?

– pqnet
Sep 1 '14 at 7:48










1 Answer
1






active

oldest

votes


















0














The errors indicate a hardware problem with the disk but only on sectors containing the data.



The reason that under Windows you don't see these errors (until now), is probably caused by the difference in file browsing software: most Linux file browsers read more of the file information, from the file when opening a folder, than Windows Explorer does. This is to try and make previews, and have meta-data for the files available. Windows is probably only retrieving this when explicitly asked for.



You can try and see if you can copy all of the files under Windows to a separate disc. If that works run some thorough disk analyser on the original disk before continuing to use it (after making a full backup).






share|improve this answer























  • But I can open the files under the Windows system. And a hardware problem only on these sectors seems kind of weird...

    – Steven Walton
    Sep 1 '14 at 4:57











  • @StevenWalton I'm just guessing, but opening doesn't necessarily mean complete reading. If you had a headcrash, as little as one sector could be affected, although usually there is more. How long does it take (under Linux) to get the error (i.e. is the system obviously retrying before giving up)?

    – Anthon
    Sep 1 '14 at 4:59












  • Yeah, it just seems HIGHLY unlikely that the there is a hardware problem on only a certain section of a hdd. And I get the ls error immediately. If opening through dolphin it starts to scan then fails. I can even open the files in windows though. So if it is corrupted, it isn't in that way. Why can I open it in Windows and not Linux? Usually it's the other way around, or at least I can diagnose better. But I can't find anything.

    – Steven Walton
    Sep 1 '14 at 7:13











  • What happens if you copy the files, preferably to another disk/SD etc. under Windows and then access those from Linux?

    – Anthon
    Sep 1 '14 at 7:31










Your Answer








StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);













draft saved

draft discarded


















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f153068%2flinux-cant-read-and-write-but-windows-can%23new-answer', 'question_page');

);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes









0














The errors indicate a hardware problem with the disk but only on sectors containing the data.



The reason that under Windows you don't see these errors (until now), is probably caused by the difference in file browsing software: most Linux file browsers read more of the file information, from the file when opening a folder, than Windows Explorer does. This is to try and make previews, and have meta-data for the files available. Windows is probably only retrieving this when explicitly asked for.



You can try and see if you can copy all of the files under Windows to a separate disc. If that works run some thorough disk analyser on the original disk before continuing to use it (after making a full backup).






share|improve this answer























  • But I can open the files under the Windows system. And a hardware problem only on these sectors seems kind of weird...

    – Steven Walton
    Sep 1 '14 at 4:57











  • @StevenWalton I'm just guessing, but opening doesn't necessarily mean complete reading. If you had a headcrash, as little as one sector could be affected, although usually there is more. How long does it take (under Linux) to get the error (i.e. is the system obviously retrying before giving up)?

    – Anthon
    Sep 1 '14 at 4:59












  • Yeah, it just seems HIGHLY unlikely that the there is a hardware problem on only a certain section of a hdd. And I get the ls error immediately. If opening through dolphin it starts to scan then fails. I can even open the files in windows though. So if it is corrupted, it isn't in that way. Why can I open it in Windows and not Linux? Usually it's the other way around, or at least I can diagnose better. But I can't find anything.

    – Steven Walton
    Sep 1 '14 at 7:13











  • What happens if you copy the files, preferably to another disk/SD etc. under Windows and then access those from Linux?

    – Anthon
    Sep 1 '14 at 7:31















0














The errors indicate a hardware problem with the disk but only on sectors containing the data.



The reason that under Windows you don't see these errors (until now), is probably caused by the difference in file browsing software: most Linux file browsers read more of the file information, from the file when opening a folder, than Windows Explorer does. This is to try and make previews, and have meta-data for the files available. Windows is probably only retrieving this when explicitly asked for.



You can try and see if you can copy all of the files under Windows to a separate disc. If that works run some thorough disk analyser on the original disk before continuing to use it (after making a full backup).






share|improve this answer























  • But I can open the files under the Windows system. And a hardware problem only on these sectors seems kind of weird...

    – Steven Walton
    Sep 1 '14 at 4:57











  • @StevenWalton I'm just guessing, but opening doesn't necessarily mean complete reading. If you had a headcrash, as little as one sector could be affected, although usually there is more. How long does it take (under Linux) to get the error (i.e. is the system obviously retrying before giving up)?

    – Anthon
    Sep 1 '14 at 4:59












  • Yeah, it just seems HIGHLY unlikely that the there is a hardware problem on only a certain section of a hdd. And I get the ls error immediately. If opening through dolphin it starts to scan then fails. I can even open the files in windows though. So if it is corrupted, it isn't in that way. Why can I open it in Windows and not Linux? Usually it's the other way around, or at least I can diagnose better. But I can't find anything.

    – Steven Walton
    Sep 1 '14 at 7:13











  • What happens if you copy the files, preferably to another disk/SD etc. under Windows and then access those from Linux?

    – Anthon
    Sep 1 '14 at 7:31













0












0








0







The errors indicate a hardware problem with the disk but only on sectors containing the data.



The reason that under Windows you don't see these errors (until now), is probably caused by the difference in file browsing software: most Linux file browsers read more of the file information, from the file when opening a folder, than Windows Explorer does. This is to try and make previews, and have meta-data for the files available. Windows is probably only retrieving this when explicitly asked for.



You can try and see if you can copy all of the files under Windows to a separate disc. If that works run some thorough disk analyser on the original disk before continuing to use it (after making a full backup).






share|improve this answer













The errors indicate a hardware problem with the disk but only on sectors containing the data.



The reason that under Windows you don't see these errors (until now), is probably caused by the difference in file browsing software: most Linux file browsers read more of the file information, from the file when opening a folder, than Windows Explorer does. This is to try and make previews, and have meta-data for the files available. Windows is probably only retrieving this when explicitly asked for.



You can try and see if you can copy all of the files under Windows to a separate disc. If that works run some thorough disk analyser on the original disk before continuing to use it (after making a full backup).







share|improve this answer












share|improve this answer



share|improve this answer










answered Sep 1 '14 at 3:28









AnthonAnthon

61.1k17104167




61.1k17104167












  • But I can open the files under the Windows system. And a hardware problem only on these sectors seems kind of weird...

    – Steven Walton
    Sep 1 '14 at 4:57











  • @StevenWalton I'm just guessing, but opening doesn't necessarily mean complete reading. If you had a headcrash, as little as one sector could be affected, although usually there is more. How long does it take (under Linux) to get the error (i.e. is the system obviously retrying before giving up)?

    – Anthon
    Sep 1 '14 at 4:59












  • Yeah, it just seems HIGHLY unlikely that the there is a hardware problem on only a certain section of a hdd. And I get the ls error immediately. If opening through dolphin it starts to scan then fails. I can even open the files in windows though. So if it is corrupted, it isn't in that way. Why can I open it in Windows and not Linux? Usually it's the other way around, or at least I can diagnose better. But I can't find anything.

    – Steven Walton
    Sep 1 '14 at 7:13











  • What happens if you copy the files, preferably to another disk/SD etc. under Windows and then access those from Linux?

    – Anthon
    Sep 1 '14 at 7:31

















  • But I can open the files under the Windows system. And a hardware problem only on these sectors seems kind of weird...

    – Steven Walton
    Sep 1 '14 at 4:57











  • @StevenWalton I'm just guessing, but opening doesn't necessarily mean complete reading. If you had a headcrash, as little as one sector could be affected, although usually there is more. How long does it take (under Linux) to get the error (i.e. is the system obviously retrying before giving up)?

    – Anthon
    Sep 1 '14 at 4:59












  • Yeah, it just seems HIGHLY unlikely that the there is a hardware problem on only a certain section of a hdd. And I get the ls error immediately. If opening through dolphin it starts to scan then fails. I can even open the files in windows though. So if it is corrupted, it isn't in that way. Why can I open it in Windows and not Linux? Usually it's the other way around, or at least I can diagnose better. But I can't find anything.

    – Steven Walton
    Sep 1 '14 at 7:13











  • What happens if you copy the files, preferably to another disk/SD etc. under Windows and then access those from Linux?

    – Anthon
    Sep 1 '14 at 7:31
















But I can open the files under the Windows system. And a hardware problem only on these sectors seems kind of weird...

– Steven Walton
Sep 1 '14 at 4:57





But I can open the files under the Windows system. And a hardware problem only on these sectors seems kind of weird...

– Steven Walton
Sep 1 '14 at 4:57













@StevenWalton I'm just guessing, but opening doesn't necessarily mean complete reading. If you had a headcrash, as little as one sector could be affected, although usually there is more. How long does it take (under Linux) to get the error (i.e. is the system obviously retrying before giving up)?

– Anthon
Sep 1 '14 at 4:59






@StevenWalton I'm just guessing, but opening doesn't necessarily mean complete reading. If you had a headcrash, as little as one sector could be affected, although usually there is more. How long does it take (under Linux) to get the error (i.e. is the system obviously retrying before giving up)?

– Anthon
Sep 1 '14 at 4:59














Yeah, it just seems HIGHLY unlikely that the there is a hardware problem on only a certain section of a hdd. And I get the ls error immediately. If opening through dolphin it starts to scan then fails. I can even open the files in windows though. So if it is corrupted, it isn't in that way. Why can I open it in Windows and not Linux? Usually it's the other way around, or at least I can diagnose better. But I can't find anything.

– Steven Walton
Sep 1 '14 at 7:13





Yeah, it just seems HIGHLY unlikely that the there is a hardware problem on only a certain section of a hdd. And I get the ls error immediately. If opening through dolphin it starts to scan then fails. I can even open the files in windows though. So if it is corrupted, it isn't in that way. Why can I open it in Windows and not Linux? Usually it's the other way around, or at least I can diagnose better. But I can't find anything.

– Steven Walton
Sep 1 '14 at 7:13













What happens if you copy the files, preferably to another disk/SD etc. under Windows and then access those from Linux?

– Anthon
Sep 1 '14 at 7:31





What happens if you copy the files, preferably to another disk/SD etc. under Windows and then access those from Linux?

– Anthon
Sep 1 '14 at 7:31

















draft saved

draft discarded
















































Thanks for contributing an answer to Unix & Linux Stack Exchange!


  • Please be sure to answer the question. Provide details and share your research!

But avoid


  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f153068%2flinux-cant-read-and-write-but-windows-can%23new-answer', 'question_page');

);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







-arch-linux, ls, mount

Popular posts from this blog

Frič See also Navigation menuinternal link

Identify plant with long narrow paired leaves and reddish stems Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern) Announcing the arrival of Valued Associate #679: Cesar Manara Unicorn Meta Zoo #1: Why another podcast?What is this plant with long sharp leaves? Is it a weed?What is this 3ft high, stalky plant, with mid sized narrow leaves?What is this young shrub with opposite ovate, crenate leaves and reddish stems?What is this plant with large broad serrated leaves?Identify this upright branching weed with long leaves and reddish stemsPlease help me identify this bulbous plant with long, broad leaves and white flowersWhat is this small annual with narrow gray/green leaves and rust colored daisy-type flowers?What is this chilli plant?Does anyone know what type of chilli plant this is?Help identify this plant

fontconfig warning: “/etc/fonts/fonts.conf”, line 100: unknown “element blank” The 2019 Stack Overflow Developer Survey Results Are In“tar: unrecognized option --warning” during 'apt-get install'How to fix Fontconfig errorHow do I figure out which font file is chosen for a system generic font alias?Why are some apt-get-installed fonts being ignored by fc-list, xfontsel, etc?Reload settings in /etc/fonts/conf.dTaking 30 seconds longer to boot after upgrade from jessie to stretchHow to match multiple font names with a single <match> element?Adding a custom font to fontconfigRemoving fonts from fontconfig <match> resultsBroken fonts after upgrading Firefox ESR to latest Firefox