linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Ethan Benson <erbenson@alaska.net>
To: linuxppc-dev@lists.linuxppc.org
Subject: Re: More problems with Kernel 2.4.10-pre12 and mounting
Date: Sun, 23 Sep 2001 19:17:13 -0800	[thread overview]
Message-ID: <20010923191713.E14835@plato.local.lan> (raw)
In-Reply-To: <Pine.LNX.4.21.0109232307500.13300-100000@cr242184-a.etob1.on.wave.home.com>; from tendim@tendim.cjb.net on Sun, Sep 23, 2001 at 11:09:24PM -0400

[-- Attachment #1: Type: text/plain, Size: 1436 bytes --]

On Sun, Sep 23, 2001 at 11:09:24PM -0400, patrick wrote:
> On Sun, 23 Sep 2001, Ethan Benson wrote:
> 
> > is it possible you have an x86 BIOS partition table on that disk as
> > well?  if mac-fdisk -l doesn't work then your mac partition table is
> > corrupt.  but if that does work but the kernel is getting other ideas
> > about your partitions you probably have both an x86 and mac partition
> > table (its actually possible for them to coexist, but its a gross and
> > uneeded hack).  what does /proc/partitions say?
> 
> But if the Mac partition table were corrupt, wouldn't it also be
> skewed under my 2.2.18 Kernel as well?  

yes most likely.

>    8    16    4194157 sdb
>    8    17         31 sdb1
>    8    18         64 sdb2
>    8    19    2000000 sdb3
>    8    20    2194040 sdb4
>    8    21         21 sdb5

the kernel is detecting your partition table just fine it seems.  the
8 is the major number of the device, 16, 17... are the minor numbers,
they correlate with the major/minors of the /dev/ nodes.  the third is
the number of 1k blocks that device has, sdb1 is clearly the mac
partition table as they are almost always 31.5k

the dd trick shows you can read the device without problems, are you
sure the filesystem is not corrupt? or that the disk is not failing?

try:

badblocks -sv /dev/sdb 

and see what happens.

-- 
Ethan Benson
http://www.alaska.net/~erbenson/

[-- Attachment #2: Type: application/pgp-signature, Size: 0 bytes --]

  reply	other threads:[~2001-09-24  3:17 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-23  4:21 More problems with Kernel 2.4.10-pre12 and mounting patrick
2001-09-23  5:18 ` Timothy A. Seufert
2001-09-23  7:14   ` patrick
2001-09-23  7:44     ` Ethan Benson
2001-09-23 17:33       ` patrick
2001-09-23 23:46         ` Ethan Benson
2001-09-24  3:09           ` patrick
2001-09-24  3:17             ` Ethan Benson [this message]
2001-09-24  4:22               ` patrick
2001-09-24  6:18                 ` Ethan Benson
2001-09-24 21:39                   ` patrick
2001-09-24 23:04                     ` Ethan Benson
2001-09-25  0:04                       ` Timothy A. Seufert
2001-09-25  2:10                       ` More problems with Kernel 2.4.10-pre12 and mounting (SOLVED!) patrick

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=20010923191713.E14835@plato.local.lan \
    --to=erbenson@alaska.net \
    --cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).