Hi there,
There was a power outage two days ago when I wasn't home.
The NAS is a Western Digital My Cloud Home running Debian 11+OMV 6 as per fox_exe's instructions (followed in 2021). Off the top of my head, it simply used the original Android partitioning and replaced essential bits with Debian's, which was acceptable at the time but by no means a "clean" install.
Even though the NAS was on a UPS, I believe the cut was long enough to eventually deplete the battery and the NAS suffered a hard shutdown, although there was no active network transfer at the time, which should make things repairable.
It would repeatedly spin down then up afterwards, along with a typical LED-light pattern and recognized it just failed to boot properly.
Now I have connected a serial console and can see many issues right before it reboots:
- Can't find partitions
- Now unsure why a HDD partition would be formatted as f2fs
I tried to interrupt boot process, but of course it didn't work as UBoot apparently has it disabled
[ 7.950447] sd 0:0:0:0: [sda] 11721045168 512-byte logical blocks: (6.00 TB/5.46 TiB)
[ 7.958493] sd 0:0:0:0: [sda] 4096-byte physical blocks
[ 7.963982] sd 0:0:0:0: [sda] Write Protect is off
[ 7.968960] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 8.030575] sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9 sda10 sda11 sda12 sda13 sda14 sda15 sda16 sda17 sda18 sda19 sda20 sda21
[ 8.046239] sd 0:0:0:0: [sda] Attached SCSI disk
[ 8.164191] UDF-fs: warning (device sda19): udf_fill_super: No partition found (2)
[ 8.172167] Mount JFS Failure: -22
[ 8.189738] NILFS (sda19): couldn't find nilfs on the device
[ 8.196507] (mount,1554,2):ocfs2_fill_super:1023 ERROR: superblock probe failed!
[ 8.204100] (mount,1554,2):ocfs2_fill_super:1217 ERROR: status = -22
[ 8.210832] gfs2: gfs2 mount does not exist
[ 8.215282] F2FS-fs (sda19): Magic Mismatch, valid(0xf2f52010) - read(0x0)
[ 8.222361] F2FS-fs (sda19): Can't find valid F2FS filesystem in 1th superblock
[ 8.229994] F2FS-fs (sda19): Magic Mismatch, valid(0xf2f52010) - read(0x1906e0)
[ 8.237494] F2FS-fs (sda19): Can't find valid F2FS filesystem in 2th superblock
[ 8.245001] F2FS-fs (sda19): Magic Mismatch, valid(0xf2f52010) - read(0x0)
[ 8.252054] F2FS-fs (sda19): Can't find valid F2FS filesystem in 1th superblock
[ 8.259549] F2FS-fs (sda19): Magic Mismatch, valid(0xf2f52010) - read(0x1906e0)
[ 8.267043] F2FS-fs (sda19): Can't find valid F2FS filesystem in 2th superblock
mount: mounting /dev/sda19 on /mnt failed: Invalid argument
BusyBox v1.21.1 (2013-07-08 10:26:30 CDT) multi-call binary.
Usage: switch_root [-c /dev/console] NEW_ROOT NEW_INIT [ARGS]
Free initramfs and switch to another root fs:
chroot to NEW_ROOT, delete all in /, move NEW_ROOT to /,
execute NEW_INIT. PID must be 1. NEW_ROOT must be a mountpoint.
-c DEV Reopen stdio to DEV after switch
[ 8.325937] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000100
[ 8.325937]
[ 8.335299] CPU: 1 PID: 1 Comm: switch_root Not tainted 4.9.266 #2
[ 8.341627] Hardware name: Realtek RTD1295 Giraffe Board (DT)
[ 8.347511] Call trace:
[ 8.350025] [<ffffff8008289534>] dump_backtrace+0x0/0x1ec
[ 8.355556] [<ffffff8008289734>] show_stack+0x14/0x1c
[ 8.360732] [<ffffff8008ea4d1c>] dump_stack+0x8c/0xb4
[ 8.365908] [<ffffff8008e9b418>] panic+0x130/0x278
[ 8.370818] [<ffffff80082bd698>] do_exit+0x628/0x854
[ 8.375903] [<ffffff80082bd944>] do_group_exit+0x50/0xa0
[ 8.381344] [<ffffff80082bd9a4>] __wake_up_parent+0x0/0x28
[ 8.386962] [<ffffff8008283940>] el0_svc_naked+0x34/0x38
[ 8.392400] SMP: stopping secondary CPUs
[ 8.396421] Kernel Offset: disabled
[ 8.399993] Memory Limit: none
[ 8.411609] Rebooting in 5 seconds..
[ 13.415464] rtk-reboot 98007680.reboot: Restarting...
Display More
How do I repair the partition map, mound sda19 (mounted on /), all without killing sda21, the data partition?