I had a I/O error on an external hard drive partition sdb4 (its usual mountpoint being /run/media/yan/data). The partition was non responsive, couldn't be accessed and refused to unmount. I did not know what to do but unplug the disk and replug it. After that I had error on its fs, so I ran fsck: sudo e2fsck /dev/sdb4 -y -v It was asking for a lot of fixes (thousands) but since data is non-critical on that disk, I ran it with -y. data contains a file system with errors, check forced. Pass 1: Checking inodes, blocks, and sizes Pass 2: Checking directory structure # Fixed invalid inode numbers, incorrect filetypes, cleared links, deleted/unused inodes Pass 3: Checking directory connectivity # Connected unconnected directory inodes to /lost+found Pass 4: Checking reference counts #Fix inodes ref count, connected unattached inode to /lost+found Pass 5: Checking group summary information # Fix block bitmap differences, blocks count wrong for group # Fix inode bitmap differences, directories count wrong for group, free inodes count wrong for group data: ***** FILE SYSTEM WAS MODIFIED ***** 72955 inodes used (0.14%, out of 51200000) 2390 non-contiguous files (3.3%) 17 non-contiguous directories (0.0%) # of inodes with ind/dind/tind blocks: 0/0/0 Extent depth histogram: 72264/636/1 186984621 blocks used (91.30%, out of 204800000) 0 bad blocks 34 large files 70447 regular files 2453 directories 0 character device files 0 block device files 0 fifos 4294966642 links 46 symbolic links (46 fast symbolic links) 0 sockets ------------ 71063 files So if I understand correctly, fsck managed to salvage 70k files, so most of the files since I had like 75-80k files on that disk. The problem is that only 20k files appear in '/run/media/yan/data/lost+found', and only 24k on the entire partition. [yan@machine ~]$ find /run/media/yan/data/lost+found | wc -l 19786 [yan@machine ~]$ find /run/media/yan/data | wc -l 23691 I reran fsck but he tells me that the partition is clear (and has 74k files ?) [yan@machine ~]$ sudo fsck /dev/sdb4 fsck from util-linux 2.28 e2fsck 1.42.13 (17-May-2015) data: clean, 74200/51200000 files, 186685980/204800000 blocks[/cpp] I also have very different disk usage according to df and du (I know there should be a difference, but here it seems too big to be normal): [yan@machine ~]$ df -h /run/media/yan/data Filesystem Size Used Avail Use% Mounted on /dev/sdb4 769G 700G 31G 96% /run/media/yan/data [yan@machine ~]$ du -sh /run/media/yan/data 586G /run/media/yan/data I'm guessing there is still recovered data that I can't access. My questions are : 1) Is it possible for recovered files by fsck to not be place in lost+found ? In that case, where are they ? 2) Is there any way to get back those missing files ? 3) If not, how do I free this space ? EDIT: I tried a more recent version of e2fsck on sourcejedi's recommandation: [yan@machine build]$ sudo ./e2fsck/e2fsck -f /dev/sdb4 e2fsck 1.43.3 (04-Sep-2016) Pass 1: Checking inodes, blocks, and sizes Inode 40501578 extent tree (at level 2) could be narrower. Fix? yes Pass 1E: Optimizing extent trees Pass 2: Checking directory structure Pass 3: Checking directory connectivity Pass 4: Checking reference counts Pass 5: Checking group summary information data: ***** FILE SYSTEM WAS MODIFIED ***** data: 74200/51200000 files (3.2% non-contiguous), 186685964/204800000 blocks It did not do much, lost+found still has the same file count and size.

I am using a virtual machine on a server I cannot access and I'm having the filesystem mounted in read-only mode: # dmesg .... [2.535658] EXT4-fs (vda): Couldn't remount RDWR because of unprocessed orphan inode list. Please umount/remount instead So I tried to run: # e2fsck -f /dev/vda e2fsck 1.42.9 (28-Dec-2013) /dev/vda has unsupported feature(s): metadata_csum e2fsck: Get a newer version of e2fsck! Output of df: /dev/root 41022688 37964956 944196 98% / devtmpfs 4084008 0 4084008 0% /dev tmpfs 4085752 0 4085752 0% /dev/shm tmpfs 4085752 397012 3688740 10% /run tmpfs 4085752 0 4085752 0% /sys/fs/cgroup tmpfs 817152 0 817152 0% /run/user/0 tmpfs 817152 0 817152 0% /run/user/1000 Output of mount: /dev/vda on / type ext4 (ro,relatime,stripe=8191,data=ordered) devtmpfs on /dev type devtmpfs (rw,relatime,size=4084008k,nr_inodes=1021002,mode=755) sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime) proc on /proc type proc (rw,nosuid,nodev,noexec,relatime) securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime) tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev) devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000) tmpfs on /run type tmpfs (rw,nosuid,nodev,mode=755) tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755) cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/usr/lib/systemd/systemd-cgroups-agent,name=systemd) cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,relatime,pids) cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct) cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls,net_prio) cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory) cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset) cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices) cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer) systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=23,pgrp=1,timeout=300,minproto=5,maxproto=5,direct) configfs on /sys/kernel/config type configfs (rw,relatime) fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime) nfsd on /proc/fs/nfsd type nfsd (rw,relatime) sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw,relatime) debugfs on /sys/kernel/debug type debugfs (rw,relatime) hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime,pagesize=2M) mqueue on /dev/mqueue type mqueue (rw,relatime) tmpfs on /run/user/0 type tmpfs (rw,nosuid,nodev,relatime,size=817152k,mode=700) tmpfs on /run/user/1000 type tmpfs (rw,nosuid,nodev,relatime,size=817152k,mode=700,uid=1000,gid=1000) Of course, I cannot update e2fsck, as I have a read-only filesystem. How can I escape the loop?

Inode usage go from 1 to 100% on a single file creation in a raid array on Debian. First, clean boot, then:

sudo cryptsetup luksOpen /dev/RaidVG/LVMVol CVol
sudo mount /dev/mapper/CVol /mnt/raid/

Checking inode usage

$ df -ih
Filesystem           Inodes IUsed IFree IUse% Mounted on
/dev/mapper/CVol   117M    11  117M    1% /mnt/raid

Then, doing any touch on /mnt/raid, it failed saying disk is full. My inode usage ramped up at 100% :

$ df -ih
Filesystem           Inodes IUsed IFree IUse% Mounted on
/dev/mapper/CVol   117M  117M     0  100% /mnt/raid

Counting files inside /mnt/raid returns :

$ find | cut -d/ -f2 | uniq -c | sort -n
      1 .
   6033 d1
  14070 d2
  31211 d3
 145866 d4
 184352 d5

fsck can't seems to finish

$ sudo fsck /dev/mapper/CVol
fsck from util-linux 2.33.1
e2fsck 1.44.5 (15-Dec-2018)
/dev/mapper/CVol contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
/lost+found not found.  Create? no
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Signal (6) SIGABRT si_code=SI_TKILL

Also df -h return wrong values : there is more than 1T in use in reality:

$ df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/mapper/CVol  1.8T   77M  1.7T   1% /mnt/raid

I don't really know what to do or where to look at. My file system is "read only" but is there a risk of losing data here? How to fix the problem and be able to write on this disk again? **EDIT** smartctl -a

=== START OF INFORMATION SECTION ===
Vendor:               WD
Product:              My Passport
Revision:             1028
Compliance:           SPC-4
User Capacity:        2,000,365,289,472 bytes [2.00 TB]
Logical block size:   512 bytes
LU is resource provisioned, LBPRZ=0
Rotation Rate:        5400 rpm
Serial number:        WX22A30FX287
Device type:          disk
Local Time is:        Fri Mar 28 12:10:55 2025 GMT
SMART support is:     Unavailable - device lacks SMART capability.

=== START OF READ SMART DATA SECTION ===
Current Drive Temperature:     0 C
Drive Trip Temperature:        0 C

Error Counter logging not supported

No self-tests have been logged

mdadm --examine-badblocks

Bad-blocks list is empty in /dev/sda1
Bad-blocks list is empty in /dev/sdb1

fdisk -l /dev/sda /dev/sdb

Disk /dev/sda: 1.8 TiB, 2000365289472 bytes, 3906963456 sectors
Disk model: My Passport 
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x1dfd4f21

Device     Boot Start        End    Sectors  Size Id Type
/dev/sda1        2048 3906963455 3906961408  1.8T fd Linux raid autodetect


Disk /dev/sdb: 1.8 TiB, 2000365289472 bytes, 3906963456 sectors
Disk model: My Passport 
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x9f2cb37d

Device     Boot Start        End    Sectors  Size Id Type
/dev/sdb1        2048 3906963455 3906961408  1.8T fd Linux raid autodetect

pvs

PV         VG     Fmt  Attr PSize  PFree
  /dev/md0   RaidVG lvm2 a--

