I think that many of us have performed elementary mistakes before -
otherwise we wouldn't learn from them ;-)   The only one I have not made
so far is doing a "rm -rf /*" or similar... knock on wood.
 
I suppose there are some that have never messed up a computer system,
but people like that don't seem to be the kind of person who would wipe
Windows from a machine and install Linux or do a dual-boot or tri-boot
or octal-boot setup just to try new OSs. I admit that, with VMWare, it
is now much safer to just try an OS (while running Windows or Mac) for a
short period of time and see what you think. But you learn more from
eschewing VMWare and other virtualization software in favor of working
on the bare-metal.
 
I am glad that you got your system working! I have used parted, but did
not know about the recovery function. Good find!
 
Nick
 

---
Nicholas Floersch (pr. Floor-sh)
Stone Environmental, Inc. 

 

________________________________

From: Vermont Area Group of Unix Enthusiasts [mailto:[EMAIL PROTECTED]
On Behalf Of David
Sent: Thursday, August 14, 2008 12:18 AM
To: [email protected]
Subject: Re: cfdisk and a live hdd


Thanks for the reply, I was able to rebuild the partition table with the
tool parted, they have added a rescue function, which searches for
intact file systems and then finds their sizes and confirms if you want
to add that partition to your partition table, I was able to recovery
everything just fine, thanks for the tips and pointers, and for
replying, I wasn't sure if anyone had every performed such an elementary
mistake before, or thats the way it seems it is. All is well again. 


On Wed, Aug 13, 2008 at 10:33 PM, Nick Floersch <[EMAIL PROTECTED]>
wrote:


        Because you were not paying attention to partition sizes, you
may need to use some sort of recovery tool. If you know exactly what
your partition sizes were, you could use (c)fdisk again and create a new
partition table that was exactly the same as your old one - and then
your system *might* work again. This happened to me once a long time
ago, and I was able to do exactly that - reboot, recreate the partition
table in fdisk, reboot, and the system worked again. Having mucked up
the partition table does not mean the data that was/would/is in the now
undefined partitions is gone, it just means the computer has no
reference for how to access it.
        
        If you use a tool to look at the raw data on your drive, you
might still see things, which is how a lot of serious data recovery
programs work.
        
        But, it is at this point that I become fairly useless. I have
not had to recover a working system disk that ran Linux - OS/2, Windows,
and NeXTStep, yes, but for some reason I don't know how to handle this
in Linux.
        
        I think the second-to-worst case would be that you had to run a
data recovery program such as OnTrack. There is this tool, which I have
not used, called TestDisk, which looks for partitions on the disk and
compares against the partition table for inconsistencies, allowing you
to pick which to use...
        
        http://en.wikipedia.org/wiki/TestDisk
        
        The only encouragement I can give is that the most I have
personally learned about computers in the shortest time is when I break
something and have to fix it. Good luck!
        
        Nick
        


        -----Original Message-----
        From: Vermont Area Group of Unix Enthusiasts on behalf of David
        Sent: Wed 8/13/2008 3:48 PM
        To: [email protected]
        Subject: cfdisk and a live hdd
        
        So, I was going along repartitioning a new drive for a soon to
be Gentoo
        install. While inside of my current Ubuntu machine, I used
cfdisk, didn't
        pay attention to the partition sizes, and well I ended up
partitioning the
        drive that my current Ubuntu system is on. This is a very
"noobish" mistake,
        I know, but I figure there has to be a way to fix it. From what
I
        understand, if I reboot the machine, it will probably not boot
anymore
        because the partition table that it is used to, doesn't exist
anymore, it is
        a totally different one. Thanks in advance for helping a "noob"
out.
        
        --
        I'd say the ultimate copy protection would be an awful,
expensive product.
        On the other hand, it doesn't seem to be working for the music
industry...
        ~Some Genius From /.
        ---
        David McClellan
        




-- 
I'd say the ultimate copy protection would be an awful, expensive
product. On the other hand, it doesn't seem to be working for the music
industry...
~Some Genius From /. 
---
David McClellan

Reply via email to