Date: Tue, 22 Nov 2016 00:09:38 -0500 From: Mark Moellering <markmoellering@psyberation.com> To: freebsd-questions@freebsd.org, info@classcreator.com Subject: replacing bootloader wipes disk? Message-ID: <CAA0uU3UNzc89tGKQs658=y1N_hb1705rWYHBP1gGt8udUD_K0Q@mail.gmail.com>
next in thread | raw e-mail | index | archive | help
Everyone, I have an odd situation. I am helping a small company out, after my regular work hours, with their email server, which is on an older version FreeBSD (8.X or possibly 9.0) I got a call a few days ago, saying the server wouldn't boot. The server is at a hosting company but I was able to connect over a software KVM. They had a new 11.0 live disk to boot from, which I used to run fsck on each partition (it is running the old UFS2 partitions) and clean all the drives. When everything was finished and all drives were marked clean, I tried to boot from hard drive, it came up with GRUB and was trying to boot into linux , with the error "Can't find EXT3 Superblock". The error made sense but I had no idea why it was using GRUB, so I said there was something wrong with the bootloader. The next day (today), I was forwarded an email saying they ran the following commands to try and replace the bootloader. fdisk -B -b /boot/boot0 /dev/ada0 and boot0cfg -B ada0 When I checked the drive this evening, it appeared to be completely blank, except for a bootloader. I am not good enough with fdisk to tell but could these commands have erased the drive? They don't look like they would but fdisk is not something I use much... Any help is greatly appreciated I am hoping they put in a new drive but since I don't work on this machine until after hours, I am not talking to the tech's working on it during the day. Again, all help is greatly appreciated. Thanks in advance Mark Moellering
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAA0uU3UNzc89tGKQs658=y1N_hb1705rWYHBP1gGt8udUD_K0Q>