Discussion Forums > Technology
I broke my computer completely #_#
Lupin:
--- Quote from: Bob2004 on February 08, 2012, 01:40:13 PM ---It sounds like a slightly more complex problem than that; if it was that simple, then Windows would still be working fine.
--- End quote ---
OP used Window's resizer instead of bootcamp's to modify partitions. Partition table got modified (or even overwritten). This is why OSX no longer appears on boot. Now bootloader loads, looks for relevant Windows files for booting but since partition tables are now borked, Windows gives a tantrum.
There's an error log posted by op. Repair simply fails according to the log. You can try Startup Repair from your Windows disc to try repairing it but at this point isn't worth repairing. The op is running on a mac. Repairing windows won't work for one running from bootcamp; you're going to break the OSX.
Best course of action is to first repair OSX (repair the drive partition tables using OSX disc). Either use it or a live cd to access windows partition and copy important files. Then reinstall both OSX and windows.
Bob2004:
--- Quote from: Lupin on February 08, 2012, 04:27:42 PM ---
--- Quote from: Bob2004 on February 08, 2012, 01:40:13 PM ---It sounds like a slightly more complex problem than that; if it was that simple, then Windows would still be working fine.
--- End quote ---
OP used Window's resizer instead of bootcamp's to modify partitions. Partition table got modified (or even overwritten). This is why OSX no longer appears on boot. Now bootloader loads, looks for relevant Windows files for booting but since partition tables are now borked, Windows gives a tantrum.
--- End quote ---
Ah yeah, sorry, you didn't mention Windows in your last post, which is why I said that. That's pretty much the gist of the problem, by the sounds of it.
I've never used Bootcamp, so I don't really know much about it. If it's different to other methods of dual booting, and doesn't just boot the relevant partition for each operating system, then you may be right. I assumed that because he got at least partly into Windows (hence the BSOD), it wasn't a problem with the boot loader being borked (at least not too badly). But if it's as you say, then I agree, that Windows install is probably a goner.
Remak:
--- Quote from: krumm on February 08, 2012, 04:52:08 AM ---Resizing partitions is very risky and can cause data loss. ...[more] (click to show/hide)You should never do it unless you are backed up or don't care to lose the data on the drive. I only have about a 75% success rate with partition resizing(mostly on smaller drives). I've never used a mac before but it is really just another OS and uses the same hardware, so my options should work the same.
Simplest solution is to just write off your data and reinstall mac OS, and may be the only option. But, I would try mounting the hdd to a working OS before writing anything off. There is 2 ways to do that: pulling the drive and putting it into a computer that has one or a Linux live CD. I usually just pull the drive and hook it up to a working desktop, but I don't know how hard it is to get to the drive in your computer or if you have a desktop available to use. Best bet is probably to burn a Linux live CD, I recommend Ubuntu 10.04. Use the try option to get a working desktop that you can use to access the computers HDD and an external HDD to copy data to.
If you get access to your HDD, but the data you want is not there, probably means the data is lost. My success at recovering truly lost data(the kind that does not show up when you get access to the hdd) is zero. I always end up recovering useless OS files and stuff I don't want.
--- End quote ---
I've never had aproblem with resizing, reallocating,and creating new partitons from with in windows before with the built in utility. :-\. But I was always using ntfs and not trying to create a fat partition. And..none of those computers were duel booting something >_<.
Unfortunately there is no way that I can access the hd to put into a desktop (can you even hook up a laptop hd to a desktop hd without a special connector? :P).
--- Quote from: AnimeJanai on February 08, 2012, 06:41:36 AM ---There are software tools that claim to recover data from mis-partitioned drives. So don't write it off yet. Find at least several different softwares and read their instructions and FAQs to learn more before trying one of them.
--- End quote ---
I'm less worried about researching that right now.. because at this point I cannot even run anything :lol:
--- Quote from: Lupin on February 08, 2012, 11:41:36 AM ---This caused the problem. You should have resized the partition using OSX. Windows altered stuff that OSX needs to boot.
Just use a live cd that can read whatever format that windows partition is to recover the files.
--- End quote ---
Eeek, thank you. I was thinking it probably was because of that, but I wasn't sure. :-\. How exactly do live cd's work? Do I just burn them and plug them into the cd reader and they automatically boot up? Last time I tried any live cd was like ubuntu 6.xx or 7.xx. I don't remember how they work anymore. >_<.
--- Quote from: Bob2004 on February 08, 2012, 01:40:13 PM ---You say you can boot Windows in safe mode? Do so, go to Control Panel -> System -> Advanced system Settings -> go to the Advanced tab, and open Startup and Recovery Settings, and uncheck the box labeled "Automatically Restart". ...[more] (click to show/hide)
Now you can reboot your computer, and when the BSOD (Blue Screen Of Death - the blue screen with white letters you see) appears, your PC won't automatically reboot, and you can see what it says. It should tell you what the specific error is that's causing Windows to crash (at the least it should tell you what file the error is related to) - there'll be a whole load of complicated numbers and data that you don't need, but there should be one or two lines which state the error in (relatively) plain English; post what it is here, and it should give us a better idea of the cause of your problem.
--- Quote from: Lupin on February 08, 2012, 11:41:36 AM ---This caused the problem. You should have resized the partition using OSX. Windows altered stuff that OSX needs to boot.
Just use a live cd that can read whatever format that windows partition is to recover the files.
--- End quote ---
It sounds like a slightly more complex problem than that; if it was that simple, then Windows would still be working fine.
--- Quote from: Kyrdua on February 08, 2012, 08:51:21 AM ---Did you just say Macbook?
o_o, pretty sure stuff works differently on that even if you say it involves partitions and whatnot.
--- End quote ---
Nah, fundamentally it's still just a laptop. The main difference is OSX, which works with partitions etc just the same as any other OS.
--- Quote from: kitamesume on February 08, 2012, 07:58:21 AM ---o.o ehh.. risky? haven't encountered a single error via resizing the OS's partition by more than a dozen times ranging 30gb-50gb(seems like 40gb is my sweetspot right now, win7 starts at around 25gb @ fresh install including drivers and grows to 30+gb after ridiculous patches...).
i use "EASEUS Partition Manager" if that makes a difference.
--- End quote ---
Basically, shrinking partitions is absolutely fine... so long as you don't accidentally get rid of space that contained data. If all your data is located in the first 50GB of a 150GB partition, with nothing in the remaining 100GB, then you can, in theory, cut out that 100GB without any issues. If there's data located in that 100GB though, then at best you'll just lose that data; at worst you'll completely break everything (if it's a Windows system file that got deleted, for example). Since, due to drive fragmentation etc, even if you only have 50GB of data on the partition it might still extend further than that (with lots of empty bits in between), you need to be very careful when resizing system partitions.
--- End quote ---
Nope, I cannot even boot into safe mode. Startup repair just starts up after the bsod.
--- Quote from: Lupin on February 08, 2012, 04:27:42 PM ---
--- Quote from: Bob2004 on February 08, 2012, 01:40:13 PM ---It sounds like a slightly more complex problem than that; if it was that simple, then Windows would still be working fine.
--- End quote ---
OP used Window's resizer instead of bootcamp's to modify partitions. Partition table got modified (or even overwritten). This is why OSX no longer appears on boot. Now bootloader loads, looks for relevant Windows files for booting but since partition tables are now borked, Windows gives a tantrum.
There's an error log posted by op. Repair simply fails according to the log. You can try Startup Repair from your Windows disc to try repairing it but at this point isn't worth repairing. The op is running on a mac. Repairing windows won't work for one running from bootcamp; you're going to break the OSX.
Best course of action is to first repair OSX (repair the drive partition tables using OSX disc). Either use it or a live cd to access windows partition and copy important files. Then reinstall both OSX and windows.
--- End quote ---
Ohhh.I just remembered something~! Before I resized the partition in windows the drive names had a blue bar above them. After the bar changed to a tan/green color. And for some reason it was telling me that it wanted to make an F drive instead of the M:/ drive I wanted instead. That was when I realized I had messed something up. I should of backed up my data then...instead of restarting to see how much I screwed up. >_<.
--- Quote from: Bob2004 on February 08, 2012, 04:53:16 PM ---Ah yeah, sorry, you didn't mention Windows in your last post, which is why I said that. That's pretty much the gist of the problem, by the sounds of it.
--- End quote ---
Yay~! Now you guys agree :laugh:. So anything new to figure out with the new information and the live cd questions. :D
ps;Thank you everyone :laugh:. I was so surprised to wake up and see 10 replies to this :o
Freedom Kira:
--- Quote from: Remak on February 08, 2012, 05:07:15 PM ---Eeek, thank you. I was thinking it probably was because of that, but I wasn't sure. :-\. How exactly do live cd's work? Do I just burn them and plug them into the cd reader and they automatically boot up? Last time I tried any live cd was like ubuntu 6.xx or 7.xx. I don't remember how they work anymore. >_<.
--- End quote ---
Basically, yes. Pop it in, and if the CD drive is higher than the hard drive in boot priority, it'll just work. If it's not, or if you're in doubt, mash F12 on bootup.
Lupin:
--- Quote from: Remak on February 08, 2012, 05:07:15 PM ---I've never had aproblem with resizing, reallocating,and creating new partitons from with in windows before with the built in utility. :-\. But I was always using ntfs and not trying to create a fat partition. And..none of those computers were duel booting something >_<.
--- End quote ---
OSX (at least the recent ones) has NTFS read support out of the box. You can also install ntfs-3g on your mac to read/write from/to ntfs partitions.
--- Quote from: Remak on February 08, 2012, 05:07:15 PM ---Ohhh.I just remembered something~! Before I resized the partition in windows the drive names had a blue bar above them. After the bar changed to a tan/green color. And for some reason it was telling me that it wanted to make an F drive instead of the M:/ drive I wanted instead. That was when I realized I had messed something up. I should of backed up my data then...instead of restarting to see how much I screwed up. >_<.
--- End quote ---
Blue bar means it's a primary partition. Primary partitions have fixed sizes and can only have one filesystem. Green means it's an extended partition. Extended partitions can have as many logical partitions in it. Tan means logical partitions(?) You can only resize logical partitions inside extended partitions, which is why windows converted yours. That didn't caused the problem.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version