9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Sauparna <sauparna.palc@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Unable to boot from CD
Date: Mon, 26 Mar 2012 14:57:50 +0530	[thread overview]
Message-ID: <CAPGsGrGLyFkwa-zmJGUK_Chc1dJcR-oE97URQ_Am0MkGfq7fLQ@mail.gmail.com> (raw)
In-Reply-To: <b9872d1799b07ecd27cac35b26089214@kw.quanstro.net>

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

Here's 'fdisk -l'. (sdb is a usb disk I connected later.) The warnings
seems to corroborate cinap's comment, is it so?

The dump: http://dl.dropbox.com/u/10125317/sda.16.dump
(dd if=/dev/sda of=sda.16.dump bs=4096 count=16)

That should be the 1st. 16 sectors I hope. I checked (dumpe2fs) the bs of
sda3 (this partition is intact) to use the above bs. Also, to boot into my
Windows, I had fixed the mbr using the Windows 'fixmbr' command. So you
will find an intact mbr, and therefore not a very useful thing, the dump
will turn out to be.

This exercise is turning out to be interesting. May I ask how you would
have worked on the dump, and what could be learnt from looking into it?

And what did you mean by : cat /dev/sd*/ctl, it didn't work for me? I used
sda and sda5.

---------------------------------------------------------------------------------------------------
Warning: Partition 5 does not end on cylinder boundary.
Warning: Partition 6 does not end on cylinder boundary.
Warning: Unable to open /dev/sr0 read-write (Read-only file system).
/dev/sr0 has been opened read-only.
Error: /dev/sr0: unrecognised disk label

Disk /dev/sda: 320 GB, 320070320640 bytes
255 heads, 63 sectors/track, 38913 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *           1        6374    51199123    7  HPFS/NTFS
/dev/sda2            6375       31298   200193997    f  Extended LBA
/dev/sda5            6375       30689   195302205   83  Linux
/dev/sda6           30690       31297     4875727   82  Linux swap
/dev/sda3           31299       37359    48676950   83  Linux
/dev/sda4           37360       37759     3204967   39  Plan 9

Disk /dev/sdb: 1000 GB, 1000202273280 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1   *           1          97      779121    b  FAT32
/dev/sdb2              98        1403    10482412   83  Linux
/dev/sdb3            1404      121601   965482402   83  Linux
---------------------------------------------------------------------------------------------------

[-- Attachment #2: Type: text/html, Size: 2705 bytes --]

  parent reply	other threads:[~2012-03-26  9:27 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
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 [this message]
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=CAPGsGrGLyFkwa-zmJGUK_Chc1dJcR-oE97URQ_Am0MkGfq7fLQ@mail.gmail.com \
    --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).