9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Sauparna <sauparna.palc@gmail.com>
To: 9fans@9fans.net
Subject: Re: [9fans] Unable to boot from CD
Date: Fri, 23 Mar 2012 09:58:33 +0000	[thread overview]
Message-ID: <20158797.18.1332445256322.JavaMail.geo-discussion-forums@pbgn5> (raw)
In-Reply-To: <16922209.2557.1332231554137.JavaMail.geo-discussion-forums@pbcju1>

I tried several things, and help, again, will be appreciated. With the little knowledge I have I will try to explain the procedures.

@Thierry: I have a MBR, and not GPT. I have Windows and Linux (Ubuntu) and dual-boot through GRUB; as is the standard setup found when Ubuntu is installed second and GRUB writes the MBR. Secondly, I didn't know what to specify at the 'boot from:' prompt, and I haven't tried it yet. Yes, I can key in text at the prompt.

@cinap: 9front boots, and dies. I don't get installation / boot options at all. No prompt either.

@erik: 9atom worked. Booting from CD (option 2) didn't, but installation (option 1) proceeded fine till I got stuck at [mountdist], couldn't locate the distribution and it wouldn't proceed till I specify a correct source, so I quit at that point, rebooted and ended up losing my grub. I was careful enough to specify the right partition for installation, however I didn't choose the suggested layout but modified it (specifying start and end blocks) to occupy only 3GB of the raw free space I had. Booting from a live Ubuntu CD I can now list existing partitions using fdisk -l, but I am unable to mount my Ubuntu boot partition. 'mount' doesn't recognise the file system. The NTFS and another ext2 partition that I had can be mounted properly.

Here're my partitions. I have lost /dev/sda5 which was my boot partition. (Backed up, so no worries).

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *           1        6374    51199123+   7  HPFS/NTFS
/dev/sda2            6375       31298   200202030    f  W95 Ext'd (LBA)
/dev/sda3           31299       37359    48684982+  83  Linux
/dev/sda4           37360       37759     3213000   39  Plan 9
/dev/sda5            6375       30689   195310206   83  Linux
/dev/sda6           30690       31297     4883728+  82  Linux swap / Solaris

So,

1. Why should my MBR get overwritten when I aborted the Plan 9 installation at [mountdist]? And why did my boot partition get spoilt?
2. What should I do to get the [mountdist] step to completion?



  parent reply	other threads:[~2012-03-23  9:58 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-20  9:54 Sauparna
2012-03-20 10:15 ` tlaronde
2012-03-20 10:21   ` erik quanstrom
2012-03-20 10:20 ` cinap_lenrek
2012-03-23  9:58 ` Sauparna [this message]
2012-03-23  9:58 ` Sauparna
2012-03-23 12:10   ` cinap_lenrek
2012-03-23  9:59 ` Sauparna
     [not found] ` <1c246e87-181f-456f-b12d-5f5553fa0931@px4g2000pbc.googlegroups.co>
2012-03-23 10:12   ` erik quanstrom
2012-03-23 16:07     ` Sauparna
2012-03-26  9:27     ` Sauparna
2012-03-30 15:13       ` Sauparna

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=20158797.18.1332445256322.JavaMail.geo-discussion-forums@pbgn5 \
    --to=sauparna.palc@gmail.com \
    --cc=9fans@9fans.net \
    /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).