hdb3 = Linux ext3 partition created and formatted with qtparted

On Sun, 24 Apr 2005 15:13:14 -0500, CWO4 Dave Mann wrote:

hdb3 = Linux ext3 partition created and formatted with qtparted

Make sure the type of the partition says its a Linux one. As root,

# fdisk -l /dev/hdb

and check that the hdb3 partition has an "id" of "83". If not, use fdisk
to fix it.

HTH

Here is the output of fdisk:
[root@localhost dave]# fdisk -l /dev/hdb
Disk /dev/hdb: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/hdb1 * 1 13 104391 83 Linux
/dev/hdb2 14 4111 32917185 8e Linux LVM
/dev/hdb3 4112 19457 123266745 83 Linux

Here what I have so far in my latest fstab; the last few lines involve the
hdb3:

/dev/hda1 /mnt/windows ntfs rw,umask=0222 0 0
/dev/sda1 /mnt/firewire ntfs rw,umask=0222 0 0

/dev/hdb3 /mnt/storage ext3 rw,umask=0222 auto 0 0

On Sun, 24 Apr 2005 17:56:29 -0500, CWO4 Dave Mann wrote:

Here is the output of fdisk:
[root@localhost dave]# fdisk -l /dev/hdb
Disk /dev/hdb: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/hdb1 * 1 13 104391 83 Linux
/dev/hdb2 14 4111 32917185 8e Linux LVM
/dev/hdb3 4112 19457 123266745 83 Linux

Looks OK to me.

Here what I have so far in my latest fstab; the last few lines involve
the hdb3:

/dev/hda1 /mnt/windows ntfs rw,umask=0222 0
0
/dev/sda1 /mnt/firewire ntfs rw,umask=0222 0
0

I'd recommend that you mount NTFS partitions as "ro" because Linux
NTFS write support is broken: read this as "could corrupt the
_entire_ partition".

/dev/hdb3 /mnt/storage ext3 rw,umask=0222 auto 0
0

Nope. Too many tokens.

/dev/hdb3 /mnt/storage ext3 rw,umask=0222,auto 0 3

This should fix it.

Tommy Reynolds wrote:

On Sun, 24 Apr 2005 17:56:29 -0500, CWO4 Dave Mann wrote:

Here is the output of fdisk:
[root@localhost dave]# fdisk -l /dev/hdb
Disk /dev/hdb: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/hdb1 * 1 13 104391 83 Linux
/dev/hdb2 14 4111 32917185 8e Linux LVM
/dev/hdb3 4112 19457 123266745 83 Linux

Looks OK to me.

Here what I have so far in my latest fstab; the last few lines involve
the hdb3:

/dev/hda1 /mnt/windows ntfs rw,umask=0222
0 0
/dev/sda1 /mnt/firewire ntfs rw,umask=0222
0 0

I'd recommend that you mount NTFS partitions as "ro" because Linux
NTFS write support is broken: read this as "could corrupt the
_entire_ partition".



Yikes!

Changed to /dev/hda1 /mnt/windows ntfs ro,umask=0222 0 0
Changed to /dev/sda1 /mnt/firewire ntfs ro,umask=0222 0 0


/dev/hdb3 /mnt/storage ext3 rw,umask=0222 auto
0 0

Nope. Too many tokens.

/dev/hdb3 /mnt/storage ext3 rw,umask=0222,auto 0 3

This should fix it.


Hummm .... here's cut/paste from newest fstab:

#
/dev/hdb3 /mnt/storage ext3 rw,umask=0222,auto 0 3
#
# Sets up the big storage area on the Samsung Drive and makes it real

OK, now I get the "can't" mount - need to be root message". I know there
must be a way to place the owner into the fstab and to auto mount.

I used qtparted and made sure hdb3 is really ext3 and formatted. All OK
there.

Cold reboot (from my old Big Iron days, load in the stack of Cold Boot cards
in the Honeywell 6600 system reader and boot up .. only took a couple of
hours and 5,000 cards ...)

Boot messages showed same hdb3 message -- too many file system, not the
right stuff, etc.

