hmmm.. I'm not that religious, but remember Jesus always saves..<br><br>if you got tons of inode fsck's then that a problem...<br><br>maybe to do with geometry of the disk, or cosmic rays?<br><br>you should never really move partitions as disks....<br><br>here were you options (past tense).<br><br>make a disk image of the partion with dd, then move it over a network to your new machine, you can then mount it as a loopback filesystem.<br><br>tar ,cpio or evenbetter rsync over the network using a via netcat or something..<br><br><br>moving raw partions is like taking a stroll on the motorway with a blindfold on, it may impress your mates, but don't complain if you get run over.<br><br><br>so, if your talking about large IT networks, first thing you would do is backup files to a storage NAS, or something.. then...do work like this.<br><br>loosing your configs is a bad day, loosing data and your sacked.<br><br>I think googling for answers may not yield results, as you've gone
do the wrong<br>path, data migration should always be done at the filesystem level, not at the raw partition layer....<br><br>although you can have success, I took a nice ubuntu system from a p3 dell machine, and put into a p4 dell machine. after *BACKING* up, I stuck the disks in, rebooted, and hey presto..new machine!<br><br>I've never successful done that with a windows operating system past dos....<br><br>hahahahah!<br><br>If you XP machine is all in a mess, don't blame repair tools, blame XP inability to repair itself, I've managed to resucue unix machines with 50% of the root file system missing. just enough to bring the network up!!!! <br><br>XP...reinstall..remaster..start from scratch.<br><br>hope you get your problems sorted out, sorry to sound all doom and gloom, but there may not be a solution... it's a case of you've put disel into an unleaded petrol car.<br><br><br>Laters,<br>Lee<br><br><br><br><br><br><br><br><br><br><b><i>Bruce Stewart
<bruce_stewart@blueyonder.co.uk></i></b> wrote:<blockquote class="replbq" style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;"> On Saturday 11 August 2007 00:03:06 gordon dunlop wrote:<br>> Hi All,<br>><br>> I am just about crying here. The story is that at long last I decided to<br>> upgrade my Fedora 6 to Fedora 7. I waited this long because fedora 6 is<br>> my default system holding all my multimedia, server, virtualisation and<br>> (most importantly ) my wife's document systems. I decided that instead<br>> of upgrading via YUM or the downloaded DVD, that I should create a new<br>> system with the proper partitions (that I should have done previously),<br>> i.e. having the operating system spread out over three partitions;<br>> namely /, /home & /var where /home would take care of the multimedia<br>> and documents, and /var would take care of the server and virtualisation<br>> systems,
comprising of 80% of the disk space. Why I did not want to do a<br>> direct upgrade was that I was transferring from a 32-bit system to a<br>> 64-bit system, so by doing a clean install of Fedora 7 whilst<br>> maintaining a fedora 6 system , I was going to transfer the data from<br>> Fedora 6 To Fedora 7 when I satisfied that everything on Fedora 7 was<br>> running O.K. I used a partition manager to manipulate my two SATA disks<br>> to create the space for the Fedora 7 partitions and moving the Fedora 6<br>> partition i.e. data movement. After this was done I booted into my<br>> Ubuntu partition, I knew GRUB on my Fedora 6 partition would not work. I<br>> got a fsck superblock error in Ubuntu (because the Fedora 6 partition<br>> had been moved), this was rectified by editing fstab to set the<br>> default binary of the Fedora 6 partition to 0 0 rather than 0 2. I<br>> rebooted where the Fedora 6 partition was picked up by Ubuntu, and
using<br>> the GRUB editor reinstalled GRUB into my Fedora 6 partition with the<br>> commands:<br>> GRUB> root (hd1,6)<br>> GRUB> setup (hd1,6)<br>> GRUB> quit<br>> hd1,6 is the equivelant of /dev/sda7. I rebooted and went into the<br>> Fedora 6 system via GAG boot manager. The menu came up and the system<br>> was initiated, when it came to the file system check it went into fsck<br>> mode (as was expected) It took about 30 minutes with a lead weight on<br>> the Y key for it to go through its routine to change the inode errors.<br>> It came up with at the end errors it could not correct with root inode<br>> not a directory. I eventually rebooted and went back into the Fedora 6<br>> partition where the GRUB prompt came up and I could not re-install GRUB<br>> due to superblock errors nor could I mount this partition from other<br>> Linux partitions. I was scratching my head trying to work out what was<br>>
going on, then I realised that my Windows XP virtual machine (20GB) is a<br>> NTFS file of 20GB. Here I have a file of 20GB of the NTFS file system<br>> within an EXT 2/3 system. This is why there were problems in correcting<br>> inode errors based upon the ext2/3 fsck system where the Virtual XP file<br>> was preventing this. The virtual Windows XP machine cannot see the file<br>> system of Linux (It has an Aspberger Syndrome complex where it thinks it<br>> is important, but it is only a lowly piece of shit within the system and<br>> does not understand about hierarchies). I now cannot mount the Fedora 6<br>> partition, nor find a way to either destroy or move this XP virtual<br>> machine. I have diagnostic tools, but they only deal with Linux or<br>> Windows file systems, not both. This brings to the conclusion that there<br>> will be problems in large IT environments where heterogeneous systems<br>> using virtualisation systems,
especially in looking at Process<br>> Migration. So, if anyone can help me I would be very grateful, not that<br>> I care much for these large IT environments, it is more of how can I<br>> tell my wife that she cannot access her documents. Anyway no more<br>> googling for the answers tonight.<br>><br>> Gordon<br>><br>><br>> _______________________________________________<br>> dundee GNU/Linux Users Group mailing list<br>> dundee@lists.lug.org.uk http://dundee.lug.org.uk<br>> https://mailman.lug.org.uk/mailman/listinfo/dundee<br>> Chat on IRC, #tlug on dundee.lug.org.uk<br><br>The VM image is just a file, like a an OO.org Doc, or an .mpg, so it doesn't <br>matter what is in the image file. So unless you have created the VM on a bare <br>(filesystemless) disk, whatever fsck tool you are using should be for <br>whatever filesystem the VM image file is on.<br>You may have a base filesystem problem, ie the disk itself is actually fracked
<br>or the filesystem is damaged in such a way that it is not repairable.<br>Or you may have a VM image problem, ie the disk image inside the VM is <br>damaged, so it needs to be fixed by XP's own tools.<br><br>Bruce S.<br><br><br>_______________________________________________<br>dundee GNU/Linux Users Group mailing list<br>dundee@lists.lug.org.uk http://dundee.lug.org.uk<br>https://mailman.lug.org.uk/mailman/listinfo/dundee<br>Chat on IRC, #tlug on dundee.lug.org.uk<br></blockquote><br><p> 
<hr size=1>
Yahoo! Answers - Get better answers from someone who knows. <a
href="http://uk.answers.yahoo.com/;_ylc=X3oDMTEydmViNG02BF9TAzIxMTQ3MTcxOTAEc2VjA21haWwEc2xrA3RhZ2xpbmU">Try
it now</a>.