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.
Raid-1 Failure or incorrect configuration?
Hello,
I've been trying to fix this problem since hour but nothing is working.
I recently did yum update and rebooted the server. Server never came back online. After logging to KVM console, it shows drive related error.
It doesn't seem to be a problem with the update nor the kernel. It is halting on a drive error
Warning: /dev/md/02 does not exists
Server was delivered with 2x250 GB SSD in raid1 and additional 2x 2TB SSD was purchased.
dracut: cat /etc/fstab
No such file or directory
On exiting shell, it stucks at
a start job is running for /dev/md/2 device
If nothing works, I'll have to pull so much of data from backup server which will take a lot lot of time.
Comments
@WSS @raindog308 @Francisco and other ninjaz
You should do mdadm --examine /dev/sdxx that way you can figure out which drives belong to which membership. Once you know that (compare UUID's) you can just do:
mdadm --assemble /dev/mdX DRIVES
Francisco
You'll also want to replace your /etc/mdadm/mdadm.conf (or /etc/mdadm.conf) to make sure it has things listed properly. You'll also want to update your kernel initramfs to make sure it's assembling things.
Francisco
http://storage2.static.itmages.com/i/18/0110/h_1515547751_4627867_c5d89201c4.png
However,
Only md3 is working but if I do
http://storage7.static.itmages.com/i/18/0110/h_1515547993_6360429_6a63674189.png
DO NOT RUN CREATE, it'll wipe your data.
You want to use assemble.
mdadm --assemble /dev/md2 /dev/sda3 /dev/sdb3
Francisco
Do an fdisk -l to see which drives are showing up, or if/all..
I was pretty cautious while running those command to see if they are mounted.
Even then,
http://storage2.static.itmages.com/i/18/0110/h_1515548258_7323543_6a111c2eeb.png
Last time I used, fdisk was not available. I'll retry after reset tho.
In the meantime, @Clouvider, Please deliver the SSD soon, if this server fails, I could have a backup! #106783
I give up. I've retyped the same thing different ways- several times, and clodfart keeps blocking me. Time to go make dinner and chill for a bit. Will check back later.
Pastebin, don't give up on LET neither me. This small update took one day of my sleep. Sooner I find a solution, the sooner I can sleep.
cat /etc/fstab: No such file or directory
This actually sucks, there's no fstab! This probably going to be the tedious day of my life.
Not if your drives are there. The missing mdadm.conf is what's fucking you.
@WSS looks fine to me
http://storage9.static.itmages.com/i/18/0110/h_1515550260_1933780_c8e9f78b94.png
That does look OK. what's /proc/mdstat say?
@WSS
There were supposed to be 2 raid-1
http://storage1.static.itmages.com/i/18/0110/h_1515550582_2025923_41d9b9f1ab.png
I just almost felt asleep on my chair
After doing,
mdadm --assemble /dev/md2 /dev/sda3 /dev/sdb3It seems to be fixed, there are both array raids now, do I need to make this permanent?Need to recreate the mdadm.conf I think, it's messed up on that file
The others don't seem to exist, according to md..
after everything,
update-initramfs: command not found
fsck this, am going to sleep!
I recommend you backup your mdadm.conf and make a new file by doing...
mdadm --examine --scan > /etc/mdadm/mdadm.conf
Francisco