home bbs files messages ]

Forums before death by AOL, social media and spammers... "We can't have nice things"

   alt.os.linux.mint      Looks pretty on the outside, thats it!      30,566 messages   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]

   Message 29,956 of 30,566   
   Axel to Paul   
   Re: LM file transfer/copy issues   
   20 Dec 25 10:10:11   
   
   XPost: aus.computers   
   From: none@not.here   
      
   Paul wrote:   
   > On Fri, 12/19/2025 1:59 AM, Axel wrote:   
   >> Felix wrote:   
   >>> Paul wrote:   
   >>>> On Wed, 12/17/2025 4:38 AM, Felix wrote:   
   >>>>   
   >>>>> sorry, I think I've not explained it well. I'm using a LM PC. I'm not   
   connecting to a windows PC. I have an Ext4 drive installed in the LM PC. I   
   want to copy files to it from a NTFS drive connected via USB to a hard drive   
   box. I'm not copying or    
   moving any files to or from the main drive with LM on it.   
   >>>>>   
   >>>>> https://auslink.info/linux/case1.jpg   
   >>>>> https://auslink.info/linux/case2.jpg   
   >>>>>   
   >>>> What is the SMART status of this drive ?   
   >>>>   
   >>>> When is the last time it had a CHKDSK ?   
   >>>>   
   >>>> If you do [assumes drive is /dev/sdb]   
   >>>>   
   >>>>      sudo dd if=/dev/sdb of=/dev/null   
   >>>>   
   >>>> can the command read every sector on the drive ?   
   >>>>   
   >>>> We aren't copying the drive there, just checking for   
   >>>> CRC errors on the sectors. The Linux "dd" will stop   
   >>>> on the first CRC error it sees.   
   >>>>   
   >>>> *******   
   >>>>   
   >>>> You don't need a Windows install to run CHKDSK.   
   >>>>   
   >>>> You can boot an [era correct] installer DVD,   
   >>>> select "Troubleshooting" instead of Install Now,   
   >>>> and use the Command Prompt and run a CHKDSK in there.   
   >>>>   
   >>>>      CHKDSK /f C:   
   >>>>   
   >>>> or whatever drive letter the partition in question   
   >>>> happens to occupy.   
   >>> I've copied all files off this drive now, so I will now do this, and   
   report back. I had better success copying files using grsync   
   >> Here is the report. It seems the drive is OK. I guess the problem was   
   corrupt files?   
   >>   
   >> https://auslink.info/linux/WD_2TB.txt   
   > It is possible there were corrupt files.   
   >   
   > This is the only thing that bothers me about your disk drive.   
   >   
   >     199 UDMA_CRC_Error_Count    -O--CK   200   001   000    -    7484   
      
   the drive is connected to the computer via a cable to the motherboard   
   rear USB 3 port. I think I have good cables, but I wonder if they have   
   adequate shielding, so I'm checking out ones that do. these look good?   
   https://tinyurl.com/2jzzfntj   
      
   >   
   > That could be a bad SATA cable (or less likely, a bad SATA port   
   > on the motherboard).   
      
   The motherboard is new, and I'm not seeing any issues with transfers   
   to/from with/the internal drives   
      
   >   Check to see if the cable is kinked from bending   
   > it in half or something.   
      
   no, nothing like that   
      
   > The cables have a bend radius and the SATA   
   > cables should not be mistreated. Kinking the cable causes the transmission   
   > line impedance to change, and there are then "reflections" on the cable   
   > that upset the data in transit.   
   >   
   > The packets on the SATA cable each have a cyclic redundancy check, and   
   > one end of the link will request a retransmit if there is a problem.   
   >   
   > Other than that, if you CHKDSK the thing, first do a read-only check.   
   >   
   >      chkdsk D:   
      
   how do I tell it to check the USB connected drive?   
      
   >   
   > Only when you are convinced by that first scan, that nothing points   
   > to serious internal damage on the disk, would you do this.   
   >   
   >      chkdsk /f D:   
   >   
   > as trying to fix a sick disk that way, can cause more harm than good.   
   > A healthy disk needing a minor fix, is not a problem.   
   >   
   > *******   
   >   
   > I think I had just one bad SATA port on a motherboard, and since the   
   > motherboard died, all is forgiven :-)   
      
   lol   
      
   >   
   >     Paul   
   >   
   >   
      
      
   --   
   Linux Mint 22.2   
   {I shot Felix and buried him}   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]


(c) 1994,  bbs@darkrealms.ca