Acronis cloned a Win 7 disk, but my Linux disk now won't boot - why?!
In Win 7, I asked ATIH to clone itself to an empty disk. It did so. The linux disk was in the computer when I asked it to do so, but I pulled it out of the hot swap bay when the computer rebooted, as it was the OS disk that was to be cloned. Now back in the Linux disk seems to find itself renamed or the BIOS looking for some other disk...I can't figure it out..but can't access the disk. HELP!
Can yo see the linux diskif you connect it to another machine? Are you sure that you did not clone the Win dis to the linux disk?
Well, first I don't have another machine and I said I removed the Linux disk during the clone operation...if it cloned to that disk, it did so via the aether of space.
Actually Magic Crazybear you stated you pulled the disk out just before the after clone reboot.
but I pulled it out of the hot swap bay when the computer rebooted,
What do you mean by cloning ATH?
I think Magic Crazybear may have pulled the Linux drive out when TI rebooted to perform the clone. I would never recommend this. TI is counting on the drives being exactly as they were then the "auto-run script" was created. Changing things between that point and the point where the script runs is just asking for problems.
Most likely the Disk Signature changed on a drive that the Linux OS is looking for or trying to use. Most current Linux installations are setup using UUID values and not the older sda1/hda1 type values.
I don't know why you speak of me in the third person, but you are likely correct...so now what?!...to undo that?
I thin Mudcrab was speaking to a wider audience.
Magic Crazybear,
Sorry for any confusion. I was actually directing my comment to Colin, but it's valid for a "wider
audience" as well.
How are you booting the Linux drive? Is it from a boot manager or are you selecting the drive directly (BIOS boot menu, for example)?
Exactly what happens? Do you get an error message? If so, what?
What version of Linux are you using?
Magic Crazybear,
Sorry for any confusion. I was actually directing my comment to Colin, but it's valid for a "wider
audience" as well.How are you booting the Linux drive? Is it from a boot manager or are you selecting the drive directly (BIOS boot menu, for example)?
Exactly what happens? Do you get an error message? If so, what?
What version of Linux are you using?
I can either tell the Bios to boot from that disk or select from a list the Bios displays [still displays the correct Linux kernel]
It is Ubuntu 10.10 and I get a message: /dev/disk/vy-vvid/[long number here] Does not exit!
Does the GRUB2 menu still display properly? In other words, is the error message after selecting to boot into Ubuntu from the GRUB2 menu?
Does the GRUB2 menu still display properly? In other words, is the error message after selecting to boot into Ubuntu from the GRUB2 menu?
I assume [but don't know] what I see is what you refer to as the GRUB2 menu....it displays as it did before. If one selects any of the various kernel versions one gets that error message. [after].
Can you please edit your post and remove my email address from the quote? Hopefully, Acronis will get the problem fixed soon.
---
It sounds like it is displaying the GRUB2 menu correctly. I'll have to search for the repair instructions. At this point I'm assuming the Disk Signature got changed on the drive, most likely because it was pulled, though even in that case, TI shouldn't have changed it.
Would greatly appreciate help on this. What if I removed all disks but the Ubuntu one, and did ....something [I do not know what]...I'm not good on command line Linux, at all!...
Thank you for editing your post.
I have run serveral tests on this and I'm not getting it to break or cause the error you describe. I did find references to similar errors, but they seem to from other things.
I would try disconnecting all the other drives so that only the Ubuntu drive is connected and see what happens.
You may also want to take a look at this.
Do you have a backup image of the Linux drive?
No, no backup, but what you had at 'this' might work....or might not....dare I try it?...I'll wait for my Linux expert to come over. Acronis is a good program, but too powerful at times and doesn't give advance warnings of problems that could and DO occur!. Tonight I will try the Ubuntu disk all by itself....
but if that boots, what next?
You could make an Entire Disk Image of the drive before attempting any repairs. I would recommend this regardless of the repair method being tried. If you don't want to create a backup image, at least copy off any important files.
If the Ubuntu drive boots successfully when it's by itself, I suspect it may continue to do so when the other drives are reconnected.
You could make an Entire Disk Image of the drive before attempting any repairs. I would recommend this regardless of the repair method being tried. If you don't want to create a backup image, at least copy off any important files.
If the Ubuntu drive boots successfully when it's by itself, I suspect it may continue to do so when the other drives are reconnected.
I'm not focused on the future..but on getting my mbr or boot area back....somehow Acronis messed it up, or in combination with me. The terrifying part [and a BIG mistake IMHO] in Acronis is it stating it will do X to 'Drive#Y....that doesn't tell me which drive FOR SURE...I have multiple drives of the same make and size and they change as to their position [thus number] and I don't keep a record. If Acronis would use the names I assign to the disks, then I would know what it was planning on doing...now I don't and am always afraid of a mistake and an overwritten disk...as once happened for the same reason. Now I have a Ubuntu disk with a changed mbr or boot sector. Anyone have any ideas?! It doesn't boot by itself.
If the the MBR is bothcy, can't you just rebuild the mbr? I know for Windows Vista and 7 you can download free a free iso to make a recovery disk and run bootredc to remake the mbr or rebuild the BCD:
http://neosmart.net/blog/2008/windows-vista-recovery-disc-download/
you should be able to find something like that for ubuntu.
There's eems to be a lot of stuff about it if you google. e.g.,
http://linuxhelp.blogspot.com/2005/11/how-to-repair-corrupt-mbr-and-boo…
the matter of identifying disks when doing a rstore has been a big issue with older versions of ATI (8, 9, 10, 11) -- you had to know disk id/serial numbers -- even model numbers, much less disk size wasn't enough if you had more than one disk of the same model. In ATI 2011, you should be able to identify the disk volumes. iirc, in some of the older versions, when you browsed for disks while using the bootCD, you could pick up the bootCD-assigned drive letters and then use those as a guide when you st up the restore.
Yes, I had the same thought, as I've a few times done fixboot or rebuild mbr in Windows. Seems more difficult in Linux.....the url you gave me is not there. I have found some...but they all have different suggestions. Have yet to found one that works. Please, responses from Linux knowledgeable persons most appreciated!
There is nothing wrong with the MBR since GRUB is loading. The problem is deeper in the Linux system. Most likely, there is an invalid UUID reference being used.
Did you try booting the Ubuntu drive with the other drives disconnected?
Was this a clean install of Ubuntu 10.10 or was it an upgrade from 10.04 (or earlier)?
Can you check if the UUID value being used is correct? To do this, please reference the attached PDF file.
Well the 'Ubuntu' drive is shown [in a very unusual fashion - not the usual] and will not open up fully[only one of the three partiions 'shows' in any program I know...so cancel that suggestion! Thanks anyway.
A Linux expert is coming over today, but he was here two days ago as well and failed......lookin' bad.
I agree that it looks bad. It seems like the partitions (or their structures) have been corrupted. The base problem may not even be 'Linux' related.
Have you run any file system checks on the partitions?