Device Boot Start End Blocks Id System
/dev/hdb1 * 1 13 104391 83 Linux
/dev/hdb2 14 4111 32917185 8e Linux LVM (*
/dev/hdb3 4112 19457 123266745 83 Linux

On Mon, 25 Apr 2005 09:23:58 -0500, CWO4 Dave Mann wrote:

I used qtparted and made sure hdb3 is really ext3 and formatted. All OK
there.

Cold reboot (from my old Big Iron days, load in the stack of Cold Boot
cards in the Honeywell 6600 system reader and boot up .. only took a
couple of hours and 5,000 cards ...)

Yup. Don't you mean a CDC-6600? I remember when they hit the
street. I had a Honeywell <big-mother/> too, as well as a DDC-116
sixteen bit mini that I used to do missle telemetry: no screen, no
keyboard, just lights and switches. We don' need no steenkin' GUI!

Boot messages showed same hdb3 message -- too many file system, not the
right stuff, etc.

A few thoughts come to mind:

1) Can you mount it manually?

# mount /dev/hdb3

What is output and what shows up in "/var/log/messages"?

2) What is in the partition? Could you trash it and use fdisk( and
mkfs( to reformat it? I'm not sure I trust anything with a GUI
;-)

Hang in there, dude, we'll get there.

Tommy Reynolds wrote:

On Mon, 25 Apr 2005 09:23:58 -0500, CWO4 Dave Mann wrote:

I used qtparted and made sure hdb3 is really ext3 and formatted. All OK
there.

Cold reboot (from my old Big Iron days, load in the stack of Cold Boot
cards in the Honeywell 6600 system reader and boot up .. only took a
couple of hours and 5,000 cards ...)

Yup. Don't you mean a CDC-6600? I remember when they hit the
street. I had a Honeywell <big-mother/> too, as well as a DDC-116
sixteen bit mini that I used to do missle telemetry: no screen, no
keyboard, just lights and switches. We don' need no steenkin' GUI!


Now that you mention it, I do believe you be right. I worked on the US
Army's end of the World Wide Military Command and Control System (WWMCSS)
and the DIAOLS/COINS lash up. We had some awesome GUI terminals. You can
see them if you rent the movie The Day The Earth Stood Still and look for
the US Army's missile site scene. Oh yes, and 60 baud KSR machines with
punched tape. I really like that punched tape, if you dropped the roll it
wasn't like dropping a box of cards. Yikes!


Boot messages showed same hdb3 message -- too many file system, not the
right stuff, etc.

A few thoughts come to mind:



1) Can you mount it manually?

# mount /dev/hdb3

What is output and what shows up in "/var/log/messages"?

/var/log/messages output (clipped)

Apr 25 17:45:01 localhost crond(pam_unix)[6162]: session opened for user
root by (uid=0)
Apr 25 17:45:03 localhost crond(pam_unix)[6162]: session closed for user
root
Apr 25 17:45:27 localhost kernel: EXT3-fs: Unrecognized mount option
"umask=0222" or missing value
[root@localhost dave]#

mount/dev/hdb3 message

[dave@localhost ~]$ su
Password: klaatu varada nickto
[root@localhost dave]# mount /dev/hdb3
mount: wrong fs type, bad option, bad superblock on /dev/hdb3,
or too many mounted file systems
[root@localhost dave]#


Hummmmmaybe we need a different value .. what is the significance of the
umask=0222 statement?

If EXT3-fs is unrecognized mount option, I wonder if the system sees the
partition as a real Ext3. I notice that the hardware info returns
hdb1 as a type 8e partition and hdb3 as a type 83.

Nan-nu, Nan-nu?


Cheers,


Dave







