On Fri, 14 Jul 2017 18:01:16 +0200 "Patrick Dupre" <pdupre@xxxxxxx> wrote: > Now, what would you do with this > When I try to mount this partition: > /dev/sdd6 317001728 405065727 88064000 42G 83 Linux > (>L Linux 19732 113 30 25214 44 46 88064000 > [Backup]) The size is OK > But: > mount /dev/sdd6 /mnt/tmp > mount: wrong fs type, bad option, bad superblock on /dev/sdd6, > missing codepage or helper program, or other error > > [27212.278322] EXT4-fs (sdd6): error loading journal > [28134.857250] JBD2: no valid journal superblock found > [28134.857254] EXT4-fs (sdd6): error loading journal > [29533.339281] JBD2: no valid journal superblock found > [29533.339286] EXT4-fs (sdd6): error loading journal > > > Should I run fsck? Yes. The first run I would use e2fsck -c -v /dev/sdd6 which is verbose and read only, so it should be faster. It doesn't make any changes to the disk. The disk is already unmounted, which is what you want when doing these diagnostics and repairs. Once you have that output, it will tell you what kind of shape the filesystem is in, and you can decide your next step. You will probably need to use the -b option to point to a valid superblock, and the -p option to fix any errors, at some point. Depending on how much time you have, you could also run e2fsck -c -c -v /dev/sdd6 before that, which does a non-destructive read-write test. This is slower, but will tell you if the disk is bad; there will be lots of write failures if it is bad. Slow and deliberate is the way to go, measuring 3 times before you cut once. man e2fsck for more information. If you install smartmontools, you can use smartctl to get data from the disks themselves, if they have it. man smartctl _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
