earthbased wrote:
> I monitored / partition and it never went over 90% used. I upgraded to
> 7.9.0 June 4th and / usage is the same. Will see how it goes.
7.9.0 has not shown similar errors. It has been running well for 5 days
now. 7.8.1 then system corruption beyond LIBRARY.DB that was
mherger wrote:
> For the moment I wouldn't worry to much about the cause of the
> corruption. It happens. Just shut down LMS, delete the file, restart.
>
> Should this kind of problem occur more often, then it's probably time to
>
> investigate the root cause.
>
> BTW: some of your
For the moment I wouldn't worry to much about the cause of the
corruption. It happens. Just shut down LMS, delete the file, restart.
Should this kind of problem occur more often, then it's probably time to
investigate the root cause.
BTW: some of your partitions are rather small (in
earthbased wrote:
> Would scanning Library.DB for viruses potentially cause a crash?
maybe if lms want to add information to the db and its loked it not
unpossible.
I have no qnap - so i cant test it for you.
DJanGo's
earthbased wrote:
> do failed: disk I/O error
thats a really bad error/warning - look @ free disk space and the state
of your harddrives.
DJanGo's Profile: http://forums.slimdevices.com/member.php?userid=1516
View this
mherger wrote:
> I must silence that warning... it's confusing too many people.
please not!!!
may you change that to > Slim::Schema::init (162) Info: Creating new database -
empty, outdated
> or invalid database found
>
or > Slim::Schema::init (162) Info start from scratch
or you may can
mherger wrote:
> > Does this:
> >
> > 47250: [16-05-30 11:19:17.1490] Slim::Schema::init (162) Warning:
> > Creating new database - empty, outdated or invalid database found
> >
> > indicate a new db was created?
>
> No, it only indicates that there is no music data in the database. When
>
> a
Does this:
47250: [16-05-30 11:19:17.1490] Slim::Schema::init (162) Warning:
Creating new database - empty, outdated or invalid database found
indicate a new db was created?
No, it only indicates that there is no music data in the database. When
a new db is created, then of course you would
mherger wrote:
> > Attached are the log records; have no idea why this happened; Qnap
> > dashboard indicates system health is good with no errors.
>
> It could happen when LMS crashes, or when it is not stopped properly.
> Just stop LMS, delete the file, and re-start. It will re-build the
>
Attached are the log records; have no idea why this happened; Qnap
dashboard indicates system health is good with no errors.
+---+
|Filename: LMS_DB_Corruption_2016-05-30.txt |
|Download:
10 matches
Mail list logo
