public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Paul Hartman <paul.hartman+gentoo@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] lilo 'duplicate volume id' issue after attaching esata enclosure
Date: Mon, 23 Apr 2012 18:25:45 -0500	[thread overview]
Message-ID: <CAEH5T2Ni7HYgNeqHeis9F8C7Q9k1njCQKCjwO+LV6aYViqE0oA@mail.gmail.com> (raw)
In-Reply-To: <CALxYTP5JvQJnikwiSaH8=Xx8d-upVs1utng1XrnYT79X4g2u8g@mail.gmail.com>

On Mon, Apr 23, 2012 at 7:30 AM, Doug Hunley <doug.hunley@gmail.com> wrote:
> The subject line pretty much says it all. I've been happily using lilo
> to boot from my internal 4-disk sata array (md, raid 1) for a while
> now and I recently bought an external sata enclosure. I cabled it up
> to my machine, added 4 disks I had sitting around, and on boot, lilo
> throws a 'duplicate vol-id detected' error and halts...
> I did a bunch of googling, and it looks like if I could just get
> booted, running 'lilo' would actually fix the problem, but I can't get
> lilo booted past this error.

The LILO source code contains a diagnostics diskette that you can
build, maybe it can be of some assistance. It has been over a decade
since the last time I saw LILO so I'm unfortunately no help beyond
this bit of trivia.

> Ideas on how I can fix/remove the vol-id from the external disks?

Do you have another machine with SATA ports that you can hook them up
to temporarily and alter those troublesome bytes?



  parent reply	other threads:[~2012-04-23 23:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-23 12:30 [gentoo-user] lilo 'duplicate volume id' issue after attaching esata enclosure Doug Hunley
2012-04-23 12:47 ` Michael Mol
2012-04-23 17:30   ` Doug Hunley
2012-04-24 16:23     ` Michael Mol
2012-04-23 23:25 ` Paul Hartman [this message]
2012-04-24 16:11   ` Doug Hunley

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=CAEH5T2Ni7HYgNeqHeis9F8C7Q9k1njCQKCjwO+LV6aYViqE0oA@mail.gmail.com \
    --to=paul.hartman+gentoo@gmail.com \
    --cc=gentoo-user@lists.gentoo.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