While creating an install USB disk, I made the trivial error of indicating the wrong device, and ended up overwriting the initial few hundred megabytes of a 230 GB disk. The data was not extremely important, but I would still like to recover what I can. The first, obvious attempt, was `photorec`, which did find some stuff. But then, I hoped I could "fix" what was left of the filesystem (after all, I overwrote less than 0.5%). So I tried to run `e2fsck` with several combinations of parameters, including using a backup superblock (in an analogous way to what is suggested in an answer to a related question ), and I ended up with a bunch of folders in "lost+found" - fair enough. The problem is that some of these folders still give errors such as

ls: cannot access 'lost+found/#26128': Structure needs cleaning

... but if I now run again `e2fsck -f` (as suggested in other answers ), I get nothing strange

e2fsck 1.47.0 (5-Feb-2023)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
EData: 191504/15269888 files (0.1% non-contiguous), 48227460/61049344 blocks

... and by the way, this only takes a couple of seconds, so it is clear that it's not actually check all the content of the disk. I tried to check for other options, and for instance tried `-E discard, but nothing changed: the check is still very quick, and some folders inside lost+found` still give the same errors. How can I fix the errors with those folders that say "Structure needs cleaning"? Note that the device is perfectly working from a hardware point of view.

I am trying to utilize e2fsck but it produces the following:

sudo e2fsck -f /dev/vgtrisquel/home
e2fsck 1.46.5 (30-Dec-2021)
Pass 1: Checking inodes, blocks, and sizes
Inode  extent tree (at level 1) could be shorter.  Optimize?

It continues to show many other Inodes that could be shorter. Should I say yes to optimizing all of them? Does this have any potential issues? The data on this drive has been backed up. Thank you so much for any support you can provide.

observe the below error - How to get past this? Ran fsck -y, fsck -a and fsck -f on nvme0n1p1, nvme0n1p2, etc. Initially I recall seeing some "ignore error" prompts which were automatically answered with a y. But later runs just succeed. Yet I am unable to login to my debian system. EDIT: Copying out of the partition with dd yielded the below; but running badblocks showed none of it -

dd: error reading '/dev/nvme0n1p3': Input/output error
536299424+414 records in
536299838+0 records out
274585517056 bytes (275 GB, 256 GiB) copied, 7226.72 s, 38.0 MB/s
dd: error reading '/dev/nvme0n1p3': Input/output error
536299424+415 records in
536299839+0 records out
274585517568 bytes (275 GB, 256 GiB) copied, 7226.84 s, 38.0 MB/s
283465585152 bytes (283 GB, 264 GiB) copied, 7615 s, 37.2 MB/s
553647712+416 records in
553648128+0 records out
283467841536 bytes (283 GB, 264 GiB) copied, 7618.66 s, 37.2 MB/s
    ~                                                                                   ✔  2h 6m 59s  
    ~  sudo badblocks -v /dev/nvme0n1p3 > badblocks3.txt                                              ✔ 
Checking blocks 0 to 276824063
Checking for bad blocks (read-only test): 
done                                                 
Pass completed, 0 bad blocks found. (0/0/0 errors)

“Multiply claimed blocks” is an error reported by fsck when blocks appear to belong to more than one file. This causes data corruption since both files change when one of the files are written. **But what can be the original causes of multiply claimed blocks? How are they created and how can I avoid them?**

I have a mystery ... a reproducibile one, but still a mystery. My ideapad 100s has a SD card reader which I use to store stuff while I work on it, as its built-in drive is super tiny. Its really just a temporary use, because I normally git push stuff quite frequently. This has worked for sometime, but now stuff that I add to this SD card filesystem disappears at the time of umount. All the files I did put before are still there, it's just the new stuff that disappears. It happens all the times I do umount. I have tried to issue sync . in the new folder, I have also tried to change a bit the fstab line for this SD card, but cannot solve this. I noted that in dmesg there is a message about the filesystem

[Sun Dec 10 19:34:48 2023] EXT4-fs (mmcblk1p1): warning: mounting unchecked fs, running e2fsck is recommended
[Sun Dec 10 19:34:48 2023] EXT4-fs (mmcblk1p1): mounted filesystem without journal. Opts: (null)

and I did try a simple e2fsck and it insists that it was not cleanly unmounted even after repeating.

sudo e2fsck /dev/mmcblk1p1 
e2fsck 1.46.2 (28-Feb-2021)
/dev/mmcblk1p1 was not cleanly unmounted, check forced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/mmcblk1p1: 18783/15622144 files (0.1% non-contiguous), 17101516/62459904 blocks

The exit code is 1, which means it has corrected errors according to the man page of e2fs. Any idea what I am doing wrong here?

I try to move all data from one SSD to another SSD. The old SSD is 500 GB, and the new SSD is 1000 GB. Firstly I've created a backup:

dd if=/dev/nvme0n1 | gzip -c /media/ubuntu/local/backup1.img.gz

Then I tried to restore the backup:

gunzip -c /media/ubuntu/local/backup1.img.gz | dd of=/dev/nvme0n1

After that, I got an error:

$ sudo e2fsck /dev/nvme0n1
e2fsck 1.46.5 (30-Dec-2021)
ext2fs_open2: Bad magic number in super-block
e2fsck: Superblock invalid, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open /dev/nvme0n1

The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem.  If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
    e2fsck -b 8193 
 or
    e2fsck -b 32768 

Found a gpt partition table in /dev/nvme0n1

Do you know how I can fix it? Additional output for details:

$ lsblk -f
NAME        FSTYPE   FSVER            LABEL                    UUID                                 FSAVAIL FSUSE% MOUNTPOINTS
sdc                                                                                                                
└─sdc1      ntfs                      local                    824A5D3E4A5D2FE1                        244G    49% /media/ubuntu/local
nvme0n1                                                                                                            
├─nvme0n1p1                                                                                                        
├─nvme0n1p2                                                                                                        
├─nvme0n1p3                                                                                                        
├─nvme0n1p4                                                                                                        
├─nvme0n1p5                                                                                                        
├─nvme0n1p6                                                                                                        
└─nvme0n1p7

I have dd error reading # sudo dd if=/dev/sda1 of=backup.img bs=4M status=progress 16478679040 bytes (16 GB, 15 GiB) copied, 154 s, 107 MB/s dd: error reading '/dev/sda1': Input/output error 3928+1 records in 3928+1 records out 16478679040 bytes (16 GB, 15 GiB) copied, 156.816 s, 105 MB/s I thought this probably means disk has bad blocks. I ran # e2fsck -cfpv -C 0 /dev/sda1 /dev/sda1: Updating bad block inode. 700895 inodes used (3.66%, out of 19144704) 2596 non-contiguous files (0.4%) 1226 non-contiguous directories (0.2%) # of inodes with ind/dind/tind blocks: 0/0/0 Extent depth histogram: 638434/974/3 9995951 blocks used (13.05%, out of 76571648) 1 bad block 3 large files 515535 regular files 117354 directories 57 character device files 26 block device files 0 fifos 284 links 67853 symbolic links (61332 fast symbolic links) 61 sockets ------------ 701170 files It apparently fixed not what important for dd. How to fix what is needed?

When running

-bash
e2fsck -cck /dev/mapper/xxx

I am prompted with

