About your bad disk, use something like smartctl to find out the s/n on the physical devices and then check on the actual drives stickers. There are probably better ways but when a disk is dead, all we want is to be 100% sure before disconnecting it. I know I did that the last time a drive died. Thanks for a good video. I needed the reminder to check my own servers logs.
Could you please discuss about bsd rc and differences between bsd rc and sys v rc since managing rc in bsd seems to be an odd one for those who come from sys v types like solaris etc. and, did you say anything about "tail -f" to capture the log entries that update dynamically! Thanks for the video. 👍
Old school, to work on win 7 and some clasters on FreeBSD instances with high loads staff. I always told - get your user friendli OS 7 in Virtual domain on Xen or KVM with PCIe devices passthrued. Oh! No with duty strugles they continued torchen Windows.
Awesome! I made a local LLM that checks my logs, and tells me about anomalies.
@@fredrikhansen75 i made one too: grep -rinE "(err|warn)" /var/log (just joking lol)
About your bad disk, use something like smartctl to find out the s/n on the physical devices and then check on the actual drives stickers. There are probably better ways but when a disk is dead, all we want is to be 100% sure before disconnecting it. I know I did that the last time a drive died. Thanks for a good video. I needed the reminder to check my own servers logs.
Thanks for the suggestions, turns out it was a faulty sata cable, thankfully a very easy swap 😁
Could you please discuss about bsd rc and differences between bsd rc and sys v rc since managing rc in bsd seems to be an odd one for those who come from sys v types like solaris etc. and, did you say anything about "tail -f" to capture the log entries that update dynamically! Thanks for the video. 👍
Old school, to work on win 7 and some clasters on FreeBSD instances with high loads staff. I always told - get your user friendli OS 7 in Virtual domain on Xen or KVM with PCIe devices passthrued. Oh! No with duty strugles they continued torchen Windows.
Linux/BSD logs are way more accessible and useful IMHO. I mean compared to Windows event logging.