LinuxMCE Forums
General => Users => Topic started by: ccoudsi on August 01, 2009, 08:20:06 pm
-
After switching to 810, I found a problem playing music from the \NAS-323\sharedfolder\ (No Password) on the squeezebox, there was no issue using the same shared folder “Multimedia” on 710 setup, debugging this with ColinJones, we found out there is a permissions/ownership problem, the shared Folder mount has a “501” user access, searching the core users/Group, there is no such a user or Group. We suspect this user came from the NAS!!
linuxmce@dcerouter:~$ ls -al /mnt/device
total 4
drwxr-xr-x 3 root root 0 2009-07-30 16:20 .
drwxr-xr-x 4 root root 4096 2009-07-29 20:20 ..
drwxrwx--- 7 501 501 0 2009-06-17 23:15 92
linuxmce@dcerouter:~$ ls -al /mnt/device/92
ls: cannot open directory /mnt/device/92: Permission denied
FYI Here's the output of the mount command
//192.168.80.139/Multimedia on /mnt/device/92 type cifs (rw,mand,unc=\\192.168.80.139\Multimedia,username=guest,posixpaths,acl,rsize=16384,wsize=57344)
linuxmce@dcerouter:~$
Please see this thread for complete info.
http://forum.linuxmce.org/index.php?topic=8078.msg58002#msg58002 (http://forum.linuxmce.org/index.php?topic=8078.msg58002#msg58002)
Can someone please compare your results, and give us any recommendations on how we can override these options without breaking the automouting system so that we can check if that is the issue.
Thanks
-
Hi,
Not sure if this is what your looking for but from my Fedora box if I connect to my DNS-323
smbclient //NAS-1/volume_1 -U
And since I presently have no username/password when prompted I hit enter.
Enter Pigdog's password:
Domain=[LINUXMCE] OS=[Unix] Server=[Samba 3.0.24]
Server not using user level security and no password supplied.
smb: \>
If you have a username/password you enter...
smbclient //NAS-1/volume_1 -U username
Enter username password:
A stat command on the box shows that uid&gid is 501.
smb: \> stat public
File: \public
Size: 0 Blocks: 0 directory
Inode: 76808193 Links: 3
Access: (0777/drwxrwxrwx) Uid: 501 Gid: 501
Access: 2009-08-01 11:21:49 -0400
Modify: 2009-07-07 23:50:49 -0400
Change: 2009-07-07 23:50:49 -0400
There is a chown on the DNS but I haven't tried it.
smb: \> help chown
HELP chown:
<src> <uid> <gid> chown a file using UNIX uids and gids
That's probably where 501 is coming from.
-
pigdog, thank you very much this explains the problem.
Here's my output using terminal windows from the core
linuxmce@dcerouter:~$ smbclient //Dns-323/volume_1 -U
Enter linuxmce's password:
Domain=[LINUXMCE] OS=[Unix] Server=[Samba 3.0.24]
Server not using user level security and no password supplied.
smb: \> stat public
File: \public
Size: 0 Blocks: 0 directory
Inode: 168919041 Links: 3
Access: (0777/drwxrwxrwx) Uid: 501 Gid: 501
Access: 2009-07-31 21:11:09 -0700
Modify: 2009-01-25 10:29:13 -0800
Change: 2009-01-25 10:29:13 -0800
smb: \>
According to Colin this should not happens, possible a bug in 810 mounting, should I file this in the Trac??
-
as a clarification - I haven't said that this shouldn't happen on 0810, I merely pointed out that this is not what happens on 0710. Either it is the source of your problem, or perhaps this is normal for 0810 and it is a red herring, I simply don't know. (I don't have 0810 to test)
What we need is someone with 0810 and a NAS/Windows share that is working (but not a DNS unit) to post here and tell us what they see when they do the same thing. And particularly what the ownership and permissions are of their /mnt/device/<dev#> directory is when they ls -al it.
If it is drwxrwxrwx and root:root then I think we can safely say that this is your issue, and there is an update required to 0810's mounting system to take that into account and ensure that DNS devices are mounted as drwxrwxrwx root:root rather than drwxrwx--- 501:501
However, if everybody else also gets something like you for their mounts, then it is probably just a red herring (ie normal for 0810), but I would like to know whether they can cd into that directory, as that does seem to be the critical issue here.
-
Colin,
I apologize, I just went back to DNS web configuration because I remembered I updated the NAS FW to the latest 1.07, I saw UPnP AV Server was enabled by default, that's why I was getting the 501 access, now after rebooting the NAS I saw the access for the shared folder "102" changed to "root" from 501 "ls -al /mnt/device", I believe it should be pluto_charlie is this correct?? Becasue I still need SUDO to see the content of the "ls -al /mnt/device/102"
linuxmce@dcerouter:/home/public/data/audio$ ls -al
total 12
drwxrwsr-x 3 root public 4096 2009-07-31 20:57 .
drwxrwsr-x 11 root public 4096 2009-07-31 22:44 ..
drwxrwsr-x 2 pluto_charlie public 4096 2009-07-18 20:15 Arabic Helene 1
lrwxrwxrwx 1 root public 33 2009-07-31 20:57 Windows Share-Multimedia [102] -> /mnt/device/102/public/data/audio
linuxmce@dcerouter:/home/public/data/audio$ cd /mnt/device/102/
bash: cd: /mnt/device/102/: Permission denied
linuxmce@dcerouter:/home/public/data/audio$
UPDATE1
=======
Sorry back to square one, the mount still "501", I got it confused with the link access, and this also after reinstalling the NAS on the third time, disabling uPnP AV server settings didn't change anything
linuxmce@dcerouter:/mnt/device$ ls -al
total 4
drwxr-xr-x 3 root root 0 2009-08-01 21:13 .
drwxr-xr-x 4 root root 4096 2009-08-01 21:10 ..
drwxrwx--- 7 501 501 0 2009-06-17 23:15 102
linuxmce@dcerouter:/mnt/device$ cd /home/public/data/audio/
linuxmce@dcerouter:/home/public/data/audio$ ls -al
total 12
drwxr-xr-x 3 root public 4096 2009-08-01 21:11 .
drwxrwxr-x 11 root public 4096 2009-08-01 21:11 ..
drwxrwsr-x 2 pluto_charlie public 4096 2009-07-18 20:15 Arabic Helene 1
lrwxrwxrwx 1 root public 33 2009-08-01 21:11 Windows Share-Multimedia [102] -> /mnt/device/102/public/data/audio
linuxmce@dcerouter:/home/public/data/audio$
UPDATE 2
=======
I'm not sure if this will help, but I was able to rip a music CD (11songs in 20Minutes??) into the NAS and play it back on the MD, but not the Squeezebox
-
I don't know if its of any use to you but DNS-323...
uid 500 = admin
uid 501 = nobody
If you create a username/password on the dns uid = 502.
-
Pigdog - do you have a PC at all?? We seem to be having difficulty attracting attention from anyone else!
If you do, can you plug it into your internal network and share out a folder? Then tell LinuxMCE to add it once it is detected. Then check the above to see how LinuxMCE 0810 sees the permissions and ownership under /mnt/devices
btw, ccoudsi - you did try pigdogs trick of adding client lanman auth = yes into your smb.conf didn't you? That is a fix for a new level of security that Kubuntu required from 0804 onwards, and could be the thing that changes permissions/ownership on the mount.
-
HI,
Connected a old 20G drive to my Fedora and installed WIN2K.
Did an ipconfig and was address of 192.168.80.131 and gateway of 192.168.80.1 so I guess it worked.
Why is LinuxMCE detecting a DCS-5300G, Axis IP camera, Hauppauge MediaMVP and 2 Aastra SIP phones?
Did 'No, ignore at this time'.
Anyway added it as File Server. Reloaded Router. Might not be good because Fedora is dhcp.
I was asked for username/password for both drives.
I made directory just public. Created drives are 53 and 54.
DNS-323 is drive 50 and 51.
From LinuxMCE (no username/password on DNS)
ls -al /mnt/device
total 4
drwxr-xr-x 6 root root 0 date .
drwxr-xr-x 4 root root 4096 date ..
dr-xr-xr-x 2 root root 0 date 50
dr-xr-xr-x 2 root root 0 date 51
dr-xr-xr-x 2 root root 0 date 53
dr-xr-xr-x 2 root root 0 date 54
ls -al /mnt/device/50
total 50
drwxrwxrwx 5 root root 0 date .
drwxr-xr-x 6 root root 0 date ..
-rwxrwxrwx 1 501 501 0 date .check_mounted
drwxrwxrwx 3 501 501 0 date public
drwx------ 2 root root 0 date .systemfile
drwxrwxrwx 3 501 501 0 date user_1
Mounting 51 provided similar results.
Trying to mount 53 and 54 provided No such file or directory.
I don't really think I'd have to go much further with permissions because I can mount my DNS-323 no problem.
the . & .. directories plus .systemfile are root on DNS. The created files are 501 - nobody (all access r/w privilages)
My smb.conf has both
lanman auth = yes
client lanman auth = yes
but I have no username/password in DNS or required in device tree.
Is the DNS setup as all acess against each share with read write checked?
I will play around a bit to see if I can get WIN2K uid gid stuff on shared files in a directory.
-
Colin,
Yes, I did the modification in the beginning, adding client lanman auth = yes into your smb.conf
but because I was using user=all which means no password, I removed it.
I just purchased another NS4300N Promise Technology NAS just to test it with LinuxMCE, I've been using these NAS for a while, I just changed the workgroup to linuxmce, and added 1 drive for testing, it was PnP, I selected Public folder to use, it asked me for username/password, and voila I ripped another music CD to it and now i'm lisneting to it on my Squeezebox as I'm writting this post.
Here's the output for both shares DNS-323 & NS4300N
linuxmce@dcerouter:/mnt/device$ ls -al
total 4
drwxr-xr-x 4 root root 0 2009-08-02 21:00 .
drwxr-xr-x 4 root root 4096 2009-08-01 21:10 ..
drwxrwx--- 7 501 501 0 2009-06-17 23:15 102
drwxrwxrwx 6 root root 0 2009-08-02 09:59 104
linuxmce@dcerouter:/mnt/device$ cd /home/public/data/audio/
linuxmce@dcerouter:/home/public/data/audio$ ls -al
total 12
drwxrwsr-x 3 root public 4096 2009-08-02 20:59 .
drwxrwsr-x 11 root public 4096 2009-08-02 21:00 ..
drwxrwsr-x 2 pluto_charlie public 4096 2009-07-18 20:15 Arabic Helene 1
lrwxrwxrwx 1 root public 33 2009-08-02 20:59 Windows Share-Multimedia [102] -> /mnt/device/102/public/data/audio
lrwxrwxrwx 1 root public 33 2009-08-02 20:59 Windows Share-PUBLIC [104] -> /mnt/device/104/public/data/audio
linuxmce@dcerouter:/home/public/data/audio$ cd Windows\ Share-PUBLIC\ \[104\]
linuxmce@dcerouter:/home/public/data/audio/Windows Share-PUBLIC [104]$ ls -al
total 0
drwxrwxr-x 2 root public 0 2009-08-02 09:58 .
drwxr-xr-x 8 root 300 0 2009-08-02 09:58 ..
linuxmce@dcerouter:/home/public/data/audio/Windows Share-PUBLIC [104]$
Here's my smb.conf
[global]
## BEGIN : Domain and Hostname
workgroup = LinuxMCE
server string = DCERouter
netbios name = DCERouter
## END : Domain and Hostname
smb ports = 139
log level = 2
invalid users = root
log file = /var/log/samba/log.%m
max log size = 1000
syslog = 0
encrypt passwords = true
socket options = TCP_NODELAY
dns proxy = no
passwd program = /usr/bin/passwd %u
passwd chat = *Enter\snew\sUNIX\spassword:* %n\n *Retype\snew\sUNIX\spassword:* %n\n .
username map = /etc/samba/usermap.txt
unix extensions = yes
security = user
[public]
As far the Dlink NAS, not sure what to do???
Update2:
=======
I compared both configuration DNS-323 & NS4300N in the WebAdmin, there is 2 items are difference in the shared Folder first the read only check box in the DNS323 it says read only where in the NS4300N it is not checked, the second item is the admin username & password, so I added that to DNS-323 and I got the following output:
linuxmce@dcerouter:~$ cd /mnt/device/
linuxmce@dcerouter:/mnt/device$ ls -al
total 4
drwxr-xr-x 4 root root 0 2009-08-02 21:51 .
drwxr-xr-x 4 root root 4096 2009-08-01 21:10 ..
dr-xr-xr-x 2 root root 0 2009-08-02 21:49 102
drwxrwxrwx 6 root root 0 2009-08-02 10:50 104
linuxmce@dcerouter:/mnt/device$ ls -al /home/public/data/audio/
total 12
drwxrwsr-x 3 root public 4096 2009-08-02 21:49 .
drwxrwsr-x 11 root public 4096 2009-08-02 21:50 ..
drwxrwsr-x 2 pluto_charlie public 4096 2009-07-18 20:15 Arabic Helene 1
lrwxrwxrwx 1 root public 33 2009-08-02 21:49 Windows Share-Multimedia [102] -> /mnt/device/102/public/data/audio
lrwxrwxrwx 1 root public 33 2009-08-02 21:49 Windows Share-PUBLIC [104] -> /mnt/device/104/public/data/audio
linuxmce@dcerouter:/mnt/device$ $But still I can not "cd" to "Windows Share-Multimedia [102]" also on reboot I got a lot of CIFS VFS: send error....
It looks like it goes offline from the WebAdmin!!!I tried to check the box and reload, after it reload it says online but when I do "mount" it is not there only NS4300N, but when I do "ls -al /mnt/device" I see DNS-323 but not NS4300N, very confusing
//192.168.80.144/PUBLIC on /mnt/device/104 type cifs (rw,mand,unc=\\192.168.80.144\PUBLIC,username=admin,posixpaths,acl,rsize=16384,wsize=57344)
linuxmce@dcerouter:/home/public/data/audio$ cd /mnt/device/
linuxmce@dcerouter:/mnt/device$ ls -al
total 4
drwxr-xr-x 3 root root 0 2009-08-02 22:04 .
drwxr-xr-x 4 root root 4096 2009-08-01 21:10 ..
dr-xr-xr-x 2 root root 0 2009-08-02 21:49 102
linuxmce@dcerouter:/mnt/device$
-
I don't know if this is related but I have a Fedora 11 box that i have configured as a NAS server. Once I got passed the configuration stage of letting LMCE create the folder structure my Media was not visible on the orbiter. I did some digging around in the storage/network scripts and had to add "client lanman auth = yes" to the script "Network_Setup.sh", or you can add it directly to smb.conf.
I found that StorageDevices_StatusRadar.sh checks if a device is online using the smbclient as follows, and was always failing.
smbclient -U $Share_Username%$Share_Password "//$Device_IP/$Share_Name" -c 'pwd' 1>/dev/null 2>/dev/null
to test if your NAS device is online run this script from the core. If it returns 1 then your device is online.
/usr/pluto/bin/StorageDevices_StatusRadar.sh background
This solved my problem, hope it helps.
gadget
-
Hi gadget,
For clarification...on the DNS-323 if you have an username/password programmed Fedora or LMCE needs client lanman auth = yes in smb.conf or Network_Setup.sh to login.
On LMCE the share volumes under device tree need username/password fields programmed and use password checked.
If your are not using username/password then client lanman auth = yes is not required in smb.conf and no programming is required in LMCE share volumes.
All you need for LMCE is workgroup=linuxmce in either case.
Cheers.
-
Hi Pigdog,
You are correct. I did a test with smbclient using smbclient - u ""%"" and lanman auth is not required.
However i still think the Network_Setup.sh script requires the lanman auth for anyone adding a NAS that would like it to be secure by using a username/password.
gadget
-
Hi,
Secured networks = yes.
Unfortunately the DNS-323 support only password=share (windows weak passwords) and not password=domain. That's why you have to use lanman auth.
The DNS uses a modified Linux distro the only way to get around it is to hack it with ffp (fonz fun_plug) plus other steps.
To get around streaming audio for ccousdi he might have to go this route and look at http://wiki.dns323.info/.
Thanks.
-
Gadget,
I run “/usr/pluto/bin/StorageDevices_StatusRadar.sh background”
Here’s the output, they are both online!!
Tue, 04 Aug 2009 12:03:16 -0700 Device 101 (192.168.80.139) is online trying each of samba kids to see it they are still available
Tue, 04 Aug 2009 12:03:16 -0700 ----------------- DEVICE 102 1 (unchanged)
Tue, 04 Aug 2009 12:03:16 -0700 Device 103 (192.168.80.144) is online trying each of samba kids to see it they are still available
Tue, 04 Aug 2009 12:03:16 -0700 ----------------- DEVICE 104 1 (unchanged)
Here’s the results of my latest try.
I just went back to DNS-323, created a user “charlie” & password, assigned it to the shared folder "Multimedia", then I modified the “smb.conf“ I added the following line to the [Global] section:
lanman auth = yes
client lanman auth = yes
Then I went to WebAdmin and modified the Multimedia share folder, I added user “charlie” & password I checked the checkbox “required password” rebooted the core I got a lot of these messages
[ 469.667819] CIFS VFS: cifs_read_super: get root inode failed
[ 470.362566] CIFS VFS: Send error in QFSAttributeInfo = -5
[ 470.363052] CIFS VFS: Send error in QFSUnixInfo = -5
The results of this trial is, 102 share has root access now not 501, I can cd to it, but when I do “ls –al” I get no such file or directory???
linuxmce@dcerouter:/mnt/device$ ls -al
total 4
drwxr-xr-x 4 root root 0 2009-08-04 11:24 .
drwxr-xr-x 4 root root 4096 2009-08-04 11:01 ..
dr-xr-xr-x 2 root root 0 2009-08-04 11:01 102
drwxrwxrwx 6 root root 0 2009-08-04 00:23 104
linuxmce@dcerouter:/mnt/device$
linuxmce@dcerouter:/mnt/device$ cd 102
linuxmce@dcerouter:/mnt/device/102$ ls -al
ls: cannot open directory .: No such file or directory
linuxmce@dcerouter:/mnt/device/102$
Not sure what to do anymore on the D-link NAS, the NS4300N working as expected no issues,
Pigdog,
What is the FW version of your DNS-323, mine is 1.07??
-
Hi,
I tried 1.08 alpha but went back to 1.07.
Just to verify on the DNS.
When you created user group charlie you deleted the volume shares ALL and then created new volume shares with user group charlie r/w oplocks and archive = yes...
-
Yes, correct, I just updated my last post.
-
Here's the screenshot of the shared folder
-
Hi Charlie,
Is volume_1 and Multimedia the same HDD?
Multimedia is a directory under volume_1?
-
Pigdog,
That's correct.
-
Hi Charlie,
Is there a reason why you aren't using the LMCE directory tree?
It looks like you have created a folder under volume_1 called mutilmedia.
If you've done that you might have to play with the share name, Directories and other stuff in the device tree to get it recognized.
If you've got videos just put them in the public/data/videos directory and LMCE will deal with them. Music in public/data/music on the NAS.
Them it should be as simple as volume_1 Volume_1 user=charlie read/wite and oplocks/archive=yes (for windows systems if they are accessing).
-
pigdog,
I do have a linuxmce directory structure as follow:
/Volume_1/Multimedia/public/data/audio,documents,games,pictures,pvr,videos
/user_1
/user_2
I'm thinking to go ahead and use Volume_1 as the shared folder instead Multimedia, and move my data from Multimedia to Volume_1, then it will look exactly like yours, and my other NS4300N NAS.
I will let you know the results.
-
Hi Charlie,
The BT share is something different that you won't access from LMCE (Bit Torrent stuff) - You must have clicked the button - were you intending on using it?
You now have that NAS-PROG/BT directory. It's not easy to delete.
Anyway,
You must delete the volume_1 ALL share and the Multimedia share - which might have cause problems, the 2 of them existing, in the first place.
LMCE directory structure would not have listed multimedia in the main menu Media>subfolder anyway.
This would have to have been mounted as public originally and not using the LMCE directory tree.
We started all of this because our public folders weren't coming up properly because of the changes in 810 & the DNS version needing to be 1.07 or higher than we oriiginally were.
When you are finished you should have, with user "charlie" and password,
Share = volume_1
Path = volume_1
User/Group = charlie
oplock/archive=yes
r/w=checked.
Then with video in /public/data/video, music in public/data/music you should get it listed from main menu>videos or music
with username/password/ password required checked in device tree.
Cheers-Beers.
-
pigdog,
I enabled this BT in the past to test it out, I'm not intending to use it with LMCE.
I'm planning to move my data to NS4300N then re-format the D-link and start from scratch.
-
Hi Charlie,
:o Reformat seems extreme - is that because you tried get rid of the BT directory?
-
That's correct.
-
I managed to get rid of it using the smbclient command to deleted what I could.
Then I had to upgrade to 1.08 which allowed me to removed the rest.
In 1.08 BT is a module (there is a NAS module - which I tried for my problem) that has to be added instead of something that gets bundled automatically.
Then I de-graded to 1.07 because the NAS module didn't help.
Finding the 1.08 beta patch was a little stupid.
-
Well, I went back and re-formatted the DNS-323 NAS, and re-installed it on my core using "Volume_1" as the shared folder, removed "user=all", added new user, and that's it, worked as expected.
The access issue I had before using the squeezebox could be related to the following issues "either one or both", was not sure which one:
1) I was using /Volume_1/Multimedia as my shared folder where now i'm using the root directory /Volume_1
2) The NAS had already data copied from Windows machine into already created directory structure, where now I started with clean drive, then after LMCE added the shared folder, I copied my data to the directories that was already created for me
Thanks to all the people who supported me :)
-
ccoudsi - its gone through so many convoluted twists and turns to get here... could you please summarise only the necessary steps to get the NAS working in a wiki article?
-
Colin,
Sure no problem, I'll try to completed by this weekend.
-
Hi Charlie & Colin,
My personal 2 cents is I think the problem was having the share as ALL access and then the Multimedia subdir as Charlie user on the DNS-323.
I think it's hierarchical related. The linux version seems to be pretty dumb-downed on the NAS.
When I started my journey down the rabbit hole my troubles began as public directory structure, ALL access.
Which was fine in earlier alphas. There has been work in pluto-storage/network/etc. and things haven't been as lenient.
Changing to LMCE directory tree, I'm still ALL access- r/w, no username/password has allowed my media to be fully detected.
I have one odd problem I'm still trying to investigate IF i could only figure out how to create an ip3v2 GEOB.
Until the next challenge.
Cheers guys.
-
It does not look I'm done with this yet, when I came home the D-link was off-line but not the NS4300N, after quick look I noticed as soon I turn any MD ON, the D-link goes off-line and the Readonly checkbox is checked even though it is still mounted, so I unchecked the Readonly and checked Online checkbox, reloaded the router, now it is On-line, as long as I don't reboot any MD, or turn ON an MD that was OFF??
I already checked http://forum.linuxmce.org/index.php?topic=8517.msg57073#msg57073 (http://forum.linuxmce.org/index.php?topic=8517.msg57073#msg57073)
If I understood it correctly, I do have the modifications of the SMB.CONF, and I have 1.07 FW !!! Just a note my NS4300N does not have a password on the shared folder, is this why it stays ON-LINE ???
Any clues ???
-
Don't forget! MD's don't access their media through the core, they do it directly. They only use the core as the central media library (the MySQL database pluto_media) to look up the media... then because of the clever way that LMCE mounts the remote shares and symlinks them to construct a consistent folder structure, the "local" path to media on the core/hybrid and all MDs appears to be exactly the same.
So each MD constructs the consistent path to the media on the "local" filesystem, then accesses this file to play it. For your NAS, this means the MD then uses its own SAMBA client to connect to the NAS directly (not the core's). Your MD's SAMBA client is causing the same issue as your core was as you haven't modified its configuration yet. And any MD can end up marking the media device as offline/readonly/whatever. So that is what is happening.
Make the same changes on your MD (either directly, or by cd'ing into /usr/pluto/diskless/<MDdevice#>/etc/blahblah), then reboot all MDs and Core....
-
Colin,
Thank you for the explanation, I SSH from the core to the MDs, and modified "smb.conf", that took care of the On-line problem.
Last night when I was trying to figure out the problem with the MDs, I SSH to the MD from the core, I did "apt-get update & dist-upgrade" also I installed "libdvdcss2 & w32codecs" to play DVD, then I rebooted the MD it stalled on the PVR-150, same results on the other MD, then I went back to WebAdmin and recreated the images rebooted the MDs then I got the AVwizard, is this a correct way to update the MDs?? because I noticed the "libdvdcss2 & w32codecs" were not installed, I had to reinstall them again???
-
Rebuilding an MD's image will not update it to the same config or version as the core, because the images are unzipped from an archive on the core, not based on the core's files themselves. So yes, if you rebuild the image, you need to re-do any upgrades/config-changes to the MDs manually. I don't know why what you did, didn't work as I have never tried to do this. Sounds like it should have....
-
if I understood you correctly, if I do "apt-get update & dist-upgrade" on the MD, and reboot the MD, it should come up with the latest version?? and no need to do any image rebuild.
In my case the core has the latest version, the MD has an older version, what I did is, I updated the MD first then it didn't boot, so I rebuilt the images and rebooted the MD and it was ok with the matching version as the core using the orbiter "Advanced screen" .
From your reply, I should have and older version on the MD not the new version because I did an image rebuild? right??
-
As I say, I don't know how you are supposed to upgrade an MD.
However, rebuilding an MD image will rebuild it to whatever version is packed inside the MD image archive sitting on the core. If you modify the core versions or config manually, these changes will not appear in an MD when you rebuild it, as the MD image archive will still contain the original image for the version of the core that you installed.
However, if you update the core's LMCE version using the update/dist-upgrade approach (ie automatically), then presumably those updates will also include a new MD image archive (its basically just like a zip file that contains a basic LMCE installation for an MD) which is at the same version as your newly updated core. So from then, if you rebuild an MD image, it will be based on the files in this new archive and so be at the same level as your core....
-
Thanks, Colin I got it. :)