Skip to main content
Unix & Linux

Return to Question

Revised title; Removed 'disk' tag, because 'hard-disk' is used here; Removed cross-post link because linked question was removed by author.
Source Link
edit approved Sep 19, 2013 at 23:26
Thomas Ward
edit approved Sep 19, 2013 at 23:26
Thomas Ward
  • 2.9k
  • 3
  • 21
  • 32

cannot Disk problems prevent me from booting, or set the disk to read-only. How do I fix ext4 hard drivethe disk?

** This post is Cross-posted from http://askubuntu.com/questions/347631/cannot-fix-ext4-hard-drive

cannot fix ext4 hard drive

** This post is Cross-posted from http://askubuntu.com/questions/347631/cannot-fix-ext4-hard-drive

Disk problems prevent me from booting, or set the disk to read-only. How do I fix the disk?

Massive formatting changes - attempting to put code underneath an ordered list doesn't work, so you either have to use code formatting, or not use ordered lists (fails to number correctly).
Source Link
edit approved Sep 19, 2013 at 23:13
Thomas Ward
edit approved Sep 19, 2013 at 23:13
Thomas Ward
  • 2.9k
  • 3
  • 21
  • 32

(1) Problem:Problem:

 

(2) Attempts:Attempts to Fix:

  1. first of all, fdisk -l shows the following message (copy only the part relevant to /dev/sda1 I am trying to fix):

    WARNING: GPT (GUID Partition Table) detected on '/dev/sda'! The util fdisk doesn't support GPT. Use GNU Parted.

    Disk /dev/sda: 1000.2 GB, 1000204886016 bytes

    255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors

    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 identifier: 0x00000000

    Device Boot Start End Blocks Id System

    /dev/sda1 1 1953525167 976762583+ ee GPT

    Partition 1 does not start on physical sector boundary.

  2. run sudo fsck.ext4 -ck /dev/sda1, trying to fix the hard drive

    e2fsck 1.42.5 (29-Jul-2012)

    ext2fs_open2: Bad magic number in super-block

    fsck.ext4: Superblock invalid, trying backup blocks...

    fsck.ext4: Bad magic number in super-block while trying to open /dev/sda1

    The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 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

  3. sudo e2fsck -b 8193 /dev/sda1, trying to recover super block from block 8193

    first of all, fdisk -l shows the following message (copy only the part relevant to /dev/sda1 I am trying to fix):

e2fsck 1.42.5 (29-Jul-2012) e2fsck: Invalid argument while trying to open /dev/sda1

The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 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 

 WARNING: GPT (GUID Partition Table) detected on '/dev/sda'! The util fdisk doesn't support GPT. Use GNU Parted. Disk /dev/sda: 1000.2 GB, 1000204886016 bytes 255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors 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 identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sda1 1 1953525167 976762583+ ee GPT Partition 1 does not start on physical sector boundary.
  1. run sudo fsck.ext4 -ck /dev/sda1, trying to fix the hard drive
 e2fsck 1.42.5 (29-Jul-2012) ext2fs_open2: Bad magic number in super-block fsck.ext4: Superblock invalid, trying backup blocks... fsck.ext4: Bad magic number in super-block while trying to open /dev/sda1 The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 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
  1. sudo e2fsck -b 8193 /dev/sda1, trying to recover super block from block 8193
 e2fsck 1.42.5 (29-Jul-2012) e2fsck: Invalid argument while trying to open /dev/sda1 The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 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 
 mke2fs 1.42.5 (29-Jul-2012) Filesystem label= OS type: Linux Block size=1024 (log=0) Fragment size=1024 (log=0) Stride=4 blocks, Stripe width=4 blocks 48768 inodes, 194560 blocks 9728 blocks (5.00%) reserved for the super user First data block=1 Maximum filesystem blocks=67371008 24 block groups 8192 blocks per group, 8192 fragments per group 2032 inodes per group Superblock backups stored on blocks: 8193, 24577, 40961, 57345, 73729   
sudo`sudo parted -l `

(1) Problem:

(2) Attempts:

  1. first of all, fdisk -l shows the following message (copy only the part relevant to /dev/sda1 I am trying to fix):

    WARNING: GPT (GUID Partition Table) detected on '/dev/sda'! The util fdisk doesn't support GPT. Use GNU Parted.

    Disk /dev/sda: 1000.2 GB, 1000204886016 bytes

    255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors

    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 identifier: 0x00000000

    Device Boot Start End Blocks Id System

    /dev/sda1 1 1953525167 976762583+ ee GPT

    Partition 1 does not start on physical sector boundary.

  2. run sudo fsck.ext4 -ck /dev/sda1, trying to fix the hard drive

    e2fsck 1.42.5 (29-Jul-2012)

    ext2fs_open2: Bad magic number in super-block

    fsck.ext4: Superblock invalid, trying backup blocks...

    fsck.ext4: Bad magic number in super-block while trying to open /dev/sda1

    The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 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

  3. sudo e2fsck -b 8193 /dev/sda1, trying to recover super block from block 8193

e2fsck 1.42.5 (29-Jul-2012) e2fsck: Invalid argument while trying to open /dev/sda1

The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 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 

 mke2fs 1.42.5 (29-Jul-2012) Filesystem label= OS type: Linux Block size=1024 (log=0) Fragment size=1024 (log=0) Stride=4 blocks, Stripe width=4 blocks 48768 inodes, 194560 blocks 9728 blocks (5.00%) reserved for the super user First data block=1 Maximum filesystem blocks=67371008 24 block groups 8192 blocks per group, 8192 fragments per group 2032 inodes per group Superblock backups stored on blocks: 8193, 24577, 40961, 57345, 73729   
sudo parted -l

Problem:

 

Attempts to Fix:

  1. first of all, fdisk -l shows the following message (copy only the part relevant to /dev/sda1 I am trying to fix):
 WARNING: GPT (GUID Partition Table) detected on '/dev/sda'! The util fdisk doesn't support GPT. Use GNU Parted. Disk /dev/sda: 1000.2 GB, 1000204886016 bytes 255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors 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 identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sda1 1 1953525167 976762583+ ee GPT Partition 1 does not start on physical sector boundary.
  1. run sudo fsck.ext4 -ck /dev/sda1, trying to fix the hard drive
 e2fsck 1.42.5 (29-Jul-2012) ext2fs_open2: Bad magic number in super-block fsck.ext4: Superblock invalid, trying backup blocks... fsck.ext4: Bad magic number in super-block while trying to open /dev/sda1 The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 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
  1. sudo e2fsck -b 8193 /dev/sda1, trying to recover super block from block 8193
 e2fsck 1.42.5 (29-Jul-2012) e2fsck: Invalid argument while trying to open /dev/sda1 The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 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 
 mke2fs 1.42.5 (29-Jul-2012) Filesystem label= OS type: Linux Block size=1024 (log=0) Fragment size=1024 (log=0) Stride=4 blocks, Stripe width=4 blocks 48768 inodes, 194560 blocks 9728 blocks (5.00%) reserved for the super user First data block=1 Maximum filesystem blocks=67371008 24 block groups 8192 blocks per group, 8192 fragments per group 2032 inodes per group Superblock backups stored on blocks: 8193, 24577, 40961, 57345, 73729 
`sudo parted -l `
added 98 characters in body
Source Link
Fashandge
Fashandge
  • 173
  • 2
  • 4
Source Link
Fashandge
Fashandge
  • 173
  • 2
  • 4