Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - pigdog

Pages: [1] 2 3 ... 60
Hi phenigma,


From my earlier statement in this post.

I run LMCE on a dedicated network without username/password access.

....basically don't be lazy and not use username/password credentials on 12.04 NAS drives.

The errors in topic=13655.0 helped a bit.

But why symbolic link errors? - that throws you way off.  At least it did me.

I feel kinda silly being lazy with an unsecured NAS but I at least learned something - I hope.

Thank you very much for your time (that I wasted).


Installation issues / Re: NAS CIFS errors on April 13 28939 snap
« on: April 16, 2014, 10:52:00 pm »
Hi Michaeltree,

FYI my smb.conf is exactly the same in 12.04 as it was in 10.04.

security = user   was already set.

My NAS was open (I'm a bad boy) but it was on an internal network where only LMCE devices could access it.

I played around but I could not get 12.04 to connect.

So to fix it I started from scratch, reloading the Core/Hybrid (because of so many things) and then added a username/password to the NAS.

In my smb.conf I had to add     client lanman auth = yes.

My Core/Hybrid upon NAS discovery asked for NAS credentials and everyone is happy.

I guess we can't be lazy anymore and leave storage devices unsecured.

Thanks for your input.


Installation issues / Re: Snap April 13 28939 ehci_hcd errors
« on: April 16, 2014, 10:26:56 pm »

I reloaded from scratch and no more error messages.

I went into KDE Desktop and put a USB stick into a port and received...

An error occurred while accessing 'USBNAME', the system responded:
An unexpected error has occurred. : Not Authorized

I have not seen any error messages on the terminal.

I will play with this when I get spare time to see if it can be reproduced and to find out why I'm not authorized.


Installation issues / Re: Snap April 13 28939 ehci_hcd errors
« on: April 16, 2014, 04:14:07 pm »

I ended up adding...

dmesg -n 1

to /etc/rc.local

This stopped the intermittent terminal messages but it also stops any kernel generated error messages.

Users / Re: wrong resolution on hybrid/MD after boot
« on: April 16, 2014, 12:31:54 am »

What's your make and model of amp?

I have probably asked this question many times before, on various threads, but, it always helps to state make and model when you ask about an issue.

If it happens to be a Denon (and most other makes) - look at the HDMI pass-through setting.

Please, if it works, respond so that other users aren't left hanging to know if that was the solution.


Installation issues / Re: NAS CIFS errors on April 13 28939 snap
« on: April 15, 2014, 11:00:54 pm »

I've gone through a lot of on-line stuff with solutions re: manually mounting drives etc. to get things to work.

O.K. I figure I could try to manually mount and set permissions and stuff but why? Really?

This use to work great in LMCE as is - was fantastic, phenomenal, etc, etc.

What is the underlying issue?

Are we looking at a 12.04 bug?

Just curious I guess.


Just in case anyone was interested.


Installation issues / Snap April 13 28939 ehci_hcd errors - Kinda
« on: April 15, 2014, 09:26:37 pm »

On this snap (could have been earlier as well) I received a...


...error on usb 3-4 at boot up with lots of usb 3-4: device descriptor read/64 and device not accepting address XX messages .

So I ...

cd /sys/bus/pci/drivers/ehci_hcd

and did ...

ls -l

In my case this displayed two files with 0000:00:XX.X names.

I entered the command...

echo -n "0000:00:XX.X" > unbind

for both files and this slowed the messages down quite a bit.  At least it made it easier to enter command prompt entries without having everything overwritten by the terminal output messages.

This had to be re-entered every time I rebooted.

So I put the commands into /etc/rc.local and rebooted.

echo -n "0000:00:XX.X" > unbind /sys/bus/pci/drivers/ehci_hcd

They don't come up as nearly often but they still annoy during troubleshooting.

I don't understand why they still pop up - period, but it's way less annoying than before.


Hi phenigma,

Even though I might not get anywhere with this, (a.k.a. get discouraged), I appreciate your feedback.

It's all about the challenge.  Thanks!



Looks like some error reporting was turned on.

The handshaking between LMCE and DNS 323 NAS continues as reported in reply #19 but I am now getting flooded with (it is spring) a few    Error connecting to socket - aborting operation     and continuous...

CIFS VFS: Send error in SessSetup = -13
CIFS VFS: cifs_mount failed w/return code = -13


Hi phenigma,

I've downloaded many snaps, reloaded many from scratch (because I tried so many things I lost continuity) with the same results.

I run LMCE on a dedicated network without username/password access.

On 12.04 I've deleted the symlinks from Windows Shares [34 & 35] and when I go to /mnt/device/XX and try an cd or ls I get symbolic link error.

The NAS HDD's are using the LMCE directory tree, nothing is different on it from 10.04.

I can run the NAS fine under 10.04 and have even reloaded 10.04 from scratch (more than once after playing with it).

One thing is that with the  ls -l cmd file permissions on 10.04 for /mnt/device are drwxrwxrwx (777) with ownership root:root

When i go down the tree to /mnt/device/XX permissions are the same but ownership changes to 501:501 (DNS-323 ownership format)

On 12.04 the /mnt/device permissions are 555 (why?).  I chmod 777 XX but can't change them -R option because of symlink error.

On a reboot the deleted Windows Share links gets recreated and the permissions for /mnt/device/XX go back to 555.

On 10.04 & 12.04 the Windows Shares are lrwxrwxrwx (777) permission and ownership root:public.

However on 10.04 using the ls -l command on /home/public/data/videos the Windows Share is cyan with the symlink to /mnt/device/XX/public/data/videos with green background.

On 12.04 the Windows Share-Volume-X [XX] is red and symlink -> mnt/device/XX/public/data/videos as well.

Red is bad.  Why is it red?  It was autodetected and created but the drives aren't being handled the same.

So. do I look into detection scripts for 12.04 permissions/etc,  or do I look into NAS ownership?  (I don't know if I can do ownership changes on the DNS.)

There are other DNS 323 users out there but I haven't heard from any.

I've tried smb.conf follow symlinks=yes but no joy.

I could try to build NAS4Free or FreeNAS and see if that'll work.  It might give me a hint.

I don't really want to run funplug or jerk around with the DLink if I don't have to.



I have been spending a lot of time on this issue.  MAXSYMLINKS on 10.04 and 12.04 appears to be set @ 20.

Nothing I do seems to correct the problem.

Not being to access the content on my NAS with 12.04 is a game stopper.

I have been following the symbolic link error but could it be something else?

My NAS is being queried/accessed (there seems to be communication to the hardware controller but the HDD's don't act like they normally would when being interrogated by UpdateMedia).

Right now I'm "what the heck has changed between the 10.04 and 12.04 OS's"?



So I used the following command to count the number of symlinks ...

find $directory -type l -exec echo symlinks \; | sort | uniq -c

as root and cd .. back to main dir.

10.04 had 86242 symlinks

12.04 complained during find: ' ./mnt/device/XX' : Too many levels of symbolic links ... and reported only 53044 symlinks.


I deleted the symlink from /home/public/data/videos/Windows Share-Volume_X [XX] -> /mnt/device/XX/public/data/videos

Then from /mnt/device I tried to cd into XX but got the 'too many symbolic links' message.

I couldn't rm -r or -R from /mnt/device because of 'too many - you guessed it! - symbolic links.'

Sym links get recreated on boot.

I noticed the permissions were 555 so I chmod to 777 but no luck.  They get written back to 555 on boot.

I've gone through smb.conf, dhcp stuff, other silly things but I can't see anything.


Installed the April 5 svr 28895 and am getting "failed to load PLUTO VDR" message.

Results of ps ax | grep autofs ...

8762 tty1       S+     0:00  grep  --color=auto  autofs


Pages: [1] 2 3 ... 60