has 487 multiply-claimed block(s), shared with 84 file(s): 
 ... (inode #221446306, mod time Tue Feb 20 19:48:38 2018) 
 ... (inode #221446305, mod time Tue Feb 20 19:48:32 2018) 
 ... (inode #221446304, mod time Tue Feb 20 19:48:38 2018) 
 ... (inode #221446303, mod time Tue Feb 20 19:48:12 2018) 
 ... (inode #221446302, mod time Tue Feb 20 19:59:04 2018) 
 ... (inode #221446300, mod time Tue Feb 20 19:47:52 2018) 
Clone multiply-claimed blocks?

What will be the possible consequence of continuing with "yes"? Will there be complete data loss? What is the result if continue with "no"?

On my server, I had an SSD as the boot drive with 11 6TB HDDs in a RAID6 setup as additional storage. However, after running into some issues with the motherboard, I switched the motherboard to one with only 4 SATA ports, so I reduced the size of the RAID6 setup from 11 to 4 drives. With ? no Pass 1: Checking inodes, blocks, and sizes Error reading block 3401580576 (Invalid argument) while getting next inode from scan. Ignore error? yes Force rewrite? yes Error reading block 3401580577 (Invalid argument) while getting next inode from scan. Ignore error? yes Force rewrite? yes Error reading block 3401580578 (Invalid argument) while getting next inode from scan. Ignore error? yes Force rewrite? yes Error reading block 3401580579 (Invalid argument) while getting next inode from scan. Ignore error? yes Force rewrite? yes Error reading block 3401580580 (Invalid argument) while getting next inode from scan. Ignore error? yes Force rewrite? yes Error reading block 3401580581 (Invalid argument) while getting next inode from scan. Ignore error? yes Force rewrite? yes Error reading block 3401580582 (Invalid argument) while getting next inode from scan. Ignore error? yes Force rewrite?

My hypothesis is that there is probably some inconsistency in the reported size of the drives. I do not believe I had any partitions on the RAID nor any LVM volumes.

sudo fdisk -l ... Disk /dev/sda: 5.46 TiB, 6001175126016 bytes, 11721045168 sectors Disk model: WDC WD60EZAZ-00S Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/sdb: 5.46 TiB, 6001175126016 bytes, 11721045168 sectors Disk model: WDC WD60EZAZ-00S Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/sdc: 5.46 TiB, 6001175126016 bytes, 11721045168 sectors Disk model: WDC WD60EZAZ-00S Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/sdd: 5.46 TiB, 6001175126016 bytes, 11721045168 sectors Disk model: WDC WD60EZAZ-00S Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/md127: 10.92 TiB, 12002079539200 bytes, 23441561600 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 524288 bytes / 1048576 bytes ``` The data on the 4 currently in use may or may not be altered by fsck / e2fsck, but the data should also be on the other 7 unused drives with the zeroed superblocks. It is not important to me which drives I recover the data from, so working solutions to recover from any grouping of the drives would be highly appreciated! If any additional information is needed, I would be more than happy to provide it.

When I run "e2fsck" command through cli it asks for options like asking for abort, force rewrite etc, and the process get completed successfully. But I want to run "e2fsck" command using apache by executing this command through a bash script, from here I cannot pass these arguments. I have tries using -a, -p arguments the don't work. The closest solution that worked was from https://unix.stackexchange.com/a/487438/563769 , it successfully passed n to abort but cannot pass yes to all others.

Notebook fails to boot. I started it with a live USB Ubuntu 20.04 and tried mount /dev/sda5 but receive this error: mount: /mnt: can't read superblock on /dev/sda5 So I tried the commands below: ubuntu@ubuntu:~$ sudo fdisk -l /dev/sda Disk /dev/sda: 931,53 GiB, 1000204886016 bytes, 1953525168 sectors Disk model: WDC WD10SPZX-21Z Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: gpt Disk identifier: 8798743C-1711-4EC3-9829-F392872338D3 Device          Start        End    Sectors   Size Type /dev/sda1        2048     206847     204800   100M EFI System /dev/sda2      206848     239615      32768    16M Microsoft reserved /dev/sda3      239616  408477642  408238027 194,7G Microsoft basic data /dev/sda4  1951424512 1953521663    2097152     1G Windows recovery environment /dev/sda5   408477696 1951424511 1542946816 735,8G Linux filesystem Partition table entries are not in disk order. I have tried the solution presented here but I have not been successful. ubuntu@ubuntu:~$ sudo mke2fs -n /dev/sda5 mke2fs 1.45.5 (07-Jan-2020) Creating filesystem with 192868352 4k blocks and 48218112 inodes Filesystem UUID: 9f522638-1d6a-451f-b608-dc03acd3250b Superblock backups stored on blocks: 32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, 4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968, 102400000 Consulted here , I tried with all the blocks: block 98304 * 4 = 393216, without success. ubuntu@ubuntu:~$ sudo mount -o sb=393216 /dev/sda5 /mnt mount: /mnt: can't read superblock on /dev/sda5. ubuntu@ubuntu:~$ sudo mount -o sb=655360 /dev/sda5 /mnt mount: /mnt: wrong fs type, bad option, bad superblock on /dev/sda5, missing codepage or helper program, or other error. ubuntu@ubuntu:~$ sudo mount -o sb=917504 /dev/sda5 /mnt mount: /mnt: can't read superblock on /dev/sda5. ubuntu@ubuntu:~$ sudo mount -o sb=1179648 /dev/sda5 /mnt mount: /mnt: can't read superblock on /dev/sda5. ubuntu@ubuntu:~$ sudo mount -o sb=3276800 /dev/sda5 /mnt mount: /mnt: can't read superblock on /dev/sda5. ubuntu@ubuntu:~$ sudo mount -o sb=3538944 /dev/sda5 /mnt mount: /mnt: wrong fs type, bad option, bad superblock on /dev/sda5, missing codepage or helper program, or other error. ubuntu@ubuntu:~$ sudo mount -o sb=6422528 /dev/sda5 /mnt mount: /mnt: wrong fs type, bad option, bad superblock on /dev/sda5, missing codepage or helper program, or other error. ubuntu@ubuntu:~$ sudo mount -o sb=10616832 /dev/sda5 /mnt mount: /mnt: wrong fs type, bad option, bad superblock on /dev/sda5, missing codepage or helper program, or other error. ubuntu@ubuntu:~$ sudo mount -o sb=16384000 /dev/sda5 /mnt mount: /mnt: can't read superblock on /dev/sda5. ubuntu@ubuntu:~$ sudo mount -o sb=31850496 /dev/sda5 /mnt mount: /mnt: wrong fs type, bad option, bad superblock on /dev/sda5, missing codepage or helper program, or other error. ubuntu@ubuntu:~$ sudo mount -o sb=44957696 /dev/sda5 /mnt mount: /mnt: can't read superblock on /dev/sda5. ubuntu@ubuntu:~$ sudo mount -o sb=81920000 /dev/sda5 /mnt mount: /mnt: can't read superblock on /dev/sda5. ubuntu@ubuntu:~$ sudo mount -o sb=95551488 /dev/sda5 /mnt mount: /mnt: can't read superblock on /dev/sda5. ubuntu@ubuntu:~$ sudo mount -o sb=286654464 /dev/sda5 /mnt mount: /mnt: wrong fs type, bad option, bad superblock on /dev/sda5, missing codepage or helper program, or other error. ubuntu@ubuntu:~$ sudo mount -o sb=314703872 /dev/sda5 /mnt mount: /mnt: wrong fs type, bad option, bad superblock on /dev/sda5, missing codepage or helper program, or other error. ubuntu@ubuntu:~$ sudo mount -o sb=409600000 /dev/sda5 /mnt mount: /mnt: wrong fs type, bad option, bad superblock on /dev/sda5, missing codepage or helper program, or other error. After that I have runned e2fsck for 3 days, without success. ubuntu@ubuntu:~$ sudo e2fsck -f -y -v -c -b 32768 /dev/sda5 e2fsck 1.45.5 (07-Jan-2020) Error reading block 1149 (Input/output error).  Ignore error? yes Force rewrite? yes Superblock has an invalid journal (inode 8). Clear? yes *** journal has been deleted *** Resize inode not valid.  Recreate? yes Error reading block 1117 (Input/output error) while reading inode and block bitmaps.  Ignore error? yes Force rewrite? yes Error reading block 1133 (Input/output error) while reading inode and block bitmaps.  Ignore error? yes Force rewrite? yes Error reading block 1118 (Input/output error) while reading inode and block bitmaps.  Ignore error? yes Force rewrite? yes Error reading block 1134 (Input/output error) while reading inode and block bitmaps.  Ignore error? yes Force rewrite? yes Error reading block 1119 (Input/output error) while reading inode and block bitmaps.  Ignore error? yes Force rewrite? yes Error reading block 1120 (Input/output error) while reading inode and block bitmaps.  Ignore error? yes Force rewrite? yes Error reading block 1122 (Input/output error) while reading inode and block bitmaps.  Ignore error? yes Error dmesg: [217797.911529] ata1: EH complete [217807.220171] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 [217807.220191] ata1.00: irq_stat 0x40000001 [217807.220198] ata1.00: failed command: READ DMA EXT [217807.220203] ata1.00: cmd 25/00:08:d8:e0:98/00:00:18:00:00/e0 tag 24 dma 4096 in                          res 51/40:08:d8:e0:98/00:00:18:00:00/e0 Emask 0x9 (media error) [217807.220220] ata1.00: status: { DRDY ERR } [217807.220225] ata1.00: error: { UNC } [217812.260182] ata1.00: qc timeout (cmd 0xec) [217812.260211] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x5) [217812.260222] ata1.00: revalidation failed (errno=-5) [217812.260240] ata1: hard resetting link [217812.575276] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310) [217818.410875] ata1.00: configured for UDMA/133 [217818.410924] sd 0:0:0:0: [sda] tag#24 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=20s [217818.410936] sd 0:0:0:0: [sda] tag#24 Sense Key : Medium Error [current] [217818.410945] sd 0:0:0:0: [sda] tag#24 Add. Sense: Unrecovered read error - auto reallocate failed [217818.410955] sd 0:0:0:0: [sda] tag#24 CDB: Read(10) 28 00 18 98 e0 d8 00 00 08 00 [217818.410960] blk_update_request: I/O error, dev sda, sector 412672216 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 [217818.411029] ata1: EH complete [217821.396529] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 [217821.396556] ata1.00: irq_stat 0x40000001 [217821.396568] ata1.00: failed command: READ DMA EXT [217821.396575] ata1.00: cmd 25/00:08:d8:e0:98/00:00:18:00:00/e0 tag 20 dma 4096 in                          res 51/40:08:d8:e0:98/00:00:18:00:00/e0 Emask 0x9 (media error) [217821.396604] ata1.00: status: { DRDY ERR } [217821.396612] ata1.00: error: { UNC } [217826.592096] ata1.00: qc timeout (cmd 0xec) [217826.592112] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x5) [217826.592116] ata1.00: revalidation failed (errno=-5) [217826.592122] ata1: hard resetting link [217826.908977] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310) [217845.710563] ata1.00: configured for UDMA/133 [217845.710611] sd 0:0:0:0: [sda] tag#20 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=27s [217845.710624] sd 0:0:0:0: [sda] tag#20 Sense Key : Medium Error [current] [217845.710632] sd 0:0:0:0: [sda] tag#20 Add. Sense: Unrecovered read error - auto reallocate failed [217845.710641] sd 0:0:0:0: [sda] tag#20 CDB: Read(10) 28 00 18 98 e0 d8 00 00 08 00 [217845.710647] blk_update_request: I/O error, dev sda, sector 412672216 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 [217845.710670] Buffer I/O error on dev sda5, logical block 524315, async page read [217845.710722] ata1: EH complete [217861.384383] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 [217861.384409] ata1.00: irq_stat 0x40000001 [217861.384420] ata1.00: failed command: READ DMA EXT [217861.384428] ata1.00: cmd 25/00:08:d8:e0:98/00:00:18:00:00/e0 tag 0 dma 4096 in                          res 51/40:08:d8:e0:98/00:00:18:00:00/e0 Emask 0x9 (media error) [217861.384457] ata1.00: status: { DRDY ERR } [217861.384465] ata1.00: error: { UNC } [217866.528299] ata1.00: qc timeout (cmd 0xec) [217866.528326] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x5) [217866.528335] ata1.00: revalidation failed (errno=-5) [217866.528352] ata1: hard resetting link [217866.843346] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310) [217885.732336] ata1.00: configured for UDMA/133 [217885.732383] sd 0:0:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=40s [217885.732395] sd 0:0:0:0: [sda] tag#0 Sense Key : Medium Error [current] [217885.732404] sd 0:0:0:0: [sda] tag#0 Add. Sense: Unrecovered read error - auto reallocate failed [217885.732414] sd 0:0:0:0: [sda] tag#0 CDB: Read(10) 28 00 18 98 e0 d8 00 00 08 00 [217885.732419] blk_update_request: I/O error, dev sda, sector 412672216 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 [217885.732442] Buffer I/O error on dev sda5, logical block 524315, async page read [217885.732492] ata1: EH complete [217895.039725] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 [217895.039750] ata1.00: irq_stat 0x40000001 [217895.039761] ata1.00: failed command: READ DMA EXT [217895.039769] ata1.00: cmd 25/00:08:60:e0:98/00:00:18:00:00/e0 tag 1 dma 4096 in                          res 51/40:08:60:e0:98/00:00:18:00:00/e0 Emask 0x9 (media error) [217895.039797] ata1.00: status: { DRDY ERR } [217895.039806] ata1.00: error: { UNC } [217900.067695] ata1.00: qc timeout (cmd 0xec) [217900.067710] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x5) [217900.067715] ata1.00: revalidation failed (errno=-5) [217900.067723] ata1: hard resetting link [217900.383017] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310) [217919.221200] ata1.00: configured for UDMA/133 [217919.221247] sd 0:0:0:0: [sda] tag#1 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=33s [217919.221260] sd 0:0:0:0: [sda] tag#1 Sense Key : Medium Error [current] [217919.221269] sd 0:0:0:0: [sda] tag#1 Add. Sense: Unrecovered read error - auto reallocate failed [217919.221279] sd 0:0:0:0: [sda] tag#1 CDB: Read(10) 28 00 18 98 e0 60 00 00 08 00 [217919.221285] blk_update_request: I/O error, dev sda, sector 412672096 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 [217919.221353] ata1: EH complete In this topic it is presented how to find a sector offset in the partition to safely zero the block, but I didn't feel confident to proceed.   ubuntu@ubuntu:~$ sudo smartctl -a /dev/sda5 smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.11.0-27-generic] (local build) Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family:     Western Digital Blue Device Model:     WDC WD10SPZX-21Z10T0 Serial Number:    WD-WXS1A877RJED LU WWN Device Id: 5 0014ee 6081e1249 Firmware Version: 02.01A02 User Capacity:    1.000.204.886.016 bytes [1,00 TB] Sector Sizes:     512 bytes logical, 4096 bytes physical Rotation Rate:    5400 rpm Form Factor:      2.5 inches Device is:        In smartctl database [for details use: -P show] ATA Version is:   ACS-3 T13/2161-D revision 5 SATA Version is:  SATA 3.1, 6.0 Gb/s (current: 1.5 Gb/s) Local Time is:    Wed Nov 10 02:11:30 2021 UTC SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: FAILED! Drive failure expected in less than 24 hours. SAVE ALL DATA. See vendor-specific Attribute list for failed Attributes. General SMART Values: Offline data collection status:  (0x00) Offline data collection activity was never started. Auto Offline Data Collection: Disabled. Self-test execution status:      (   0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: ( 7680) seconds. Offline data collection capabilities: (0x71) SMART execute Offline immediate. No Auto Offline data collection support. Suspend Offline collection upon new command. No Offline surface scan supported. Self-test supported. Conveyance Self-test supported. Selective Self-test supported. SMART capabilities:            (0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability:        (0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time: (   2) minutes. Extended self-test routine recommended polling time: ( 223) minutes. Conveyance self-test routine recommended polling time: (   1) minutes. SCT capabilities:       (0x3035) SCT Status supported. SCT Feature Control supported. SCT Data Table supported. SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE   1 Raw_Read_Error_Rate     0x002f   001   001   051    Pre-fail  Always   FAILING_NOW 19950   3 Spin_Up_Time            0x0027   194   187   021    Pre-fail  Always       -       1258   4 Start_Stop_Count        0x0032   092   092   000    Old_age   Always       -       8733   5 Reallocated_Sector_Ct   0x0033   200   200   140    Pre-fail  Always       -       0   7 Seek_Error_Rate         0x002e   200   200   000    Old_age   Always       -       0   9 Power_On_Hours          0x0032   093   093   000    Old_age   Always       -       5258  10 Spin_Retry_Count        0x0032   100   100   000    Old_age   Always       -       0  11 Calibration_Retry_Count 0x0032   100   100   000    Old_age   Always       -       0  12 Power_Cycle_Count       0x0032   099   099   000    Old_age   Always       -       1222 191 G-Sense_Error_Rate      0x0032   001   001   000    Old_age   Always       -       31491 192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       44 193 Load_Cycle_Count        0x0032   181   181   000    Old_age   Always       -       59346 194 Temperature_Celsius     0x0022   104   098   000    Old_age   Always       -       39 196 Reallocated_Event_Count 0x0032   200   200   000    Old_age   Always       -       0 197 Current_Pending_Sector  0x0032   198   198   000    Old_age   Always       -       441 198 Offline_Uncorrectable   0x0030   100   253   000    Old_age   Offline      -       0 199 UDMA_CRC_Error_Count    0x0032   200   200   000    Old_age   Always       -       0 200 Multi_Zone_Error_Rate   0x0008   100   253   000    Old_age   Offline      -       0 SMART Error Log Version: 1 ATA Error Count: 219 (device log contains only the most recent five errors) CR = Command Register [HEX] FR = Features Register [HEX] SC = Sector Count Register [HEX] SN = Sector Number Register [HEX] CL = Cylinder Low Register [HEX] CH = Cylinder High Register [HEX] DH = Device/Head Register [HEX] DC = Device Command Register [HEX] ER = Error register [HEX] ST = Status register [HEX] Powered_Up_Time is measured from power on, and printed as DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes, SS=sec, and sss=millisec. It "wraps" after 49.710 days. Error 219 occurred at disk power-on lifetime: 5257 hours (219 days + 1 hours)   When the command that caused the error occurred, the device was active or idle.   After command completion occurred, registers were:   ER ST SC SN CL CH DH   -- -- -- -- -- -- --   40 51 02 02 a8 03 e0  Error: UNC 2 sectors at LBA = 0x0003a802 = 239618   Commands leading to the command that caused the error were:   CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name   -- -- -- -- -- -- -- --  ----------------  --------------------   c8 00 02 02 a8 03 e0 08   2d+00:46:14.317  READ DMA   ec 00 00 00 00 00 a0 08   2d+00:46:14.316  IDENTIFY DEVICE   ef 03 46 00 00 00 a0 08   2d+00:46:14.316  SET FEATURES [Set transfer mode]   ec 00 00 00 00 00 a0 08   2d+00:46:14.212  IDENTIFY DEVICE Error 218 occurred at disk power-on lifetime: 5200 hours (216 days + 16 hours)   When the command that caused the error occurred, the device was active or idle.   After command completion occurred, registers were:   ER ST SC SN CL CH DH   -- -- -- -- -- -- --   40 51 08 00 28 03 e0  Error: UNC 8 sectors at LBA = 0x00032800 = 206848   Commands leading to the command that caused the error were:   CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name   -- -- -- -- -- -- -- --  ----------------  --------------------   c8 00 08 00 28 03 e0 08      02:27:11.836  READ DMA   e5 00 00 00 00 00 00 08      02:27:11.836  CHECK POWER MODE   ec 00 00 00 00 00 a0 08      02:27:11.835  IDENTIFY DEVICE   ef 03 46 00 00 00 a0 08      02:27:11.825  SET FEATURES [Set transfer mode]   ec 00 00 00 00 00 a0 08      02:27:11.704  IDENTIFY DEVICE Error 217 occurred at disk power-on lifetime: 5200 hours (216 days + 16 hours)   When the command that caused the error occurred, the device was active or idle.   After command completion occurred, registers were:   ER ST SC SN CL CH DH   -- -- -- -- -- -- --   40 51 08 00 28 03 e0  Error: UNC 8 sectors at LBA = 0x00032800 = 206848   Commands leading to the command that caused the error were:   CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name   -- -- -- -- -- -- -- --  ----------------  --------------------   c8 00 08 00 28 03 e0 08      02:26:57.401  READ DMA   e5 00 00 00 00 00 00 08      02:26:57.400  CHECK POWER MODE   ec 00 00 00 00 00 a0 08      02:26:57.384  IDENTIFY DEVICE   ef 03 46 00 00 00 a0 08      02:26:57.384  SET FEATURES [Set transfer mode] Error 216 occurred at disk power-on lifetime: 5200 hours (216 days + 16 hours)   When the command that caused the error occurred, the device was active or idle.   After command completion occurred, registers were:   ER ST SC SN CL CH DH   -- -- -- -- -- -- --   40 51 08 80 27 03 e0  Error: UNC 8 sectors at LBA = 0x00032780 = 206720   Commands leading to the command that caused the error were:   CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name   -- -- -- -- -- -- -- --  ----------------  --------------------   c8 00 08 80 27 03 e0 08      02:26:15.363  READ DMA   ec 00 00 00 00 00 a0 08      02:26:15.349  IDENTIFY DEVICE   ef 03 46 00 00 00 a0 08      02:26:15.337  SET FEATURES [Set transfer mode]   ec 00 00 00 00 00 a0 08      02:26:15.223  IDENTIFY DEVICE Error 215 occurred at disk power-on lifetime: 5200 hours (216 days + 16 hours)   When the command that caused the error occurred, the device was active or idle.   After command completion occurred, registers were:   ER ST SC SN CL CH DH   -- -- -- -- -- -- --   40 51 08 80 27 03 e0  Error: UNC 8 sectors at LBA = 0x00032780 = 206720   Commands leading to the command that caused the error were:   CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name   -- -- -- -- -- -- -- --  ----------------  --------------------   c8 00 08 80 27 03 e0 08      02:26:03.763  READ DMA   ec 00 00 00 00 00 a0 08      02:26:03.762  IDENTIFY DEVICE   ef 03 46 00 00 00 a0 08      02:26:03.759  SET FEATURES [Set transfer mode]   ec 00 00 00 00 00 a0 08      02:26:03.630  IDENTIFY DEVICE SMART Self-test log structure revision number 1 No self-tests have been logged.  [To run self-tests, use: smartctl -t] SMART Selective self-test log data structure revision number 1  SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS     1        0        0  Not_testing     2        0        0  Not_testing     3        0        0  Not_testing     4        0        0  Not_testing     5        0        0  Not_testing Selective self-test flags (0x0):   After scanning selected spans, do NOT read-scan remainder of disk. If Selective self-test is pending on power-up, resume after 0 minute delay. I don't have some files backed up so I need to find a way to recover the hard drive, any ideas?

I have a broken ext4 partition which I want to recover. The problem occurred because of a sudden power loss. The partition is an encrypted luks partition. Opening the luks container works. Say I open it to /dev/mapper/test. Then I am able to mount the partition like

mount -t ext4 -o sb=131072,ro /dev/mapper/test /mnt

Where 131072 is the location of the [superblock multiplied by 4](https://superuser.com/q/1137415/53616) . Then I can access the files (which I already backed up after the successful mount). However if I try to [repair the superblock](https://linuxexpresso.wordpress.com/2010/03/31/repair-a-broken-ext4-superblock-in-ubuntu/) the following happens:

e2fsck -b 32768 /dev/mapper/test 
e2fsck 1.46.3 (27-Jul-2021)
/dev/mapper/test was not cleanly unmounted, check forced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Free blocks count wrong for group #0 (23391, counted=280).
Fix?

If I press y the same message Free blocks count wrong for group #0 (23391, counted=280). appears again and again (with another number at the end). I already pressed yes several times and then hold the y key down for a certain time. Now I am looking for an advice what to do to repair the the partition. Is there an automatic way to answer y to this question so I don't have to hold the y key for an indefinite time? I could use the -y command line parameter, but then other questions would be also answered with yes. Or should I do something else?

I have a Sandisk 1TB SDD that is in SMART Pre-fail as my boot disk on a machine running Ubuntu 22.04. Recently this disk failed to boot the machine, and is no longer mountable when removed and mounted in a USB enclosure. The filesystem is ext4 on top of an LVM VG. The disk is the only PV in the Volume group ubuntu-vg. I was able to pull a full dd image of this drive after replacing it and installing the OS from scratch. The physical drive and the image both give me the same fsck errors when trying to repair the root partition. I am unable to mount this partition even though the system recognizes it as an ext4 filesystem. I have tried running fsck with multiple backup superblocks with no difference in the output, other than an extra "Filesystem was modified" line if I use a backup superblock. When trying to mount I get "can't read superblock" errors. If I hexedit the image I can data on the disk so it seems like there is just a problem with the superblock or the journal, but I'm not sure what to do at this point.

$ sudo mount /dev/mapper/ubuntu--vg-root /mnt/oldroot/
mount: /mnt/oldroot: can't read superblock on /dev/mapper/ubuntu--vg-root.


$ sudo fsck -v /dev/mapper/ubuntu--vg-root 
fsck from util-linux 2.37.2
e2fsck 1.46.5 (30-Dec-2021)
/dev/mapper/ubuntu--vg-root: recovering journal
Superblock needs_recovery flag is clear, but journal has data.
Run journal anyway? yes
fsck.ext4: Input/output error while recovering journal of /dev/mapper/ubuntu--vg-root
fsck.ext4: unable to set superblock flags on /dev/mapper/ubuntu--vg-root


/dev/mapper/ubuntu--vg-root: ********** WARNING: Filesystem still has errors **********

I imaged a failing SSD as best I could using ddrescue or dd (it's been too long to recall which). With the resulting .img, I've burnt a disk which is not recognised as mountable. Using e2fsck -fyvC 0 upon the disk, I'm able to subsequently mount it, recovering some, but certainly not all, files originally on the SSD. Is this the best option I'd have for data retrieval, or is there a better tool which could recover more? Running e2fsck with the above flags, I receive various warnings about orphaned or deleted inodes, which are either fixed or deleted. Unfortunately, these seem to correspond to the data I'm most seeking from the disk. The output is 227,000 lines, but some highlights below:

ext2fs_open2: Bad magic number in super-block
e2fsck: Superblock invalid, trying backup blocks...
Superblock has an invalid journal (inode 8).
Clear? yes

*** journal has been deleted ***

Superblock has_journal flag is clear, but a journal is present.
Clear? yes

Truncating orphaned inode 6302578 (uid=1000, gid=1000, mode=0100664, size=3600)
Pass 1: Checking inodes, blocks, and sizes

[...]

Inode 1048618 was part of the orphaned inode list.  FIXED.
Inode 1048634 was part of the orphaned inode list.  FIXED.
Deleted inode 1048662 has zero dtime.  Fix? yes

[...]

Entry '..' in / (9965526) has deleted/unused inode 6291748.  Clear? yes

[...]

Unattached inode 9712327
Connect to /lost+found? yes

Inode 9712327 ref count is 2, should be 1.  Fix? yes

[...]

Free blocks count wrong for group #740 (32768, counted=3012).
Fix? yes

[...]

Directories count wrong for group #4593 (0, counted=114).
Fix? yes

[...]

Padding at end of inode bitmap is not set. Fix? yes

Recreate journal? yes

Creating journal (262144 blocks):  Done.

*** journal has been regenerated ***

/dev/sdc: ***** FILE SYSTEM WAS MODIFIED *****

     2205797 inodes used (4.52%, out of 48807936)
       20864 non-contiguous files (0.9%)
        1884 non-contiguous directories (0.1%)
             # of inodes with ind/dind/tind blocks: 0/0/0
             Extent depth histogram: 2154021/1685/13
   128999150 blocks used (66.08%, out of 195210139)
           0 bad blocks
          18 large files

     1869601 regular files
      282774 directories
          10 character device files
           1 block device file
           5 fifos
  4294963048 links
       53513 symbolic links (50169 fast symbolic links)
          14 sockets
------------
     2164179 files

Are there more advisable methods of data recovery here? Thanks in advance for any assistance.

I am an novice to servers and RAID arrays, but I am trying to restore a raid 5 array that has recently started to have problems with mounting onto our server. Full disclosure, I was not the one who originally set up this array. I am working with a Dell 2950 PowerEdge server that we have installed CentOS 7 on to manage programs and files. My issue began when I couldn't start up the server after a restart. My current set up tries to mount the array when the main server is started up. The command in /etc/fstab currently is commented out on bootup of our server because it causes the server to crash on start up. When the server is started, we uncomment out the line

/dev/sdc  /array   ext4   defaults    1 2

Then when I try and mount with:

mount /array

I get the following:

mount: wrong fs type, bad option, bad superblock on /dev/sdc,
       missing codepage or helper program, or other error

       In some cases useful info is found in syslog - try
       dmesg | tail or so.

Tailing the dmesg:

[1625373.377926] sd 1:2:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
[1625373.377929] sd 1:2:0:0: [sdc] tag#0 CDB: Read(16) 88 00 00 00 00 00 00 00 00 00 00 00 00 08 00 00
[1625373.377931] blk_update_request: I/O error, dev sdc, sector 0
[1625373.377933] Buffer I/O error on dev sdc, logical block 0, async page read
[1633765.092732] nf_conntrack: falling back to vmalloc.
[1633765.093244] nf_conntrack: falling back to vmalloc.
[1633782.909748] sd 1:2:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
[1633782.909757] sd 1:2:0:0: [sdc] tag#0 CDB: Read(16) 88 00 00 00 00 00 00 00 00 02 00 00 00 02 00 00
[1633782.909761] blk_update_request: I/O error, dev sdc, sector 2
[1633782.909782] EXT4-fs (sdc): unable to read superblock

It appears that there is a bad superblock. I am not sure where to even begin on how to approach fixing this issue. I don't want to reformat the entire array at loss of the data (over 10 TB) if I can avoid it. Some other helpful information might be that this is not a MD compatible server (might be obvious, wasn't to me initially) so

commands are not applicable. It is set up with a EXT4 file system. The array was also not likely properly partitioned when it was initialized 5+ years ago, i.e., there is no sdc0, sdc1, etc. I am not sure as to the full ramifications of that might have, but it sounds like certain functions/scripts will assume that the array is properly partitioned and can cause things to get "hairy" if used improperly. Any help with this issue would be greatly appreciated. If there is information that I am not providing that would help in diagnosing the issue, please let me know. Update: I wanted to see if I could find which superblock was having trouble. With the array unmounted, I tried the following:

$ dumpe2fs /dev/sdc | grep -i superblock

output from that command gave me:

dumpe2fs 1.42.9 (28-Dec-2013)
dumpe2fs: Attempt to read block from filesystem resulted in short read while trying to open /dev/sdc
Couldn't find valid filesystem superblock.

I also tried running

-n /dev/sdc

to try and see if I could get more information on the Superblocks. this was the results

# mke2fs -n /dev/sdc
mke2fs 1.42.9 (28-Dec-2013)
/dev/sdc is entire device, not just one partition!
Proceed anyway? (y,n) y
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
335577088 inodes, 2684616704 blocks
134230835 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=4294967296
81928 block groups
32768 blocks per group, 32768 fragments per group
4096 inodes per group
Superblock backups stored on blocks: 
        32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, 
        4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968, 
        102400000, 214990848, 512000000, 550731776, 644972544, 1934917632, 
        2560000000

Update (2022-11-15) I was able to get some assistance from our IT team and we were able to get into the BIOS for our server. It might be helpful to know our raid 5 was a PERC 5/E, and in the BIOS we found that the slot 8 disk was considered "foreign". We "import"ed (NOT "clear") the disk in slot 8 and the array came back up, but in a degraded state. Odd thing was that our disk in slot 0 was marked as "missing" which was odd. I believe that there was a disk inserted into the array as a global hot spare, and I think that it was used by the array to maintain parody. To ensure we don't lose the data, I am backing up the array on the external 15 TB drive with "rsync" before trying to figure out how to reestablish the global hot spare. Fingers crossed the copy process goes smoothly. Thanks everyone for all the help!

I wanted to run disk check on my Ubuntu 22.04 boot partition, so I rebooted the machine into recovery mode and tried to run fsck. However, I got this error:

/lib/recovery-mode/recovery-menu: line 80: /etc/default/rcS: No such file or directory
fsck from util-linux 2.34
/dev/nvme0n1p2 is mounted.
e2fsck: Cannon continue, aborting. 

Finished, please press ENTER

What could be the reason?

My raspberry pi will no longer boot up due to the following error: End Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(179,2) I've tried fsck and I'm unable to get it to fix or even attempt to fix my drive: pi@raspberrypi:~ $ sudo fsck -p /dev/sda2 fsck from util-linux 2.36.1 fsck.ext4: Read-only file system while trying to open /dev/sda2 Disk write-protected; use the -n option to do a read-only check of the device. Sadly I have some arduino sketches I would really like to recover from this drive. I can do a read only scan and see there are issues, but how do I change the protections so that fsck can try to repair it? Here is the read scan (sudo fsck -nf /dev/sda2): pi@raspberrypi:~ $ sudo fsck -nf /dev/sda2 fsck from util-linux 2.36.1 e2fsck 1.46.2 (28-Feb-2021) Warning: skipping journal recovery because doing a read-only filesystem check. Pass 1: Checking inodes, blocks, and sizes Inode 772 extent tree (at level 1) could be shorter. Optimize? no Inodes that were part of a corrupted orphan linked list found. Fix? no Inode 3589 was part of the orphaned inode list. IGNORED. Inode 3700 was part of the orphaned inode list. IGNORED. Inode 3719 was part of the orphaned inode list. IGNORED. Inode 4631 was part of the orphaned inode list. IGNORED. Inode 5440 was part of the orphaned inode list. IGNORED. Inode 5441 was part of the orphaned inode list. IGNORED. Inode 6036 was part of the orphaned inode list. IGNORED. Inode 6053 was part of the orphaned inode list. IGNORED. Inode 26345 was part of the orphaned inode list. IGNORED. Inode 265227 was part of the orphaned inode list. IGNORED. Inode 771825 seems to contain garbage. Clear? no Inode 771825 is in use, but has dtime set. Fix? no Inode 771825 has corrupt extent header. Clear inode? no Inode 771825, i_size is 148618787707562243, should be 0. Fix? no Inode 771825, i_blocks is 83951626, should be 0. Fix? no Inode 771826 seems to contain garbage. Clear? no Inode 771826 was part of the orphaned inode list. IGNORED. Inode 771826 has inline data and extent flags set but i_block contains junk. Clear inode? no Inode 771826 has INLINE_DATA_FL flag on filesystem without inline data support. Clear? no Inode 771826 is in use, but has dtime set. Fix? no Inode 771826 has imagic flag set. Clear? no Inode 771826 has a extra size (296) which is invalid Fix? no Inode 771826, i_size is 4507998747628544, should be 60. Fix? no Inode 771826, i_blocks is 33686536, should be 0. Fix? no Inode 771827 seems to contain garbage. Clear? no Inode 771827 is in use, but has dtime set. Fix? no Inode 771827 has corrupt extent header. Clear inode? no Inode 771827, i_size is 16140901064495857973, should be 0. Fix? no Inode 771827, i_blocks is 4104, should be 0. Fix? no Inode 771828 seems to contain garbage. Clear? no Inode 771828 has a extra size (1072) which is invalid Fix? no Inode 771828 has encrypt flag but no encryption extended attribute. Clear flag? no Inode 771828, i_size is 576465152514195458, should be 0. Fix? no Inode 771828, i_blocks is 2169503768, should be 0. Fix? no Inode 771829 seems to contain garbage. Clear? no Inode 771829 is in use, but has dtime set. Fix? no Inode 771829 has a extra size (16416) which is invalid Fix? no Inode 771829 has corrupt extent header. Clear inode? no Inode 771829 is a zero-length directory. Clear? no Inode 771829, i_size is 6755399445385280, should be 0. Fix? no Inode 771829, i_blocks is 74, should be 0. Fix? no Inode 771830 seems to contain garbage. Clear? no Inode 771830 has a bad extended attribute block 524288. Clear? no Extended attribute block 524288 has h_blocks > 1. Clear? no Inode 771830 has illegal extended attribute value inode 4294967295. Clear? no Inode 771830 has illegal extended attribute value inode 4294967295. Clear? no Inode 771********* WARNING: Filesystem still has errors ********** e2fsck: aborted rootfs: ********** WARNING: Filesystem still has errors **********830 has illegal extended attribute value inode 4294967295. Clear? no Inode 771830 has illegal extended attribute value inode 4294967295. Clear? no Inode 771830 has illegal extended attribute value inode 4294967295. Clear? no Inode 771830 has illegal extended attribute value inode 4294967295. Clear? no Inode 771830 has illegal extended attribute value inode 4294967295. Clear? no Inode 771830 has illegal extended attribute value inode 4294967295. Clear? no Inode 771830, i_size is 4503600701112341, should be 0. Fix? no Inode 771830, i_blocks is 33686536, should be 15801896177070021640. Fix? no Inode 771831 seems to contain garbage. Clear? no Inode 771831 is in use, but has dtime set. Fix? no Inode 771831 has corrupt extent header. Clear inode? no Inode 771831, i_size is 9840365185804536413, should be 0. Fix? no Inode 771831, i_blocks is 4194312, should be 0. Fix? no Inode 771832 seems to contain garbage. Clear? no Inode 771832 was part of the orphaned inode list. IGNORED. Inode 771832 is in use, but has dtime set. Fix? no Inode 771832 has encrypt flag but no encryption extended attribute. Clear flag? no Inode 771832 has a bad extended attribute block 4112. Clear? no Extended attribute block 4112 has h_blocks > 1. Clear? no Inode 771832 has corrupt extent header. Clear inode? no Inode 771832, i_size is 72202731720278510, should be 0. Fix? no Inode 771832, i_blocks is 2181038168, should be 8. Fix? no Inode 771833 seems to contain garbage. Clear? no Inode 771833 is in use, but has dtime set. Fix? no Inode 771833 has a extra size (12320) which is invalid Fix? no Inode 771833 has corrupt extent header. Clear inode? no Inode 771833, i_blocks is 67117083, should be 0. Fix? no Inode 771834 seems to contain garbage. Clear? no Inode 771834 has inline data and extent flags set but i_block contains junk. Clear inode? no Inode 771834 has INLINE_DATA_FL flag on filesystem without inline data support. Clear? no Inode 771834, i_blocks is 131344, should be 0. Fix? no Inode 771835 seems to contain garbage. Clear? no Inode 771835 is in use, but has dtime set. Fix? no Inode 771835 has corrupt extent header. Clear inode? no Inode 771835, i_size is 6953557824664244236, should be 0. Fix? no Inode 771835, i_blocks is 4194320, should be 0. Fix? no Inode 771836 seems to contain garbage. Clear? no Inode 771836 is in use, but has dtime set. Fix? no Inode 771836 has a bad extended attribute block 4113. Clear? no Extended attribute block 4113 has h_blocks > 1. Clear? no Inode 771836 has corrupt extent header. Clear inode? no Inode 771836, i_size is 216207966485882557, should be 0. Fix? no Inode 771836, i_blocks is 24, should be 8. Fix? no Inode 771837 seems to contain garbage. Clear? no Inode 771837 is in use, but has dtime set. Fix? no Inode 771837 has corrupt extent header. Clear inode? no Inode 771837 is a zero-length directory. Clear? no Inode 771837, i_size is 148618787708604416, should be 0. Fix? no Inode 771837, i_blocks is 270346, should be 0. Fix? no Inode 771838 seems to contain garbage. Clear? no Inode 771838, i_blocks is 33686540, should be 0. Fix? no Inode 771839 seems to contain garbage. Clear? no Inode 771839 is in use, but has dtime set. Fix? no Inode 771839 has corrupt extent header. Clear inode? no Inode 771839, i_size is 13839561657061741032, should be 0. Fix? no Inode 771839, i_blocks is 4112, should be 0. Fix? no Inode 771840 seems to contain garbage. Clear? no Inode 771840 is in use, but has dtime set. Fix? no Inode 771840 has encrypt flag but no encryption extended attribute. Clear flag? no Inode 771840 has corrupt extent header. Clear inode? no Inode 771840, i_size is 216172784278055494, should be 0. Fix? no Inode 771840, i_blocks is 16777240, should be 0. Fix? no Inode 771841 seems to contain garbage. Clear? no Inode 771841 has a bad extended attribute block 2098692. Clear? no Extended attribute block 2098692 has h_blocks > 1. Clear? no Inode 771841, i_size is 148618787707576904, should be 0. Fix? no Inode 771841, i_blocks is 270402, should be 8. Fix? no Inode 771842 seems to contain garbage. Clear? no Inode 771842 was part of the orphaned inode list. IGNORED. Inode 771842 is in use, but has dtime set. Fix? no Inode 771842 has imagic flag set. Clear? no Inode 771842 has a extra size (4128) which is invalid Fix? no Inode 771842, i_size is 4503599627439962, should be 0. Fix? no Inode 771842, i_blocks is 262152, should be 15801896177070021640. Fix? no Inode 771843 seems to contain garbage. Clear? no Inode 771843 is in use, but has dtime set. Fix? no Inode 771843 has corrupt extent header. Clear inode? no Inode 771843 is a zero-length directory. Clear? no Inode 771843, i_size is 10380798240600625412, should be 0. Fix? no Inode 771843, i_blocks is 262152, should be 0. Fix? no Inode 771845 seems to contain garbage. Clear? no Inode 771845 is in use, but has dtime set. Fix? no Inode 771845 has a bad extended attribute block 2097152. Clear? no Extended attribute block 2097152 has h_blocks > 1. Clear? no Inode 771845 has illegal extended attribute value inode 4294967295. Clear? no Inode 771845 has illegal extended attribute value inode 4294967295. Clear? no Inode 771845 has illegal extended attribute value inode 4294967295. Clear? no Inode 771845 has illegal extended attribute value inode 4294967295. Clear? no Inode 771845 has illegal extended attribute value inode 4294967295. Clear? no Inode 771845 has illegal extended attribute value inode 4294967295. Clear? no Inode 771845 has illegal extended attribute value inode 4294967295. Clear? no Inode 771845 has corrupt extent header. Clear inode? no Inode 771845, i_size is 6755399445389763, should be 0. Fix? no Inode 771845, i_blocks is 67108872, should be 176932271371126920. Fix? no Inode 771846 seems to contain garbage. Clear? no Inode 771846 has inline data and extent flags set but i_block contains junk. Clear inode? no Inode 771846 has INLINE_DATA_FL flag on filesystem without inline data support. Clear? no Inode 771846 is in use, but has dtime set. Fix? no Inode 771846 has imagic flag set. Clear? no Inode 771846 has a extra size (296) which is invalid Fix? no Inode 771846, i_size is 4503599635848405, should be 0. Fix? no Inode 771846, i_blocks is 33554480, should be 15801896177070021640. Fix? no Inode 771847 seems to contain garbage. Clear? no Inode 771847 is in use, but has dtime set. Fix? no Inode 771847 has a bad extended attribute block 6291456. Clear? no Extended attribute block 6291456 has h_blocks > 1. Clear? no Inode 771847 has illegal extended attribute value inode 4294967295. Clear? no Inode 771847 has illegal extended attribute value inode 4294967295. Clear? no Inode 771847 has illegal extended attribute value inode 4294967295. Clear? no Inode 771847 has illegal extended attribute value inode 4294967295. Clear? no Inode 771847 has illegal extended attribute value inode 4294967295. Clear? no Inode 771847 has illegal extended attribute value inode 4294967295. Clear? no Inode 771847 has illegal extended attribute value inode 4294967295. Clear? no Inode 771847 has corrupt extent header. Clear inode? no Inode 771847, i_size is 1157425106382226396, should be 0. Fix? no Inode 771847, i_blocks is 4194312, should be 6909130127295187080. Fix? no Inode 771848 seems to contain garbage. Clear? no Inode 771848 is in use, but has dtime set. Fix? no Inode 771848 has a extra size (160) which is invalid Fix? no Inode 771848 has a bad extended attribute block 4097. Clear? no Extended attribute block 4097 has h_blocks > 1. Clear? no Inode 771848 has corrupt extent header. Clear inode? no Inode 771848, i_size is 216172784261274474, should be 0. Fix? no Inode 771848, i_blocks is 2148532304, should be 8. Fix? no Inode 771849 seems to contain garbage. Clear? no Inode 771849 is in use, but has dtime set. Fix? no Inode 771849 has a extra size (5152) which is invalid Fix? no Inode 771849 has a bad extended attribute block 329216. Clear? no Extended attribute block 329216 has h_blocks > 1. Clear? no Inode 771849 has illegal extended attribute value inode 523238. Clear? no Inode 771849 has corrupt extent header. Clear inode? no Inode 771849, i_blocks is 32, should be 8892766049774834568. Fix? no Inode 771850 seems to contain garbage. Clear? no Inode 771850 has inline data and extent flags set but i_block contains junk. Clear inode? no Inode 771850 has INLINE_DATA_FL flag on filesystem without inline data support. Clear? no Inode 771850, i_size is 2251800887495463, should be 0. Fix? no Inode 771850, i_blocks is 35782664, should be 0. Fix? no Inode 771851 seems to contain garbage. Clear? no Inode 771851 is in use, but has dtime set. Fix? no Inode 771851 has a bad extended attribute block 18874368. Clear? no Extended attribute block 18874368 has h_blocks > 1. Clear? no Inode 771851 has illegal extended attribute value inode 4294967295. Clear? no Inode 771851 has illegal extended attribute value inode 4294967295. Clear? no Inode 771851 has illegal extended attribute value inode 4294967295. Clear? no Inode 771851 has illegal extended attribute value inode 4294967295. Clear? no Inode 771851 has corrupt extent header. Clear inode? no Inode 771851, i_size is 13835058055282177670, should be 0. Fix? no Inode 771851, i_blocks is 4368, should be 17124320125389786632. Fix? no Inode 771852 seems to contain garbage. Clear? no Inode 771852 has a extra size (1200) which is invalid Fix? no Inode 771852 has corrupt extent header. Clear inode? no Inode 771852 is a zero-length directory. Clear? no Inode 771852, i_size is 14400, should be 0. Fix? no Inode 771852, i_blocks is 18874368, should be 0. Fix? no Inode 771853 seems to contain garbage. Clear? no Inode 771853 is in use, but has dtime set. Fix? no Inode 771853 has a extra size (20576) which is invalid Fix? no Inode 771853 has corrupt extent header. Clear inode? no Inode 771853, i_blocks is 1056778, should be 0. Fix? no Inode 771854 seems to contain garbage. Clear? no Inode 771854 was part of the orphaned inode list. IGNORED. Inode 771854 is in use, but has dtime set. Fix? no Inode 771854, i_blocks is 33686528, should be 0. Fix? no Inode 771855 seems to contain garbage. Clear? no Inode 771855, i_size is 9259541573513807567, should be 0. Fix? no Inode 771855, i_blocks is 8, should be 0. Fix? no Inode 771856 seems to contain garbage. Clear? no Inode 771856 is in use, but has dtime set. Fix? no Inode 771856 has a bad extended attribute block 17. Clear? no Extended attribute block 17 has h_blocks > 1. Clear? no Inode 771856 has illegal extended attribute value inode 4096017. Clear? no Inode 771856 has corrupt extent header. Clear inode? no Inode 771856, i_size is 216172784278048420, should be 0. Fix? no Inode 771856, i_blocks is 88, should be 8892766049774834568. Fix? no Inode 771857 seems to contain garbage. Clear? no Inode 771857 has a extra size (4192) which is invalid Fix? no Inode 771857 has corrupt extent header. Clear inode? no Inode 771857, i_size is 150870587517961694, should be 0. Fix? no Inode 771857, i_blocks is 1073741834, should be 0. Fix? no Inode 771858 seems to contain garbage. Clear? no Inode 771858 was part of the orphaned inode list. IGNORED. Inode 771858 is in use, but has dtime set. Fix? no Inode 771858 has a extra size (416) which is invalid Fix? no Inode 771858, i_size is 4503600701113609, should be 0. Fix? no Inode 771858, i_blocks is 33554440, should be 15801896177070021640. Fix? no Inode 771859 seems to contain garbage. Clear? no Inode 771859 was part of the orphaned inode list. IGNORED. Inode 771859 is in use, but has dtime set. Fix? no Inode 771859 has a extra size (16416) which is invalid Fix? no Inode 771859 has an invalid extent (logical block 131088, invalid physical block 8592572336, len 3) Clear? no Inode 771859 has an invalid extent (logical block 0, invalid physical block 4362076160, len 0) Clear? no Inode 771859 has an invalid extent (logical block 0, invalid physical block 39977986, len 2048) Clear? no HTREE directory inode 771859 has an invalid root node. Clear HTree index? no Inode 771859 is a zero-length directory. Clear? no Inode 771859, i_size is 16181433463289679880, should be 0. Fix? no Inode 771859, i_blocks is 4248, should be 0. Fix? no Inode 771860 seems to contain garbage. Clear? no Inode 771860 is in use, but has dtime set. Fix? no Inode 771860 has a extra size (32800) which is invalid Fix? no Inode 771860 has corrupt extent header. Clear inode? no Inode 771860, i_size is 72057600480430372, should be 0. Fix? no Inode 771860, i_blocks is 2702180456, should be 8. Fix? no Inode 771861 seems to contain garbage. Clear? no Inode 771861 has a extra size (4128) which is invalid Fix? no Inode 771861 has corrupt extent header. Clear inode? no Inode 771861, i_size is 35184376299449, should be 0. Fix? no Inode 771861, i_blocks is 1048608, should be 0. Fix? no Inode 771862 seems to contain garbage. Clear? no Inode 771862 was part of the orphaned inode list. IGNORED. Inode 771862 is in use, but has dtime set. Fix? no Inode 771862 has a extra size (4392) which is invalid Fix? no Inode 771862, i_blocks is 33686536, should be 0. Fix? no Inode 771863 seems to contain garbage. Clear? no Inode 771863 was part of the orphaned inode list. IGNORED. Inode 771863 is in use, but has dtime set. Fix? no Inode 771863 has a extra size (32804) which is invalid Fix? no Inode 771863 has corrupt extent header. Clear inode? no Inode 771863, i_size is 13835058058772360485, should be 0. Fix? no Inode 771863, i_blocks is 24, should be 0. Fix? no Inode 771864 seems to contain garbage. Clear? no Inode 771864 was part of the orphaned inode list. IGNORED. Inode 771864 is in use, but has dtime set. Fix? no Inode 771864 has a extra size (176) which is invalid Fix? no Inode 771864 has encrypt flag but no encryption extended attribute. Clear flag? no Inode 771864 has corrupt extent header. Clear inode? no Inode 771864, i_size is 72057596185458043, should be 0. Fix? no Inode 771864, i_blocks is 16777328, should be 8892766049774834568. Fix? no Inode 771865 seems to contain garbage. Clear? no Inode 771865 is in use, but has dtime set. Fix? no Inode 771865 has corrupt extent header. Clear inode? no Inode 771865, i_blocks is 1310731, should be 0. Fix? no Inode 771866 seems to contain garbage. Clear? no Inode 771866 has corrupt extent header. Clear inode? no Inode 771866, i_blocks is 33555464, should be 15801896177070021640. Fix? no Inode 771867 seems to contain garbage. Clear? no Inode 771867 is in use, but has dtime set. Fix? no Inode 771867 has a bad extended attribute block 524416. Clear? no Extended attribute block 524416 has h_blocks > 1. Clear? no Extended attribute block 524416 is corrupt (invalid name). Clear? no Extended attribute block 524416 is corrupt (allocation collision). Clear? no Inode 771867 has corrupt extent header. Clear inode? no Inode 771867, i_size is 16434197992380043265, should be 0. Fix? no Inode 771867, i_blocks is 4198408, should be 8. Fix? no Inode 771868 seems to contain garbage. Clear? no Inode 771868 was part of the orphaned inode list. IGNORED. Inode 771868 is in use, but has dtime set. Fix? no Inode 771868 has encrypt flag but no encryption extended attribute. Clear flag? no Inode 771868 has corrupt extent header. Clear inode? no Inode 771868, i_size is 166773923717842966, should be 0. Fix? no Inode 771868, i_blocks is 2685403272, should be 0. Fix? no Inode 771869 seems to contain garbage. Clear? no Inode 771869 was part of the orphaned inode list. IGNORED. Inode 771869 is in use, but has dtime set. Fix? no Inode 771869 has a extra size (16480) which is invalid Fix? no Inode 771869 has corrupt extent header. Clear inode? no Inode 771869, i_size is 4616189618058964450, should be 0. Fix? no Inode 771869, i_blocks is 1048842, should be 0. Fix? no Inode 771870 seems to contain garbage. Clear? no Inode 771870 was part of the orphaned inode list. IGNORED. Inode 771870 seems to have inline data but extent flag is set. Fix? no Inode 771870 has inline data and extent flags set but i_block contains junk. Clear inode? no Inode 771870 has INLINE_DATA_FL flag on filesystem without inline data support. Clear? no Inode 771870 is in use, but has dtime set. Fix? no Inode 771870 has a extra size (288) which is invalid Fix? no Inode 771870, i_blocks is 132104, should be 0. Fix? no Inode 771871 seems to contain garbage. Clear? no Inode 771871 is in use, but has dtime set. Fix? no Inode 771871 has corrupt extent header. Clear inode? no Inode 771871, i_size is 13839561654909534230, should be 0. Fix? no Inode 771871, i_blocks is 134219784, should be 0. Fix? no Inode 771872 seems to contain garbage. Clear? no Inode 771872 was part of the orphaned inode list. IGNORED. Inode 771872 is in use, but has dtime set. Fix? no Inode 771872 has encrypt flag but no encryption extended attribute. Clear flag? no Inode 771872, i_size is 72057594054714491, should be 0. Fix? no Inode 771872, i_blocks is 2147483736, should be 0. Fix? no Inode 771873 is in use, but has dtime set. Fix? no Inode 771873 has a extra size (16416) which is invalid Fix? no Inode 771873 has a bad extended attribute block 262144. Clear? no Extended attribute block 262144 has h_blocks > 1. Clear? no Inode 771873 extent tree could be more shallow (64; could be 1. Clear? no Inode 771876 has corrupt extent header. Clear inode? no Inode 771876, i_blocks is 96, should be 8. Fix? no Error reading extended attribute block 17 (Extended attribute block has a bad header). rootfs: ********** WARNING: Filesystem still has errors ********** e2fsck: aborted rootfs: ********** WARNING: Filesystem still has errors **********