Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FS#1842 - BT Home Hub 2B (lantiq) has nand / ubi errors on boot with 18.06.1 #7165

Closed
openwrt-bot opened this issue Sep 11, 2018 · 5 comments
Closed
Labels

Comments

@openwrt-bot
Copy link

@openwrt-bot openwrt-bot commented Sep 11, 2018

jaimet:

I've flashed my BT Home Hub 2B with OpenWrt 18.06.1 (using sysupgrade) and it boots (just!) but the log shows a lots of errors during boot.

I've attached the boot log produced via a serial console.

Previously to me flashing this router with openwrt 18.06.1, it was running lede 17.01.4 with no errors.

@openwrt-bot
Copy link
Author

@openwrt-bot openwrt-bot commented Sep 11, 2018

jaimet:

I forgot to mention that https://bugs.openwrt.org/index.php?do=details&task_id=245 looks similar (same architecture and similar error messages) - perhaps this bug is related.

@openwrt-bot
Copy link
Author

@openwrt-bot openwrt-bot commented Sep 12, 2018

jaimet:

More info: I force-flashed the router back down to (lede) release 17.01.4 and I see very similar errors on boot, so I now think that my previous "belief" (that I was "running lede 17.01.4 with no errors") is incorrect. I now think that the nand on this router is failing and that therefore the router needs to be binned/thrown away. I have attached the "17.01.4.bootlog" - could anyone please confirm whether or not the nand on this router is broken? Many thanks.

@openwrt-bot
Copy link
Author

@openwrt-bot openwrt-bot commented Sep 13, 2018

jaimet:

OK, more info. Instead of reflashing by running sysupgrade from within a running openwrt, I booted the initramfs from the Porta-Danube prompt and then (once that had booted) I ran sysupgrade from there. This worked perfectly for the first couple of hours (no more nand/ubifs errors at all) but then the router rebooted itself (?!), and then the nand/ubifs errors all returned. I'm beginning to think that the nand/ubifs errors are simply the result of instant reboots caused by either me pulling the power or kernel crashes combined with a new sync semantic whereby an unclean shutdown will trash the ubifs filesystem (I'm guessing here!!)

I'm going to bail out of this and go back to 17.01.4 until I have the time to work out what's going on.

@openwrt-bot
Copy link
Author

@openwrt-bot openwrt-bot commented Sep 13, 2018

jaimet:

Just found https://bugs.openwrt.org/index.php?do=details&task_id=1755
It looks very similar...

@openwrt-bot
Copy link
Author

@openwrt-bot openwrt-bot commented May 16, 2019

jaimet:

I'm not sure when this was fixed, but I've been running 18.06.2 on three different HH2Bs for a couple of weeks now, and they all seem to be working perfectly. Closing this bug now. Many thanks. JT

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant