• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Invalid partition table on my freebsd server.... recovery options, anyone?

skyking

skyking

Lifer
I rebooted after making no changes, just rearranging things physically. I had not added or changed partitions since last reboot, but now I get that message in the BIOS, right before the bootloader would normally get going. . Is there any chance I can recover this drive, and how would you go about it?
 
Sounds to me like it's probably just a drive gone bad, rather than an actual partition table problem. But if you have backups of your disklabel, you could try fdisk'ing a new partition table, and restoring the original disklabel. I have a feeling that's not the issue, though...
 
I think I am sol as far as remembering the disklabel. Of course, I do not have a backup😀
I will try making another build on another disk, and see if I can mount it there and recover anything. Any other good ideas, or is that my likely best option?
 
Could it be that your cord or something is messed up or it thinks that maybe the original master is now a slave and vesa versa? or something like that?

Seems like it would give that error it is trying to access the partition, or maybe a non-existant partition... could be just confused.
 
Oh as far as a fix. If FreeBSD is like Linux. I would boot up the install CD and get a boot prompt. Mount the disk and re-run to bootloader.

May have to use chroot to make your root partition your "virtual root", so that even you boot up with your CDROM and that or a ramdisk is real "root" you can cd to were the HD is mounted and run chroot and make that your operating enviroment...
 
D'oh! I totally read through "rearranging things physically". Thanks for catching me being a dumbass, Drag. What exactly did you rearrange? Probably you just need to adjust the BIOS settings to get at least the bootloader. Might need to reinstall bootblocks or something similar after that, depending on what was changed.
 
No, I meant moved the box. No internal mucking about inside the case or anything. BIOS still auto-detects the drive as secondary master ( primary channel being long dead, LOL! ), it just cant parse that partition table as is.
Edit: I always do a net install using the boot floppies. I will look at the /stand/sysinstall menu and see what I can do there. Thanks for the replies!
 
Still coulda knocked a cord lose or something ... I know very weird things happend when you have a plug or something that is only partially connected, like to high a resistance or a vibration of a fan or footsteps or something small causing it to disconnect and reconnect randomly. Also dust is a issue, If you haven't cleaned out a case for a long time dust bunnies can fall down and cause shorts and stuff.

I know its a long shot, but it's worth checking out.
 
OK, I have done it now. I managed to lose my usr slice, trying to mount it on another running machine. I have some of the config files, but mostly I have that hosed feeling. I recovered some data on another storage slice, but I lost all the docs in my usr, as well as the configs for samba, etc. ARGH!
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top