June 16, 201313 yr Hi guys, I am seeing this lately every time i rebooted in the syslog. Do i need to worry about this? Jun 16 16:21:19 Tower kernel: initial memory mapped: [mem 0x00000000-0x01bfffff] Jun 16 16:21:19 Tower kernel: Base memory trampoline at [c0096000] 96000 size 16384 Jun 16 16:21:19 Tower kernel: init_memory_mapping: [mem 0x00000000-0x000fffff] Jun 16 16:21:19 Tower kernel: [mem 0x00000000-0x000fffff] page 4k (Errors) Jun 16 16:21:19 Tower kernel: init_memory_mapping: [mem 0x37800000-0x379fffff] Jun 16 16:21:19 Tower kernel: [mem 0x37800000-0x379fffff] page 2M (Errors) Jun 16 16:21:19 Tower kernel: init_memory_mapping: [mem 0x34000000-0x377fffff] Jun 16 16:21:19 Tower kernel: [mem 0x34000000-0x377fffff] page 2M (Errors) Jun 16 16:21:19 Tower kernel: init_memory_mapping: [mem 0x00100000-0x33ffffff] Jun 16 16:21:19 Tower kernel: [mem 0x00100000-0x001fffff] page 4k (Errors) Jun 16 16:21:19 Tower kernel: [mem 0x00200000-0x33ffffff] page 2M (Errors) Jun 16 16:21:19 Tower kernel: init_memory_mapping: [mem 0x37a00000-0x37bfdfff] Jun 16 16:21:19 Tower kernel: [mem 0x37a00000-0x37bfdfff] page 4k (Errors) Jun 16 16:21:19 Tower kernel: BRK [0x01620000, 0x01620fff] PGTABLE Jun 16 16:21:19 Tower kernel: RAMDISK: [mem 0x7dfa4000-0x7fffffff] Jun 16 16:21:19 Tower kernel: Allocated new RAMDISK: [mem 0x35ba2000-0x37bfdffb] Jun 16 16:21:19 Tower kernel: Move RAMDISK from [mem 0x7dfa4000-0x7ffffffb] to [mem 0x35ba2000-0x37bfdffb]
June 16, 201313 yr Hi guys, I am seeing this lately every time i rebooted in the syslog. Do i need to worry about this? Jun 16 16:21:19 Tower kernel: initial memory mapped: [mem 0x00000000-0x01bfffff] Jun 16 16:21:19 Tower kernel: Base memory trampoline at [c0096000] 96000 size 16384 Jun 16 16:21:19 Tower kernel: init_memory_mapping: [mem 0x00000000-0x000fffff] Jun 16 16:21:19 Tower kernel: [mem 0x00000000-0x000fffff] page 4k (Errors) Jun 16 16:21:19 Tower kernel: init_memory_mapping: [mem 0x37800000-0x379fffff] Jun 16 16:21:19 Tower kernel: [mem 0x37800000-0x379fffff] page 2M (Errors) Jun 16 16:21:19 Tower kernel: init_memory_mapping: [mem 0x34000000-0x377fffff] Jun 16 16:21:19 Tower kernel: [mem 0x34000000-0x377fffff] page 2M (Errors) Jun 16 16:21:19 Tower kernel: init_memory_mapping: [mem 0x00100000-0x33ffffff] Jun 16 16:21:19 Tower kernel: [mem 0x00100000-0x001fffff] page 4k (Errors) Jun 16 16:21:19 Tower kernel: [mem 0x00200000-0x33ffffff] page 2M (Errors) Jun 16 16:21:19 Tower kernel: init_memory_mapping: [mem 0x37a00000-0x37bfdfff] Jun 16 16:21:19 Tower kernel: [mem 0x37a00000-0x37bfdfff] page 4k (Errors) Jun 16 16:21:19 Tower kernel: BRK [0x01620000, 0x01620fff] PGTABLE Jun 16 16:21:19 Tower kernel: RAMDISK: [mem 0x7dfa4000-0x7fffffff] Jun 16 16:21:19 Tower kernel: Allocated new RAMDISK: [mem 0x35ba2000-0x37bfdffb] Jun 16 16:21:19 Tower kernel: Move RAMDISK from [mem 0x7dfa4000-0x7ffffffb] to [mem 0x35ba2000-0x37bfdffb] no need to worry, it is just telling you how memory is being allocated. If you update your version of unMENU, the extra error message will go away. (An old pattern in the syslog_match.conf file matched some "mem" lines.) The update will download and install the new files that will fix that.
June 16, 201313 yr Author Updated unmenu, checked and updated three times but this one will not update: Downloading myMain_local.conf rev $Revision: 182 $ $Date: 2010-12-04 08:15:52 -0500 (Sat, 04 Dec 2010)$ 5a0630afc49c196a23db71a5d02bf18f != a5d02879e3d52eb0dffda20f12d0111c or 7799da8e46bf08d7a328617cb1a48442, /tmp/unmenu_tmp/myMain_local.conf not installed Now rebooting
June 16, 201313 yr Updated unmenu, checked and updated three times but this one will not update: Downloading myMain_local.conf rev $Revision: 182 $ $Date: 2010-12-04 08:15:52 -0500 (Sat, 04 Dec 2010)$ 5a0630afc49c196a23db71a5d02bf18f != a5d02879e3d52eb0dffda20f12d0111c or 7799da8e46bf08d7a328617cb1a48442, /tmp/unmenu_tmp/myMain_local.conf not installed Now rebooting myMain_local will NEVER install itself. It is the "local" file where YOU put local changes (if any) If you've not made changes, you can just delete the existing file and the new will be put int place when you next check updates, or you can type: cp /tmp/unmenu_tmp/myMain_local.conf /boot/unmenu/myMain_local.conf
June 16, 201313 yr Author Also,.. not related. If i want to stop the array i am getting Retry unmounting over and over and over and over.. I need to go to unmenu array management and stop the array there to get it to stop.
June 16, 201313 yr Also,.. not related. If i want to stop the array i am getting Retry unmounting over and over and over and over.. That indicates one of your add-ons has an open file on one of the array disks, or a process that has one of the disks as its current directory. You MUST stop your add-ons prior to stopping the unRAID array. I need to go to unmenu array management and stop the array there to get it to stop. That button will KILL the processes holding disks busy, but it does not do it as gracefully as if you stop them correctly. As I said, it just blindly sends them a KILL signal. I recommend you get updated add-ons that tie into the 5.0 event system to stop themselves.
June 16, 201313 yr Author hmmm: cp: cannot stat `/tmp/unmenu_tmp/myMain_local.conf': No such file or directory root@Tower:~# ls mdcmd* mkmbr* powerdown@ samba@ root@Tower:~# cd .. root@Tower:/# ls bin/ dev/ home/ lib/ proc/ sbin/ tmp/ var/ boot/ etc/ init@ mnt/ root/ sys/ usr/ root@Tower:/# cp /tmp/unmenu_tmp/myMain_local.conf /boot/unmenu/myMain_local.conf cp: cannot stat `/tmp/unmenu_tmp/myMain_local.conf': No such file or directory root@Tower:/# cd tmp root@Tower:/tmp# ls crontab root@Tower:/tmp#
June 16, 201313 yr An add-on (or telnet session) is accessing the array. Do not use unMenu to stop the array. Fix the config of the add-on.
June 16, 201313 yr hmmm: cp: cannot stat `/tmp/unmenu_tmp/myMain_local.conf': No such file or directory root@Tower:~# ls mdcmd* mkmbr* powerdown@ samba@ root@Tower:~# cd .. root@Tower:/# ls bin/ dev/ home/ lib/ proc/ sbin/ tmp/ var/ boot/ etc/ init@ mnt/ root/ sys/ usr/ root@Tower:/# cp /tmp/unmenu_tmp/myMain_local.conf /boot/unmenu/myMain_local.conf cp: cannot stat `/tmp/unmenu_tmp/myMain_local.conf': No such file or directory root@Tower:/# cd tmp root@Tower:/tmp# ls crontab root@Tower:/tmp# You apparently rebooted? If so, it is gone. /tmp is in memory. Just type: rm /boot/unmenu/myMain_local.conf and then check for updates once more. It will get installed.
June 16, 201313 yr Author Also,.. not related. If i want to stop the array i am getting Retry unmounting over and over and over and over.. That indicates one of your add-ons has an open file on one of the array disks, or a process that has one of the disks as its current directory. You MUST stop your add-ons prior to stopping the unRAID array. I need to go to unmenu array management and stop the array there to get it to stop. That button will KILL the processes holding disks busy, but it does not do it as gracefully as if you stop them correctly. As I said, it just blindly sends them a KILL signal. I recommend you get updated add-ons that tie into the 5.0 event system to stop themselves. Ahhh i think i know what that is. My logitech media server...
June 16, 201313 yr Author hmmm: cp: cannot stat `/tmp/unmenu_tmp/myMain_local.conf': No such file or directory root@Tower:~# ls mdcmd* mkmbr* powerdown@ samba@ root@Tower:~# cd .. root@Tower:/# ls bin/ dev/ home/ lib/ proc/ sbin/ tmp/ var/ boot/ etc/ init@ mnt/ root/ sys/ usr/ root@Tower:/# cp /tmp/unmenu_tmp/myMain_local.conf /boot/unmenu/myMain_local.conf cp: cannot stat `/tmp/unmenu_tmp/myMain_local.conf': No such file or directory root@Tower:/# cd tmp root@Tower:/tmp# ls crontab root@Tower:/tmp# You apparently rebooted? If so, it is gone. /tmp is in memory. Just type: rm /boot/unmenu/myMain_local.conf and then check for updates once more. It will get installed. Still wont install 'root@Tower:/# cd tmp root@Tower:/tmp# ls crontab unmenu_new_files unmenu_release_list Did a check for updates and install updates Downloading myMain_local.conf rev $Revision: 182 $ $Date: 2010-12-04 08:15:52 -0500 (Sat, 04 Dec 2010)$ 5a0630afc49c196a23db71a5d02bf18f != a5d02879e3d52eb0dffda20f12d0111c or 7799da8e46bf08d7a328617cb1a48442, /tmp/unmenu_tmp/myMain_local.conf not installed root@Tower:/tmp# ls crontab unmenu_new_files unmenu_release_list unmenu_tmp/ root@Tower:/tmp# cd unmenu_tmp root@Tower:/tmp/unmenu_tmp# ls myMain_local.conf root@Tower:/tmp/unmenu_tmp# rm -f myMain_local.conf Again did a check and a install Downloading myMain_local.conf rev $Revision: 182 $ $Date: 2010-12-04 08:15:52 -0500 (Sat, 04 Dec 2010)$ 5a0630afc49c196a23db71a5d02bf18f != a5d02879e3d52eb0dffda20f12d0111c or 7799da8e46bf08d7a328617cb1a48442, /tmp/unmenu_tmp/myMain_local.conf not installed root@Tower:/tmp/unmenu_tmp# ls myMain_local.conf root@Tower:/tmp/unmenu_tmp#
June 16, 201313 yr Author Hi guys, I am seeing this lately every time i rebooted in the syslog. Do i need to worry about this? Jun 16 16:21:19 Tower kernel: initial memory mapped: [mem 0x00000000-0x01bfffff] Jun 16 16:21:19 Tower kernel: Base memory trampoline at [c0096000] 96000 size 16384 Jun 16 16:21:19 Tower kernel: init_memory_mapping: [mem 0x00000000-0x000fffff] Jun 16 16:21:19 Tower kernel: [mem 0x00000000-0x000fffff] page 4k (Errors) Jun 16 16:21:19 Tower kernel: init_memory_mapping: [mem 0x37800000-0x379fffff] Jun 16 16:21:19 Tower kernel: [mem 0x37800000-0x379fffff] page 2M (Errors) Jun 16 16:21:19 Tower kernel: init_memory_mapping: [mem 0x34000000-0x377fffff] Jun 16 16:21:19 Tower kernel: [mem 0x34000000-0x377fffff] page 2M (Errors) Jun 16 16:21:19 Tower kernel: init_memory_mapping: [mem 0x00100000-0x33ffffff] Jun 16 16:21:19 Tower kernel: [mem 0x00100000-0x001fffff] page 4k (Errors) Jun 16 16:21:19 Tower kernel: [mem 0x00200000-0x33ffffff] page 2M (Errors) Jun 16 16:21:19 Tower kernel: init_memory_mapping: [mem 0x37a00000-0x37bfdfff] Jun 16 16:21:19 Tower kernel: [mem 0x37a00000-0x37bfdfff] page 4k (Errors) Jun 16 16:21:19 Tower kernel: BRK [0x01620000, 0x01620fff] PGTABLE Jun 16 16:21:19 Tower kernel: RAMDISK: [mem 0x7dfa4000-0x7fffffff] Jun 16 16:21:19 Tower kernel: Allocated new RAMDISK: [mem 0x35ba2000-0x37bfdffb] Jun 16 16:21:19 Tower kernel: Move RAMDISK from [mem 0x7dfa4000-0x7ffffffb] to [mem 0x35ba2000-0x37bfdffb] no need to worry, it is just telling you how memory is being allocated. If you update your version of unMENU, the extra error message will go away. (An old pattern in the syslog_match.conf file matched some "mem" lines.) The update will download and install the new files that will fix that. The updates that did install have worked and the memory errors are gone from the syslog ;D
June 16, 201313 yr Hi guys, I am seeing this lately every time i rebooted in the syslog. Do i need to worry about this? Jun 16 16:21:19 Tower kernel: initial memory mapped: [mem 0x00000000-0x01bfffff] Jun 16 16:21:19 Tower kernel: Base memory trampoline at [c0096000] 96000 size 16384 Jun 16 16:21:19 Tower kernel: init_memory_mapping: [mem 0x00000000-0x000fffff] Jun 16 16:21:19 Tower kernel: [mem 0x00000000-0x000fffff] page 4k (Errors) Jun 16 16:21:19 Tower kernel: init_memory_mapping: [mem 0x37800000-0x379fffff] Jun 16 16:21:19 Tower kernel: [mem 0x37800000-0x379fffff] page 2M (Errors) Jun 16 16:21:19 Tower kernel: init_memory_mapping: [mem 0x34000000-0x377fffff] Jun 16 16:21:19 Tower kernel: [mem 0x34000000-0x377fffff] page 2M (Errors) Jun 16 16:21:19 Tower kernel: init_memory_mapping: [mem 0x00100000-0x33ffffff] Jun 16 16:21:19 Tower kernel: [mem 0x00100000-0x001fffff] page 4k (Errors) Jun 16 16:21:19 Tower kernel: [mem 0x00200000-0x33ffffff] page 2M (Errors) Jun 16 16:21:19 Tower kernel: init_memory_mapping: [mem 0x37a00000-0x37bfdfff] Jun 16 16:21:19 Tower kernel: [mem 0x37a00000-0x37bfdfff] page 4k (Errors) Jun 16 16:21:19 Tower kernel: BRK [0x01620000, 0x01620fff] PGTABLE Jun 16 16:21:19 Tower kernel: RAMDISK: [mem 0x7dfa4000-0x7fffffff] Jun 16 16:21:19 Tower kernel: Allocated new RAMDISK: [mem 0x35ba2000-0x37bfdffb] Jun 16 16:21:19 Tower kernel: Move RAMDISK from [mem 0x7dfa4000-0x7ffffffb] to [mem 0x35ba2000-0x37bfdffb] no need to worry, it is just telling you how memory is being allocated. If you update your version of unMENU, the extra error message will go away. (An old pattern in the syslog_match.conf file matched some "mem" lines.) The update will download and install the new files that will fix that. The updates that did install have worked and the memory errors are gone from the syslog ;D Ignore the message about the file not being installed. You don't need it. Joe L.
Archived
This topic is now archived and is closed to further replies.