Hi, i’m into programming, sexual transmutation and psychedelics!
I wonder why we don’t have AI browser extensions that can recognise and obscure possible ads / unwanted content yet
This is a lovely story
That looks way more than a home server, it looks like something i would expect to see for a small business!
The revolt will continue.
Here is the correct version.
TIme to find out what the vulnerabilieties are and EXPOSE them in a OPEN repository.
Can’t we even avoid that by using lineage or graphene? We’re really fucked unless we are like cybersec experts…
What machine is it?
Am i forgetting something?
Thank you so much for taking the time to answer!
I’m not sure how to get the
N
from session history, nor how to check my session history…but this might be some relevant output I’ve found with
journalctl -k -b
Nov 21 16:08:18 rpi kernel: usb 2-2.1-port2: cannot reset (err = -110) Nov 21 16:08:19 rpi kernel: usb 2-2.1-port2: cannot reset (err = -110) Nov 21 16:08:19 rpi kernel: usb 2-2.1-port2: Cannot enable. Maybe the USB cable is bad? Nov 21 16:41:57 rpi kernel: I/O error, dev sdb, sector 2466347032 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 2 Nov 21 16:41:57 rpi kernel: EXT4-fs warning (device sdb1): ext4_dx_find_entry:1796: inode #75497968: lblock 42: comm apache2: error -5 reading directory block Nov 21 16:41:57 rpi kernel: EXT4-fs error (device sdb1): ext4_journal_check_start:83: comm apache2: Detected aborted journal Nov 21 16:41:57 rpi kernel: Buffer I/O error on dev sdb1, logical block 0, lost sync page write Nov 21 16:41:57 rpi kernel: EXT4-fs (sdb1): I/O error while writing superblock Nov 21 16:41:57 rpi kernel: EXT4-fs (sdb1): Remounting filesystem read-only
The output is from yesterday, when the device stopped working correctly.
I’m not familiar with linux kernel, but I can see there is definitely something wrong…
The HDD (old) is attached to a USB hub (new), I tried switching port of the hub but the same issue happened again, if I try to mount it with
sudo mount /mnt/2tb
, it says it is already mounted:sudo dmesg | grep sdb
gives back:[147776.801028] I/O error, dev sdb, sector 77904 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 2 [147776.815452] EXT4-fs warning (device sdb1): htree_dirblock_to_tree:1083: inode #2: lblock 0: comm ls: error -5 reading directory block [147796.731734] sdb1: Can't mount, would change RO state