Re: Unreadable files on NTFS partition

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello!

Nothing appears in dmesg when I try to read the file.
The file has no lock on the file manager.
The following appears in dmesg when I plug-in the disk:

[  209.554207] sd 0:0:0:0: [sda] Very big device. Trying to use READ
CAPACITY(16).
[  209.584067] sd 0:0:0:0: [sda] 7814037168 512-byte logical blocks:
(4.00 TB/3.64 TiB)
[  209.584575] sd 0:0:0:0: [sda] Write Protect is off
[  209.584578] sd 0:0:0:0: [sda] Mode Sense: 03 00 00 00
[  209.584856] sd 0:0:0:0: [sda] No Caching mode page found
[  209.584858] sd 0:0:0:0: [sda] Assuming drive cache: write through
[  209.585405] sd 0:0:0:0: [sda] Very big device. Trying to use READ
CAPACITY(16).
[  209.643622]  sda: sda1 sda2
[  209.644494] sd 0:0:0:0: [sda] Attached SCSI disk
[  210.215945] ntfs3: Unknown parameter 'windows_names'



Il giorno gio 4 lug 2024 alle ore 16:05 Enrico Mioso
<mrkiko.rs@xxxxxxxxx> ha scritto:
>
> Hello!
>
> do you see any messages in the dmesg?
> Do the files appear with something like a padlock icon?
>
> Enrico
>
> On Thu, Jul 04, 2024 at 03:48:24PM +0200, Tom wrote:
> > Howdy,
> >
> > I have an NTFS partition which contains a few files which are
> > unreadable. All the other files are fine.
> >
> > This seems weird as I can't even read them as root.  I do not believe
> > the disk's physical blocks belonging to the files are damaged.
> >
> > I did run from a Windows system 'chkdsk /f d:' to check the partition
> > and try to fix it but no issue was detected.
> >
> > I am running Linux 6.1.90 x86_64.
> >
> > mount command excerpt:
> >
> > /dev/sda2 on /media/tomas/DiskWithTheIssue type fuseblk
> > (ro,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096,uhelper=udisks2)
> >
> > ls command excerpt:
> >
> > # ls -lh
> > total 1.5G
> > -rwxrwxrwx 1 tomas tomas 583M Nov 14  2014 TRE_8446.MOV
> > -rwxrwxrwx 1 tomas tomas 581M Nov 14  2014 TRE_8447.MOV
> > -rwxrwxrwx 1 tomas tomas 170M Nov 14  2014 TRE_8448.MOV
> > -rwxrwxrwx 1 tomas tomas  19M Nov 14  2014 TRE_8449.MOV
> > -rwxrwxrwx 1 tomas tomas  42M Nov 14  2014 TRE_8450.MOV
> > -rwxrwxrwx 1 tomas tomas 116M Nov 14  2014 TRE_8452.MOV
> >
> >
> > file command excerpt:
> >
> > # file *
> > TRE_8446.MOV: ERROR: cannot read `TRE_8446.MOV' (Permission denied)
> > TRE_8447.MOV: ERROR: cannot read `TRE_8447.MOV' (Permission denied)
> > TRE_8448.MOV: ERROR: cannot read `TRE_8448.MOV' (Permission denied)
> > TRE_8449.MOV: ERROR: cannot read `TRE_8449.MOV' (Permission denied)
> > TRE_8450.MOV: ERROR: cannot read `TRE_8450.MOV' (Permission denied)
> > TRE_8452.MOV: ERROR: cannot read `TRE_8452.MOV' (Permission denied)
> >
> >
> > Does anyone have an idea what's going on here? Is this due to some
> > weird NTFS feature to encrypt files or something which is not
> > implemented in the Linux driver? or what..?
> >
> >
> > Thanks all a lot.
> >




[Index of Archives]     [Linux Driver Backports]     [DMA Engine]     [Linux GPIO]     [Linux SPI]     [Video for Linux]     [Linux USB Devel]     [Linux Coverity]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Yosemite Backpacking]
  Powered by Linux