KatieKat

Rebooted again and have an ip address now, so im able to get back into the webgui

I was wrong about that syslog, it was only for a specific day that i was apparently playing with the syslog settings. pictures of the terminal work? how can you scroll up to look at things before the tower login?

okay so ram is my entire problem? ive been booting fine for 40 days, why wont it boot now?

and i have 2gb?

The wiki is here. What i dont understand is that is basically all im trying to do is a basic nas.

As per the wiki, i have over twice the amount i need. to use this as a basic nas.... is that not correct? Not trying to argue. its just been a frustrating little event here.

So went and tried to boot in the same manner, didnt work, so i tried to save the diag file to the flash drive and powerdown. the terminal said that the flashdrive has no space. but its got 3.7gb left? and the file its trying to create in the drive is only a couple of mb at best? very very odd. i do however have the full syslog?

Whoops sorry, one moment, thank you ,

after trying to boot several times with no luck, dockers shut off in the config on the flash drive. tower-diagnostics-20200629-1523.zip

Im sorry, i should have read that again and thought about it before i posted i only run "netdata" i believe? and this is why i only use this singular docker currently.

Thank you so much for the help thus far. How do i figure out which docker is the problem child?

Also new problem, when i went to reboot in safemode, (safemode gui) It never set an ip adress. so i cant admin the server, and at the same it never booted into a GUI, ie, its still in the terminal command line structure. Sorry my jargons a little off, im still learning.

to confirm, rootfs is the flashdrive correct?

I was migrating user files after a clean install of windows on a clients computer (pulling from the server back onto the laptop) and keep getting this error and have no idea where to start on this one. UNRAID 6.8.3 on a trial. tower-diagnostics-20200629-1425.zip