Forum Replies Created
You can set up a RAID with NVMe drives in slots 3 and 4 on the MAG Z790 Tomahawk MAX WiFi motherboard without affecting your Windows 11 installation on slot 1, as long as the OS drive is not included in the RAID.
The motherboard supports Intel RST (Rapid Storage Technology) RAID for NVMe drives. You can create the RAID array through the BIOS or using the Intel RST utility in Windows. Check the motherboard manual for lane sharing, since some NVMe slots share PCIe lanes with SATA ports, which could disable certain ports if not configured correctly.
With two NVMe drives, you can choose:
RAID 0 (striping): Faster performance, no redundancy. If one drive fails, all data is lost.
RAID 1 (mirroring): Data is duplicated on both drives. One drive can fail without losing data.
SATA drives can also be configured in RAID using Intel RST. The same options apply depending on the number of drives.
Because your OS drive is separate, creating a RAID on slots 3 and 4 will not affect Windows 11.
Thanks everyone. Gonna give the full firmware flash a try tonight. Hoping it boots at least once so I can recover my stuff. Appreciate all the tips
Just adding this..don’t keep it on that error screen for too long, it can cause AMOLED burn-in. Try forcing a reboot every few minutes while you prep your files for flashing.
Smart move. There’s PC-based Android data recovery software that works once the phone gets detected again — it can scan internal storage and help you save photos, videos, etc. before you mess with system files again.
Got it, I’ll try that battery trick. If I manage to bring it back, I’ll use recovery software to pull my data before I flash anything else again.
I’ve had this exact thing happen on an A7 after a failed TWRP flash. What worked for me: disconnect battery for 5 minutes (if you can open the phone safely), reconnect, then immediately boot to download mode and re-flash full firmware.
If you’ve already soft-bricked it and the PC still recognizes it under Odin mode, that’s a good sign. You can still get data back later. But if the flash fails completely and it doesn’t get detected, you’ll need to look into data recovery software that can scan bricked phones once they’re at least partially functional again.
Yeah, don’t flash just the recovery next time. Re-flash BL + AP + CP + CSC (not HOME_CSC though, that one wipes). If you’re lucky, it’ll boot back normally and your data should still be intact.
If it’s looping back to that error screen, it’s probably a corrupted bootloader or recovery partition. You’ll need to re-flash the full stock firmware through Odin again — not just TWRP.
You can get the official firmware from SamMobile or Frija Tool, depending on your region. Just make sure you match your phone’s model number exactly.
Tried that combo, but it just goes back to the same screen again after reboot. I can’t reach recovery or download mode.
Classic Odin soft brick situation. You basically interrupted the firmware flash or used a mismatched TWRP image. The phone isn’t dead though..it’s just in a fail safe state.
Try holding Power + Volume Down for around 10 seconds; it should force a restart. Then immediately go into Download Mode (Power + Vol Down + Bixby).
Hey everyone,
So I was trying to install TWRP on my Samsung Galaxy A15 using Odin. Everything seemed fine at first, but after flashing, my phone rebooted and got stuck on this weird screen that says:
“An error has occurred while updating the software.”
It’s been like that for hours now — it won’t power off, won’t go into recovery, and I’m scared it’s gonna get screen burn if it stays like this much longer. Holding Power + Volume Down + Bixby isn’t helping either.
Any idea how to fix this? And more importantly, is there any way to save my data? I had tons of photos and notes that weren’t backed up 😩
The SSD issues reported with Windows 11 version 24H2 appear to be limited and not widespread. Microsoft and SSD maker Phison tested affected drives and found no evidence that the update was causing failures. The few reports that did appear are likely due to defective hardware rather than the update itself. While there’s no official fix, it’s recommended to keep SSD firmware and drivers updated, monitor announcements from Microsoft or the SSD manufacturer, and take precautions like pausing updates on critical systems or avoiding large file transfers on nearly full drives. Overall, most users are not affected.
On a clean Windows 11 install, the “Bad image” error when running the Dropbox installer usually points to a corrupted installer, missing or damaged system files, or interference from security software. Make sure the installer is downloaded directly from Dropbox and fully intact. Run sfc /scannow to check for and repair system files, and install any pending Windows updates. Temporarily disable antivirus or Windows Defender, as these can block installers. Use the Dropbox offline installer that matches your system’s architecture (32-bit or 64-bit) and try running it in Windows 10 compatibility mode. If the problem persists, repairing Windows with DISM /Online /Cleanup-Image /RestoreHealth can resolve deeper system issues.
For your HP 800 G4 Mini, the two NVMe drives can be set up in a RAID 1 for Docker applications with MySQL. The simplest and most reliable option is mdadm with Ext4, which gives stable RAID 1 redundancy, predictable database performance, and easy monitoring with LibreNMS. A ZFS mirror is also an option if you want checksums and snapshots, but it requires tuning for database performance and uses more memory. BTRFS RAID 1 is less suitable for write-heavy databases due to potential fragmentation and slower writes. Using two identical NVMe drives is recommended for consistent performance. Drive failure alerts can be handled through mdadm or ZFS and integrated with LibreNMS. Overall, mdadm + Ext4 is the straightforward choice, while ZFS adds extra protection with more complexity.