rebuild partitions/label from existing partitions - used parted on wrong drive
After seeing a GPT warning on a 500G drive I wanted to assimilate, I used parted on the wrong drive--my OS drive. Is there a way to reconstruct what I've broken?
The drive I wanted to use Code:
fdisk -l Unfortunately, I ran it on /dev/sda and not /dev/sdb. When it complained again about being in use, I figured it was a residual tag or something. Not noticing I'd typed the wrong drive letter, I verified in another console that the drive was indeed unmounted. It was, I proceeed, and now I am fearful to reboot. The drive before I killed it Code:
Disk /dev/sda: 160.0 GB, 160041885696 bytes Code:
Disk /dev/sda: 160.0 GB, 160041885696 bytes Ugh. I've begun a lovely pattern; my last LQ post began with a typo as well, and it bore a strikingly similar theme. :-( Is there a way to reinstate from the still-running partitions? /n00b |
You can just use fdisk to recreate the partitions with the exact same blocks (gladly you have the start- and end-sectors), or you could install Testdisk and let it scan for your partitions.
|
Quote:
Quote:
Code:
/dev/sda1 won't be reported to kernel Quote:
|
Quote:
disable automount ! or use a live dvd/cd like gparted livd cd or System Rescue CD |
Quote:
I ran the parted utility on the wrong drive with a typo and therefore processed partitions which were still mounted in the first place--I'd already unmounted the drive I intended to impact. I'm not at home right now so am paraphrasing the message it actually gave**. It was something along the lines of Code:
partition /dev/sda1 has been rewritten, but this has not yet been reported to the kernel, please reboot for changes to take effect ** I also can't unequivocally mark this thread as solved, since only a reboot will verify the fix worked, and I'm not going to try that remotely. I may run with scissors, but I'm not going to do it in the dark! :-) |
All times are GMT -5. The time now is 04:41 PM. |