While I was away on holidays, my home suffered a power outage. When I came home and tried to access my GoFlexHome (that I usually turn off when going away), I couldn't. The NC Console showed me this:
I tried recreating initrd.img-5.3.2-kirkwood-tld-1 and uInitrd several times and came up with the same result. I haven't changed my u-boot env variables in months and a checked the ones mentioned in the install-a-new-kernel-instructions looked good. I don't know what to do next. Is what being tagged as bad uInitrd? Suggestions?
sparks
Found bootable drive on usb 0 Bootargs = console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data) init=/bin/systemd loading uImage ... 5102272 bytes read in 1603 ms (3 MiB/s) loading uInitrd ... 12593467 bytes read in 2124 ms (5.7 MiB/s) loading DTB /boot/dts/kirkwood-goflexhome.dtb ... 10249 bytes read in 1138 ms (8.8 KiB/s) ## Booting kernel from Legacy Image at 00800000 ... Image Name: Linux-5.3.2-kirkwood-tld-1 Created: 2019-12-01 15:21:21 UTC Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 5102208 Bytes = 4.9 MiB Load Address: 00008000 Entry Point: 00008000 Verifying Checksum ... OK ## Loading init Ramdisk from Legacy Image at 01100000 ... Image Name: initramfs-5.3.2-kirkwood-tld-1 Created: 2019-12-01 15:22:11 UTC Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 12593403 Bytes = 12 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... Bad Data CRC Ramdisk image is corrupt or invalid NAND read: device 0 offset 0x100000, size 0x400000 4194304 bytes read: OK ## Booting kernel from Legacy Image at 00800000 ... Image Name: Linux-3.3.2-kirkwide Created: 2012-10-29 22:52:12 UTC Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 3627768 Bytes = 3.5 MiB Load Address: 00008000 Entry Point: 00008000 Verifying Checksum ... OK Starting kernel ...
I tried recreating initrd.img-5.3.2-kirkwood-tld-1 and uInitrd several times and came up with the same result. I haven't changed my u-boot env variables in months and a checked the ones mentioned in the install-a-new-kernel-instructions looked good. I don't know what to do next. Is what being tagged as bad uInitrd? Suggestions?
sparks