NAS recognized and added but no meddia addded

[pigdog]

Hi,

I have finally got the pieces together to rebuild my dev box (to try to get cu-box working - haven't managed to do ANYTHING since October/14).  I loaded on 12041002114429514, which is my bullet load, running on my main system.  I did update, upgrade, dist-upgrade.  Everything fine.  Fired up my NAS, it was discovered, added username/password.  No media discovered.  I rebooted, nothing. I tried a resync from webadmin Media Files Sync  and received the following.

sudo -u root /usr/pluto/bin/UpdateMedia -d \"/home/public/data/videos\"

21   02/09/15 10:05:02.390      lock(0x9151a8c) (>2) alarm: AlarmManager.cpp:102  <0xb7713b40>
21   02/09/15 10:05:02.390      acquired(0x9151a8c) #0 (>2) alarm AlarmManager.cpp:102  <0xb7713b40>
21   02/09/15 10:05:02.390      start cond wait AlarmManager.cpp:102 (0x9151a8c)  <0xb7713b40>
10   02/09/15 10:05:02.394      Activating Pluto Media Identifier... <0xb7715700>
10   02/09/15 10:05:02.395      Pluto Media Identifier activated. Extensions 74 <0xb7715700>
10   02/09/15 10:05:02.395      MediaState::LoadDbInfo ready to run big query <0xb7715700>
10   02/09/15 10:05:02.398      MediaState::LoadDbInfo got 1 rows <0xb7715700>
10   02/09/15 10:05:02.398      UpdateMedia::ReadDirectory /home/public/data/videos <0xb7715700>
10   02/09/15 10:05:02.399      Sync'ing db with directory... <0xb7715700>
10   02/09/15 10:05:02.399      DB sync'd with directory! <0xb7715700>
10   02/09/15 10:05:02.399      AlarmManager::~AlarmManager start 0x9151a48 <0xb7715700>
21   02/09/15 10:05:02.399      lock(0x9151a8c) (>3) alarm: AlarmManager.cpp:87  <0xb7715700>
21   02/09/15 10:05:02.399      acquired(0x9151a8c) #0 (>3) alarm AlarmManager.cpp:87  <0xb7715700>
21   02/09/15 10:05:02.399      unlock(0x9151a8c) #0 (>3) alarm: AlarmManager.cpp:87  <0xb7715700>
21   02/09/15 10:05:02.399      end cond wait AlarmManager.cpp:102 (0x9151a8c)  <0xb7713b40>
21   02/09/15 10:05:02.399      unlock(0x9151a8c) #0 (>2) alarm: AlarmManager.cpp:102  <0xb7713b40>
21   02/09/15 10:05:02.399      removed from map (0x9151a8c) #0 (>2) alarm: AlarmManager.cpp:102  was: 2 size, now 1 Rel: Y Got: Y <0xb7713b40>
21   02/09/15 10:05:02.399      removed from map (0x9151a8c) #0 (>3) alarm: AlarmManager.cpp:87  was: 1 size, now 0 Rel: Y Got: Y <0xb7715700>
10   02/09/15 10:05:02.399      AlarmManager::~AlarmManager done 0x9151a48 <0xb7715700>

PS

When NAS was added as a Windows file share I received QT4 and QT5 download error messages when the file server software was beiing asdded and installed.

Cheers.

[pigdog]

Hi,

So I have reloaded from scratch, did not do an update, upgrade, dist-upgrade (yet) and my media was picked up.

When all is done I will do an update, upgrade and dist-upgrade - then I will add some new media and see if it is picked up.

Cheers

[pigdog]

Hi,

HDD got corrupted and now boots into initramfs.

Ran diag tool from WD and HDD was reported as physically OK.

Before crash NAS volume 2 was not being unlocked and reported too many symbolic links.  Volume 1 was fine.

Will reload software and try again.

Cheers

[pigdog]

Wow!

I had a whole lot of weirdness going on.

Two hard drives with Ubuntu and (awk!) Win10.  Both corrupted. 

The ASRock B75M-DGS motherboard constantly making clicking noises - like a mechanical relay being operated

I have an old 430W power supply in that system, but, there may have been an issue with an IDE to SATA power adapter.

Once swapped the clicking stopped.  I've rebuilt both drives and so far no major issues.

Still have a couple of minor issues to resolve.

Hopefully soon I can get back to pursuing the Cubox.

Cheers.

[phenigma]

Wow!  I've been following your progress.  Great work with all your troubleshooting!  You should meet up on IRC to discuss the cubox more.  There is now CEC support for it in libcec

J.