Topic: SME RESCUE - how can I access the machine?

[SchulzStefan]

A few weeks ago, I had a crash of one harddisk. The other disk was (still is) fine, but not bootable. I opened a bug. Right now, I would like to post the logs to the bugtracker team.

I searched the forum, but I didn't find a HOW-TO or a hint, that works for me. So, is there anybody with a step by step procedure, that allows in the RESCUE mode, to access via ssh or ftp the machine?

Thx in advance for any help.

stefan

[RvLardin]

You don't give enough information for us.

1) You're system is still running -it was a raid0- and you want to rebuild the array ? was a soft or hard raid ?

2) You have no system at all running on your machine and you want to make a new system and recover the data that were on the second HD ?

3) Do you have physical access to the machine ?

...

[SchulzStefan]

I'm sorry for the information leak:

1. ) System hangs with a grub error and cannot be booted. Originally there have been two identical hard-disks in the machine.
2.) Booting the sme install-disk with sme rescue.
3.) Filesystem is completly mounted under /mnt/sysimage.
4.) Files in directories can be viewed/accessed with less/cp/mv/rm.
5.) IP-adress can be given manually or via dhcp.
6.) If entering IP-adress manually, the machine can be pinged from the network.
7.) Machine can be accessed on the console.
8.) Machine cannot be accessed via putty or winscp or veeam.
9.) I don't want to recover the filesystem or the system. Why should I? I'm able to access the files. No need to recover, I build a new server and the backup worked fine.
10.) I do want to copy the LOGS over the network on an other sme-server or on a win-client.
11.) Why? I want to send the logs to bugzilla. Maybe it helps to recover the grub-error.

More information needed?

stefan

[RvLardin]

More information needed?

Thks.

What was the "grub error message" ?

2 solutions :
Either you want to repair your crashed system. For the moment, with the informations we have, the most credible situation is that you have used a raid mirroring system. One of you disk get out of the raid and you can't boot on it. If it's that, you can try to boot on a single disk, unplugging the other. You just have to find wich one is the more accurate.

Either you are in the way to make a new install on a new hardware. If ssh not available in "rescue" mode, you can try, from the "rescue" machine scp or rsynch to migrate your datas to the new one.

A+,
RV.

[CharlieBrady]

1. ) System hangs with a grub error and cannot be booted. Originally there have been two identical hard-disks in the machine.
2.) Booting the sme install-disk with sme rescue.
3.) Filesystem is completly mounted under /mnt/sysimage.
...
10.) I do want to copy the LOGS over the network on an other sme-server or on a win-client.

chroot /mnt/sysimage
ifup eth0
ping a.b.c.d # your other server - check it's reachable
scp /var/log/messages.* root@a.b.c.d:/root

You will need to enable ssh with password access allowed to root on the other server first.

[SchulzStefan]

Thank you for your reply, RV

What was the "grub error message" ?

grub grub grub grub grub grub ............. on the whole screen.

For the moment, with the informations we have, the most credible situation is that you have used a raid mirroring system.

correct.

One of you disk get out of the raid and you can't boot on it.

the disk crashed.

If it's that, you can try to boot on a single disk, unplugging the other. You just have to find wich one is the more accurate.

the other is not bootable because of the grub-error.

Either you are in the way to make a new install on a new hardware. If ssh not available in "rescue" mode, you can try, from the "rescue" machine scp or rsynch to migrate your datas to the new one.

I build a new server with new hardware. Did a clean installation from the installation-disk and used my data-backup. The box is running stable, no problems at all.


Charlie,

chroot /mnt/sysimage
ifup eth0
ping a.b.c.d # your other server - check it's reachable
scp /var/log/messages.* root@a.b.c.d:/root

on Monday I'll try your suggestions. I'll let you know, if it works.

stefan

[SchulzStefan]

Charlie,

worked.

I created (of all messages) a rar-archiv an send it to the bugtracker.

stefan