public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andreas Dilger <adilger@turbolabs.com>
To: arvest@orphansonfire.com
Cc: Alexander Viro <viro@math.psu.edu>, linux-kernel@vger.kernel.org
Subject: Re: 2.4.11 loses sda9
Date: Thu, 11 Oct 2001 00:08:14 -0600	[thread overview]
Message-ID: <20011011000814.B23927@turbolinux.com> (raw)
In-Reply-To: <Pine.GSO.4.21.0110110121270.21168-100000@weyl.math.psu.edu> <01101100452300.00621@lithium>
In-Reply-To: <01101100452300.00621@lithium>

On Oct 11, 2001  00:45 -0500, arvest@orphansonfire.com wrote:
> > On Thu, 11 Oct 2001 arvest@orphansonfire.com wrote:
> > >   I can get the system booted enough to work on (and totaly up) with this
> > > partition failing.  I dont know what more information from fdisk I can
> > > give you, sda9 is there with .10, and gone with .11  It even allowed me
> > > to add a new partition (i didnt save)  I tried sfdisk but it gave me
> > > these errors.
>
> Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
> SCSI device sda: 17783250 512-byte hdwr sectors (9105 MB)
>  sda: sda1 sda2 sda3 sda4 < sda5 sda6 sda7 sda8 >
> omitting empty partition (9)
>  
> /dev/sda1   *         1       501    513008   83  Linux
> /dev/sda2           502      3698   3273728   83  Linux
> /dev/sda3          3699      4199    513024   83  Linux
> /dev/sda4          4200      8683   4591616    5  Extended
> /dev/sda5          4200      4700    513008   83  Linux
> /dev/sda6          4701      5725   1049584   83  Linux
> /dev/sda7          5726      5918    197616   82  Linux swap
> /dev/sda8          5919      6419    513008   83  Linux

You probably need to go into fdisk and change the partition type of
sda9 from "0" to "83" (or any other non-zero type).  There is a
reason that it is saying "omitting empty partition (9)" at boot,
and "fdisk -l" doesn't list it - because type "0" means "I don't exist".

In fdisk, use the "t" option to set the type of sda9.

Cheers, Andreas
--
Andreas Dilger  \ "If a man ate a pound of pasta and a pound of antipasto,
                 \  would they cancel out, leaving him still hungry?"
http://www-mddsp.enel.ucalgary.ca/People/adilger/               -- Dogbert


  reply	other threads:[~2001-10-11  6:08 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-11  5:07 2.4.11 loses sda9 Alexander Viro
2001-10-11  5:20 ` arvest
2001-10-11  5:23   ` Alexander Viro
2001-10-11  5:45     ` arvest
2001-10-11  6:08       ` Andreas Dilger [this message]
2001-10-11  6:17         ` Alexander Viro
2001-10-11 16:41         ` arvest
2001-10-11 16:46           ` Ignacio Vazquez-Abrams
2001-10-11 16:50             ` Alexander Viro
2001-10-11 17:23               ` Alexander Viro
2001-10-11 18:22 ` Guest section DW
2001-10-11 18:25   ` Alexander Viro
  -- strict thread matches above, loose matches on Subject: below --
2001-10-12  0:07 Andries.Brouwer
2001-10-11 22:11 Andries.Brouwer
2001-10-11 22:26 ` Alexander Viro
2001-10-11 20:29 Andries.Brouwer
2001-10-11 20:54 ` Alexander Viro
2001-10-11 19:07 Andries.Brouwer
2001-10-11 19:19 ` Alexander Viro
2001-10-11  4:22 arvest

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=20011011000814.B23927@turbolinux.com \
    --to=adilger@turbolabs.com \
    --cc=arvest@orphansonfire.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viro@math.psu.edu \
    /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