Keep getting "?" question marks in permissions spot when doing ls -al on a New USB HD
I had this error before, I ran e2fsck several times, then gave up and bought a brand new USB HD....
Now I am getting the same errors. I am not sure when exactly it is happening, however I have a DUMP Backup running late at night, and when I come in the morning, I get I/O error in the log for it Code:
DUMP: Date of this level 0 dump: Thu Feb 3 22:00:01 2011 Code:
ls -al PS--- Below is the script I am using for Dump Backups.... Code:
#!/bin/csh Code:
Feb 3 22:00:11 stpgeosvr kernel: Device sdb not ready. |
Your best bet is to check dmesg output for clues. It definitely looks like it could be a hardware issue (or possibly a driver issue, but it appears somehow corruption is getting written to disk).
|
Just ran e2fsck....
Code:
e2fsck -pv /dev/sdb PS Dmesg showed nothing of interest that wasn't in /var/log/messages... |
DUMP Log.....
Code:
cat /var/log/backups/dump_usb_backup.2011.02.04 Code:
cd /coldback/ |
Given it made it all the way to sector 728760391 before it ran an I/O error, this is almost surely a problem with the drive itself. Maybe try starting with a clean filesystem on it and write a significant amount of data to it again. If the I/O errors are happening at around the same spot, then that's a pretty good indicator it's not a driver issue or something.
|
Problem is that this is the second USB Drive that has had this issue. This Drive is brand New out the box and a totally different model than the previous one with the exact same issues. The OS is picking up errors on the drive but, I run e2fsck and manually run my backup script and it seems to work half a$$ed.
So I Highly doubt this is an issue with the drive but an issue with the OS, just not sure what.... Quote:
|
Exact same meaning the kernel I/O errors are around the same spot? Even with the old drive?
|
No I'm not sure if they were in the same spot but, it was the same errors. Holes in offset blah blah blah; I/O error etc
|
try running 'badblocks' on it (as root)
badblocks -b 8192 -n /dev/sdc Replace sdc with the device your USB stick is. Back it up before doing this too. If there are errors, this should pick it up. Sounds like a hardware issue to me. I've had a new USB stick go kaput almost immediately too, giving wierd errors as if there was a hole in it. |
this is a Seagate 500GB external Hard drive. Are there Diagnostic tools somewhere? Cant find 'em....
Either way the very first one that had this issue, has been working perfectly on my win7 machine since I replaced it with this one... Has to be something with the os, just not sure what to be checking on that end.... |
All times are GMT -5. The time now is 06:21 PM. |