Attempted to restore...

[WarheadsSE]

I've been extremely occupied, my apologies. It looks like it is having trouble with the filesystem. Re-create the rootfs partition, an be sure to extract it as root (or sudo su)

[DocTauri]

Understood, you have a life too, and I appreciate your help!

I've done it 3 times now and basically get the same results. I'm going to try a different HD next, and re-download all of the tarballs.

I'll report back.

Thanks.

[WarheadsSE]

Try the very latest oxnas tarball that was just updated.

[DocTauri]

Ok, so I finally got my repaired (replaced) tty board back and got to messing with this again. I redownloaded the tarballs, but still had problems.

First, it was bitching because it couldn't find /dev/urandom. I recreated that, but it still would fail at boot with processes respawning too fast error. I dropped it into runlevel 1 and finally got a shell. Woohoo!

So, I tried to run the oxnas-revert.sh script again, but got an open mtd: no such file error. A quick search of the forum showed the fix to be another mknod for /dev/mtd0, and oxnas-revert.sh ran without error and pronounced it's success.

So, I pulled off the esata drive and tried to reboot. Nothing. It just sits there with absolutely no output. Turn it off, plug in the esata, and it boots and outputs just fine.

SO... I'm assuming (based on the revert script's output) that my boot parms are back to what they should be, so my problem must be with my NAND boot image?

Before I venture off to that and eh-f it up worse, just looking for some validation and any suggestions.

Thanks,
Doc

[WarheadsSE]

Fragged nand boot sector. Some how.

[DocTauri]

Awesome, story of my life

Any suggestions on moving forward?

Thanks,
Doc

[tilator]

Reflashing made my /dev/mtd2 partition totally bad blocks.

How can this be recovered? I know the nand have really only a few bad blocks, so how to get the good ones back?