Lilo Error Duplicated Volume Id

Login lilo duplicated volume ID The place to post if you need help or advice Moderators: ChriThor, LXF moderators Post a reply 7 posts • Page 1 of 1 lilo duplicated volume ID by SimonRobert » Tue Dec 27, 2005 7:28 pm Hi recently, I don't know why, I have been getting a lilo error. First on boot a black screen with LIL across the top for 40 secs, then ERROR: DUPLICATE VOLUME ID. The bot prcess then takes a while to start and the visible part (Mandriva 2006 official) takes an age checking file systems. Also the whole system seems slower, apps taking more power to use, stuttering mouse movements when two or more memory intensive things running. All new. I have checked. The advice is to run lilo -T vol-id. This produces BIOS Volume ID 0x80 0D179473 0x81 0D179473 * Volume ID's are NOT unique. '*' marks a volume ID which is duplicated. Duplicated ID's must be resolved before installing a new boot loader. The volume ID may be cleared using the '-z' and '-M' switches. Running lilo -z -M /dev/hdb or even the same for hda makes no difference. As the advice says then run lilo -v to re-install. How can I actually see what these bios ids relate to in drives? Does it make any difference? It may relate to the USB dvd burner as when I load a dvd on this device the entire system slows down to access it. Again new, but attempting to remove BIOs IDs from disk drives just results in lio saying they're inaccesable. Help recieved gratefuly. Simon SimonRobert Posts: 6Joined: Sat May 28, 2005 9:41 am Top RE: lilo duplicated volume ID by shifty_ben » Fri Feb 03, 2006 12:27 am I assume you are running all this as root? I had a similar issue a while back, I cant remember how I solved it, but as I am quite bad at remembering I am also quite anal at writing things down I will hunt out what I did and post back if/when I find it. Thats even assuming you havent already resolved it? ---B Taskerhttps://www.bentasker.co.uk shifty_ben LXF regular Posts: 1293Joined: Tue Oct 04, 2005 9:56 amLocation: Ipswich Website Top RE: lilo duplicated volume ID by SimonRobert » Tue Feb 21, 2006 6:56 am Please could you look out y

this post in threaded view ♦ ♦ | Report Content as Inappropriate ♦ ♦ 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 https://linuxformat.com/forums/viewtopic.php?t=1995 the vol-id from the external disks? -- Douglas J Hunley ([hidden email]) Twitter: @hunleyd                                               Web: douglasjhunley.com G+: http://goo.gl/sajR3 Michael Mol Reply | Threaded Open this post in threaded view ♦ ♦ | Report Content as Inappropriate ♦ ♦ Re: lilo 'duplicate volume id' issue after attaching esata enclosure On Mon, Apr 23, 2012 at 8:30 http://gentoo.2317880.n4.nabble.com/lilo-duplicate-volume-id-issue-after-attaching-esata-enclosure-td121474.html AM, Doug Hunley <[hidden email]> 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 Douglas J Hunley Reply | Threaded Open this post in threaded view ♦ ♦ | Report Content as Inappropriate ♦ ♦ Re: lilo 'duplicate volume id' issue after attaching esata enclosure On Mon, Apr 23, 2012 at 08:47, Michael Mol <[hidden email]> wrote: > On Mon, Apr 23, 2012 at 8:30 AM, Doug Hunley <[hidden email]>

Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about http://serverfault.com/questions/195345/generate-a-new-volume-id-in-linux Stack Overflow the company Business Learn more about hiring developers or posting ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault is a question and answer site for system and https://github.com/a2o/lilo/blob/master/readme/README.volumeID network administrators. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top Generate lilo error a new Volume ID in Linux up vote 1 down vote favorite Sparing most details/reasons, I have a situation in which I'm cloning drives for mass production. Some of them are being installed in servers that only need one disk (in that case this is a non-issue), but some are being installed in servers that will use 2 of them in RAID1. In another case we're building a tool to assist the lilo error duplicated admin in replacing a faulty disk by ensuring the new disk is large enough and then copying the MBR and Partition Table, and then adding it to the RAID1. When this happens LILO complains about duplicate volume IDs (which makes sense). This is why I would like to generate new volume IDs for the partition being added to the RAID1 array. Does it make sense to use sfdisk to rewrite a disks partition table, or is there a more straightforward command/technique to create a new volume id for an existing volume? linux raid software-raid mdadm fdisk share|improve this question asked Oct 27 '10 at 14:32 andyortlieb 604618 add a comment| 1 Answer 1 active oldest votes up vote 1 down vote accepted Read the mbr from the disk, change the disk signature which is the 4 bytes @ offset 440 in the mbr then write it back to the disk. dd if=/dev/sda of=mbr.dat bs=512 count=1 sigchange.pl # see script below dd if=newmbr.dat of=/dev/sda bs=512 count=1 Note: I tested this by saving the output of od -x for mbr.dat and newmbr.dat and then running a diff on the 2 text files which shows that only the relevant 4 bytes are changed. #!/usr/bin/perl #sigchange.pl open FILE,"

Sign in Pricing Blog Support Search GitHub This repository Watch 2 Star 1 Fork 0 a2o/lilo Code Issues 0 Pull requests 0 Projects 0 Pulse Graphs Permalink Branch: master Switch branches/tags Branches Tags feature/xvda-support master Nothing to show Nothing to show Find file Copy path lilo/readme/README.volumeID Fetching contributors… Cannot retrieve contributors at this time Raw Blame History 240 lines (181 sloc) 9.9 KB Technical Documentation for LILO 22.5 and later Use of the Volume ID (aka serial number) updated: 20-May-2003 MOTIVATION ========== In the past, the biggest headache to getting LILO to boot reliably was the determination of the assignment of BIOS device codes to disks. This assignment is made by the BIOS, and is quite simple on single hard disk systems: the hard disk receives BIOS device code 0x80. However, even two disk systems can confuse LILO if the disks are attached non-sequentially: viz., if the disks are /dev/hda and /dev/hdb, they are assigned device codes 0x80 and 0x81, respectively; however, if the disks are /dev/hda and /dev/hdc (perhaps, /dev/hdb is an IDE CDROM), LILO will mistakenly think that the second disk is 0x82. Just because /dev/hdb is not mentioned in the configuration file (/etc/lilo.conf), does not mean that it does not exist. But on a two-disk system, attaching the second disk to the second IDE controller has performance advantages. The solution was to explicitly tell LILO, in the configuration file, that the second disk was attached as /dev/hdc: viz., disk = /dev/hda bios = 0x80 disk = /dev/hdc bios = 0x81 The above assignment can be determined automatically in most cases, if the system was booted with a recent version of LILO that supports the "BIOS data check". This scheme makes the results of certain key BIOS calls available to the Boot Installer (/sbin/lilo), even though it cannot execute BIOS calls directly (far too dangerous). However, if one used a rescue disk created with another boot loader, the BIOS data check information is not available, and the necessity of the two lines above becomes necessary for