pgnyc

hi, subject : cannot do a tar incremental on a share linked to a docker. so , i have a share connected to a docker ( piwigo ) , and when i do a tar with incremental option, it doesn't work. Another share with a copy of the same files , no pb. i tried with the docker stopped , same effect. Can someone explain to me the reason why ? Regards, Pascal

THX.

hi knex666 is the docker install MariaDB ? i installed 3 days ago for test with sqllite , was working but the install of onlyoffice document server was missing !!! So did a new install and was trying with MariaDB but got error. by the way , continued with sqllite and now i have onlyoffice document server running. regards, pascal

hi, what would be the best way to upgrade a VM debian from stretch to buster ? thx Pascal

hi ! First : thank you for this plugin second: Could you add the name of the system in the email subject status report ? i was pre-clearing 2 drives in 2 differents system at the same time and couldn't know which system it was in the email. thx.

yes you are right , i could have use a unassigned devices drive , but since i was using a terminal screen , i did not think about it , was not on a df listing !!! same using an array disk !!! next time !! in fact , the biggest pb is everything works so well, that you do not touch and forget . Pascal

hello, i had the same pb yesterday, trying to go from 6.3.2 to 6.5.3. i have the same rootfs size : 867M used 700M. After tracking the pb to not enough space in /tmp for download and unzip. my solution was to move /tmp to /boot because i have 7G available there ( i know i was using the usb stick for that) [do not copy, if you do not understand] mv /tmp to /tmpori (rename tmp) ln -s /tmp /boot/tmp (create a link from /tmp to /boot/tmp) mkdir /boot/tmp tested by touch /tmp/toto , ls -l /boot/tmp , ok the file toto is present cp -R * /tmpori /tmp ( recopy old tmp to new tmp) and there upgrade , everything went fine , reboot , OK , restart array , OK. My new rootfs is : rootfs 867M 703M 165M 81% / i think i will have to do the same for each upgrade, since i have only 2G memory and no pb for a file server only purpose.

NEWS : so i tried with cpu mode = QEMU and now it's working. why the original setting is not working ( host passthrough ) ?

hello, so i have a pb with an upgrade to 6.4.0 from 6.3.5 . a VM slackware 64 14.2 has a kernel panic at startup. the server is new, i just created 2 VM , a debian and a slackware, they were up and running on 6.3.5 . that's all i did not even started to do something with them just created an started. with 6.4.0 , the debian VM is still running ok. but not the slackware. the boot screen is ok , the kernel start but panic immediately. if try to create another VM , i have the grub page and nothing more after. here diagnostic and screnshoot. Pascal. Templates aserv1-diagnostics-20180126-1411.zip