27th Feb, 2015, 02:17 AM
27th Feb, 2015, 02:35 AM
(27th Feb, 2015 02:17 AM)f1vefour Wrote: [ -> ]What was your overclock set to? And what is it now?
i changed this from
High
950 ARM
450 CORE
500 SDRAM
2 Overvolt
to
Medium
900 ARM
333 CORE
450 SDRAM
0 Overvolt
27th Feb, 2015, 08:49 AM
Ok, so now I arrived home after work and the Pi is nowhere to be seen in the network. Everything else is working fine.
The only error I see in kodi.log is:
18:57:05 T:3034968064 ERROR: Dbus: Error org.freedesktop.UDisks.Error.PermissionDenied - Not Authorized
19:17:20 T:2759848976 ERROR: Previous line repeats 1 times.
Any other logs I can look at?
Thanks
The only error I see in kodi.log is:
18:57:05 T:3034968064 ERROR: Dbus: Error org.freedesktop.UDisks.Error.PermissionDenied - Not Authorized
19:17:20 T:2759848976 ERROR: Previous line repeats 1 times.
Any other logs I can look at?
Thanks
27th Feb, 2015, 04:40 PM
dmesg
28th Feb, 2015, 04:11 AM
So here is the dmesg output:
http://pastebin.com/fu5WjYaG
There are a couple of errors but I can't asses their severity or if they're related to a LAN failure.
Hope it helps tho!
http://pastebin.com/fu5WjYaG
There are a couple of errors but I can't asses their severity or if they're related to a LAN failure.
Hope it helps tho!
28th Feb, 2015, 05:45 AM
It appears you have a potentially severe disk issue, see this thread about a similar GPT issue: http://ubuntuforums.org/showthread.php?t=1956173
28th Feb, 2015, 07:44 AM
Disk, as in external disk or SD card?
Could this cause the network fail?
Could this cause the network fail?
28th Feb, 2015, 08:36 AM
External drive.
You can wait until the next kernel comes out (I activated a USB feature that may help) or try downgrading the kernel.
You can wait until the next kernel comes out (I activated a USB feature that may help) or try downgrading the kernel.
28th Feb, 2015, 08:40 AM
Ok, I think I will upgrade to the next kernel, and report back when the time comes.
Thanks a lot!
Thanks a lot!
12th Mar, 2015, 07:29 PM
I have the same problem with XBian on Raspi 2, which I can reproduce even on the untouched original image (i.e., without installing anything or mounting network drives).
It typically appears 20-30 hours after not having touched the Raspi. OpenElec runs fine (at least for 35 hours now). I have a 2A charger (from Nexus 7 tablet), and no rainbow icon is shown.
As the crashes occur in sleep mode, it seems that the overclocking settings affect the sleep states.
What are the regular, non-overclocked settings for the Pi2?
It typically appears 20-30 hours after not having touched the Raspi. OpenElec runs fine (at least for 35 hours now). I have a 2A charger (from Nexus 7 tablet), and no rainbow icon is shown.
As the crashes occur in sleep mode, it seems that the overclocking settings affect the sleep states.
What are the regular, non-overclocked settings for the Pi2?
14th Mar, 2015, 08:27 AM
I've been very busy lately so a bunch of updates.
First, like one week ago I got another external hard drive failure. I attach the dmesg log.
And yesterday I got another kernel panic. Photo attached. I apologize for the background image that makes it difficult to read.
[attachment=408]
First, like one week ago I got another external hard drive failure. I attach the dmesg log.
And yesterday I got another kernel panic. Photo attached. I apologize for the background image that makes it difficult to read.
[attachment=408]
14th Mar, 2015, 10:22 AM
What is on sda1 and sda2?
From that screenshot that is a btrfs panic which is different than the other panics I jave seen.
From that screenshot that is a btrfs panic which is different than the other panics I jave seen.
15th Mar, 2015, 06:13 AM
(14th Mar, 2015 10:22 AM)f1vefour Wrote: [ -> ]What is on sda1 and sda2?
From that screenshot that is a btrfs panic which is different than the other panics I jave seen.
This is the output of sudo blkid
Terminal
sudo blkid
[sudo] password for xbian:
/dev/mmcblk0p1: SEC_TYPE="msdos" LABEL="xbianboot" UUID="394B-4E95" TYPE="vfat"
/dev/mmcblk0p2: LABEL="xbian" UUID="c7db0049-ae21-4ec8-a3b8-40b08f04c173" UUID_SUB="7f47877d-e9b4-4aca-87c4-394e423d508a" TYPE="btrfs"
/dev/mmcblk0p3: UUID="c4e79c35-73a6-4d3d-83dc-9f86bb9c153d" TYPE="swap"
/dev/root: LABEL="xbian" UUID="c7db0049-ae21-4ec8-a3b8-40b08f04c173" UUID_SUB="7f47877d-e9b4-4aca-87c4-394e423d508a" TYPE="btrfs"
/dev/sdb1: LABEL="EFI" UUID="70D6-1701" TYPE="vfat"
/dev/sdb2: LABEL="SERIEATOR" UUID="FC39-1E17" TYPE="vfat"
[sudo] password for xbian:
/dev/mmcblk0p1: SEC_TYPE="msdos" LABEL="xbianboot" UUID="394B-4E95" TYPE="vfat"
/dev/mmcblk0p2: LABEL="xbian" UUID="c7db0049-ae21-4ec8-a3b8-40b08f04c173" UUID_SUB="7f47877d-e9b4-4aca-87c4-394e423d508a" TYPE="btrfs"
/dev/mmcblk0p3: UUID="c4e79c35-73a6-4d3d-83dc-9f86bb9c153d" TYPE="swap"
/dev/root: LABEL="xbian" UUID="c7db0049-ae21-4ec8-a3b8-40b08f04c173" UUID_SUB="7f47877d-e9b4-4aca-87c4-394e423d508a" TYPE="btrfs"
/dev/sdb1: LABEL="EFI" UUID="70D6-1701" TYPE="vfat"
/dev/sdb2: LABEL="SERIEATOR" UUID="FC39-1E17" TYPE="vfat"
19th Mar, 2015, 03:21 AM
(14th Mar, 2015 10:22 AM)f1vefour Wrote: [ -> ]What is on sda1 and sda2?
From that screenshot that is a btrfs panic which is different than the other panics I jave seen.
Since i have a similiar problem (on other thread) i'm posting my latest kernel panic photo here... i hope you can give me some help.
Thks.
22nd Mar, 2015, 06:51 AM
Could you post that picture to github with @mk01 in the post, he knows a lot more than I about btrfs.