Please, how to mount linux partition ? (ext2 does not work…)
Andy
Hi,
Please, how to mount linux partition ? (ext2 does not work…)
This works good:
mount -t ext2 /dev/hd0t131 /fs/linux
Sergiy Uvarov <colonel@rts-ukraine.com> wrote:
Hi,
Please, how to mount linux partition ? (ext2 does not work…)
This works good:
mount -t ext2 /dev/hd0t131 /fs/linux
I get error message like “… probably corrupted file system”,
but Linux fs is not corrupted surely.
Andy
andy@microstep-mis.com wrote:
Sergiy Uvarov <> colonel@rts-ukraine.com> > wrote:
Hi,Please, how to mount linux partition ? (ext2 does not work…)
This works good:
mount -t ext2 /dev/hd0t131 /fs/linuxI get error message like “… probably corrupted file system”,
but Linux fs is not corrupted surely.
Are you using ext2 or is it ext3? Are you using any of ext2’s extended
features that are not normally used under Linux?
chris
–
Chris McKillop <cdm@qnx.com> “The faster I go, the behinder I get.”
Software Engineer, QSSL – Lewis Carroll –
http://qnx.wox.org/
Chris McKillop <cdm@qnx.com> wrote:
andy@microstep-mis.com > wrote:
Sergiy Uvarov <> colonel@rts-ukraine.com> > wrote:
Hi,Please, how to mount linux partition ? (ext2 does not work…)
This works good:
mount -t ext2 /dev/hd0t131 /fs/linuxI get error message like “… probably corrupted file system”,
but Linux fs is not corrupted surely.
Are you using ext2 or is it ext3? Are you using any of ext2’s extended
features that are not normally used under Linux?
I am not familiar with Linux, so I installed it without any special
option, simply as is. I used Red Hat 7.2. From protocols it seems really
that my filesystem is ext3… Isn’t ext3 supported under QNX6.2 ?
Andy
chris
–
Chris McKillop <> cdm@qnx.com> > “The faster I go, the behinder I get.”
Software Engineer, QSSL – Lewis Carroll –
http://qnx.wox.org/
<andy@microstep-mis.com> wrote in message
news:af6j1e$2db$1@charon.microstep-mis.sk…
Chris McKillop <> cdm@qnx.com> > wrote:
andy@microstep-mis.com > wrote:
Are you using ext2 or is it ext3? Are you using any of ext2’s extended
features that are not normally used under Linux?I am not familiar with Linux, so I installed it without any special
option, simply as is. I used Red Hat 7.2. From protocols it seems really
that my filesystem is ext3… Isn’t ext3 supported under QNX6.2 ?
Isn’t ext3 supposed to be fully backwards compatible, i.e. appearing as an
ext2 partition? (after it has been left in an uncorrupted state, of
course).
Regards,
Leon
well, ext3 would be compatible. It differs in journaling and similiar sevices
- not formats, AFAIK…
Leon Woestenberg <leon.woestenberg@gmx.net> wrote:
andy@microstep-mis.com> > wrote in message
news:af6j1e$2db$> 1@charon.microstep-mis.sk> …
Chris McKillop <> cdm@qnx.com> > wrote:
andy@microstep-mis.com > wrote:
Are you using ext2 or is it ext3? Are you using any of ext2’s extended
features that are not normally used under Linux?I am not familiar with Linux, so I installed it without any special
option, simply as is. I used Red Hat 7.2. From protocols it seems really
that my filesystem is ext3… Isn’t ext3 supported under QNX6.2 ?
Isn’t ext3 supposed to be fully backwards compatible, i.e. appearing as an
ext2 partition? (after it has been left in an uncorrupted state, of
course).Regards,
Leon
In article <aeue2u$tj$2@charon.microstep-mis.sk>, andy@microstep-mis.com wrote:
Sergiy Uvarov <> colonel@rts-ukraine.com> > wrote:
Hi,Please, how to mount linux partition ? (ext2 does not work…)
This works good:
mount -t ext2 /dev/hd0t131 /fs/linuxI get error message like “… probably corrupted file system”,
but Linux fs is not corrupted surely.Andy
Depending on which partition it is, what else might be mounted where,
you may need to add the designator for it, such as…
mount -t ext2 /dev/hd0t131.1 /fs/linux
I also found that the linux partition ( or any partition ) you wish
to mount MUST be a primary partition.
I have not been able to get NTO to mount ANY extended partition
containing ANY file system.
–
Cowboy
“All we have to fear is fear itself!”
“And almost but not quite free software…”
“That too.”
“And binary only kernel drivers.”
“Okay, yeah, that too.”
“And…”
“—shush.”
Cowboy <curt@gwis.com> wrote:
Depending on which partition it is, what else might be mounted where,
you may need to add the designator for it, such as…
mount -t ext2 /dev/hd0t131.1 /fs/linux
I also found that the linux partition ( or any partition ) you wish
to mount MUST be a primary partition.
I have not been able to get NTO to mount ANY extended partition
containing ANY file system.
This seems contradictory, as the first statement does seem to imply that
extended partitions are recognised/enumerated and are mountable. Unless
by the last statements you mean that “diskboot does not automatically
mount extended partitions for you”. This was true, but I extended it in
August 2001 to automatically do this, so this functionality should be
present in, if not 6.1.1, then certainly 6.2 …
I believe that Red Had 7.2 creates an ext3 partition on a new
installation.
I can’t read my ext3 partition after upgrading from 7.1 to 7.2 with
journaling either.
—Thom
andy@microstep-mis.com wrote:
Chris McKillop <> cdm@qnx.com> > wrote:
andy@microstep-mis.com > wrote:
Sergiy Uvarov <> colonel@rts-ukraine.com> > wrote:
Hi,
Please, how to mount linux partition ? (ext2 does not work…)
This works good:
mount -t ext2 /dev/hd0t131 /fs/linux
I get error message like “… probably corrupted file system”,
but Linux fs is not corrupted surely.
Are you using ext2 or is it ext3? Are you using any of ext2’s extended
features that are not normally used under Linux?
I am not familiar with Linux, so I installed it without any special
option, simply as is. I used Red Hat 7.2. From protocols it seems really
that my filesystem is ext3… Isn’t ext3 supported under QNX6.2 ?Andy
chris
\Chris McKillop <> cdm@qnx.com> > “The faster I go, the behinder I get.”
Software Engineer, QSSL – Lewis Carroll –
http://qnx.wox.org/
\
In article <agsqpt$en$1@nntp.qnx.com>, John Garvey wrote:
Cowboy <> curt@gwis.com> > wrote:
Depending on which partition it is, what else might be mounted where,
you may need to add the designator for it, such as…
mount -t ext2 /dev/hd0t131.1 /fs/linux
I also found that the linux partition ( or any partition ) you wish
to mount MUST be a primary partition.
I have not been able to get NTO to mount ANY extended partition
containing ANY file system.This seems contradictory, as the first statement does seem to imply that
extended partitions are recognised/enumerated and are mountable.
If by that you infer that /dev/hd0t131.1 refers to an extended partition,
it does not. It is the second primary partition on the drive.
A simple
mount -t/dev/shmem/fs-ext2.so /dev/hd0t131 /fs/linux2
for instance, does mount the fourth primary partition, created last.
Why this happens, I know not.
I have noticed that QNX does recognise the designator such that a
primary partition containing extended partitions exists, but have
been unable to get it to identify or mount any extended partion
within that primary.
Not being intended as a general purpose desktop OS, none of this
has concerned me much, nor struck me as significant enough to report.
Unless
by the last statements you mean that “diskboot does not automatically
mount extended partitions for you”. This was true, but I extended it in
August 2001 to automatically do this, so this functionality should be
present in, if not 6.1.1, then certainly 6.2 …
That’s not what I meant, no.
I’ve found that the version I’m playing with ( identifies itself as
6.1.0A Release 2 ) is incapable of mounting a filesystem in an
extended partition by any means, regardless of what file system
it is, with the exception of an MSDOS file system. It MAY have worked
with that, but I don’t remember.
As a result, I’ld been forced to re-make the machine with ONLY
primary partitions so that they are all visible.
Since it was my habit to use a partition for swap, this has
forced me to learn ( never a bad thing ) to re-configure some
systems to use a swapfile instead of a swap partition.
This wastes some disk space, but not enough for me to be
concerned with.
I’ve been quite busy the last two months, and haven’t been able to
keep up with the latest and greatest. It’s entirely possible that
I’ve missed something along the way. 
–
Cowboy
“Its failings notwithstanding, there is much to be said in favor
of journalism in that by giving us the opinion of the uneducated,
it keeps us in touch with the ignorance of the community.”
- Oscar Wilde
Cowboy <curt@gwis.com> wrote:
If by that you infer that /dev/hd0t131.1 refers to an extended partition,
it does not. It is the second primary partition on the drive.
For that to be the case then you must have more than one t131 partition
within the primary partition table (QNX fdisk won’t let you do this, so
the drive must have been partitioned elsewhere). In that case, since they
both can’t be called hd0t131 I append a suffix to one of them. Similarly,
if your first Linux parition was buried 3 or 4 layers of t133/extended
deep, then it would just be named hd0t131. The suffix is used only where
necessary to give uniqueness (so the “.n” doesn’t mean “n-th extended”
but rather “n-th instance of a tXXX”).
mount -t/dev/shmem/fs-ext2.so /dev/hd0t131 /fs/linux2
for instance, does mount the fourth primary partition, created last.
Why this happens, I know not.
Partitions actually number backwards in the partition table; a historic
DOS-ism. Some versions of fdisk didn’t know this, but new ones should.
That’s not what I meant, no.
I’ve found that the version I’m playing with ( identifies itself as
6.1.0A Release 2 ) is incapable of mounting a filesystem in an
extended partition by any means, regardless of what file system
Hmm, this makes no sense. If a partition is enumerated/discovered
anywhere (primary or extended) and given a name, then that name is
irrelevant to the subsequent mounting of any filesystem within in.
Can you give an “ls -ls /dev” and a “mount” line which fails … ?
As a result, I’ld been forced to re-make the machine with ONLY
primary partitions so that they are all visible.
As I said, early versions of “diskboot” didn’t do this (automatic
handling of multiple tXXX partitions) properly, but as far as I know
the filesystem itself (io-blk.so) has always done the right thing and
should enumerate/name all partitions correctly leaving them available
for a manual mount.
I’ve been quite busy the last two months, and haven’t been able to
keep up with the latest and greatest. It’s entirely possible that
The latest-and-greatest filesystem stuff doesn’t seem to ship, but as
far as partition enumeration goes, I think it has always worked. I am
of course willing to be proven wrong, and if you can give an example
partitioning (I’m not talking about diskboot here) I will reproduce on
a disk drive here and fix it …
In article <ah0v8c$4lm$1@nntp.qnx.com>, John Garvey wrote:
Cowboy <> curt@gwis.com> > wrote:
If by that you infer that /dev/hd0t131.1 refers to an extended partition,
it does not. It is the second primary partition on the drive.For that to be the case then you must have more than one t131 partition
within the primary partition table (QNX fdisk won’t let you do this, so
//snip//
I’ve been quite busy the last two months, and haven’t been able to
keep up with the latest and greatest. It’s entirely possible thatThe latest-and-greatest filesystem stuff doesn’t seem to ship, but as
far as partition enumeration goes, I think it has always worked. I am
of course willing to be proven wrong, and if you can give an example
partitioning (I’m not talking about diskboot here) I will reproduce on
a disk drive here and fix it …
I shall do so…
Please stand by while the technician experiences difficulty…
\
Cowboy
Maj. Bloodnok: Seagoon, you’re a coward!
Seagoon: Only in the holiday season.
Maj. Bloodnok: Ah, another Noel Coward!
In article <slrnajbj76.179.curt@ctx.dummy>, Cowboy wrote:
In article <ah0v8c$4lm$> 1@nntp.qnx.com> >, John Garvey wrote:
Cowboy <> curt@gwis.com> > wrote:
If by that you infer that /dev/hd0t131.1 refers to an extended partition,
it does not. It is the second primary partition on the drive.For that to be the case then you must have more than one t131 partition
within the primary partition table (QNX fdisk won’t let you do this, so//snip//
I’ve been quite busy the last two months, and haven’t been able to
keep up with the latest and greatest. It’s entirely possible thatThe latest-and-greatest filesystem stuff doesn’t seem to ship, but as
far as partition enumeration goes, I think it has always worked. I am
of course willing to be proven wrong, and if you can give an example
partitioning (I’m not talking about diskboot here) I will reproduce on
a disk drive here and fix it …
I shall do so…
Please stand by while the technician experiences difficulty…
Well, I bought the bullet, trashed 9 gigs worth of stuff that was
in the most likely canditate for space to try this in.
It was all experimental, and backups, so nothing really lost
but time. Since your comments, I figgured this WAS important enough.
Conclusion:
I stand corrected ( and educated a bit ) !
I wiped a primary, then created three extended partitions.
A second Win95LBA
a second QNX ( t78 )
and a second ext2.
While QNX fdisk won’t show anything in the extended area,
mounting the partitions DOES work, if the nomenclature
and syntax is correct.
Not realizing that the partition designations may be reversed,
and not knowing the limitations of QNX fdisk, led me to some
faulty conslusions, and several failed attempts.
Methinks it’s inadequate documentation, and misunderstanding.
As a result of this discussion, I have made some progress !
We’ll get there, eventually.
Thanks for the incentive to dive into it.
–
Cowboy
hangover, n.:
The wrath of grapes.
Cowboy <curt@gwis.com> wrote:
The latest-and-greatest filesystem stuff doesn’t seem to ship, but as
far as partition enumeration goes, I think it has always worked. I am
I shall do so…
Conclusion:
I stand corrected ( and educated a bit ) !
Thanks very much for trying this out! Glad to hear that (at least behind
the scenes) things all work.
While QNX fdisk won’t show anything in the extended area, mounting the
partitions DOES work, if the nomenclature and syntax is correct.
Yes, sadly the shipped fdisk is of no use in manipulating extended
partitions. I recall there was an internal version of fdisk that did
allow this; I will make inquiries as to its state and if we can ship it …
In article <ahcrbu$5if$1@nntp.qnx.com>, John Garvey wrote:
Cowboy <> curt@gwis.com> > wrote:
The latest-and-greatest filesystem stuff doesn’t seem to ship, but as
far as partition enumeration goes, I think it has always worked. I am
I shall do so…
Conclusion:
I stand corrected ( and educated a bit ) !Thanks very much for trying this out! Glad to hear that (at least behind
the scenes) things all work.
Yup. The only thing weird, was the t131.1 when it wasn’t ( as best
I can recall ) the second type ext2 partition. It had been at one time,
though.
While QNX fdisk won’t show anything in the extended area, mounting the
partitions DOES work, if the nomenclature and syntax is correct.Yes, sadly the shipped fdisk is of no use in manipulating extended
partitions. I recall there was an internal version of fdisk that did
allow this; I will make inquiries as to its state and if we can ship it …
I would recomend it !
While an embedded system is unlikely to have multiple file systems,
and multiple partitions, it’s not unlikely that a development
platform would !
In my case, my “work station” boots many different systems, and multiple
versions of those systems, to enable testing of various scenarios on
known hardware, and allows comparisons without hardware variables.
Of course, that also means that I don’t need QNX fdisk to be able
to manipulate partition tables…
\
Cowboy
QOTD:
“It’s been Monday all week today.”