Crunchbang overwrote partition table => Windows messed up

tomet · 2013-12-27 21:25:48

Hello everyone!

Here's what happened:

I wanted to install Crunchbang alongside Windows 7. After some issues with the live USB I had to create it using dd on my netbook which already has Crunchbang installed. It then worked in live session and I wanted to install it. I selected to manually partition the drives (I have two). I had freed up space on both before which was unallocated now. On the SSD (my system drive for windows) the installer correctly identified the existing partitions and I partitioned the rest to my liking. On the HDD however it didn't recognize any partition (though there was one there). I didn't think about that too much (which turned out to be pretty dumb) aand just created the Crunchbang partitions at the end of that drive because I kney that the existing one was at the beginning. I installed Crunchabgn and then booted into Windows again. Not Windows turned out not to see its partition on the HDD anymore. Apparantly, Crunchbang had overwritten the partition table (as a very helpful friend explained too me). I then used DiskTool (?) to recreate the partition for windows (which of course destroyed the #! installation but I didn't care about that.

Well, ahving said all that, the point that actually concerns me: If I still want to install #! (which I want although it caused a lot of trouble), what can I do? Was that just a problem that doesn't occur next time? Has anyone else experienced something similar? Has anyone suggestions about what to do? Or is this a bug yikes ?

Thanks for any help

Tony

retf · 2013-12-27 22:26:03

It's possible the Crunchbang live image does not include the NTFS partition library - which may explain why the NTFS Windows 7 partition was not detected. If this is the case, you might need to re-size the NTFS partition from inside Windows... then install Crunchbang in the newly freed space...

I really know nothing about MS products anymore - since I haven't used them in about 10 years... but here's a link to "free for personal use" partition resizing tool...
http://www.partition-tool.com/personal.htm

Again - I'm not an MS products expert and I haven't used the linked tool... maybe someone else has a better suggestion?

tomet · 2013-12-27 23:18:15

I actually installed #! on unallocated space. But apparently becuase #! didn't recognize the windows partition, it overwrote the partition table.

On my netbook I have sort of the same setup (only one drive though) and #! recognized the Windows partitions on the other drive of my PC, too. So I don't think NTFS is the problem here.

retf · 2013-12-27 23:58:52

Perhaps I'm misunderstanding the problem...

You have a computer currently running Windows 7.
You installed Crunchbang in the "free space" on one or two drives in the machine.
You expect the computer to now be a "dual boot" machine...
However... choose your scenario...

1. The computer only boots into Crunchbang.
2. The computer only boots into Windows 7.
3. The computer can boot either Crunchbang or Windows 7, but the user data stored in an NTFS partition is no longer accessible to Windows 7.
4. The computer does not boot.
5. Other.

If the problem is #1 - then the problem most likely relates to the Master Boot Record [MBR] - not the entire partition table - and is fixable in a couple of ways:
a. Install Crunchbang first - then install Windows 7...
aa. Activate boot menu in Windows 7 to boot into Crunchbang.
b. Install Crunchbang as you described already.
bb. Modify grub to list the Windows 7 partition.
bbb. Modify grub options to pause for a "long" time so that it will be clear that the machine can booted into either OS.
c. There is some tool out there that will allow installation of GNU/Linux in a VM-like file within a Windows partition.
cc. This will not require any modifications to your Windows install...
d. Install Crunchbang first...
dd. Install xen hypervisor...
ddd. many complicated steps later you can install as many different OSes as you want - and boot them up at will...

ew · 2013-12-28 00:28:52

If you used guided mode, then don`t do that. Always go with "manual". It`s not necessary to modify grub. Write grub to MBR. The os-prober will detect and add a entry for W7, as long as W7 is installed in legacy-mode, and not uefi/gpt.

If the disk uses gpt-table instead of msdos, you need an additional partition (bios-grub). 1MB is more than enough, use as "reserved bios boot area". The rest of the install is the same as if you install to a msdos-disk.

If you use manual mode, the partitioner will not overwrite anything, other than what you tell it to do. I`ve installed Crunchbang hundreds of times, and it has never messed with my partitions...

retf · 2013-12-28 02:11:21

My typical installation of GNU/Linux on a Windows machine goes like this:
0. Never boot into Windows.
1. Wipe the drive/s completely using DBAN bootable wipe CD.
http://www.dban.org/
2. Set BIOS to boot USB.
3. Insert Debian [testing] bootable USB stick - sometimes Crunchbang if the machine is low spec.
4. Choose a few options - and a few minutes later - done.

I've never had any problems with MS Windows messing up my GNU/Linux installation
smile

tomet · 2013-12-28 09:59:52

Thank you all for your replies. Just to clarify, I have things restored now in Windows so that's not the problem. The probem rather is that I'm afraid of starting another attempt to install #!.

@retf:
My situation is closest to scenario 3. It's just that because Windows couldn't access its data on the HDD anymore that it formatted that drive and then #! doesn't work anymore.

I have Windows already installed and I don't want to reinstall it. To me, the problem seems to be that #! just didn't see the Windows partition on the HDD.

I think what I'll do is delete the #!-partitions and then try to install #! again. If the installer again doesn't see the Windows partition, I'll stop the installation.

@ew: I used manual partitioning, but #! didn't recognize th Windows partition. It declared the HDD to be all unallocated.

Thanks again for your help, I'll report on my progress in the reinstall here.

KrunchTime · 2013-12-28 10:44:37

Hmmm, I've never installed into a dual-drive setup before, but I have two separate partitions besides the Windows partition for data and disc burning. I've never had CrunchBang not recognize the Data and Burn partitions when installing.

Anyway, here's a thought. Using CrunchBang live, startup GParted and create another partition for CrunchBang use on the HDD. Make note what it's called; e.g. sda/b/c 5/6/7... Then use the manual install option when you attempt to install CrunchBang.

Another thing to do before my previous tip would be to run GParted and see how it recognizes the setup of your HDD.

retf · 2013-12-28 12:21:56

You could open a "root" terminal after booting with the Crunchbang install USB/CD and view - and post it here too - the output of:

lsblk -fmi

Which will tell you quickly and concisely the drive/partition designations as well as the filesystem for each partition recognized...

Here's my output as an example - I have the Crunchbang install USB plugged in too...

NAME   FSTYPE  LABEL      MOUNTPOINT NAME     SIZE OWNER GROUP  MODE
sda                                  sda    111.8G root  disk   brw-rw----
|-sda1 ext4               /          |-sda1 107.2G root  disk   brw-rw----
|-sda2                               |-sda2     1K root  disk   brw-rw----
|-sda5 ext4               /boot      |-sda5   953M root  disk   brw-rw----
`-sda6 swap               [SWAP]     `-sda6   3.7G root  disk   brw-rw----
sdb                                  sdb      1.8T root  disk   brw-rw----
`-sdb1 ext4               /home      `-sdb1   1.8T root  disk   brw-rw----
sdc    iso9660 CrunchBang            sdc      3.8G root  floppy brw-rw----
`-sdc1 iso9660 CrunchBang            `-sdc1   739M root  floppy brw-rw----

Last edited by retf (2013-12-28 12:33:14)

ew · 2013-12-28 13:24:06

tomet wrote:

@ew: I used manual partitioning, but #! didn't recognize th Windows partition. It declared the HDD to be all unallocated.

Strange. This has never happened to me. Are you sure that you still got a windows-partition. To me it sounds like it has been deleted, and that`s why wbm can`t access it. Well, good luck. I hope that the windows-partition still is there, and that your second attempt will work for you.

yeop · 2013-12-28 16:06:38

Hi all, currently i have same problem with tomet, crunchbang didn't recognize any partition on my laptop, althought there is windows 7 x64 with 3 partition.

Crunchbang state that the hd is free 500gb, im using crunchbang 64 bit

output for lsblk -fmi

ew · 2013-12-28 16:30:20

What does "sudo blkid" or "sudo fdisk -l" tell you?

And in GParted, choose: View - Device Information

Does the column for partition table say msdos or gpt?

Last edited by ew (2013-12-28 16:38:34)

retf · 2013-12-28 16:37:37

@yeop

If could post the output as @ew indicated, that might be helpful...
Also in the terminal you opened from the #! install USB/CD see what the output of this is:

sudo mount -t ntfs /dev/sda2 /mnt

tomet · 2013-12-28 16:46:07

Unfortunately, I can't attempt another install right now because the live USB isn't working. I foramtted the one I used the first time to use clonezilla on it and when I now try to create another one using various methods (dd, unetbootin, win32diskimage), the boot always hangs at "Populating dev list". I don't know whether that might be another clue for the experts around here why the installation failed. If anyone has a suggestion other than trying again and again for how to create a working live usb stick, you're very welcome.

I should add that the original usb-stick (the one that failed to instal #! correctly) did work in a live session.

Thanks again for the tips and suggestion from all of you. I always find it great how nicely newbies are treated in linux communities smile

retf · 2013-12-28 16:53:20

tomet wrote:

live USB isn't working... the boot always hangs at "Populating dev list"

Were you able to verify the Crunchbang install image using the posted md5sums on the Download page?

It's possible that the iso is corrupted or not complete.

tomet · 2013-12-28 18:31:14

The md5 checksum is correct fo rmy download. When it worked the one time, I used that very same .iso file.

KrunchTime · 2013-12-28 20:42:36

@tomet...try reformatting the thumb drive as FAT32. Then try installing the CrunchBang ISO to the thumb drive again using the dd command.

tomet · 2013-12-28 21:38:01

I got a working usb stick now again. But bravely wink attempting to install #!, I ran into the same problem: It didn't see the windows partition when I was in manual partitioning. But it did see the partitions from the last install which Windows doesn't. I really want to install #! still, so please help me out!

KrunchTime · 2013-12-28 21:48:28

How exactly are you attempting to install CrunchBang? What partitions are you setting up, and where, in the manual partitioning process? Perhaps you should install CrunchBang entirely on the SSD and then attempt to move desired folders under CrunchBang to the HDD using GParted. Other than that, you've exhausted my grey matter at this point.

Have you attempted to search the Internet for a possible solution? I would try using the search terms install Linux on dual drives. Also consider posting your issue to the Linux Format forums; www.linuxformat.com/forums/

tomet · 2013-12-28 22:03:37

Of course I've searched the internet but I haven't found anything useful.

After going through all the "easy" installation steps (language, keyboard layout etc.) I clicked on "manual partitioning" when it asked me to partition the drive. Then I saw that it didn't see Window's partition as it was showing that my hard drive was entirely (apart from those partitions from the preious try which Widnows doesn't see) free space.

I then quit the installation to avoid a disaster like the first time.

Would it be a possibility to use clonezilla to clone the Windows partition to an external drive, then format the drive, install Crunchbang, create a new Windows partition in Windows and copy the clone from the external drive back on there?
Just an idea...

damo · 2013-12-28 22:17:38

tomet wrote:

Would it be a possibility to use clonezilla to clone the Windows partition to an external drive, then format the drive, install Crunchbang, create a new Windows partition in Windows and copy the clone from the external drive back on there?
Just an idea...

That would probably be my next step, except I use fsarchiver (you can run it from a live session if you need to - apt-get fsarchiver though)

fsarchiver savefs /mnt/backup/windoze.fsa /dev/<windoze partition>

Partition the troublesome drive and install crunchbang

fsarchiver restfs /mnt/backup/windoze.fsa dest=/dev/<new windoze partition>

sudo update-grub

Last edited by damo (2013-12-28 22:19:12)

yeop · 2013-12-28 23:50:57

"sudo blkid" or "sudo fdisk -l"

gparted error

if answer yes and no

sudo mount -t ntfs /dev/sda2 /mnt
5Oig35BfdQk02egOEL1YHKbdozc6wLqXvNMuc7G47zY=w1148-h861-no

Im not sure about this GPT things, not research yet, but then this laptop come with Windows 7 and I only reinstall using Windows 7,
isn't this GPT things related to Windows 8 right?

retf · 2013-12-29 00:33:19

Found this --- great answer --- probably will work for you...
http://superuser.com/questions/293339/g … en-but-why

ew · 2013-12-29 01:20:33

yeop wrote:

"sudo blkid" or "sudo fdisk -l"
https://lh4.googleusercontent.com/-5IY0 … 072730.jpg
gparted error
https://lh6.googleusercontent.com/-cNoQ … 072918.jpg
if answer yes and no
https://lh6.googleusercontent.com/-ccrL … 073142.jpg
sudo mount -t ntfs /dev/sda2 /mnt
https://lh6.googleusercontent.com/5Oig3 … 48-h861-no
Im not sure about this GPT things, not research yet, but then this laptop come with Windows 7 and I only reinstall using Windows 7,
isn't this GPT things related to Windows 8 right?

Nope. MS has used GPT for a while. UEFI and W8 depends on GPT, but GPT doesn`t depend on either W8 or EFI. The trick for installing a linux-distro to a gpt-disk, is to create a partion that is often called bios_grub. When you are partitioning, create a 1 MB partition anywhere, and choose USE AS "Reserved Bios Boot Area". That`s it. The rest of the install is like you`ve always done it.

But I`m not quite sure what is going on with you. It seems like it`s somehow corrupted. If at all possible, I would strongly recommend doing as follows: ( It will wipe your disk clean, so you have to reinstall windows)

There is two ways in which you can convert your disk from gpt to msdos. You can run a linux live-cd with gparted on it. Launch Gparted, click on Device, then "Create Partition Table". The default in GParted is to create a "msdos"-table, so when you do this and apply the changes, your disk will be empty and a msdos-table has been created, That means that the disk is converted from gpt to msdos, which is the preferred table for linux.

You can also use a tool in Windows that`s called Diskpart, which you can access by "shift+F10" when you get to the "Install Windows 7 screen", but let`s stick with the GParted way....

So I guess the procedure would be like this:

1. Launch GParted from a live-CD. Choose: Device-> Create Partition Table.... Then OK, apply the changes, and exit Gparted.

2. Put in your W7 install-media, and reboot into it. Install W7 like normal...
(remember to leave unallocated space for Crunchbang and other linux-distros you might want to install)

3. When you Windows install is finished, you are ready to install Crunchbang.
Boot from the #!-install-media, choose manual partitioning, create and set the partitions
and mountpoints, write the changes, and when you are asked where to put grub,
choose to write it to MBR.

4. When the install is finished, reboot, and hopefully you already have a entry for W7 in grub.
If not, then boot into Crunchbang, and run "sudo update-grub" from terminal. Reboot again,
and now you will have a W7 entry.

If you don`t have access to a W7-installation media, then you`ll find legal download links here:
http://www.overclock.net/t/1156654/sean … -ssds-hdds

PS. Download the version that is on your sticker. It will not work to install Ultimate, if you have Home Premium. You will not be able to activate the wrong version.

Last edited by ew (2013-12-29 01:22:47)

yeop · 2013-12-30 06:16:26

thanks for reply, really appreciate it smile
right now my laptop use for work, so may be on 1/1 or weekend ill reinstall/test

thanks again

edit!

My problem solved!! lol
im using fixparts run on windows, and then boot the usb drive BAAMM it detect the Windows/Parition !!

Thank you very much all! wink

Last edited by yeop (2014-01-01 08:58:38)

CrunchBang Linux

SEARCH

#1 2013-12-27 21:25:48

Crunchbang overwrote partition table => Windows messed up

#2 2013-12-27 22:26:03

Re: Crunchbang overwrote partition table => Windows messed up

#3 2013-12-27 23:18:15

Re: Crunchbang overwrote partition table => Windows messed up

#4 2013-12-27 23:58:52

Re: Crunchbang overwrote partition table => Windows messed up

#5 2013-12-28 00:28:52

Re: Crunchbang overwrote partition table => Windows messed up

#6 2013-12-28 02:11:21

Re: Crunchbang overwrote partition table => Windows messed up

#7 2013-12-28 09:59:52

Re: Crunchbang overwrote partition table => Windows messed up

#8 2013-12-28 10:44:37

Re: Crunchbang overwrote partition table => Windows messed up

#9 2013-12-28 12:21:56

Re: Crunchbang overwrote partition table => Windows messed up

#10 2013-12-28 13:24:06

Re: Crunchbang overwrote partition table => Windows messed up

#11 2013-12-28 16:06:38

Re: Crunchbang overwrote partition table => Windows messed up

#12 2013-12-28 16:30:20

Re: Crunchbang overwrote partition table => Windows messed up

#13 2013-12-28 16:37:37

Re: Crunchbang overwrote partition table => Windows messed up

#14 2013-12-28 16:46:07

Re: Crunchbang overwrote partition table => Windows messed up

#15 2013-12-28 16:53:20

Re: Crunchbang overwrote partition table => Windows messed up

#16 2013-12-28 18:31:14

Re: Crunchbang overwrote partition table => Windows messed up

#17 2013-12-28 20:42:36

Re: Crunchbang overwrote partition table => Windows messed up

#18 2013-12-28 21:38:01

Re: Crunchbang overwrote partition table => Windows messed up

#19 2013-12-28 21:48:28

Re: Crunchbang overwrote partition table => Windows messed up

#20 2013-12-28 22:03:37

Re: Crunchbang overwrote partition table => Windows messed up

#21 2013-12-28 22:17:38

Re: Crunchbang overwrote partition table => Windows messed up

#22 2013-12-28 23:50:57

Re: Crunchbang overwrote partition table => Windows messed up

#23 2013-12-29 00:33:19

Re: Crunchbang overwrote partition table => Windows messed up

#24 2013-12-29 01:20:33

Re: Crunchbang overwrote partition table => Windows messed up

#25 2013-12-30 06:16:26

Re: Crunchbang overwrote partition table => Windows messed up

Board footer