Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I have a usb drive that now only mounts read only. dmesg | tail gives the following:
SCSI device sda: 312581808 512-byte hdwr sectors (160042 MB)
WARNING: USB Mass Storage data integrity not assured
USB Mass Storage device found at 2
USB Mass Storage support registered.
parport0: PC-style at 0x378 [PCSPP,TRISTATE,EPP]
lp0: using parport0 (polling).
apm: BIOS version 1.2 Flags 0x03 (Driver version 1.16)
EXT3-fs error (device sd(8,0)): ext3_check_descriptors: Block bitmap for group 880 not in group (block 0)!
EXT3-fs: group descriptors corrupted !
This drive holds my backups so I don't want to take unnecessary chances if I can avoid it. Since it is read only I have though about getting another drive and copying everything over before messing with it. It is 160GB about 75% full.
One more thing...as my status to the left says I am a debian newbie.
Any ideas on saving this drive without buying another?
Look up the program 'fsck.ext3' or whatever, and try running that. It may help you when you look for information on the drive. I would warn you to be certain of the drive not being mounted, because sometimes funny things can happen. I would specifically look for the option where you can test the drive without potentially damaging the information on it (which, if it is EXT3 or whatever it is, and you are running different various versions of linux, then it helps because you can check one if it reports errors)
Last edited by PenGUiN_6_1; 11-30-2006 at 10:22 PM.
errors=continue / errors=remount-ro / errors=panic
Define the behaviour when an error is encountered. (Either ignore errors and just mark the file system erroneous and
continue, or remount the file system read-only, or panic and halt the system.) The default is set in the filesystem
superblock, and can be changed using tune2fs(8).
sb=n Instead of block 1, use block n as superblock. This could be useful when the filesystem has been damaged. (Earlier,
copies of the superblock would be made every 8192 blocks: in block 1, 8193, 16385, ... (and one got thousands of copies
on a big filesystem). Since version 1.08, mke2fs has a -s (sparse superblock) option to reduce the number of backup
superblocks, and since version 1.15 this is the default. Note that this may mean that ext2 filesystems created by a
recent mke2fs cannot be mounted r/w under Linux 2.0.*.) The block number here uses 1k units. Thus, if you want to use
logical block 32768 on a filesystem with 4k blocks, use "sb=131072".
See if you can mount it with the options "ro", "errors=remount-ro" and "sb=8193". Perhaps the superblock is currupt leading to the errors you are seeing. Copying the data to another drive is a good idea by the way.
Sound like my drive is basically hosed. I will buy a second drive. I have been wanting to play with setting up a RAID array so that I can expand. I think what I will do is set up a second drive and copy as much data from the bad drive as I can and then figure out what to do with the bad drive.
Distribution: Mandrake, maybe Ubuntu if I can ever get it to install
I wouldn't know if this would have anything to do with it, but I never could get an external usb2 hd to work decently under linux. I decided to try the firewire interface instead, and the drive runs much better.
I guess I should add that the drive is running ntfs. I probably should have made it fat32 though.
Thanks for the suggestion. The USB drive is a old drive I had that I am using because I have it on hand. It is storing backups of other computers on my network using BackupPC. I don't know of any 160GB USB sticks. It would be awesome however if we could get rid of disks altogether and just use chip memory.
What's the filesystem type on this external drive???
Are any other computer that uses this drive running Windoze software???
Perhaps the filesystem has been locked by another system. Or the "BackupPC"...
Have you tried the remount switch of the mount command?
Or simply umount it and mount it with the rw switches.
Are you the root user when you try to access it???
DO NOT run the fsck command until you know the filesystem type, otherwise ......