@george1421
Hello george,
I did not succeed in restoring the database, I do a complete reinstallation of the server.
Thank you for everything

@george1421
Hello george,
I did not succeed in restoring the database, I do a complete reinstallation of the server.
Thank you for everything

@george1421
thank you for your answer george, I go through google translate that’s why I take time to answer
I will try to rebuild the database as you told me, tomorrow because suir I have to go to bed, I will work early tomorrow
I’ll keep you informed tomorrow
thank you

@george1421
I plugged the disk into usb and I had 0 bytes left. I then deleted 3 disk images and then I plugged the disk back into the computer, it started (no more problem with maria DB).
I then have in firefox: Database connection unavailable

@george1421
Here is the result
I removed 3 disk images to restart the PC

@george1421

Voici le résulltat:

Sys. de fichiers Taille Utilisé Dispo Uti% Monté sur
udev               7,8G       0  7,8G   0% /dev
tmpfs              1,6G    1,9M  1,6G   1% /run
/dev/sda2          1,9T    1,7T   53G  98% /
tmpfs              7,8G     57M  7,8G   1% /dev/shm
tmpfs              5,0M    4,0K  5,0M   1% /run/lock
tmpfs              7,8G       0  7,8G   0% /sys/fs/cgroup
/dev/loop0         2,5M    2,5M     0 100% /snap/gnome-calculator/826
/dev/loop1         1,0M    1,0M     0 100% /snap/gnome-logs/100
/dev/loop2          98M     98M     0 100% /snap/core/10185
/dev/loop3         146M    146M     0 100% /snap/opera/99
/dev/loop4         163M    163M     0 100% /snap/gnome-3-28-1804/145
/dev/loop6          15M     15M     0 100% /snap/gnome-characters/399
/dev/loop5         3,8M    3,8M     0 100% /snap/gnome-system-monitor/127
/dev/loop8         4,3M    4,3M     0 100% /snap/gnome-calculator/544
/dev/loop7         146M    146M     0 100% /snap/opera/97
/dev/loop10         45M     45M     0 100% /snap/gtk-common-themes/1440
/dev/loop9          55M     55M     0 100% /snap/core18/1668
/dev/loop11        161M    161M     0 100% /snap/gnome-3-28-1804/116
/dev/loop12        1,0M    1,0M     0 100% /snap/gnome-logs/81
/dev/loop14         56M     56M     0 100% /snap/core18/1932
/dev/loop13        218M    218M     0 100% /snap/gnome-3-34-1804/60
/dev/loop15        2,3M    2,3M     0 100% /snap/gnome-system-monitor/148
/dev/loop16         33M     33M     0 100% /snap/chromium-ffmpeg/17
/dev/loop18         63M     63M     0 100% /snap/gtk-common-themes/1506
/dev/loop17         90M     90M     0 100% /snap/core/8268
/dev/loop19        384K    384K     0 100% /snap/gnome-characters/570
/dev/sda1          511M    6,1M  505M   2% /boot/efi
tmpfs              1,6G     40K  1,6G   1% /run/user/1000

@george1421 @Sebastian-Roth
apologies, as I’m not the one using fog I didn’t think about looking at the disk space.
I was able to arrive on the graphical interface, but on firefox I cannot connect: Database connection unavailable
I think the database did not like :
2021-03-01 19:01:48 140500859161728 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB.

2021-03-01 19:01:48 140500859161728 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2021-03-01 19:01:48 140500859161728 [Note] InnoDB: The InnoDB memory heap is disabled
2021-03-01 19:01:48 140500859161728 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2021-03-01 19:01:48 140500859161728 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2021-03-01 19:01:48 140500859161728 [Note] InnoDB: Compressed tables use zlib 1.2.11
2021-03-01 19:01:48 140500859161728 [Note] InnoDB: Using Linux native AIO
2021-03-01 19:01:48 140500859161728 [Note] InnoDB: Using SSE crc32 instructions
2021-03-01 19:01:48 140500859161728 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2021-03-01 19:01:48 140500859161728 [Note] InnoDB: Completed initialization of buffer pool
2021-03-01 19:01:48 140500859161728 [Note] InnoDB: Highest supported file format is Barracuda.
2021-03-01 19:01:48 140500859161728 [Note] InnoDB: 128 rollback segment(s) are active.
2021-03-01 19:01:48 140500859161728 [Note] InnoDB: Waiting for purge to start
2021-03-01 19:01:48 140500859161728 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.46-86.2 started; log sequence number 1618255
2021-03-01 19:01:48 140500187215616 [Note] InnoDB: Dumping buffer pool(s) not yet started
2021-03-01 19:01:48 140500859161728 [Note] Plugin ‘FEEDBACK’ is disabled.
2021-03-01 19:01:48 140500859161728 [Note] Recovering after a crash using tc.log
2021-03-01 19:01:48 140500859161728 [ERROR] Can’t init tc log
2021-03-01 19:01:48 140500859161728 [ERROR] Aborting

@sebastian-roth
I installed the server last year in January or February , the FOG station has never been updated.

@sebastian-roth
here are the screenshots

@sebastian-roth
Thank you very much for your answer.
The old system does not start anymore, when loading it becomes very slow and crashes at the level of maria DB

I think the SSD is broken
I will try to reinstall fog identically (ubuntu 18.04 and fog 1.5.8)
thank you for your reply.

Hello
I had a fog 1.5.8 server on ubuntu 18.04, but the system crashed, how can I restore the images and hosts to the new fog 1.5.9 (ubuntu 20.04) system?
I copied the / opt / fog and / images directories and executed chmod 777 –vR / images but the images and hosts do not appear on the fog interface.
thank you for your answers