search

Waziup / WaziGate

Waziup LoRa Edge gateway
21 stars 20 forks source link

Kernel panic #135

Closed cdupont closed 2 years ago

cdupont commented 3 years ago

I have a WaziGate with ISO 2.1.3-beta. I was powered one since before christmas. Today I tried to reconnect but I couldn't. Plugging a screen I see this Kernel panic:

20210107_122220

mojtaba-esk commented 3 years ago

It seems like Rasbian cannot boot up, can you check if your SD card is not corrupted?

On Thu, Jan 7, 2021 at 12:30 PM Corentin Dupont notifications@github.com wrote:

Assigned #135 https://github.com/Waziup/WaziGate/issues/135 to @mojtaba-esk https://github.com/mojtaba-esk.

— You are receiving this because you were assigned. Reply to this email directly, view it on GitHub https://github.com/Waziup/WaziGate/issues/135#event-4179465720, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADJAXHAOR4Y7KITEK3OL7ETSYWLLVANCNFSM4VY3IKSA .

-- Mojtaba Eskandari

cdupont commented 3 years ago

I can mount it from my PC and see the files. Earlier I saw a message "cannot find init files"

cdupont commented 3 years ago

There is a lot of corrupt data it seems:

$ sudo fsck /dev/mmcblk0p2
fsck from util-linux 2.31.1
e2fsck 1.44.1 (24-Mar-2018)
/dev/mmcblk0p2 contains a file system with errors, check forced.
Resize inode not valid.  Recreate<y>? yes
Pass 1: Checking inodes, blocks, and sizes

Inodes that were part of a corrupted orphan linked list found.  Fix<y>? yes
Inode 1445 was part of the orphaned inode list.  FIXED.
Inode 1445 has corrupt extent header.  Clear inode<y>? yes
Inode 1445, i_blocks is 2104, should be 0.  Fix<y>? yes
Inode 1446 has corrupt extent header.  Clear inode<y>? yes
Inode 1446, i_blocks is 81364934197424, should be 0.  Fix<y>? yes
Inode 1447 has a extra size (33) which is invalid
Fix<y>? yes

The list goes on. I think I'd better reflash

mojtaba-esk commented 3 years ago

Was your pi up and running? you rebooted it or it was off for a while?

On Thu, Jan 7, 2021 at 1:00 PM Corentin Dupont notifications@github.com wrote:

There is a lot of corrupt data it seems:

$ sudo fsck /dev/mmcblk0p2 fsck from util-linux 2.31.1 e2fsck 1.44.1 (24-Mar-2018) /dev/mmcblk0p2 contains a file system with errors, check forced. Resize inode not valid. Recreate? yes Pass 1: Checking inodes, blocks, and sizes

Inodes that were part of a corrupted orphan linked list found. Fix? yes Inode 1445 was part of the orphaned inode list. FIXED. Inode 1445 has corrupt extent header. Clear inode? yes Inode 1445, i_blocks is 2104, should be 0. Fix? yes Inode 1446 has corrupt extent header. Clear inode? yes Inode 1446, i_blocks is 81364934197424, should be 0. Fix? yes Inode 1447 has a extra size (33) which is invalid Fix? yes

The list goes on.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/Waziup/WaziGate/issues/135#issuecomment-756074072, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADJAXHDSAJ3RXRSLPNFO7SLSYWO57ANCNFSM4VY3IKSA .

-- Mojtaba Eskandari

cdupont commented 3 years ago

No it was ON for a long time, this morning I could not connect. RPI4

mojtaba-esk commented 3 years ago

Strange! Probably it was rebooted suddenly maybe due to power outage or some other issue and that led to SD corruption. it happens to me sometimes as well even though I use a SanDisk SD card.

On Thu, Jan 7, 2021 at 1:09 PM Corentin Dupont notifications@github.com wrote:

No it was ON for a long time, this morning I could not connect. RPI4

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/Waziup/WaziGate/issues/135#issuecomment-756078051, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADJAXHDWHYDA2JTS7EUMWBTSYWP6HANCNFSM4VY3IKSA .

-- Mojtaba Eskandari

cdupont commented 2 years ago

closing as not reproduced