New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Is there anyone nearby the Hetzner Finlan data center who can help restore Raid
I am using the AX42 series server in the Hetzner Finland data center, where the main programs are running. However, the Hetzner platform replaced the motherboard of the server without my confirmation message, resulting in the loss of my Raid data (Raid 0 array composed of two hard drives). Currently, the server cannot be started. I would like to ask if there are any nearby users who can help restore the array. I am willing to pay for it.
Comments
Does the new board see both disks? was this soft or hard raid? have you tried just importing mdadm arrays?
The software RAID is used, and the motherboard can recognize the hard drive, but it cannot be recognized in the emergency rescue system.no tried just importing mdadm arrays.
I sense you're not using Debian. IIRC Gentoo has problems like this with hardware replacements.
You might boot from a live Debian image.
Are you saying that the rescue system I enabled is not Debian? Because Hetzner's default rescue system cannot select a specific release version. Because I haven't dealt with the relevant situation before, I dare not operate. Can you help me handle it? I can provide Hetzner backend and am willing to pay for processing.
If Debian is on the hard disks, the OS itself should work with the new motherboard. Gentoo instead creates a hardware-specific ramfs that may fail to boot when the hardware is replaced.
Do you have boot logs from IPMI, do you know what part of the boot fails to boot? At least describe your disks layout.
Thank you.
I originally used the debian system and then virtualized it using PVE. The Hetzner platform currently does not provide IPMI, so I cannot know the specific log situation.
I don't think hetzner do on site access for rented servers.
Ask them to attach a remote console / LARA to your server and then you can try and fix the problem. Data loss is a serious risk with raid0 so there's a very real chance your system is not recoverable.
Edit: https://docs.hetzner.com/robot/dedicated-server/maintainance/kvm-console/
I can pay a deposit to send out the hard drive or process it through Hetzner's Remote Console (KVM) backend.
Can you help solve it through KVM?
You can request a temporary IPMI through Robot support. They are usually setup within a hour.
If you haven't seen the output are you then sure it's the RAID that is the issue? Changing motherboard can result in the network interface changing names and thus have to be updated to regain networking.
You should also be able to check if the RAID indeed is broken by going into system rescue and using lsblk. That should show if the raid still is running.
If you check what the boot error is and post it in here, I and others might have seen it before and someone might be able to provide advice.
I would suggest that if you're going to do something as risky as raid0 you'll need to become comfortable fixing problems with it yourself.
I originally thought it was a network interface issue, so I applied for KVM. However, I saw that I couldn't enter the system and could see two hard drives in BIOS. But when I used the lsblk command in the emergency rescue system, I saw no hard drive information or RAID information, so I felt like it was a RAID problem. But I'm not sure if my judgment is accurate because I'm afraid of data loss due to misoperation.
Did your OS show in the boot options in bios? If yes, what error comes up when you boot from there?
There might be two boot entries, one for each hard drive. Try both, you might have invalid grub on one and valid grub on the other.
If neither succeed and you don't have a meaningful error message, boot in to the rescue system and check if the drives are present under /dev. You probably need to
mdadm --assemble --scanto try to start the array.I am now applying for the KVM backend and will send screenshots of the relevant situation. Thank you for your suggestion.
When I first created the server, I had configured data backup operations, but recently, due to the death of my grandmother, I was unable to check in a timely manner, resulting in this problem. I can only try my best to restore it.
I remember that there were no system boot entries when checking the BIOS initially, and no hard drive was found in the emergency rescue system. I have applied for the KVM backend, and I will check again after receiving the activation email. If it is true as you said that you did not see any hard drive information in the rescue system, can you use the (mdadm -- assembly -- scan) command to restore it?
Mdadm will only find the array if the drives are detected, so if the drives aren't present it's possible the drives weren't properly reconnected after your motherboard was replaced. It would be unusual but not impossible for both drives to be improperly connected after this.
If that is the case, i suggest asking hetzner to reseat the drives as a first measure.
The information currently viewed in the rescue system is as follows.
I have already attached some information. Could you please help me determine if the hard drive is not installed properly or if there are other issues?
I can't see any information provided from your KVM console.
I couldn't find any valid information in raritan kvm. You need me to provide that information, I'll go get it. (I'm sorry, I know nothing about this part)
I haven't got a lot of experience working with nvme drives yet (majority of my systems are SATA SSD or HDD).
I'd suggest asking hetzner to reseat the drives. The drives seem to be detected but can't initialise properly. So, perhaps reseating them will help.
The work order has been issued, let's see how Hetzner responds.