DJanGo wrote:
> I have no clue about picoreplayer but every *ux OS uses UUIDS for their
> HDs.
>
> moving the content from one Disk to another without changing mountpoints
> to the new hd is the first maybe missing step i would think of.
>
> did you alter the uuids somewhere after the move?
I have no clue about picoreplayer but every *ux OS uses UUIDS for their
HDs.
moving the content from one Disk to another without changing mountpoints
to the new hd is the first maybe missing step i would think of.
did you alter the uuids somewhere after the move?
> On 3 Mar 2019, at 22:25, Michael Herger wrote:
>
>> [19-03-03 18:55:34.7449] main::init (387) Starting Logitech
>> Media Server (v7.9.2, 1543258616, Mon Nov 26 20:30:03 CET 2018) perl
>> 5.024000 - arm-linux-gnueabihf-thread-multi-64int
>> [19-03-03 18:55:34.7826] YAML::XS::LoadFile (48)
[19-03-03 18:55:34.7449] main::init (387) Starting Logitech
Media Server (v7.9.2, 1543258616, Mon Nov 26 20:30:03 CET 2018) perl
5.024000 - arm-linux-gnueabihf-thread-multi-64int
[19-03-03 18:55:34.7826] YAML::XS::LoadFile (48) Warning: YAML::XS::Load
Error: The problem:
Delete the prefs file
And I get the same error when using no cache and LMS config.
rkrug's Profile: http://forums.slimdevices.com/member.php?userid=62249
View this thread: http://forums.slimdevices.com/showthread.php?t=110261
Uninstalled LMS, installed LMS again, and I am back to the first error:
[19-03-03 18:55:34.7449] main::init (387) Starting Logitech
Media Server (v7.9.2, 1543258616, Mon Nov 26 20:30:03 CET 2018) perl
5.024000 - arm-linux-gnueabihf-thread-multi-64int
[19-03-03 18:55:34.7826] YAML::XS::LoadFile
Now I updated the libraries (Download and update LMS Binaries and
Libraries ) and now I get
[ INFO ] Starting LMS...
[ INFO ] The following CPAN modules were found but cannot work with
Logitech Media Server:
Audio::Scan (loaded 1.02, need 0.93)
which sounds not nice.
Hi
I bought a new ssd for my piCorePlayer (I want to eliminate moving
parts) and copied all due Music and server cache data (after shutting
down LMS).
Now the LMS doses not start anymore, not even from the original LMS
cache / data.
I get the following error:
```
[19-03-03 18:26:25.2250]
