ls: reading directory .: Input/output error when copying data to new drive
Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
ls: reading directory .: Input/output error when copying data to new drive
I get this error when coping data to a new drive. It will backup about 20Gig, then the copy will stop and I can't access anything on the backup drive, even a simple ls returns this error:
ls: reading directory .: Input/output error
That was on a brand new drive, I tried it with a second new drive, same error.
Is the new drive formatted, if so what filesystem and partitions? Have you checked how much free space is available before starting to copy? Try running
Code:
df -h
after the drive is mounted to see what partitions are mounted and what free space is available.
check the output of dmesg for (hopefully) more detail. I had
issues like that when we first got a MoBo with a brand-new
nvidia chipset. Went away with a newer kernel.
check the output of dmesg for (hopefully) more detail. I had
issues like that when we first got a MoBo with a brand-new
nvidia chipset. Went away with a newer kernel.
Cheers,
Tink
Thanks its working now, and I believe it was the kernel that was causing it to fail. I just backed up 300GB to the drive.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.