[Ilugc] Urgent help needed regarding Debian 5.0 release 0 server
- From: knura9@xxxxxxxxx (Arun Khan)
- Date: Thu Aug 5 10:23:46 2010
On Wed, Aug 4, 2010 at 11:17 PM, Zico <mailzico@xxxxxxxxx> wrote:
Hi, One of my server crashed last night! It was a hardware crash,
motherboard burned! Today, my IBM local vendor changed the motherboard and
now, my Debian 5.0 release 0 is not booting! Here, the point is, I had
postgresql and mysql database there and those had lot of data. Now, I really
need to get back those data and I do not want to change my any configuration
of that server. Say, I had postgresql 8.3 installed, I need exactly
postgresql 8.3 now too. Is it possible to bring back that server with it`s
previous data?
You have *not* posted any error message (if any).
Have you tried to boot it with the latest version of Fedora/Ubuntu
LiveCD? If so what are the symptoms?
I would suggest that inquire from vendor if replacement motherboard is
100% one-to-one at chip level with the fried motherboard.
If the above is not the case then your installed Debian is not booting
because most likely the initrd image does not have the proper drivers
installed for the new motherboard installed by your vendor.
OR your GRUB and /etc/fstab has stuff like UUID="blahblah" Before
spinning your wheels I would suggest that you boot the system with a
systemrescuecd and change the UUID lines to appropriate /dev/sd[A][B]
device mappings and ensure /boot/grub/device.map is consistent with
/dev/sd[A][B] mappings.
If the above does not solve your problem then - you can try the
following steps to make yourself an initrd file compatible to your
"new" motherboard (hope you have access to a spare disk - even a 20GB
should be OK)
1. Use spare disk as primary aka /dev/sda to install a minimal Debian
of the version you have on the "production" system. Backup important
PG and MySQL dirs to another disk and make production disk as /dev/sdb
(eg.)
2. Copy the initrd image to your "production" disk /dev/sdb in this example.
3. Make production disk primary
4. Boot the system and hopefully it should solve your dilemma without
having to do a full re-install of Debian and copying your PG and MySQL
data
I would suggest that you make a backup of your data to a safe
location before embarking on any "surgery" activity.
-- Arun Khan
PS If all of the above fails - your last resort would be a fresh
install, config, and copy of files as others have suggested.
Other related posts:
