Invalid argument passed to ext2 library while setting up superblock

I solved this problem. How do I delete this message form this forum?

Mark



Disk /dev/sdc: 120.0 GB, 120034123776 bytes
255 heads, 63 sectors/track, 14593 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sdc1 1 14593 117218241 5 Extended
[root@explorer /]# mkfs -t ext2 /dev/sdb1
mke2fs 1.35 (28-Feb-2004)
/dev/sdb1: Invalid argument passed to ext2 library while setting up superblock
[root@explorer /]#

It would be better if you just post your solution, then anyone else with a similar problem can find out what you did.

yeah, like me now!

Its so annoying when you see the same problem your having after googleing and then all you read is "I fixed it" :end:

Arrrggg!

and like me
I only found this:
http://www.sage.org/mailarchive/sage.../msg00532.html

but i didnt found an alternative

johnniefp: did you found a solution?

I didn't find a solution as such. What I did do is go back to square one and fdisk'ed the drive from the rescue command line.

I followed this and it worked.

http://www.idevelopment.info/data/Un...ive_ext3.shtml

What i found:
- Must reboot after resize

- Must define the partition type as ext2/ext3 .
This is
"83 Linux" or
"85 Linux extended" to cfdisk/fdisk?
I set type=85

- Maybe is something wrong with the BIOS & hdd. Maybe we have to recheck the jumpers and all this stuff. I think here is the problem

Anyone know if the problem can be caused when resizing an other partition on the same hdd where linux run?

msross: if you read this topic can you post the solution?

Finally, i solved the problem
I set the bus cable to "Cable Select" & the hdd got formated

Originally Posted by JJX Finally, i solved the problem I set the bus cable to "Cable Select" & the hdd got formated

I was also running into this error. For some reason when I changed the hard drive jumper from master to cable select I was able to fix it. After moving the jumper I reformatted and then the mkfs command worked.

Before I added it to my current system as a second disk it was set to cable select. My guess would be that if you formated the disk as cable select and changed the jumper to master and then formated it again that it might also work. I have not tried it but I think it would work.

Hi - I experienced this problem and found that the solution was in fdisk - rather than selecting extended as the type of partition, I chose primary partitions only. I was then able to mkfs.ext3 all partitions.

This is a very good clear, step-by-step introduction:

http://www.ehow.com/how_1000631_hard-drive-linux.html

And I've found that the best way to experiment is to work with VMware images. Like get an .iso of something really small and cute (like Tiny Core Linux), get an empty virtual disk, and play away without the anxiety of dealing with actual hardware.

steve d.

Hi

Have you created an extended partition? If so, you have to add to the extended partition a logical partition, which you add, after creating the extended partition, also with fdisk -> n (add partition).
Afterwards you can run mkfs.ext3 /dev/sda3. You get the error if you would like to format the extended partition, so sda3 is the logical.
To one extended partition you can add multiple logical partitions.

Greets
Joschi