Keep getting "?" question marks in permissions spot when doing ls -al on a New USB HD
Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
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.
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
DUMP: Dumping /dev/sda5 (/usr) to /coldback/weekly/usr.2011.02.03
DUMP: Label: /usr1
DUMP: Writing 10 Kilobyte records
DUMP: mapping (Pass I) [regular files]
DUMP: mapping (Pass II) [directories]
DUMP: estimated 14397298 blocks.
DUMP: Cannot open output "/coldback/weekly/usr.2011.02.03": Input/output error
DUMP: Do you want to retry the open? - forced abort
DUMP: The ENTIRE dump is aborted.
Code:
ls -al
total 32
drwxr-xr-x 5 root root 4096 Nov 17 14:28 .
drwxr-xr-x 26 root root 4096 Nov 17 13:56 ..
drwx------ 2 root root 16384 Nov 17 14:19 lost+found
?--------- ? ? ? ? ? metal
drwx------ 2 root root 4096 Jan 22 22:20 weekly
It happens to both the dirs in that drive. I'm not sure how I would find out if its the dump creating the error, or what is going on here...could it be a bad usb port? How would I find exactly when the OS reads the permissions as "?"'s
PS--- Below is the script I am using for Dump Backups....
Code:
#!/bin/csh
#
# Script to perform dump of directories to USB external drive.
#
#
# Set variables to dump
setenv USB /coldback/weekly
setenv TODAY "`date '+%Y.%m.%d'`"
setenv LOGFILE /var/log/backups/dump_usb_backup.$TODAY
setenv FILESYSTEM1 /usr
setenv FILESYSTEM2 /var
setenv FILESYSTEM3 /home
setenv FILESYSTEM4 /
setenv FILESYSTEM5 /boot
#
#
# Create today's LOGFILE
touch $LOGFILE
#
# Dump filesystems to tape
/sbin/dump -0 -f $USB/usr.$TODAY -q $FILESYSTEM1 >>& $LOGFILE
/sbin/dump -0 -f $USB/var.$TODAY -q $FILESYSTEM2 >>& $LOGFILE
/sbin/dump -0 -f $USB/home.$TODAY -q $FILESYSTEM3 >>& $LOGFILE
/sbin/dump -0 -f $USB/root.$TODAY -q $FILESYSTEM4 >>& $LOGFILE
/sbin/dump -0 -f $USB/boot.$TODAY -q $FILESYSTEM5 >>& $LOGFILE
#
#
# Check for errors
set ERR="`grep -i 'DUMP IS DONE' ${LOGFILE}|wc -l`"
#
#
if ( $ERR < 5 ) then
mail -s "USB Backup failed on `hostname`" root </dev/null
else
mail -s "USB Backup succeeded on `hostname`" root </dev/null
endif
Here's cat /var/log/messages for the time of the Cron Job Backup
Code:
Feb 3 22:00:11 stpgeosvr kernel: Device sdb not ready.
Feb 3 22:00:11 stpgeosvr kernel: end_request: I/O error, dev sdb, sector 728760391
Feb 3 22:00:11 stpgeosvr kernel: EXT3-fs error (device sdb1): read_inode_bitmap: Cannot read inode bitmap - block_group = 2780, inode_bitmap = 91095041
Feb 3 22:00:11 stpgeosvr kernel: Aborting journal on device sdb1.
Feb 3 22:00:15 stpgeosvr kernel: EXT3-fs error (device sdb1) in ext3_new_inode: IO failure
Feb 3 22:00:15 stpgeosvr kernel: EXT3-fs error (device sdb1) in ext3_create: IO failure
Feb 3 22:00:19 stpgeosvr kernel: ext3_abort called.
Feb 3 22:00:19 stpgeosvr kernel: EXT3-fs error (device sdb1): ext3_journal_start_sb: Detected aborted journal
Feb 3 22:00:19 stpgeosvr kernel: Remounting filesystem read-only
Again this is the second USB Drive with this issue & this Drive is straight out the box. I am going to run e2fsck and the DUMP again, but I am pretty sure I will get these errors again
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).
e2fsck -pv /dev/sdb
/dev/sdb: Superblock has a bad ext3 journal (inode 8).
CLEARED.
*** ext3 journal has been deleted - filesystem is now ext2 only ***
/dev/sdb: Resize inode not valid.
/dev/sdb: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
(i.e., without -a or -p options)
[root@stpgeosvr ~]# e2fsck -pv /dev/sdb1
/dev/sdb1: recovering journal
/dev/sdb1 contains a file system with errors, check forced.
38 inodes used (0%)
5 non-contiguous inodes (13.2%)
# of inodes with ind/dind/tind blocks: 25/25/5
27587271 blocks used (22%)
0 bad blocks
11 large files
25 regular files
4 directories
0 character device files
0 block device files
0 fifos
0 links
0 symbolic links (0 fast symbolic links)
0 sockets
--------
29 files
I am running my Dump now, I will post happens....
PS Dmesg showed nothing of interest that wasn't in /var/log/messages...
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:
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.
I did this just now as per above.... I ran e2fsck and then manually ran the dump backup
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....
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
