28
votes
Connection problem with USB3 external storage on Linux (UAS driver problem)
I had this same issue on Mint 18, but the solution I found can probably be applied to *Ubuntu 15/16 as well as similar Linux distributions. For me, however, I was getting an irrecoverable system ...
23
votes
Accepted
Should I answer yes to "Clone multiply-claimed blocks<y>?" when running e2fsck?
Multiply-claimed blocks are blocks which are used by multiple files, when they shouldn’t be. One consequence of that is that changes to one of those files, in one of the affected blocks, will also ...
16
votes
Accepted
Connection problem with USB3 external storage on Linux (UAS driver problem)
I ran into this issue today on a 4.8.0 kernel.
According to this forum post it can be circumvented by
$ echo options usb-storage quirks=357d:7788:u | sudo tee /etc/modprobe.d/blacklist_uas_357d.conf
...
12
votes
Accepted
Does "recovering journal" prove an unclean shutdown/unmount?
The “recovering journal” message is output by e2fsck_run_ext3_journal, which is only called if ext2fs_has_feature_journal_needs_recovery indicates that the journal needs recovery. This “feature” is a ...
8
votes
Connection problem with USB3 external storage on Linux (UAS driver problem)
In order to apply the quirk mentioned by other answers on the fly, you can also set it at runtime:
echo "152d:0583:u" | sudo tee /sys/module/usb_storage/parameters/quirks
Replace 152d:0583 ...
7
votes
Accepted
Is it possible to run e2fsck in a way that'll give false results?
That's a broken disk. SMART values of interest (last column):
1 Raw_Read_Error_Rate ... Pre-fail Always FAILING_NOW 48799
5 Reallocated_Sector_Ct ... Pre-fail Always - ...
5
votes
mount can't read superblock on /dev/sda5
The worst thing you might ever do is to try to run filesystem repair on the broken hardware. There is a huge chance you are already lost your data (remains of filesystem were irreversibly corrupted ...
5
votes
Accepted
rhel + efsck + Deleted inode xxxxx has zero dtime
It’s OK to let fsck fix this, it refers to a deleted inode — the data has already been deleted, nothing more will be deleted.
5
votes
How to resolve e2fsck Superblock problem?
Stop.
According to e2fsck, your /etc/fstab file, and your lsblk output, the filesystem type on /dev/sdb1 is ufs.
e2fsck is only for filesystem types ext2, ext3 and ext4. It cannot fix filesystem ...
4
votes
What is it that e2fsck does not say?
To supplement the helpful contributions to my question, I did some research on my own. Because parts of the results might be of also of some general interest, I summarize them in this self-answer.
...
4
votes
Accepted
How can I see if this fsck operation corrected any filesystem errors?
The best way to determine whether this particular fsck operation corrected any errors would have been to check its exit code: e2fsck sets bit 1 of its exit code if it corrected errors, and bit 2 if it ...
4
votes
Accepted
e2fsck aftercare
Unless you have a fresh backup to compare with, there's nothing you can do.
In rare cases e2fsck truncates files to zero - you might look for them.
4
votes
Accepted
What can cause “multiply claimed blocks” on an ext4 drive?
As stated very early by Theodore Tso himself, there can be two immediate reasons for “Multiply claimed blocks” to be reported by fsck :
One is that one or more blocks in the inode table get written ...
3
votes
Accepted
ssd won't mount: bad superblock but no bad blocks: write errors
I don't know what you've been doing with this disk, but that's crazy numbers! Looking at that output that SSD has been on:
1470 hours (61 days)
performed 4312400063 (2.0GiB) block erases
163210068006 ...
3
votes
Accepted
How can I tell when my file system was last fsck-ed at all?
When the partition is in clean state, there is no actual fsck run, which is why the date isn't updated.
If you want to force it, the -f option does just that: sudo fsck -f /dev/sda1.
2
votes
How do I use yes with e2fsck?
i had to enter "n" (don't abort) before "yes", so i used script:
(echo n; yes) | script --return -c "e2fsck /dev/sda1"
2
votes
Ctrl-D prompt ,unable to boot the Linux system, after block-device shrink without file-system shrink beforehand
Before doing any more changes which might cause a lot of damage, make a sector-by-sector copy of the physical volume (as in: dd if=/dev/sdXY of=/path/to/safe/place.img) at its current state and store ...
2
votes
Accepted
Resized partition to too small value after shrinking filesystem
I resized the partition to a too small value have corrupted the fs?
It's unlikely in your case, especially since you were kind enough to stop that fs(c)killer, but you can't rule out the possibility ...
2
votes
What are the conditions that qualify a file as lost and found?
I expect that it is just #2 (a file has no entry in any directory).
If a file is pointed to by one or more directory entries,
fsck should just set the link count to equal the number of directory ...
2
votes
How to fix "Bad magic number in super-block"
I fell into this problem when failingly moving a ext4 debian "/" partition with KDE partition manager in live debian USB session.
Long story for me:
I think problem was in old/corrupted USB ...
2
votes
What can cause “multiply claimed blocks” on an ext4 drive?
Multiply claimed blocks can occur with Network/Shared Storage, eg Fibre Channel, iscsi, SAN, JBOD devices etc. With these setups, if they are configured incorrectly, then two systems (Virtual or bare ...
1
vote
Optimize ext4 for 1 giant file
Since you want to store a journalling file system on that, turn off journalling on the ext4 file system; the additional journal doesn't help you.
With a single file, this basically reverts the ...
1
vote
Superblock problem on a crypto_LUKS drive
You are trying to fsck the wrong thing. Fsck thinks that partition is LUKS encrypted. Looking at the photo you also appear to be using LVM.
So I guess you have an LVM physical volume encrypted with ...
1
vote
Superblock problem on a crypto_LUKS drive
The filesystem on your root logical volume is corrupted, not the LUKS device itself. /dev/sda5 is partition that holds the LUKS/dm-crypt device, with encryption (and also LVM which you are also using),...
1
vote
How to enforce fsck during booting system and before rootfs is mounted?
I may misunderstand your question, but:
There is no need to run tune2fs to run fsck. As you are not "tuning" any fs parameters, using tune2fs as a proxy for fsck simply adds overhead & ...
1
vote
e2fsck aftercare
On old Unix, lost+found was (I think) used for any orphaned file. In e2fsck, I believe it is only used for orphaned directories. e2fsck also only ever seems to have one fix for an error.
In any case,...
1
vote
Accepted
diagnose I/O error on WD Blue SSD
I have found a solution from LinuxTechi. When my boot attempt failed I had to do a hard shutdown and this non-clean shutdown has caused a problem with LVM.
The solution:
# lvchange -an /dev/ubuntu-vg/...
1
vote
Accepted
How to clean and reboot HDDs pulled from LVM groups (showing bad super blocks)?
After creating a new LVM logical volume, have you run mkfs without the -n option on it?
You should think of storage as a multi-layered cake: at the bottom is hardware, then there are various ...
1
vote
Does "recovering journal" prove an unclean shutdown/unmount?
The journal contains commands to the filessytem that haven't been yet ben commited. On a clean unmount, whatever is in there is commited, and the journal cleared.
So yes, replaying a journal means an ...
1
vote
Accepted
e2fsck -n + how to know if need to run e2fsck in order to fix corrupted blocks?
You probably are looking for the output of tune2fs rather than e2fsck
tune2fs -l /dev/sdXX |grep "Filesystem state\|Last checked\|Check interval"
which should yield something like this:
Filesystem ...
Only top scored, non community-wiki answers of a minimum length are eligible
Related Tags
e2fsck × 68fsck × 29
filesystems × 20
linux × 18
ext4 × 17
lvm × 9
hard-disk × 6
resize2fs × 6
ubuntu × 5
mount × 5
data-recovery × 5
superblock × 5
boot × 4
partition × 4
fstab × 4
disk × 3
corruption × 3
badblocks × 3
ssd × 2
sd-card × 2
crash × 2
external-hdd × 2
synology × 2
bash × 1
centos × 1