SlackwareThis Forum is for the discussion of Slackware Linux.
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.
I've been dual booting now for a while. Running Slackware 10.2 and Windows XP. XP is located on one drive with only 30G on it. I split that drive in half so XP gets 15, and Slack can have the rest.
Now this is the issue. I've booted back into Slack after some time (I need XP for games, Cedega just doesn't cut it, and I've got no additional hardware at the moment to make a box just for windows) and now all of a sudden, everything is working fine, but fdisk and cfdisk report on all my partitions that there is free space, and each drive and device has never been partitioned.
not sure what's going on, never seen this before. If I try and make a new partition (which I don't want to do since obviously there is stuff on each of these partitions) it makes for example, /dev/hdb2p1
Also... and this is a slightly different issue all together, at least I think it is... but I was in XP the other day, working on a new mix (I'm a DJ) and I was recording, and filled my backup drive up. It was my 160gig backup drive, and I was recording the mix to that drive because it had the most available space, about 4gigs. Well I wasn't paying attention and got lost in my music, and filled the drive up. Windows of course freaks out at this, my recording app (Audacity) crashes, I stop my mix, and windows starts to throw up on itself. So I reboot, and after I reboot I pull up my backup drive, and now XP wants to tell me that my drive needs to be formated before I can continue. BullShit. I pull up Slackware, and it won't mount the drive either, it reports "FATAL ERROR: Bad primary partition 0: Partition ends after end-of-disk"
What exactly happened? I need everything on that drive of course, and I'm not going to format it. I would try and recover it , but I even if I could, I don't have any other drives to put the data that I recover on to. Is there a way I can fix the NTFS partition or header or whatever that's been destroyed/removed from the drive, that is now causing it to not read the partition correctly???
Now for a new issue, I have a second box, that appears on startup to start loading up the kernel, and says that all the partitions are listed at read-only. and when I do df it lists each partition as the same. IE
all have the same size, available free space, and are all at 59% but are mapped to the appropriate locations. It starts up in the linux "safe" mode, and won't allow me to do much to it.
Any ideas? I haven't tried playing around with that issue much, but I am desperate to recover this 160gig drive.