Image 1 — Can't login to maya app for no reason
Image 2 — Can't login to maya app for no reason
▲ 4 r/MayaPh+1 crossposts

Can't login to maya app for no reason

I haven't opened my Maya app for a while since I decided to use another bank as my daily/main.

When I tried opening it again now, all I'm getting is this even after multiple reinstalls and clearing of data.

How to resolve this issue?

u/BarHuge9034 — 2 days ago
▲ 1 r/Cebu

Naa paba mga company nangita ug Interns/OJT for Devs ron?

Medyo dugay mn ko naka pangita sugod ug ma applyan nya karon murag wala naman kaayo koy makit-an. Naa pud uban kay dili align sa ako path. Basin naa mo ma recommend or nahibaw an.

reddit.com
u/BarHuge9034 — 2 months ago
▲ 16 r/Fedora

No hope? Fedora BTRFS issue...

Is there no hope for this? I spent almost a day straight debugging it.

I powered off my laptop because I had to go to school. When I turned it on at school, it was stuck at the boot animation for 30 minutes. I tried different solutions that I could find online and also resorted to using LLMS with deep research (Gemini 3.5 Flash Extended Thinking + Web Search, Perplexity Pro Claude 4.6 Sonnet Thinking) but still made no progress.

Changing grub config, bypass, live usb, and btrfs restore. None worked... Maybe I'm just venting out, it's been almost a day straight trying to fix this. I guess I'll have to forget about my files and unbacked-up work there.

Issue: Fedora’s Btrfs root on /dev/nvme0n1p6 is broken because Btrfs thinks a second device is missing, so the chunk root cannot be read and the filesystem will not mount.

> I only have 1 nvme ssd dual booting windows and fedora

Device: Lenovo LOQ 15IAX9E Essential i5-12450HX, RTX3050

Failed solutions tried:

GRUB/kernel boot bypass attempts, including init=/bin/bash, rd.break, and NVMe power-saving tweaks.

Power drain / BIOS checks for Intel VMD and storage passthrough.

Failed live usb solution:

btrfs filesystem show.

mount -o degraded,rw /dev/nvme0n1p6 /mnt/recovery.

mount -o degraded,rw,rescue=nologreplay /dev/nvme0n1p6 /mnt/recovery.

btrfs rescue super-recover -v /dev/nvme0n1p6.

btrfs rescue chunk-recover -v -y /dev/nvme0n1p6.

btrfs restore -iv /dev/nvme0n1p6 /mnt/windows/fedora_recovery.

btrfs restore -l /dev/nvme0n1p6.

btrfs restore -iv -u 0 /dev/nvme0n1p6 /mnt/windows/fedora_recovery.

btrfs restore -iv -u 1 /dev/nvme0n1p6 /mnt/windows/fedora_recovery.

btrfs restore -iv -u 2 /dev/nvme0n1p6 /mnt/windows/fedora_recovery.

btrfs-find-root -g 760746 -l 0 /dev/nvme0n1p6.

btrfs-find-root -a /dev/nvme0n1p6. �

Short version: I tried mounting, Btrfs rescue tools, restore tools, and root-finding tools, but every path still hits device 2 is missing / cannot read chunk root.

I guess I just have skill issues.

u/BarHuge9034 — 3 months ago