Memperbaiki Superblock ext4 - Revision history

Onnowpurbo at 00:55, 14 July 2014

2014-07-14T00:55:41Z

← Older revision		Revision as of 00:55, 14 July 2014
Line 2:		Line 2:


	~~First~~, ~~figure out what partition we’re dealing with.~~		Cek partisi yang ada,

	sudo fdisk -l		sudo fdisk -l

	~~The above will list all the partitions on all the drives in your computer. To recover a lost partition~~, ~~your going to need Testdisk. Testdisk is included in Parted Magic~~, ~~and there’s a great guide on their site. For this though, we just need the partition number, such as~~ /dev/sda3 or /dev/hdb1.		Dapatkan nomor partisi yang digunakan,seperti, /dev/sda3 atau /dev/hdb1.

	~~Now, make sure your~~ superblock ~~is the problem~~, ~~by starting a~~ filesystem ~~check, replacing~~ xxx ~~with your partition name~~. ~~Here, you can change~~ ext4 to ext3~~, or~~ ext2 ~~to suit the filesystem.~~		Pastikan superblock yang menjadi masalah, cek filesystem ganti xxx dengan nama partisi. Kita dapat mengubah ext4 menjadi ext3 atau ext2

	sudo fsck.ext4 -v /dev/xxx		sudo fsck.ext4 -v /dev/xxx

	~~If your~~ superblock ~~is corrupt~~, ~~the output will look like this~~		Jika superblock korup, keluaran akan seperti berikut

	fsck /dev/sda5		fsck /dev/sda5
Line 26:		Line 26:
	e2fsck -b 8193 <device>		e2fsck -b 8193 <device>

	~~Now lets find where your~~ superblock ~~backups are kept~~.		Selanjutnya kita perlu menemukan dimana backup superblock di simpan.

	sudo mke2fs -n /dev/xxx		sudo mke2fs -n /dev/xxx

	~~Down at the bottom of this output, should be a list of the backups~~		Akan tampak daftar tempat backup

	Superblock backups stored on blocks:		Superblock backups stored on blocks:
	32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208		32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208

	~~Your almost there. Finally, restore the~~ superblock ~~from the~~ backup, ~~again replacing the x’s with your partition name, and~~ block_number ~~with the first~~ backup ~~superblock~~.		Restore superblock dari backup, ganti xxx dengan nama partisi dan block_number dengan nomor backup.

	sudo e2fsck -b block_number /dev/xxx		sudo e2fsck -b block_number /dev/xxx

	~~Now reboot~~, ~~and your~~ superblock ~~should be fixed~~. ~~If it’s not, repeat the steps, but restore a different backup superblock~~		Reboot, dan superblock harusnya fix.




			Jika tidak, ulangi langkah di atas, tapi restore dari backup superblock lainnya.

Onnowpurbo at 00:44, 14 July 2014

2014-07-14T00:44:05Z

← Older revision		Revision as of 00:44, 14 July 2014
Line 1:		Line 1:
	Sumber: http://linuxexpresso.wordpress.com/2010/03/31/repair-a-broken-ext4-superblock-in-ubuntu/		Sumber: http://linuxexpresso.wordpress.com/2010/03/31/repair-a-broken-ext4-superblock-in-ubuntu/



	~~HOWTO: Repair a broken Ext4 Superblock in Ubuntu~~
	~~31Mar10~~

	This has happened to me a few times, and it’s not a nice problem to find yourself in. You computer won’t boot, all your filesystem checks tell you you’ve a bad superblock, but you cant seem to find how to fix it. Well, here goes :)

	This guide is for ext4 , though I’ll explain how other filesystems can be cured along the way. The easiest way to carry all this out, seeing as your computer probably won’t boot at this stage, is to download and burn a copy of Parted Magic. Boot from that, and you’ll access to a number of useful tools.

	First, figure out what partition we’re dealing with.		First, figure out what partition we’re dealing with.

	1		sudo fdisk -l

	sudo fdisk -l

	The above will list all the partitions on all the drives in your computer. To recover a lost partition, your going to need Testdisk. Testdisk is included in Parted Magic, and there’s a great guide on their site. For this though, we just need the partition number, such as /dev/sda3 or /dev/hdb1.		The above will list all the partitions on all the drives in your computer. To recover a lost partition, your going to need Testdisk. Testdisk is included in Parted Magic, and there’s a great guide on their site. For this though, we just need the partition number, such as /dev/sda3 or /dev/hdb1.
