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.
Did you umount the device before running e2fsck? Which distribution you are using? Any particular reason to run e2fsck with -n switch? Because here is what I can see in e2fsck manpage when it runs with -n switch:
Code:
-n Open the filesystem read-only, and assume an answer of `no' to
all questions. Allows e2fsck to be used non-interactively.
(Note: if the -c, -l, or -L options are specified in addition to
the -n option, then the filesystem will be opened read-write, to
permit the bad-blocks list to be updated. However, no other
changes will be made to the filesystem.) This option may not be
specified at the same time as the -p or -y options.
I am using crunchbang linux.
Linux crunchbang 2.6.39-bpo.2-686-pae #1 SMP Thu Aug 4 11:02:22 UTC 2011 i686 GNU/Linux
I didn't need to umount to run e2fsck because the disk won't mount anymore. I just get the stale nfs file handle error... (I have rebooted but this made no difference to the stale nfs file handle error message appearing)
It does not appear in the list of mounted volumes when I running the "mount" command.
It does appear in the list of disks from fdisk -l
user@crunchbang:~$ fdisk -l
Device Boot Start End Blocks Id System
/dev/sdd1 * 1 60801 488384001 83 Linux
I ran e2fsck with the -n switch just to get a quick look at the errors without changing anything...
The attachment from the previous post is the output of : e2fsck -nv /dev/sdd
So the result of running without the -n and just with the -v, is being prompted for the first error :
user@crunchbang:~$ e2fsck -v /dev/sdd1
e2fsck 1.42 (29-Nov-2011)
/dev/sdd1 was not cleanly unmounted, check forced.
Resize inode not valid. Recreate<y>?
I don't feel confident in my knowledge of disks and storage to be sure that my answers to the e2fsck prompts would be the right ones...
Nor do I trust the -y switch to answer yes to everything !
Alright. Can you let me know how you are trying to mount the disk. Let me know the exact command. From the fdisk output it looks like you have got single partition on this disk. Do you have entry to mount this partition in /etc/fstab? Which filesystem this partition is formatted with? Any changes that you made which lead to this situation. Was it working before?
The drive used to mount automatically when I plugged it in.... there is no entry is /etc/fstab
The command I would use to mount it, if I was doing it manually would be nothing special, and I get the same result :
user@crunchbang:~$ sudo mount /dev/sdd1 /home/user/backup
[sudo] password for user:
mount: Stale NFS file handle
The disk has only 1 partition.... It was formatted to EXT2 or 3 - I can't remember which....
And the thing which lead to this situation was a powerloss during an rsync process... (this disk was being written to)
It was working fine before this and I'd had no problems at all... it was not a "dodgy" disk with bad sectors etc...
Number Start End Size Type File system Flags
1 32.3kB 500GB 500GB primary ext2 boot
user@crunchbang:~$ cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
# / was on /dev/sda1 during installation
UUID=728ae5bc-0457-4fa4-ae4d-e68731b2a43e / ext4 errors=remount-ro 0 1
# swap was on /dev/sda5 during installation
#UUID=6dfd3603-58f5-4c19-8c23-8375f42868c9 none swap sw 0 0
UUID=e79808fb-0e67-4973-90f6-2affc8ebf68e none swap sw 0 0
/dev/scd0 /media/cdrom0 udf,iso9660 user,noauto 0 0
#/dev/sdc5 /home/user/oldlinux ext3 defaults 0 0
UUID="decbf26e-89d0-439d-ab9e-6d54108ed5e9" /home/user/DATA ext4 defaults 0 0
#/dev/sdc2 /home/user/XP vfat defaults 0 0
#/dev/sdc3 /home/user/OTHER ext3 defaults 0 0
UUID="1911cb3b-b0df-4c69-b7ee-fb71ff9e8f62" /home/user/DATA_ ext4 defaults 0 0
user@crunchbang:~$ cat /etc/exports
cat: /etc/exports: No such file or directory
From the output I can see that it is ext2 filesystem. Did you try connecting this hdd to any other linux system. Were you able to access the drive there? If it is accessible on another machine then it could be an issue with this machine (a reboot should fix then). If you get the same error on the other machines as well then try this:
Try to stop the nfs client. It might be possible that nfs.client is trying to access the file system as soon as it tries to mount. You can do that using the following command:
Code:
sudo /etc/init.d/nfs.client stop
If this doesn't work then I would suggest you to make an image of your hdd and then run:
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.