Other files corrubted after copy them to NTFS partition

islamux

islamux

Hi,
There is a strange problem that when I'm transferring files it did but after that the file transferred it become unreadable.
I used pcmanfm ,doublecmd but the same result every time. These problem don't exits in FreeBSD 11 but it appeared after update to 11.1.

the files transfered form FreeBSD UFS to NTFS. This file "turkic" it appeared like this when I want to ls it
Code: 
ls: Turkic: Input/output error

Now :( any file I'm transferring it become unreadable and how to restore my corrupted files:(.
thanx to all
 
Last edited by a moderator:
https://pastebin.com/dCjLgrnx
Code: 
gpart show
=>       63  976773105  ada0  MBR  (466G)
         63          1        - free -  (512B)
         64   60817408     1  freebsd  [active]  (29G)
   60817472     615088        - free -  (300M)
   61432560   61448625     2  linux-data  (29G)
  122881185        863        - free -  (432K)
  122882048   67584000     4  linux-data  (32G)
  190466048        653        - free -  (327K)
  190466701  786301364     3  ebr  (375G)
  976768065       5103        - free -  (2.5M)

=>       0  60817408  ada0s1  BSD  (29G)
         0  58720256       1  freebsd-ufs  (28G)
  58720256   2097151       2  freebsd-swap  (1.0G)
  60817407         1          - free -  (512B)

=>        0  786301364  ada0s3  EBR  (375G)
          0   55304194       1  linux-data  (26G)
   55304194    6143345  877845  linux-swap  (2.9G)
   61447539       1025          - free -  (513K)
   61448564  228685275  975375  ntfs  (109G)
  290133839  160633935  4605300  ntfs  (77G)
  450767774  335533590  7155045  ntfs  (160G)
thanx for helping :)
 
No problem :)

Nothing weird in dmesg, or at least that I saw. That's a pretty intense layout! I see you've gone to great lengths to get around the limits of MBR. I assume there's no issues with the other Operating Systems on this disk?

You might want to try dropping into single user mode and running fdisk. What told you there was a corrupted inode?
 
i have no problem in other linux distro and these is the fdisk outbut
Code: 
******* Working on device /dev/ada0 *******
parameters extracted from in-core disklabel are:
cylinders=15504336 heads=1 sectors/track=63 (63 blks/cyl)

Figures below won't work with BIOS for partitions not in cyl 1
parameters to be used for BIOS calculations are:
cylinders=15504336 heads=1 sectors/track=63 (63 blks/cyl)

Media sector size is 512
Warning: BIOS sector numbering starts with sector 1
Information from DOS bootblock is:
The data for partition 1 is:
sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD)                         
    start 64, size 60817408 (29696 Meg), flag 80 (active)                 
        beg: cyl 1/ head 0/ sector 2;                                               
        end: cyl 1023/ head 255/ sector 63                                               
The data for partition 2 is:                                                             
sysid 131 (0x83),(Linux native)
    start 61432560, size 61448625 (30004 Meg), flag 0
        beg: cyl 1023/ head 254/ sector 63;
        end: cyl 1023/ head 254/ sector 63
The data for partition 3 is:
sysid 15 (0x0f),(Extended DOS (LBA))
    start 190466701, size 786301364 (383936 Meg), flag 0
        beg: cyl 1023/ head 254/ sector 63;
        end: cyl 1023/ head 254/ sector 63
The data for partition 4 is:
sysid 131 (0x83),(Linux native)
    start 122882048, size 67584000 (33000 Meg), flag 0
        beg: cyl 1023/ head 254/ sector 63;
        end: cyl 1023/ head 254/ sector 63
 
if there are no solution i want to delet all the files corrubted :(
i think there are a problem in hd could i fix it without formating the hd
 
What exactly is this file turkic? What is the full path? Where did it come from? Have you experienced this with any other file on your UFS slice?
 
You must log in or register to reply here.
Back
Top