git is already a decentralized version control software. Your local git repos are mirrors by themselves.
Put some git fetch
in a server crontab, and you’re done. You can access them via ssh if your user have permissions.
Errar es humano. Propagar errores automáticamente es #devops
git is already a decentralized version control software. Your local git repos are mirrors by themselves.
Put some git fetch
in a server crontab, and you’re done. You can access them via ssh if your user have permissions.
Wait.
Does Portainer ask your email? I haven’t used it in years. I though it was just a container that you run, with mounted docker socket, and that’s it.
Is it now doing some “telemetry” and sending user data, like email, to their servers? If so, I’m glad I’m not using that anymore.
“Have taken up farming.”
Oh, it’s gonna use polkit. Sudo bloat is a grain of sand compared to polkit.
Why people want to replace sudo with polkit? Visudo is no near as obscure as configuring polkit.
I hope distro maintainers don’t follow this.
I used a hand dust blower intended for photography gear. I opened the laptop, blew the dust, disconnected the SSD and blew the socket and it’s surroundings.
Now I will monitor the logs and see if it helps.
Thanks.
I opened it. All cables were looking good. I used a hand blower to clean the dust. Taked out the SSD and blew the socket and everything around.
Now I’m going to monitor if it keeps happening.
$ journalctl --since yesterday | grep -c "nvme 0000:02:00.0: PCIe Bus Error: severity=Corrected, type=Physical"
16
sudo smartctl -a /dev/nvme0
$ sudo smartctl -a /dev/nvme0
[sudo] password for ****:
smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.7.6-arch1-2] (local build)
Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Number: INTEL HBRPEKNX0202A
Serial Number: BTTE95101RQM512B-1
Firmware Version: G002
PCI Vendor/Subsystem ID: 0x8086
IEEE OUI Identifier: 0x5cd2e4
Controller ID: 1
NVMe Version: 1.3
Number of Namespaces: 1
Namespace 1 Size/Capacity: 512,110,190,592 [512 GB]
Namespace 1 Formatted LBA Size: 512
Local Time is: Fri Mar 8 12:09:53 2024 CET
Firmware Updates (0x14): 2 Slots, no Reset required
Optional Admin Commands (0x0016): Format Frmw_DL Self_Test
Optional NVM Commands (0x005f): Comp Wr_Unc DS_Mngmt Wr_Zero Sav/Sel_Feat Timestmp
Log Page Attributes (0x0f): S/H_per_NS Cmd_Eff_Lg Ext_Get_Lg Telmtry_Lg
Maximum Data Transfer Size: 32 Pages
Warning Comp. Temp. Threshold: 77 Celsius
Critical Comp. Temp. Threshold: 80 Celsius
Supported Power States
St Op Max Active Idle RL RT WL WT Ent_Lat Ex_Lat
0 + 3.50W - - 0 0 0 0 0 0
1 + 2.70W - - 1 1 1 1 0 0
2 + 2.00W - - 2 2 2 2 0 0
3 - 0.0250W - - 3 3 3 3 2000 5000
4 - 0.0040W - - 4 4 4 4 5000 9000
Supported LBA Sizes (NSID 0x1)
Id Fmt Data Metadt Rel_Perf
0 + 512 0 0
=== START OF SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
SMART/Health Information (NVMe Log 0x02)
Critical Warning: 0x00
Temperature: 30 Celsius
Available Spare: 100%
Available Spare Threshold: 10%
Percentage Used: 32%
Data Units Read: 6,877,173 [3.52 TB]
Data Units Written: 9,397,485 [4.81 TB]
Host Read Commands: 54,359,124
Host Write Commands: 239,213,047
Controller Busy Time: 2,412
Power Cycles: 536
Power On Hours: 6,350
Unsafe Shutdowns: 62
Media and Data Integrity Errors: 0
Error Information Log Entries: 0
Warning Comp. Temperature Time: 0
Critical Comp. Temperature Time: 0
Error Information (NVMe Log 0x01, 16 of 256 entries)
No Errors Logged
Self-test Log (NVMe Log 0x06)
Self-test status: No self-test in progress
Num Test_Description Status Power_on_Hours Failing_LBA NSID Seg SCT Code
0 Extended Completed without error 6334 - - - - -
1 Short Completed without error 6334 - - - - -
OK. I’ll use a dust blower for photography gear. Thanks. Let’s see if it works.
I did a short and a long test. It looks good
$ sudo smartctl -l selftest /dev/nvme0
smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.7.6-arch1-2] (local build)
Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF SMART DATA SECTION ===
Self-test Log (NVMe Log 0x06)
Self-test status: No self-test in progress
Num Test_Description Status Power_on_Hours Failing_LBA NSID Seg SCT Code
0 Extended Completed without error 6334 - - - - -
1 Short Completed without error 6334 - - - - -
[…] by replacing the motherboard, by replacing the processor, by reseating the NVME drive in its slot, by verifying that your power supply is reliable…
I will start with the cheapest option 😅
I assume the power supply is reliable. Having a battery should make it more stable I guess.
Wow! this is exactly what I needed. Although, I didn’t exactly ask for it.
Thank you very much
see federated network
looks inside
mastodon.social
Pros:
Cons:
Welcome to Lemmy. Hope you enjoy it.
Meme language? It was not rewritten in Javascript.
Those who don’t understand Unix are condemned to reinvent it, poorly. ~HS
UI/UX 101, my friend.
If people are used to see specific symbols for years is hard for them to use different ones.
There’s a reason why floppy disk is still the icon for “save”.
Those people drive cars on the road!
Imagine if they change all road signs designs suddenly before you go for a ride.
That’s why it’s not always an option.
Some servers have some kind remote console hardware, with their own security issues.
Your “threat model” is important too. Do you expect that server to get stolen? If it happens, is there critical data that should not leak?
Maybe you need to encrypt a directory, and not the whole drive.
If the device get stolen, your drive and its files can be easily read.
Other attacks like malware or ransomware are almost the same if the drive is encrypted or not.
Disk encryption is important for laptops and phones because these devices are frequently stolen. For desktop or servers is still good idea, though.
me before reading this: I know the basics of CSS.
me after reading this: I know nothing about CSS.