Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I have a 3TB drive that I have been having quite a lot of problems with.
I have partitioned it into 3 gpt partitions, approximately 1TB for the first two and 841 (what's left) for the last one.
I am using mostly Windows 7, but I have ubuntu installed too.
My problem is that I have 312GB in the last partition (841) it but it's full. How could that be ? If I use the software windirstat, it says that 528GB are 'unknown', and indeed that's approximately 841-312. There are no hidden/system files. These tests were from Windows 7, but apparently ubuntu also says it's full.
I tried to ls into /media/... and in some cases it says io error.
The disk is new and its integrity seems fine (no smart errors).
Can you help me to solve this please ?
ps: the disk is actually not mine so please be precise with your questions/tests/walkthroughs so that I don't have to borrow it every time.
Device Boot Start End Blocks Id System
/dev/sdd1 * 1 13 102400 7 HPFS/NTFS
Partition 1 does not end on cylinder boundary.
/dev/sdd2 13 15566 124930048 7 HPFS/NTFS
Last edited by kateausten; 04-30-2011 at 01:32 PM.
And also, everytime windows starts, it tries to do a scan disk because it says that this partition contains errors. This process never ends, so it has to be skipped when the computer starts.
Can someone please help me to figure out what's wrong while I still have access to the hard drive ?
I don't understand why it says it's full if it's not...
Device Boot Start End Blocks Id System
/dev/sdb1 1 624 5009444+ ee GPT
Partition 1 has different physical/logical beginnings (non-Linux?):
phys=(0, 0, 1) logical=(0, 0, 2)
Partition 1 has different physical/logical endings:
phys=(1023, 254, 63) logical=(623, 164, 63)
The above examples are from my own machine using those commands. You will probably be unable to run those commands as a regular user so you need to sudo or use su.
Finally use the Windows tools with which I am not familiar on Vista 7.
I am sorry the spaces or tabs don't translate real well in this forum window.
In Ubuntu, did you use the parted command to list the partitions on your sdb drive? (fdisk told you to do that.)
IIRC, Windows creates a backup copy of the $mtf file at the physical end of a disk in a non-standard, hidden, partition. On a 3TB drive that would be a fairly big file, and the "standard" Windows partitioning tools would not show you that space since it's "reserved for the Windows OS. The Ubuntu tools may have shown you that space as available, but, when windows used it, it would be "gone" from your drive.
(Note that the above is speculation: I don't even know what a "GUID Patition Table" is, and haven't used Windows since XP.)
I decided I wouldn't put my oar in and decided to wait to see if someone more knowledgeable than I could chime in.
I'm going to suggest this to the OP:
Boot to a GParted Live CD or USB stick. Run GParted. Don't actually do anything; just take some pictures of what GPartED displays regarding the drive in question and about its partitions.
Screenshots will be more trouble than they are worth from a live boot. Use a digital camera.
Take more pictures than you think you will need, then post the ones that seem to convey the most information. Either post them here or, if you have a website, upload them and post the links here. You may need to take some practice shots to find the best settings.
I know it sounds like a lot of work, but we're game if you are. Sometimes a picture really is worth etc.
Edit: You may find the answer simply by using GParted. It's much more user friendly than fdisk.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.