On Tue, 17 Dec 2013 19:05:07 -0800 Paul Mullen <[email protected]> dijo:
>On Tue, Dec 17, 2013 at 05:04:05PM -0800, John Jason Jordan wrote: >> I booted to the regular Xubuntu on SDA1 and, using Gparted, I deleted >> SDB1 and then recreated it. Then I rebooted to Clonezilla and tried >> again, but it still won't clone SDA1 to SDB1. >> >> The above error message is all I have to go on. The only thing I can >> think of is that using the Grub commands on SDB1 previously changed >> something that persists even after deleting and recreating the >> partition. >> >> Does anyone know anything about Clonezilla? Or have any suggestions? > >I doubt Clonezilla cares about the presence (or absence) of a >bootloader, but I could be wrong. I've always used tar to migrate >from one hard drive to another: > >1. Boot from the installer disc (rescue mode, again!). >2. Create a file system on the new partition. >3. Mount both the old and new file systems. >4. Copy the contents of the old file system to the new file system > with tar:: > > cd /path/to/new/filesystem > tar -cC /path/to/old/filesystem . | tar x I read your later message an hour ago, but before following up with tar I decided to try once more to get Clonezilla to work. This time Google found the answer - on a Spanish Ubuntu forum. Turns out the error message that Clonezilla was giving me means that I had "inodos malos o rotos." Yeah, bad or broken inodes. I don't know what an inode is, but I know there is trouble if they are bad. And I know e2fsck can fix them. So I ran e2fsck on /dev/sdb1 and, sure enough, several bad inodes. They got fixed, so I tried Clonezilla again, but Clonezilla still errored out. Still in Clonezilla, I went to a command line and tried e2fsck again. Sure enough, still bad inodes. I let e2fsck fix them, and when I tried to clone SDA1 to SDB1 it worked! So the tar exercises can wait for another day. Now, if you choose Expert Mode in Clonezilla you get a screen with a bunch of options, and the one at the very top lets Clonezilla recreate grub and the MBR. I selected this. When Clonezilla finished I rebooted and, at the BIOS splash screen, I told it to boot to SDB. And it did! I know it did because your previous message is missing from my inbox - I had created a new clone of SDA2 (home) earlier today, so that e-mail was not cloned to SDB2. Plus, I SDA2 and SDB2 are slightly different sizes, as are SDA1 and SDB1. However, my elation was short lived. Using Palimpsest I discovered that I am currently booted still to SDA1, but SDA2 (home) is not mounted. Instead, SDB2 is mounted as home, and SDB1 is not mounted. So right now I am running on SDA1 and SDB2. I am not sure how that happened, but it must have to do with UUIDs and fstab. I should be able to fix that. I hope. _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
