Results 1 to 6 of 6

Thread: The superblock could not be read

  1. #1
    Join Date
    Mar 2014
    Beans
    39

    The superblock could not be read

    Hi,

    I'm using lutris to run a game so I run the install script and now I've got a launcher running in wine. What happen then is the game updates something and eats all the available hard drive space. The last time this happened I was able to use a bootable drive to get into an OS (xubuntu) and from there I could mount the drive the OS is on and delete some stuff.

    Now when I'm trying this again I'm unable to mount the drive. I searched for the error message and ended up here, https://askubuntu.com/questions/5398...-error-message. The commands seemed innocuous enough so I ran them. The last command, fsck -y /dev/nvme0n1, outputs
    Code:
    fsck from util-linux 2.34
    e2fsck 1.45.5 (07-Jan-2020)
    ext2fs_open2: Bad magic number in super-block
    fsck.ext2: Superblock invalid, trying backup blocks...
    fsck.ext2: 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/extr4 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 <device>
    
    or
    
    e2fsck -b 32768 <device>
    
    Found a gpt partition table in /dev/nvme0n1
    It looks like I could format the drive and reinstall xubuntu. I can look up how to extract some files from the drive first(?) but I want to know first if there's anything I can do to repair and mount the drive.

  2. #2
    Join Date
    Aug 2006
    Beans
    13,299
    Distro
    Ubuntu Mate 20.04 Focal Fossa

    Re: The superblock could not be read

    You might want to add the output of <sudo fdisk -l> or <sudo parted -l> to check if anything is recognized and /dev/nvme0n1 is the right partition.

  3. #3
    Join Date
    Sep 2009
    Location
    Pennsylvania
    Beans
    3,627
    Distro
    Xubuntu

    Re: The superblock could not be read

    Whenever I see that the message that the super block is bad, that tells me that almost always the drive is bad and you are not likely to retrieve anything from it. Also, I would not ever trust the drive again. While you may be able to reformat it and make it usable, it certainly should not be considered reliable. Personally, for what a spinner HD costs nowadays, I would just get rid of that one and replace it with new.

  4. #4
    Join Date
    Mar 2014
    Beans
    39

    Re: The superblock could not be read

    I got into ubuntu live and was able to use testdisk to backup the folders for most of my projects. Many/most of the files I tried to backup are corrupted though.

    When I try to reinstall xubuntu I get Input/output error during write on /dev/nvme0n1. So I assume the drive is baked.

  5. #5
    Join Date
    Jul 2008
    Location
    The Left Coast of the USA
    Beans
    Hidden!
    Distro
    Kubuntu

    Re: The superblock could not be read

    You may try to restore your nvme to its factory state using the method found here.

    Just be aware that this will make it utterly and absolutely impossible to ever recover its current data ever again.
    Please read The Forum Rules and The Forum Posting Guidelines

    A thing discovered and kept to oneself must be discovered time and again by others. A thing discovered and shared with others need be discovered only the once.
    This universe is crazy. I'm going back to my own.

  6. #6
    Join Date
    May 2010
    Beans
    1,948

    Re: The superblock could not be read

    Why do you not have regular backups if your data is important (you say you used testdisk to recover data so it must be worth something). Why so careless with your data?

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •