linux – mdadm raid gone after reboot due to super blocks disappearing on all but one drive

I have a raid 6 on /dev/md0 using /dev/sda /dev/sdb /dev/sdc /dev/sdd /dev/sde /dev/sdf.

I moved this raid to a different motherboard but kept the same non-raid card, and all drives including the OS which is on /dev/sdg.
I made sure to keep them all plugged in the same order on the non-raid card.

I plugged in a couple additional drives to copy some data to them.
One of those drives had windows installed on it and it managed to take boot precedence.
After it booted up I quickly rebooted fixed the boot order, only to find that my raid was gone.

After doing some digging the superblocks were gone from all drives except /dev/sdd which retains a little raid info.

After reading loads of posts about similar issues I ended up re-creating the raid with the command

mdadm --create /dev/md0 --level=6 --raid-devices=6 /dev/sda /dev/sdb /dev/sdc /dev/sdd /dev/sde /dev/sdf`

Magically I was able to then mount the drive and see my files still intact. I added the appropriate information to mdadm.conf removed the old line, then ran

update-initramfs -u

did a reboot and to my surprise the raid was gone again. Found that all the superblocks were gone again except for dev/sdd

it wouldn’t let me do a –zero-superblock due to it missing the superblock, but I was able to create the raid again, then performed a –zero-superblock on sda, sdb, sdc and re-created the raid again.

I did all the updating of mdadm.conf and update-initramfs -u, did a reboot and still the superblock keeps disappearing on all drives except sdd. I can’t seem to get my raid to stick and I can’t just wipe everything because I have at least 8 of the 16tb that I can’t afford to lose.

I’m hesitant to do –zero-superblock on sdd because that’s the only one that retains raid information, but maybe thats the one that really needs to be zeroed.

Please help! How can I get this raid to stick and not have to recreate it every time I reboot?

Thanks in advance.

OpenStack Instances not running after server reboot

After a power cut at our premise, I tried to start the instances at OpenStack, but none of them started up successfully. What could be the issue?


redmi – Stuck in ”Reboot recovery 3.0(Bootloop)” after changing dpi settings in developer options

I am stuck in a recovery mode which is like a bootloop, on my REDMI NOTE 9 PRO MAX. I tried to search for help on internet but i am not able to understand anything. I get 3 options on tge recovery page, 1]reboot:whoch ends in a bootloop. 2]WIPE DATA:i can’t wipe my data because I have importantstuff in it and i don’t have a back-up. 3]CONNECT WITH MIASSISTANT :i don’t know what that is.

Plz help

samsung – Certain apps lose all internet connectivity until reboot

I have put off asking the question for some time because I know it is vague and terrible to debug so I welcome your help refining the question as well as potential solutions.

A range of certain apps will report no internet connectivity and get stuck in that state no matter how good my WiFi and/or mobile data connection or if I force stop and/or clear their cache. So far:

  • facebook
  • instagram
  • onedrive
  • toktok

Normally only one of these at a time, sometimes two. I ignore them for a day or two and they never recover connectivity. Chrome is never affected (yet) and I still get push notifications for said apps.

I am technical and have pondered dodgy dns but apps get in this state on and off Wi-Fi which should mean different dns servers, not just a quirk on my home network. I don’t use a mobile VPN. I do have a work profile. My phone is a standard build Samsung S10 that behaved normally for over a year until recently.

Drives me mad because all advice out there is for fixing general/global connectivity as people always complain about that and turn it off and on again is a good solution for any single app getting into a funky state but this feels dumb, like the OS is caching/blocking/blacklisting something and I kinda wanna blame samsung or put on a tin hat and blame the government… yeah I am mocking myself now 🙂

So, any suggestions?

reboot and select proper boot device or insert boot media in selected boot device and press a key

Cuando estaba trabajando me ha salido este mensaje y he entrado a la BIOS para ver qué es lo que ha fallado, pero a diferencia de las fallas usuales en el sistema, el boot UEFI si está cargado entonces según lo que he buscado eso significaría que el disco duro está dañado .
No soy un entendido en esto por ello si alguien sabe si hay alguna solución le agradecería.
Adjunto las imágenes de la BIOS y lo demás que sale

introducir la descripción de la imagen aquí

introducir la descripción de la imagen aquí

introducir la descripción de la imagen aquí

4.4 kitkat – ADB Reboot Failed: -1 When using “adb reboot bootloader”. (Infocus M530)

I have an Old Infocus M530 running on Android 4.4.2 (KK) (Which i believe is made by Foxconn), I’ve been trying to make some Custom Recoveries for this device for quite some time and i always end up leaving it because of this problem that I’ve been having for about a year now. This device just doesn’t reboot into bootloader/fastboot.

I tried “adb reboot bootloader” and adb gives “reboot failed: -1”, tried “adb reboot fastboot” then the device just reboots normally back to system.

Also this device uses a program called “SUTL” to flash it’s stock firmware which i have used numerous times since I’ve bricked it by removing several apps via root. (I gained root via Kingoroot). The firmware image(archive) also can’t be extracted via 7Zip or similiar programs because it probably have some modified or custom header.

Tho this device works fine i can’t seem to get the bootloader unlocked on it. I can’t even pull images of partitions via adb shell it gives me “Permission denied” error.

So all i wanted to know at the moment is how can i unlock it’s bootloader so i can pull some system images. Thanks.

XAMPP MySQL service crash after reboot

Operating System: Window 10 64bit

When I run mysql, it immediately exits. I think this happens every 3 months. Is there any way to solve this?

12:10:51  (mysql)   Attempting to start MySQL app...
12:10:52  (mysql)   Status change detected: running
12:10:54  (mysql)   Status change detected: stopped
12:10:54  (mysql)   Error: MySQL shutdown unexpectedly.
12:10:54  (mysql)   This may be due to a blocked port, missing dependencies, 
12:10:54  (mysql)   improper privileges, a crash, or a shutdown by another method.
12:10:54  (mysql)   Press the Logs button to view error logs and check
12:10:54  (mysql)   the Windows Event Viewer for more clues
12:10:54  (mysql)   If you need more help, copy and post this
12:10:54  (mysql)   entire log window on the forums


InnoDB: using atomic writes.
(Note) InnoDB: Mutexes and rw_locks use Windows interlocked functions
(Note) InnoDB: Uses event mutexes
(Note) InnoDB: Compressed tables use zlib 1.2.11
(Note) InnoDB: Number of pools: 1
(Note) InnoDB: Using SSE2 crc32 instructions
(Note) InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
(Note) InnoDB: Completed initialization of buffer pool
(Note) InnoDB: 128 out of 128 rollback segments are active.
(Note) InnoDB: Creating shared tablespace for temporary tables
(Note) InnoDB: Setting file 'C:xamppmysqldataibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
(Note) InnoDB: File 'C:xamppmysqldataibtmp1' size is now 12 MB.
(Note) InnoDB: Waiting for purge to start
(Note) InnoDB: 10.4.17 started; log sequence number 44926144; transaction id 195314
(Note) InnoDB: Loading buffer pool(s) from C:xamppmysqldataib_buffer_pool
(Note) Plugin 'FEEDBACK' is disabled.
(Note) Server socket created on IP: '::'.```

shutdown – Why my server didn’t restart after reboot command?

I’m currently away (700Km) from my server, but did an apt upgrade through ssh and requested a reboot. The server stopped with a graceful shutdown but didn’t restart.

A friend looked at the server and it was simply stopped as if I did a shutdown. Pressing the power button started the server and it now runs without a problem.

Log file inspection shows nothing abnormal. No errors, or anything. I see the log entries of the graceful shutdown.

What could cause this behavior ? What should I look at to investigate the possible cause ? I usually don’t have a problem when rebooting this sever through ssh.

Since I’m still away from home until the end of the week I can retest it.

debian – Nftables “Error: Interface does not exist” after reboot

at using nftables on a new virtual machine (Debian 10) I installed and configured nftables as automatic service (systemd). I use also LXC and use an additional interface (lxcbr0).

I recognized the problem that the nftables service does not start successfully after reboot. The error: /etc/nftables.conf:56:32-39: Error: Interface does not exist

It seems that the interface get only up after the nftables service startup:
Startup date of nftables (log output):

Apr 05 11:41:23 WEB01 systemd(1): Starting nftables...

Startup date of the interface:

Apr 05 11:41:25 WEB01 ifup(397): Waiting for lxcbr0 to get ready

–> 2 second delay between the startups

Is there a general solution for this or a common work around? On the wiki of nftables I did not find something like that.

Thanks in advance

USB drive disconnects by itself and doesn’t reconnect until I reboot (2015 Macbook Air)

I have a USB drive which randomly disconnects. I would think that there is some hardware fault with the drive itself, but if I unplug it and plug it back, it doesn’t reconnect unless I just rebooted the computer, which gives me hope for a software issue.

I don’t know whether it’s relevant, but currently I’m trying to download something heavy directly onto the USB drive, and that’s when the disconnects happen. I’m not sure whether they would happen either way though.

Ideas on how to solve this?