InterviewSolution
Saved Bookmarks
InterviewSolution
| 1. |
Solve : OUT OF ROOM? |
|
Answer» Greetings to the Group - My system is a DUAL boot with W7 and Ubuntu 14. I seldom use W but need to keep it for a few programs. So now I got this Disk Usage Analyser which is attached here. It looks like U is RUNNING out of room. So can I go to W and change some partitions to free up some room for U, or what do I need to do? As for the W side, there aren't many programs installed on that side because I hardly go there. According to this analyses, my videos and photos don't seem to be taking up much room. I really don't see much surplus to delete, but obviously there is a space problem. I guess I would like to know exactly where the U os is and how to identify it on the hard drive. I can also reduce the footprint for W to the bare minimum but need to know what that should be. All input is appreciated. There are ways to resize partitions, but its very risky. Before doing so i would backup anything critical to an external drive. Then go in and resize partitions. And from my experience resizing partitions 9 out of 10 times something breaks, and so be prepared to have to perform a total rebuild of both OS if something goes wrong. ...Something breaks 9 out of 10 times!? Really? That's not been my experience. I've resized partitions dozens of times over the years and have never once had a problem. It's always prudent to have a good backup when doing something like this but I believe that resizing partitions is not particularly risky. Yeah, I'm sorry Dave but I also have to take issue with that. I've manipulated literally hundreds (if not thousands) of partitions and hd's over the years and the only times I ran into trouble were in the very early days when I didn't pay attention to what I was doing. Is it possible to cause significant issues when performing drive level operations? Absolutely. But with today's utilities it's as close to foolproof as it can get (assuming the user takes his or her time, pays attention, and doesn't try to bypass built-in safety features). And I also agree with Strollin that when performing any drive level operation, if you create an image first you lower the risk level to close to zero.Quote Yeah, I'm sorry Dave but I also have to take issue with that. I've manipulated literally hundreds (if not thousands) of partitions and hd's over the years and the only times I ran into trouble were in the very early days when I didn't pay attention to what I was doing. Good to hear that partition resizing has gotten better. I have avoided this practice for many years. The last time I resized partitions on a dual boot Windows/Linux system was BACK around Windows 98 and RedHat 6 and it killed RedHat 6 and Windows 98 was still happy. Back then I used Partition Magic a lot and with Dual Boot Windows 98 and 2000 Pro it worked most of the time, but I think there was an issue with partition magic and Linux based partitions to where it wasnt very well at resizing Linux partitions and having them function afterwards. So based on my experiences over 12 years ago... my main concern was that they back up their data before resizing as for its not always perfect. Friends of mine who have used partition magic also have called me in a panic that they lost their data etc, and its very unlikely that they will have access to that data ever again since resizing, and not stopping there, but formatting over top of where data once was etc. The one time was to "short stroke" the drive taking a 160GB HDD and turning a single 160GB partition into 2 x 77.5GB partitions and a single 5GB swap space partition for a system with 2GB RAM. The idea of short stroking was that it would boost drive performance where the swap space would always be located in a small allocated partition space limited to very little fragmentation and fast data response times since the arm doesnt have to sweep the entire drive for scattered data, and the OS and games on the 2 other partitions etc. This attempt with partition magic was a crash and burn. He ended up creating the partitions he wanted from scratch all new and then installing windows to the 2nd partition on the drive with the 1st being the short stroke partition, and then the 3rd partition was for games and data etc. Benchmark results showed a slight gain, but it was still just an IDE HDD and if he upgraded to a SATA drive there would have been a better performance gain. Looking at the wiki I see this here with no reference to Linux compatibility: Quote Compatibility issues As well as Quote Additionally, it had somewhat limited support for ext2 and ext3 partitions. I've been running a VIRTUAL machine [VirtualBox] on my 14.04 distro and putting Windows...whatever...there. Makes it a lot easie to get to and no 'hard' partitioning needed. Works for me. Alan <>< |
|