CentoOS 6.10- Problem with partition format

AvivKR · 11-13-2019, 07:53 AM

Hello All!!

I have Centos6.10 server that are virtual machine. (vMware Workstation Pro 15)
I added virtual hard disk with 30GB capticity.
I ran :

Code:

fdisk /dev/sdb

And this what I've done:

Code:

fdisk /dev/sdb

WARNING: DOS-compatible mode is deprecated. It's strongly recommended to
         switch off the mode (command 'c') and change display units to
         sectors (command 'u').

Command (m for help): n
Command action
   e   extended
   p   primary partition (1-4)
p
Partition number (1-4): 1
First cylinder (1-3263, default 1): 1
Last cylinder, +cylinders or +size{K,M,G} (1-3263, default 3263): +15G

Command (m for help): w
The partition table has been altered!

Calling ioctl() to re-read partition table.
Syncing disks.

Now, I want to format the the partition to ext4 with

Code:

fsck.ext4 /dev/sdb

and this is the output:

Code:

e2fsck 1.41.12 (17-May-2010)
fsck.ext4: Superblock invalid, trying backup blocks...
fsck.ext4: Bad magic number in super-block while trying to open /dev/sdb1

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 <device>

Tried to run

Code:

e2fsck -b 8193 /dev/sdb

And this is the output:

Code:

e2fsck 1.41.12 (17-May-2010)
e2fsck: Bad magic number in super-block while trying to open /dev/sdb

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 <device>

How do I can fix this issue?
Thanks for helpers!!!!

michaelk · 11-13-2019, 08:01 AM

Your using the wrong command. mkfs.ext4 creates a filesystem.

AvivKR · 11-13-2019, 08:21 AM

Quote:

Originally Posted by michaelk

Your using the wrong command. mkfs.ext4 creates a filesystem.

OMG!!!!! what a stupid am I?!?!?
I broked my head for 3 hours because of this!!!
can't belive!!!!! Thanks my friend!!!
help me a lot!

rknichols · 11-13-2019, 09:14 AM

And, since you partitioned that disk, you want to be making the filesystem on /dev/sdb1, not /dev/sdb. Yes, you can build a filesystem directly on the unpartitioned disk, but that can cause the disk to appear empty to tools that expect to find partitions.