FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Gentoo > Gentoo User

 
 
LinkBack Thread Tools
 
Old 04-23-2012, 12:30 PM
Doug Hunley
 
Default lilo 'duplicate volume id' issue after attaching esata enclosure

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.

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

--
Douglas J Hunley (doug.hunley@gmail.com)
Twitter: @hunleyd * * * * * * * * * * * * * * * * * * * * * * * Web:
douglasjhunley.com
G+: http://goo.gl/sajR3
 
Old 04-23-2012, 12:47 PM
Michael Mol
 
Default lilo 'duplicate volume id' issue after attaching esata enclosure

On Mon, Apr 23, 2012 at 8: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.
>
> Ideas on how I can fix/remove the vol-id from the external disks?

I *think* those are going to be filesystem labels. If it's ext-based,
you should be able to use tune2fs to change them.

Is there a reason you can't boot from a liveDVD or similar, chroot in,
and run lilo? You'll have to get to a working system to change things
one way or another...

--
:wq
 
Old 04-23-2012, 05:30 PM
Doug Hunley
 
Default lilo 'duplicate volume id' issue after attaching esata enclosure

On Mon, Apr 23, 2012 at 08:47, Michael Mol <mikemol@gmail.com> wrote:
> On Mon, Apr 23, 2012 at 8: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.
>>
>> Ideas on how I can fix/remove the vol-id from the external disks?
>
> I *think* those are going to be filesystem labels. If it's ext-based,
> you should be able to use tune2fs to change them.
>
> Is there a reason you can't boot from a liveDVD or similar, chroot in,
> and run lilo? You'll have to get to a working system to change things
> one way or another...
>
> --
> :wq
>

no, these are not filesystem labels. they are the first 4 bytes of
each disks MBR

lilo will correct them, if i can get lilo booted

i tried booting systemrescue cd, and it boots, but it doesn't see the
external drives (hence it boots fine)


--
Douglas J Hunley (doug.hunley@gmail.com)
Twitter: @hunleyd * * * * * * * * * * * * * * * * * * * * * * * Web:
douglasjhunley.com
G+: http://goo.gl/sajR3
 
Old 04-23-2012, 11:25 PM
Paul Hartman
 
Default lilo 'duplicate volume id' issue after attaching esata enclosure

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?
 
Old 04-24-2012, 04:11 PM
Doug Hunley
 
Default lilo 'duplicate volume id' issue after attaching esata enclosure

On Mon, Apr 23, 2012 at 19:25, Paul Hartman
<paul.hartman+gentoo@gmail.com> wrote:
> Do you have another machine with SATA ports that you can hook them up
> to temporarily and alter those troublesome bytes?

I wish ;(

--
Douglas J Hunley (doug.hunley@gmail.com)
Twitter: @hunleyd * * * * * * * * * * * * * * * * * * * * * * * Web:
douglasjhunley.com
G+: http://goo.gl/sajR3
 
Old 04-24-2012, 04:23 PM
Michael Mol
 
Default lilo 'duplicate volume id' issue after attaching esata enclosure

On Mon, Apr 23, 2012 at 1:30 PM, Doug Hunley <doug.hunley@gmail.com> wrote:
> On Mon, Apr 23, 2012 at 08:47, Michael Mol <mikemol@gmail.com> wrote:
>> On Mon, Apr 23, 2012 at 8: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.
>>>
>>> Ideas on how I can fix/remove the vol-id from the external disks?
>>
>> I *think* those are going to be filesystem labels. If it's ext-based,
>> you should be able to use tune2fs to change them.
>>
>> Is there a reason you can't boot from a liveDVD or similar, chroot in,
>> and run lilo? You'll have to get to a working system to change things
>> one way or another...
>>
>> --
>> :wq
>>
>
> no, these are not filesystem labels. they are the first 4 bytes of
> each disks MBR
>
> lilo will correct them, if i can get lilo booted
>
> i tried booting systemrescue cd, and it boots, but it doesn't see the
> external drives (hence it boots fine)

Try an Ubuntu live CD or similar. If it doesn't see the external
drives, there's a reasonable chance you can modprobe something or
enable hotplug support after you've already booted.


Alternately, can you alter your primary system's MBR to alleviate the
conflict, and then get in and fix things properly?

--
:wq
 

Thread Tools




All times are GMT. The time now is 07:07 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org