2) What is in the partition? Could you trash it and use fdisk( and
mkfs( to reformat it? I'm not sure I trust anything with a GUI
;-)

Hang in there, dude, we'll get there.

In article <vOidnWbeOqs66fDfRVn-rw@giganews.com>, CWO4 Dave Mann wrote:
Tommy Reynolds wrote:

On Mon, 25 Apr 2005 09:23:58 -0500, CWO4 Dave Mann wrote:

I used qtparted and made sure hdb3 is really ext3 and formatted. All
OK there.

Cold reboot (from my old Big Iron days, load in the stack of Cold Boot
cards in the Honeywell 6600 system reader and boot up .. only took a
couple of hours and 5,000 cards ...)

Yup. Don't you mean a CDC-6600? I remember when they hit the
street. I had a Honeywell <big-mother/> too, as well as a DDC-116
sixteen bit mini that I used to do missle telemetry: no screen, no
keyboard, just lights and switches. We don' need no steenkin' GUI!


Now that you mention it, I do believe you be right. I worked on the US
Army's end of the World Wide Military Command and Control System (WWMCSS)
and the DIAOLS/COINS lash up. We had some awesome GUI terminals. You
can see them if you rent the movie The Day The Earth Stood Still and look
for
the US Army's missile site scene. Oh yes, and 60 baud KSR machines with
punched tape. I really like that punched tape, if you dropped the roll
it
wasn't like dropping a box of cards. Yikes!


Boot messages showed same hdb3 message -- too many file system, not the
right stuff, etc.

A few thoughts come to mind:



1) Can you mount it manually?

# mount /dev/hdb3

What is output and what shows up in "/var/log/messages"?

/var/log/messages output (clipped)

Apr 25 17:45:01 localhost crond(pam_unix)[6162]: session opened for user
root by (uid=0)
Apr 25 17:45:03 localhost crond(pam_unix)[6162]: session closed for user
root
Apr 25 17:45:27 localhost kernel: EXT3-fs: Unrecognized mount option
"umask=0222" or missing value
[root@localhost dave]#

mount/dev/hdb3 message

[dave@localhost ~]$ su
Password: klaatu varada nickto
[root@localhost dave]# mount /dev/hdb3
mount: wrong fs type, bad option, bad superblock on /dev/hdb3,
or too many mounted file systems
[root@localhost dave]#


Hummmmmaybe we need a different value .. what is the significance of the
umask=0222 statement?

If EXT3-fs is unrecognized mount option, I wonder if the system sees the
partition as a real Ext3. I notice that the hardware info returns
hdb1 as a type 8e partition and hdb3 as a type 83.

Nan-nu, Nan-nu?


Cheers,


Dave







