handmade.social

0 posts0 participants0 posts today

Kevin Karhan :verified:<a href="https://mastodontech.de/@alterelefant" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@alterelefant</a> <a href="https://infosec.exchange/@Heidi" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@Heidi</a> again: Of you need to cram Petabytes of Data into a single bank vault box as <a href="https://infosec.space/tags/offline" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#offline</a> <a href="https://infosec.space/tags/backup" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#backup</a> and expect to handle the tape.maybe once a year, it's fine.I just think that longterm, both <a href="https://infosec.space/tags/Tape" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Tape</a> and <a href="https://infosec.space/tags/HDDs" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#HDDs</a> eill be superseded by <a href="https://infosec.space/tags/Flash" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Flash</a> and I'm confident that with the massive enfattening of <a href="https://infosec.space/tags/Games" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Games</a> ideas like the <a href="https://infosec.space/tags/NeoFloppy" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#NeoFloppy</a> / <a href="https://infosec.space/tags/StiffyDiskDrive" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#StiffyDiskDrive</a> will gain demand.

Kevin Karhan :verified:<a href="https://mastodon.neilzone.co.uk/@neil" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@neil</a> <a href="https://m.ai6yr.org/@ai6yr" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@ai6yr</a> <a href="https://fosstodon.org/@restic" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@restic</a> I'd say an external <a href="https://infosec.space/tags/SATA" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SATA</a>-SSD in an enclosure with <a href="https://infosec.space/tags/brtfs" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#brtfs</a> or "journalless <a href="https://infosec.space/tags/ext4" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ext4</a>" works fine.<ul><li>Maybe consider a cheap multi-port case with <a href="https://infosec.space/tags/HDDs" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#HDDs</a> and using <a href="https://infosec.space/tags/dmraid" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#dmraid</a> for <a href="https://infosec.space/tags/RAID" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RAID</a>-based failsafe?</li></ul>

Kevin Karhan :verified:<a href="https://mastodon.social/@RadioAzureus" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@RadioAzureus</a> my core problem with these is that they use a very scarce resource (<a href="https://infosec.space/tags/Helium" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Helium</a>) that should've been used for more critical applications...<ul><li>This affirms <a href="https://github.com/KBtechnologies/NeoFloppy/blob/main/docs/neofloppy.specification.md#longevity" rel="nofollow noopener noreferrer" target="_blank">my stance</a> that <a href="https://infosec.space/tags/HDDs" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#HDDs</a> are on their way out and have reached their technical limitations...</li></ul>

PerrySo there seem to be 28TB <a href="https://infosec.exchange/tags/HDDs" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#HDDs</a> available already.. And here I was surprised that I could pick up a 24TB disk after thinking 22TB was the largest you could buy.I know that there's those SMR 32TB drives as well but I want to stick with CMR for the new <a href="https://infosec.exchange/tags/NAS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#NAS</a>. Now having 3 of them means I can setup my new <a href="https://infosec.exchange/tags/unraid" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#unraid</a> parity (at 2 disks) and have a single data disk for the pool. Also being that I'm using 28TB disks I should have close to a 220TB raw pool once I'm done adding all 10 disks.I also picked up 2 4TB NVMe drives for the cache pool that I'll run in mirrored mode, so the new server should have a decent amount of throughput. I'll stick in the 10Gbe ethernet adapter I saved from my old Threadripper system but that means I might need another switch in the office that provides 10Gbe RJ45 😅<a href="https://infosec.exchange/tags/homelab" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#homelab</a> <a href="https://infosec.exchange/tags/selfhosted" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#selfhosted</a> <a href="https://infosec.exchange/tags/rackserver" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#rackserver</a>

d33p.jsStrange things happend in my homelab - as always in IT 😏 .Intel NUC with an *additional* 2,5" HDD (yes, 5400 RPM Harddisk, not an SSD). Had like 20 Docker Container running on it.A couple of weeks ago I started see some wired things happening at one of the Docker Images (just one! Grafana, Graylog... everything works fine). A Nextcloud Instance failed. Some Files just broke?! Like I mean .php Files that suddenly had garbage in them. At least, the Nextcloud Image brings original Files (/usr/src/nextcloud) with them, so I could copy the working ones over the broken ones. Problem fixed. For now at least.A week later. Same thing. Fixing the error (some other files with garbage in them). Done. Couple of days later: Some problem again. WTF?I tried to investigate and be sure it's not some sort of an cyber attack. But spending hours of forensics, there wasn't any artifacts of an attack.Then I thought it might be a bug in Nextcloud. Because I found a coincidence: Every time watchtower was updating Nextcloud, it failed with creating garbage files (randomly). But no one else had any problem, so I investigated further. After a couple of hours I made a quick S.M.A.R.T. check (although I don't entirely trust it). Nothing. Then an fsck. Some errors were found and fixed. Puh!So I thought, that's it: After a Power Failure a couple of weeks ago, I had issues with the Filesystem. fsck fixed it. And could move on. But, of course... this wasn't the end. With the upcoming Nextcloud updated, it failed again.I ran the old checks again: but fsck couldn't find any errors. But I had still broken php files - just inside the Nextcloud Container.Because the problem smelled fishy, I forced a long S.M.A.R.T. check and..... it got interrupted because of a couple of errors. The End of the story: I'm switching to a new Drive which (probably?) fixes the problem.The point of the Story:1. Some things are easier than they seem. It was just a plain old hardware failure. No sophisticated cyberattack, nor an critical nextcloud bug.2. Look at an error from different point of views. Even fsck and S.M.A.R.T. (smartctl) could point you to the wrong direction.For the ones who like to see how to temporary fix the nextcloud issue, nextcloud community helped me: <a href="https://help.nextcloud.com/t/strange-error-class-oca-themingcontroller-does-not-exist/196455/12" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://help.nextcloud.com/t/strange-error-class-oca-themingcontroller-does-not-exist/196455/12</a><a href="https://infosec.exchange/tags/harddrive" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#harddrive</a> <a href="https://infosec.exchange/tags/harddrives" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#harddrives</a> <a href="https://infosec.exchange/tags/hdd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#hdd</a> <a href="https://infosec.exchange/tags/hdds" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#hdds</a> <a href="https://infosec.exchange/tags/ssd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ssd</a> <a href="https://infosec.exchange/tags/ssds" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ssds</a> <a href="https://infosec.exchange/tags/storage" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#storage</a> <a href="https://infosec.exchange/tags/nextcloud" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#nextcloud</a> <a href="https://infosec.exchange/tags/failure" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#failure</a> <a href="https://infosec.exchange/tags/SmartMonitor" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SmartMonitor</a>

Recent searches

Search options

Administered by:

Server stats:

#hdds