Line 20:		Line 10:
	Now, make sure your superblock is the problem, by starting a filesystem check, replacing xxx with your partition name. Here, you can change ext4 to ext3, or ext2 to suit the filesystem.		Now, make sure your superblock is the problem, by starting a filesystem check, replacing xxx with your partition name. Here, you can change ext4 to ext3, or ext2 to suit the filesystem.

	1		sudo fsck.ext4 -v /dev/xxx

	sudo fsck.ext4 -v /dev/xxx

	If your superblock is corrupt, the output will look like this		If your superblock is corrupt, the output will look like this

	1		fsck /dev/sda5
	2		fsck 1.41.4 (27-Jan-2009)
	3		e2fsck 1.41.4 (27-Jan-2009)
	4		fsck.ext4: Group descriptors look bad... trying backup blocks...
	5		fsck.ext4: Bad magic number in super-block while trying to open /dev/sda5
	6
	7
	8
	9
	10
	11

	fsck /dev/sda5
	fsck 1.41.4 (27-Jan-2009)
	e2fsck 1.41.4 (27-Jan-2009)
	fsck.ext4: Group descriptors look bad... trying backup blocks...
	fsck.ext4: Bad magic number in super-block while trying to open /dev/sda5

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

	Now lets find where your superblock backups are kept.		Now lets find where your superblock backups are kept.

	1

	sudo mke2fs -n /dev/xxx		sudo mke2fs -n /dev/xxx

	Down at the bottom of this output, should be a list of the backups		Down at the bottom of this output, should be a list of the backups

			Superblock backups stored on blocks:
	1		32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208
	2

	Superblock backups stored on blocks:
	32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208

	Your almost there. Finally, restore the superblock from the backup, again replacing the x’s with your partition name, and block_number with the first backup superblock.		Your almost there. Finally, restore the superblock from the backup, again replacing the x’s with your partition name, and block_number with the first backup superblock.

			sudo e2fsck -b block_number /dev/xxx
	1

	sudo e2fsck -b block_number /dev/xxx

	Now reboot, and your superblock should be fixed. If it’s not, repeat the steps, but restore a different backup superblock		Now reboot, and your superblock should be fixed. If it’s not, repeat the steps, but restore a different backup superblock

Onnowpurbo: New page: Sumber: http://linuxexpresso.wordpress.com/2010/03/31/repair-a-broken-ext4-superblock-in-ubuntu/ HOWTO: Repair a broken Ext4 Superblock in Ubuntu 31Mar10 This has happened to me a few ...

2014-07-13T20:12:06Z

New page: Sumber: http://linuxexpresso.wordpress.com/2010/03/31/repair-a-broken-ext4-superblock-in-ubuntu/ HOWTO: Repair a broken Ext4 Superblock in Ubuntu 31Mar10 This has happened to me a few ...

New page

Sumber: http://linuxexpresso.wordpress.com/2010/03/31/repair-a-broken-ext4-superblock-in-ubuntu/

HOWTO: Repair a broken Ext4 Superblock in Ubuntu
31Mar10

This has happened to me a few times, and it’s not a nice problem to find yourself in. You computer won’t boot, all your filesystem checks tell you you’ve a bad superblock, but you cant seem to find how to fix it. Well, here goes :)

This guide is for ext4 , though I’ll explain how other filesystems can be cured along the way. The easiest way to carry all this out, seeing as your computer probably won’t boot at this stage, is to download and burn a copy of Parted Magic. Boot from that, and you’ll access to a number of useful tools.

First, figure out what partition we’re dealing with.

1

sudo fdisk -l

The above will list all the partitions on all the drives in your computer. To recover a lost partition, your going to need Testdisk. Testdisk is included in Parted Magic, and there’s a great guide on their site. For this though, we just need the partition number, such as /dev/sda3 or /dev/hdb1.

Now, make sure your superblock is the problem, by starting a filesystem check, replacing xxx with your partition name. Here, you can change ext4 to ext3, or ext2 to suit the filesystem.

1

sudo fsck.ext4 -v /dev/xxx

If your superblock is corrupt, the output will look like this

1
2
3
4
5
6
7
8
9
10
11

fsck /dev/sda5
fsck 1.41.4 (27-Jan-2009)
e2fsck 1.41.4 (27-Jan-2009)
fsck.ext4: Group descriptors look bad... trying backup blocks...
fsck.ext4: Bad magic number in super-block while trying to open /dev/sda5

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

Now lets find where your superblock backups are kept.

1

sudo mke2fs -n /dev/xxx

Down at the bottom of this output, should be a list of the backups

1
2

Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208

Your almost there. Finally, restore the superblock from the backup, again replacing the x’s with your partition name, and block_number with the first backup superblock.

1

sudo e2fsck -b block_number /dev/xxx

Now reboot, and your superblock should be fixed. If it’s not, repeat the steps, but restore a different backup superblock

==Referensi==

* http://linuxexpresso.wordpress.com/2010/03/31/repair-a-broken-ext4-superblock-in-ubuntu/