RAIDar Corrupt Root RN31400 Could Not Mount Root Raid d(isk)

[styks1987]

LCD SCREEN: Could Not Mount Root Raid d(isk)

RAIDar Status: Corrupt Root 

Issue after power loss.

I do not want to reset to factory as I have data I do not want to lose.

I have tried:

- OS Reinstall (stalls with  "verifying fs")

- Flash recovery (stalls at "Boot via external usb")

I can access the busybox via telnet. 

I can mount my data drive via:

# echo DEVICE partitions > /etc/mdadm.conf
# mdadm --examine --scan >> /etc/mdadm.conf
# mdadm --assemble --scan
message: mdadm: /dev/md/data-0 has been started with 4 drives.
# mount /dev/md/data-0 /mnt

I can see my data and it appears to all be there.

I am comfortable at the command line. I cannot find any solid resources for how to fix this and I don't feel like paying $150 for tier 2 tech support. 

Any assistance would be appreciated. I don't mind sending beer money if your solution helps.

[mdgm-ntgr]

From what you've posted the problem is with the 4GB root volume.

This is not a situation that would suggest the use of USB Boot Recovery.

USB Boot Recovery is for some specific extreme situations e.g. where the boot menu won't come up even if you power down and remove all disks first (note some boot menu options do rely on disks being installed, but you can bring up the menu still with the disks removed). USB Boot Recovery is very rarely the answer to a problem.

[styks1987]

Yes, I believe this is true. It looks totally corrupted. It cannot even be mounted. Any way to reinstall the os from scratch?

# /bin/start_raids 
mdadm: /dev/md/0 has been started with 4 drives.
mdadm: /dev/md/1 has been started with 4 drives.
mdadm: /dev/md/data-0 has been started with 4 drives.
Imported RAID data-0
Updating fstab entry: 7c6ea5aa:data => 7c6ea5ab:data
mount: mounting LABEL=7c6ea5ab:data on /data failed: No such file or directory
# mount /dev/md0 /sysroot
mount: mounting /dev/md0 on /sysroot failed: Input/output error

[styks1987]

Thanks for the solution. Just posting here in case someone else needs this info.

dmesg log showed that my btrfs filesystem log was off. He zeroed out my log (which is really dangerous) but because it was only off by 1 it was not as dangerous. Also, this was on the os partition. 

I'm going to go find a battery backup....