From: Guest section DW <dwguest@win.tue.nl>
To: "Carlos Fernandez Sanz" <cfernandez@myalert.com>,
<linux-kernel@vger.kernel.org>, <linux-fsdevel@vger.kernel.org>
Subject: Re: Problem creating filesystem
Date: Tue, 27 Feb 2001 02:39:05 +0100 [thread overview]
Message-ID: <20010227023905.A17956@win.tue.nl> (raw)
In-Reply-To: <11dd01c0a04e$98b92e60$f40237d1@MIACFERNANDEZ>
In-Reply-To: <11dd01c0a04e$98b92e60$f40237d1@MIACFERNANDEZ>; from Carlos Fernandez Sanz on Mon, Feb 26, 2001 at 06:48:16PM -0500
On Mon, Feb 26, 2001 at 06:48:16PM -0500, Carlos Fernandez Sanz wrote:
> I have just purchased a new HD and I'm getting problems creating a
> filesystem for it. The HD is a Maxtor 80 Gb
>
> Disk /dev/hde: 16 heads, 63 sectors, 15871 cylinders
> Units = cylinders of 1008 * 512 bytes
>
> Device Boot Start End Blocks Id System
> /dev/hde1 1 15871 7998952+ 83 Linux
>
> Command (m for help): w
> The partition table has been altered!
>
> Calling ioctl() to re-read partition table.
>
> Syncing disks.
> ------------------
> When trying to create the filesystem, I get this:
>
> [root@alhambra /sbin]# ./mke2fs /dev/hde1
> mke2fs 1.18, 11-Nov-1999 for EXT2 FS 0.5b, 95/08/09
> /dev/hde1: Invalid argument passed to ext2 library while setting up
> superblock
> -------------------
>
> I'm using
> Linux version 2.2.17-14 (root@porky.devel.redhat.com)
Reboot. Look at the boot messages. You should see your disk mentioned
and the partitions listed (hde: hde1).
If they disappear too quickly, say "dmesg | grep hde".
Test the size of hde1 with "blockdev --getsize /dev/hde1"
or "fdisk -s /dev/hde1" or so. If you get 0 that explains
the mke2fs error.
Make sure your tools are up to date. Old versions often have
an overflow somewhere.
next prev parent reply other threads:[~2001-02-27 1:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-26 23:48 Carlos Fernandez Sanz
2001-02-27 1:39 ` Guest section DW [this message]
2001-02-27 3:53 ` Jeremy Jackson
2001-03-02 1:57 ` [Newbie] " Rogerio Brito
2001-03-02 4:16 ` Jeremy Jackson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20010227023905.A17956@win.tue.nl \
--to=dwguest@win.tue.nl \
--cc=cfernandez@myalert.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®