Can't access GUI or samba

james_b

I've been running Rune on a Pi 2 for several months without many problems, but now I can't access the GUI through Chrome (using runeaudio.local or the IP) or connect via smb in the terminal/ finder. Powering off the Pi at the power source is the only step I can think of to remedy this but it isn't working.

Runeaudio appears as a connected device in my router's settings which leads me to think that the Pi install is working, but I'm not sure what else could be the problem. What steps should I take to fix this?

Thanks!

(I should add that rune stopped working shortly (but not immediately) after disconnecting all cables while moving to a new rack. May not be relevant.)

james_b

After an hour or so of unplugging, restarting etc I'm back in action, but none the wiser as to what the problem was.

My setup is like this:

USB HDD > Powered USB hub > RP 2 using a Realtek USB adapter > Denon DA-300-USB

I have little faith in the USB hub (a cheap thing I had lying around) and the wlan adapter isn't anything special. But the Pi and the Denon should both be good. The USB cables I'm using could be at fault, they were found in the back of the drawer somewhere - but is this likely to be the problem?

Debug info is here if anyone can make any sense of it - http://pastebin.com/5Euu0rh4

james_b

Sometime later I can't access runeaudio.local yet again.

The album I started about 25 minutes ago is still playing without a problem. Attempts to ping the IP results in "ping: sendto: Host is down".

Presumably if the player is working but the network connection is down the usb wlan adapter is likely to be at fault? Though I can't quite understand why my router admin page would still think runeaudio is connected. I'm not having any trouble connecting to the router with my laptop or phone.

james_b

Still experiencing this problem despite switching to a Pi 3 - still connected according to the router, all lights functioning on the PI but unable to connect through the browser, finder or terminal. The only consistent component is the DAC and maybe the SD card

Is there anyone out there who could assist me with this? Having to unplug the power every time I want to listen to music is really taking the fun out of this.

hondagx35

Hi james_b,

I've been running Rune on a Pi 2 for several months without many problems

So it didn't happen the first months of usage?

Have you changed the power supply?

I never had such issues with my PI2 or PI3, so it's hard to help for me.

Do you know how to ssh to your PI?

Frank

james_b

hondagx35 wroteHi james_b,

I've been running Rune on a Pi 2 for several months without many problems
So it didn't happen the first months of usage?

Have you changed the power supply?

I never had such issues with my PI2 or PI3, so it's hard to help for me.

Do you know how to ssh to your PI?

Frank

Thanks for responding.

It was running fine for quite some time, maybe 3 or 4 months. I'm trying the Pi 3 now but with similar issues - the SD card and HDD have both been swapped out - same USB cables though.

I may have switched the power supply when reorganising but the one I'm using now is Pi branded, and I've tested it with a random samsung one I had here. I guess I should pick up a new official one to rule that out.

I know how to SSH to the Pi (and regularly do), but attempts to do so when it's in this state result in "Operation timed out" at first and then "Host is down". It seems that the Pi is unreachable in any way, but the green light keeps flashing intermittently as normal.

I feel like there may be some correlation between my USB DAC going into auto-standby mode and this error, is that crazy? Though given how many different configurations have led me to this same outcome in the past few days I'm starting to think it might be a router/ network issue.

EDIT: Actually it looks like the official PSU I'm using is an MK1 version which is only 1A so it could well be related to that, though it was powering a Pi 2 with openmediavault with no problems.