Posts made by Romo

Have you reseated the device by removing it from it's slot or connector and then reinserting it to make sure it is properly connected?

@scottalanmiller said:

Oh nice, do they have an RHCE too?

They do have a short series for RHCE - part 1

@scottalanmiller said:

I wonder if we can do some sort of ML study group.

Yes it would be really cool

@scottalanmiller could enabling write-intent-bitmaps help with the sudden power loss in a mdadm array? If enabled they would probably cause a big impact in performance but could they help?

@Jason said:

@scottalanmiller said:

I live in the third world too, all remote controlled AC here, too. In the US, that's unheard of (at least to me.)

Most other countries make more use of using Mini-split HVAC units. Here in the US Central HVAC is more common even if it uses more energy (and you have to heat/cool everything instead of just certain rooms like you can with mini-splits, and no duct to lose the temperature in a mini split)

Quite common in Mexico as well, we are using Mirage currently.

@DustinB3403 said:

@Romo It's outside of the norm for XenCenter.

Even if it's benign.

Yes indeed.

@DustinB3403 Not so sure about the entry on fstab, I don't have the entry in my setup and xen properly automounts it

Does xencenter see the storage?

Yes, seems ok. Reboot and try to check the status of the array once again

Don't need the metadata and name again after the devices

@DustinB3403 said:

ARRAY /dev/md0 level=raid10 num-devices=4 metadata=1.2 name=eaglexen-baby:0 UUID=5bd9375b:2166352e:622be934:4b65a7ea
devices=/dev/sdb,/dev/sdc,/dev/sdd,/dev/sde metadata=1.2 name=eaglexen-baby:0

ARRAY /dev/md0 level=raid10 num-devices=4 metadata=1.2 name=eaglexen-baby:0 UUID=5bd9375b:2166352e:622be934:4b65a7ea
devices=/dev/sdb,/dev/sdc,/dev/sdd,/dev/sde

Quite strange that the first two entries don't have a UUID set, mdadm needs the UUID set.

We could try to manually edit the file, adding the UUID from the last entry into the first entry, and then removing entries 2 and 3.

@DustinB3403 can you please show us the output of your mdadm.conf file, last time I believe it was cut off because the UUID's dont show.

@DustinB3403
ls /dev/ | grep md

What is the ouput for:
cat /dev/md/md-device-map

You can't mount /dev/md0, because according to the mdadm --examine --scan ouput, the array, is at /dev/md/0

Your could run

mdadm --examine --scan >> /etc/mdadm/mdadm.conf

To recreate the conf and see if it fixes the problem. /dev/md/0 should be a symbolic link to /dev/md0

@DustinB3403 what is in your mdadm.conf?

@DustinB3403 can you run

mdadm --examine --scan

Lost the whole array? That's strange that would imply something went really wrong. The entry added in fstab whould only cause the os to automount the array, nothing there should cause the array itself to get wiped.

What is the current status of your array?
mdadm --detail /dev/md0
cat /proc/mdstat

@BRRABill https://www.google.com.mx/webhp?sourceid=chrome-instant&ion=1&espv=2&ie=UTF-8#safe=off&q=smbitjournal.com:+raid

Posts from @scottalanmiller about raid