Format - Revision history

Onnowpurbo at 13:05, 13 January 2019

2019-01-13T13:05:24Z

← Older revision		Revision as of 13:05, 13 January 2019
Line 5:		Line 5:
	Jalankan		Jalankan

	smartctl -a /dev/sdb		smartctl -a -d sat /dev/sdb

	Format USB flashdisk / USB harddisk / harddisk dapat menggunakan		Format USB flashdisk / USB harddisk / harddisk dapat menggunakan

Onnowpurbo at 13:04, 13 January 2019

2019-01-13T13:04:07Z

← Older revision		Revision as of 13:04, 13 January 2019
Line 1:		Line 1:
			Smartmon

			apt install smartmontools

			Jalankan

			smartctl -a /dev/sdb

	Format USB flashdisk / USB harddisk / harddisk dapat menggunakan		Format USB flashdisk / USB harddisk / harddisk dapat menggunakan

	mkfs		mkfs
			mkfs.ext3
			mkfs.ext4

	Catatan penggunaan:		Catatan penggunaan:

Onnowpurbo: /* Cek Bed Blocks */

2015-05-17T07:22:03Z

Cek Bed Blocks

← Older revision		Revision as of 07:22, 17 May 2015
Line 36:		Line 36:


	==Cek ~~Bed~~ Blocks==		==Cek Bad Blocks==

			'''WARNING: Proses ini akan memakan waktu lama sekali. Mungkin semalam-an'''

	Memformat sambil cek bed blocks		Memformat sambil cek bed blocks

	mkfs -L data -c /dev/sdb1		mkfs -L data -c /dev/sdb1


	==Menggunakan badblocks==		==Menggunakan badblocks==

Onnowpurbo: /* Menggunakan badblocks */

2015-05-17T07:21:47Z

Menggunakan badblocks

← Older revision		Revision as of 07:21, 17 May 2015
Line 44:		Line 44:

	==Menggunakan badblocks==		==Menggunakan badblocks==

			'''WARNING: Proses ini akan memakan waktu lama sekali. Mungkin semalam-an'''

	Sebelum mkfs kita dapat menjalankan badblocks		Sebelum mkfs kita dapat menjalankan badblocks

Onnowpurbo: /* Menggunakan badblocks */

2015-05-17T07:18:40Z

Menggunakan badblocks

← Older revision		Revision as of 07:18, 17 May 2015
Line 45:		Line 45:
	==Menggunakan badblocks==		==Menggunakan badblocks==

	~~Before Filesystem Creation~~		Sebelum mkfs kita dapat menjalankan badblocks

	~~Alternately, this can be done before filesystem creation.~~		badblocks -wsv /dev/<drive>

	~~If badblocks is run without the -o option~~ bad ~~sectors will only be printed to stdout~~.		[...]
			done
			Pass completed, 527405 bad blocks found. (0/0/527405 errors)

	~~Example~~ output ~~for read errors in the beginning of the disk:~~		Atau output di simpan ke sebuah file

	# badblocks -wsv /dev/<~~drive~~>		badblocks -wsv -o /root/<badblocks.txt> /dev/<device>

	~~[...]~~		Checking for bad blocks in read-write mode
	Testing with pattern ~~0xff~~: done		From block 0 to 488386583
	Reading and comparing:		Testing with pattern 0xaa: done
	[.~~..]~~		Reading and comparing: 6.36% done, 0:51 elapsed. (0/0/14713 errors)
	~~37584~~		[...]
	~~37585 0.84~~% done, ~~7:31~~:08 elapsed. (0/0/~~527405~~ errors)		Testing with pattern 0x00: done
	~~37586~~		Reading and comparing: done
	[...]		Pass completed, 527405 bad blocks found. (0/0/527405 errors)
	~~done~~
	Testing with pattern 0x00:
	Reading and comparing:
	~~[...]~~
	~~37584~~
	~~37585~~
	~~[...]~~
	done
	Pass completed, 527405 bad blocks found. (0/0/527405 errors)

	~~For comfortably passing badblocks error output to the filesystem it has to be written to a~~ file.		file tersebut digunakan saat format

	~~# badblocks -wsv -o /root/<badblocks.txt> /dev/<device>~~

	~~Checking for bad blocks in read-write mode~~
	~~From block 0 to 488386583~~
	~~Testing with pattern 0xaa: done~~
	~~Reading and comparing: 6.36% done, 0:51 elapsed. (0/0/14713 errors)~~
	~~[...]~~
	~~Testing with pattern 0x00: done~~
	~~Reading and comparing: done~~
	~~Pass completed, 527405 bad blocks found. (0/0/527405 errors)~~

	~~Then (re-)create the file system with the information:~~

	# mkfs.<filesystem-type> -l /root/<badblocks.txt> /dev/<device>		# mkfs.<filesystem-type> -l /root/<badblocks.txt> /dev/<device>

	Note: ~~The meaning of~~ 0/0/527405 errors is <number of read errors>/<number of write errors>/<number of corruption errors>.		Catatan: Note: 0/0/527405 errors adalah <number of read errors>/<number of write errors>/<number of corruption errors>.

