General > Installation issues

update problems/mistakes made(solved)

(1/2) > >>

S4Howie:
In a nighly crazyness i acidently applied the LTS security updates on 1 MD.It told me Warning i should apply security updates to my hardware stack to get LTS support.But now this MD is somekind of broken. If i want to boot up it loads the vmlinuz but then it
stoping and telling me Could not find ramdisk image;   XX/initrd.img

If i look into the tftp folder the symlinks are there for initrd.img. I tried to copy the symlinks from a folder of another MD then the broken MD boots up but its then updating itself again and rebooting and then again telling Could not find ramdisk image;   XX/initrd.img

so i went into LinuxMCE admin to MD Section and rebuild the image. The rebuild MD boots up but its then updating itself again and rebooting and then again telling Could not find ramdisk image;   XX/initrd.img

I even deleted the MD,setup a new with all new Device names. It boots up applying itself updates reboots and same again Could not find ramdisk image;   XX/initrd.img.

Is there a way to get it back normal?Why even after delete and new setup it seems to apply the security updates?How can i stop that now?And just let it do the normal updates when i setup a new 1 or rebuild the image?I hope there is a way.

Thanks so far

phenigma:
What version of lmce are you running and please post the contents of your pluto.conf file.

Sent from my Nexus 5 using Tapatalk

Marie.O:
I had issues with the LTS stack as well. It was caused by the newer initrd images being larger than 32M, which causes issues with tftp. To fix it, I switched back to the old initrd and vmlinuz.

kernel upgrade brought me initrd.img-4.4.0-62-generic, now I am back at initrd.img-3.16.0-77-generic - same for the vmlinuz.

That fix helped me, but is just a band aid.

S4Howie:
Thanks for the fast awnsers.

@phenigma build is 14.04 Version: 2.0.0.47.201609281853+9638f5bc on the core

   pluto.conf from core is:
   
PK_Device = 1
MySqlDBName = pluto_main
Display = 0
PlutoVersion = 2.0.0.47.201702201459+325cc736
LogLevels = 1,5,7,8
AutostartMedia = 1
AVWizardDone = 1
Bookmark_Media = 4,5
RA_CheckRemotePort = 1
MySqlHost = localhost
MySqlUser = root
MySqlPassword =
DCERouter = localhost
MySqlPort = 3306
DCERouterPort = 3450
Activation_Code = 1111
PK_Installation = 1047743
PK_Users = 1
PK_Distro = 21
UseVideoWizard = 1
AutostartCore = 1
LTS_HES = -lts-utopic
fw_blocklist=0
DisableIPv4Firewall=1
DisableIPv6Firewall=1
AdvancedFirewall=0
Show_all_rules=0
fwVersion=ipv6
FirstBoot = false
TimeZoneSet = 1
DesktopActivated = 1
LastSearchTokenUpdate=1489087065
OfflineMode = false
AVWizardOverride = 0
DVDKeysCache = /home/.dvdcss
AddInternetRadio=0
fwVersion=ipv4
DisableIPv4Firewall=1
DisableIPv6Firewall=0
DisableIPv4Firewall=0
DisableIPv6Firewall=0
DisableIPv4Firewall=1
DisableIPv6Firewall=0
DisableIPv4Firewall=1
DisableIPv6Firewall=1
fwVersion=ipv6
DisableIPv4Firewall=1
DisableIPv6Firewall=0
DisableIPv4Firewall=0
DisableIPv6Firewall=0
fwVersion=ipv4
DisableIPv4Firewall=1
DisableIPv6Firewall=0

@posde Yes excactly the newer init.rd is a bit over 32 MB,looks like you are all right with this.
             But i dont understand how to switch back now?

Thank you

Marie.O:
I just re-linked the older (3.x) init.rd and vmlinuz files and rebooted. And take care not to apt-get autoremove them ;)

Navigation

[0] Message Index

[#] Next page