2) What is in the partition? Could you trash it and use fdisk( and
mkfs( to reformat it? I'm not sure I trust anything with a GUI
;-)

Hang in there, dude, we'll get there.


Just a thought, but creating a partition does not a filesystem make A
partition is a slice of disk, but you need to create a filesystem in order
to mount it. You need to do:

# mke2fs -j /dev/hdb3

Then try your mount again.

Kevin

Apr 25 17:45:27 localhost kernel: EXT3-fs: Unrecognized mount option
"umask=0222" or missing value

[root@localhost dave]# mount /dev/hdb3
mount: wrong fs type, bad option, bad superblock on /dev/hdb3,
or too many mounted file systems

If EXT3-fs is unrecognized mount option, I wonder if the system sees the
partition as a real Ext3. I notice that the hardware info returns
hdb1 as a type 8e partition and hdb3 as a type 83.

[root@localhost dave]# mke2fs -j /dev/hdb3
mke2fs 1.36 (05-Feb-2005)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
15417344 inodes, 30816686 blocks
1540834 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=33554432
941 block groups
32768 blocks per group, 32768 fragments per group
16384 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632,
2654208,
4096000, 7962624, 11239424, 20480000, 23887872

Writing inode tables: done
Creating journal (8192 blocks): done
Writing superblocks and filesystem accounting information: done

This filesystem will be automatically checked every 33 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
[root@localhost dave]#

Now check this out:

[root@localhost dave]# mount /dev/hdb3
mount: wrong fs type, bad option, bad superblock on /dev/hdb3,
or too many mounted file systems

CRAP!

(Theme from Knightrider begins)

Any Ideas???

On Mon, 25 Apr 2005 20:29:55 -0500, CWO4 Dave Mann wrote:

Apr 25 17:45:27 localhost kernel: EXT3-fs: Unrecognized mount option
"umask=0222" or missing value

Bad karma here. Please remove this option for a moment.

[root@localhost dave]# mount /dev/hdb3
mount: wrong fs type, bad option, bad superblock on /dev/hdb3,
or too many mounted file systems

This is the generic "no can do" message that attempts to provide
useful error information by mentioning lots of irrelavent items. I
have not been successful in getting patches accepted for this.

If EXT3-fs is unrecognized mount option, I wonder if the system sees
the
partition as a real Ext3. I notice that the hardware info returns
hdb1 as a type 8e partition and hdb3 as a type 83.

Type "83" is correct for your "hdb3" partition, since it is _not_ an
LVM partition.

[root@localhost dave]# mke2fs -j /dev/hdb3
mke2fs 1.36 (05-Feb-2005)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
15417344 inodes, 30816686 blocks
1540834 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=33554432
941 block groups
32768 blocks per group, 32768 fragments per group
16384 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632,
2654208,
4096000, 7962624, 11239424, 20480000, 23887872

Writing inode tables: done
Creating journal (8192 blocks): done
Writing superblocks and filesystem accounting information: done

This filesystem will be automatically checked every 33 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
[root@localhost dave]#

Now check this out:

[root@localhost dave]# mount /dev/hdb3
mount: wrong fs type, bad option, bad superblock on /dev/hdb3,
or too many mounted file systems

Two hints:

# mount /dev/hdb3 /mnt/somewhere

does *NOT* use (or need) anything from "/etc/fstab", so always use
the two-argument form to make sure the setup is correct, before you
try the:

# mount /dev/hdb3

form -- that *requires* a correct "/etc/fstab" entry. See my earlier
comment about the bogus "umask=" option for the EXT3 partition.

CRAP!

Sir! Yes, Sir! Uggh! Sir, no results, sir!

(Theme from Knightrider begins)

Any Ideas???

Yeah, you gotta get out more

On Mon, 25 Apr 2005 20:29:55 -0500, CWO4 Dave Mann wrote:

Apr 25 17:45:27 localhost kernel: EXT3-fs: Unrecognized mount option
"umask=0222" or missing value

Bad karma here. Please remove this option for a moment.

[root@localhost dave]# mount /dev/hdb3
mount: wrong fs type, bad option, bad superblock on /dev/hdb3,
or too many mounted file systems

This is the generic "no can do" message that attempts to provide
useful error information by mentioning lots of irrelavent items. I
have not been successful in getting patches accepted for this.

If EXT3-fs is unrecognized mount option, I wonder if the system sees
the
partition as a real Ext3. I notice that the hardware info returns
hdb1 as a type 8e partition and hdb3 as a type 83.

Type "83" is correct for your "hdb3" partition, since it is _not_ an
LVM partition.

[root@localhost dave]# mke2fs -j /dev/hdb3
mke2fs 1.36 (05-Feb-2005)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
15417344 inodes, 30816686 blocks
1540834 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=33554432
941 block groups
32768 blocks per group, 32768 fragments per group
16384 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632,
2654208,
4096000, 7962624, 11239424, 20480000, 23887872

Writing inode tables: done
Creating journal (8192 blocks): done
Writing superblocks and filesystem accounting information: done

This filesystem will be automatically checked every 33 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
[root@localhost dave]#

Now check this out:

[root@localhost dave]# mount /dev/hdb3
mount: wrong fs type, bad option, bad superblock on /dev/hdb3,
or too many mounted file systems

Two hints:

# mount /dev/hdb3 /mnt/somewhere

does *NOT* use (or need) anything from "/etc/fstab", so always use
the two-argument form to make sure the setup is correct, before you
try the:

# mount /dev/hdb3

form -- that *requires* a correct "/etc/fstab" entry. See my earlier
comment about the bogus "umask=" option for the EXT3 partition.

CRAP!

Sir! Yes, Sir! Uggh! Sir, no results, sir!

(Theme from Knightrider begins)

Any Ideas???

Yeah, you gotta get out more

Tommy My Main Man ....

I removed the bad kharma (Dharma, actually) of umask blah and Lo and Behold!
Yesssss!! I Say Unto You My Brothers and Sisters! Yes! I Say It Is A
Miracle. I Just KNEW that if I sent that Ten Doller Love Offering To Your
Blessed Ministry of the Holy Linux That I Would Be Annointed.

Thou Shalt Be Annointed (as soon as I find my Special Homogenous Stone of
Special Powers -- which I think is with my Power Rangers Collectables).

I'll check back when I figure out WHY the umask was the constipation factor.