Onnowpurbo: /* Cek Bed Blocks */

2015-05-17T07:15:31Z

Cek Bed Blocks

← Older revision		Revision as of 07:15, 17 May 2015
Line 41:		Line 41:

	mkfs -L data -c /dev/sdb1		mkfs -L data -c /dev/sdb1


			==Menggunakan badblocks==

			Before Filesystem Creation

			Alternately, this can be done before filesystem creation.

			If badblocks is run without the -o option bad sectors will only be printed to stdout.

			Example output for read errors in the beginning of the disk:

			# badblocks -wsv /dev/<drive>

			[...]
			Testing with pattern 0xff: done
			Reading and comparing:
			[...]
			37584
			37585 0.84% done, 7:31:08 elapsed. (0/0/527405 errors)
			37586
			[...]
			done
			Testing with pattern 0x00:
			Reading and comparing:
			[...]
			37584
			37585
			[...]
			done
			Pass completed, 527405 bad blocks found. (0/0/527405 errors)

			For comfortably passing badblocks error output to the filesystem it has to be written to a file.

			# badblocks -wsv -o /root/<badblocks.txt> /dev/<device>

			Checking for bad blocks in read-write mode
			From block 0 to 488386583
			Testing with pattern 0xaa: done
			Reading and comparing: 6.36% done, 0:51 elapsed. (0/0/14713 errors)
			[...]
			Testing with pattern 0x00: done
			Reading and comparing: done
			Pass completed, 527405 bad blocks found. (0/0/527405 errors)

			Then (re-)create the file system with the information:

			# mkfs.<filesystem-type> -l /root/<badblocks.txt> /dev/<device>

			Note: The meaning of 0/0/527405 errors is <number of read errors>/<number of write errors>/<number of corruption errors>.

Onnowpurbo at 03:11, 17 May 2015

2015-05-17T03:11:32Z

← Older revision		Revision as of 03:11, 17 May 2015
Line 34:		Line 34:

	mkfs.ext3 -J size=10000 -L repo /dev/sdb1		mkfs.ext3 -J size=10000 -L repo /dev/sdb1


			==Cek Bed Blocks==

			Memformat sambil cek bed blocks

			mkfs -L data -c /dev/sdb1

Onnowpurbo at 06:37, 14 July 2013

2013-07-14T06:37:37Z

← Older revision		Revision as of 06:37, 14 July 2013
Line 31:		Line 31:
	[-t fs-type] [-T usage-type ] [-U UUID] [-jnqvDFKSV] device [blocks-count]		[-t fs-type] [-T usage-type ] [-U UUID] [-jnqvDFKSV] device [blocks-count]

	Yang sederhana		Yang sederhana, misalnya.

	mkfs.ext3 -L ~~usbdata~~ /dev/sdb1		mkfs.ext3 -J size=10000 -L repo /dev/sdb1

Onnowpurbo: New page: Format USB flashdisk / USB harddisk / harddisk dapat menggunakan mkfs Catatan penggunaan: Usage: mkfs [options] [-t type fs-options] device [size] Options: -t, --type=TYPE fil...

2013-07-14T06:04:21Z

New page: Format USB flashdisk / USB harddisk / harddisk dapat menggunakan mkfs Catatan penggunaan: Usage: mkfs [options] [-t type fs-options] device [size] Options: -t, --type=TYPE fil...

New page

Format USB flashdisk / USB harddisk / harddisk dapat menggunakan

mkfs

Catatan penggunaan:

Usage: mkfs [options] [-t type fs-options] device [size]

Options:
-t, --type=TYPE file system type, when undefined ext2 is used
fs-options parameters to real file system builder
device path to a device
size number of blocks on the device
-V, --verbose explain what is done
defining -V more than once will cause a dry-run
-V, --version output version information and exit
-V as version must be only option
-h, --help display this help and exit

For more information see mkfs(8).

atau

Usage: mkfs.ext3 [-c|-l filename] [-b block-size] [-C cluster-size]
[-i bytes-per-inode] [-I inode-size] [-J journal-options]
[-G flex-group-size] [-N number-of-inodes]
[-m reserved-blocks-percentage] [-o creator-os]
[-g blocks-per-group] [-L volume-label] [-M last-mounted-directory]
[-O feature[,...]] [-r fs-revision] [-E extended-option[,...]]
[-t fs-type] [-T usage-type ] [-U UUID] [-jnqvDFKSV] device [blocks-count]

Yang sederhana

mkfs.ext3 -L usbdata /dev/sdb1