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 P4 running Ubuntu 10.04LTS. It has 2 HDD's; 160 GB SATA2 for Windows and a 300 GB SATA2 for Ubuntu. The PC refused to start yesterday so I booted it with 10.04LTS on a live CD. The system sees both drives and the 160GB one is accessable, but the 300GB is seen, but not accessable.
Am I able to recover data form this drive; I only want one Thunderbird mailbox and one directory of correspondence.
Yes, I know I should have backed it up a week ago! Any help will be very much appreciated.
Here are the messages:
Unable to mount 294 GB Filesystem
DBus error org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
When an attempt is made to access the drive this is the message:
Unable to mount 294 GB Filesystem
DBus error org.gtk.Private.RemoteVolumeMonitor.Failed: An operation is already pending
Error checking filesystem on volume
An error occurred while performing an operation on "294 GB Filesystem" (Partition 1 of ATA ST3300622AS): The device is busy There is already a job running
fsck is used to check and optionally repair one or more Linux filesystems. filesys can be a device name (e.g. /dev/hdc1,
/dev/sdb2), a mount point (e.g. /, /usr, /home), or an ext2 label or UUID specifier (e.g.
UUID=8868abf6-88c5-4a83-98b8-bfc24057f7bd or LABEL=root). Normally, the fsck program will try to handle filesystems on
different physical disk drives in parallel to reduce the total amount of time needed to check all of them.
If no filesystems are specified on the command line, and the -A option is not specified, fsck will default to checking
filesystems in /etc/fstab serially. This is equivalent to the -As options.
The exit code returned by fsck is the sum of the following conditions:
0 No errors
1 Filesystem errors corrected
2 System should be rebooted
4 Filesystem errors left uncorrected
8 Operational error
16 Usage or syntax error
32 Fsck canceled by user request
128 Shared-library error
The exit code returned when multiple filesystems are checked is the bit-wise OR of the exit codes for each filesystem that
In actuality, fsck is simply a front-end for the various filesystem checkers (fsck.fstype) available under Linux. The
filesystem-specific checker is searched for in /sbin first, then in /etc/fs and /etc, and finally in the directories
listed in the PATH environment variable. Please see the filesystem-specific checker manual pages for further details.
Many thanks for your suggestions, as a consequence I used e2fsck, not fsck, as the drive in question has an ext4 filesystem.
Here is the command and the message:
ubuntu@ubuntu:~$ sudo e2fsck -p /dev/sdc2
e2fsck: Attempt to read block from filesystem resulted in short read while trying to open /dev/sdc2
Could this be a zero-length partition?
I will now look at your suggested guides, and also read up on the other command options. I hope that the record of the file structure was not contained in the reported 24 bad sectors.
'fsck' is the front end for filesystem checks.
In actuality, fsck is simply a front-end for the various filesystem checkers (fsck.fstype) available under Linux. The filesystem-specific checker is
searched for in /sbin first, then in /etc/fs and /etc, and finally in the directories listed in the PATH environment variable. Please see the filesys-
tem-specific checker manual pages for further details.
If you do a 'man fsck' you will get;
Normally, the fsck program
will try to handle filesystems on different physical disk drives in parallel to reduce the total amount of time needed to check all of them.
If no filesystems are specified on the command line, and the -A option is not specified, fsck will default to checking filesystems in /etc/fstab seri-
ally. This is equivalent to the -As options.
fstab(5), mkfs(8), fsck.ext2(8) or fsck.ext3(8) or e2fsck(8), cramfsck(8), fsck.minix(8), fsck.msdos(8), fsck.jfs(8), fsck.nfs(8), fsck.vfat(8),
fsck.xfs(8), fsck.xiafs(8), reiserfsck(8).
Plus be sure to either insure no access to the filesystem by others by using 'single' user mode or boot using a LiveCD.
You might test the hdd with the manufactures diagnostic set.
UBCD Ultimate Boot CD <- 'UBCD allows users to run floppy-based diagnostic tools from most CDROM drives on Intel-compatible machines, no operating system required. The cd includes many diagnostic utilities.'
SystemRescueCd <- 'is a Linux system on a bootable CD-ROM for repairing your system and recovering your data after a crash. It aims to provide an easy way to carry out admin tasks on your computer, such as creating and editing the partitions of the hard disk. It contains a lot of system utilities (parted, partimage, fstools, ...) and basic tools (editors, midnight commander, network tools).' + 'Online-Manual
If you do not pass 'single' to the *buntu install CD the HD device may be used. Above diagnostic LIveCD should boot as 'single'.
The Ultimate Boot CD has given me access to the HDD and I have been able to retrieve all of the files I wanted, plus some. It is a far easier job with the right tools.
Many thanks for your help, I really appreciate it.