home.social

#45drives — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #45drives, aggregated by home.social.

  1. Except that there is the #45Drives C8, but they are like „pricing? Nah, you need to get a quote from us“.

  2. A cautionary tale:

    #Linux #RHEL #VideoServer

    So, at @show we have two #45Drives servers... one is a storinator, running our main video production disk set, with about 700 TiB of drives. The second is a much older (pre-storinator) storage pod, with severely limited I/O but about 400 TiB for the urgent "DO NOT DELETE" stuff on it.

    The first is called "Kennedy". It has shares on it named after the Shuttles.

    The second is called "Baikonur" it has one share - Buran. It's used for backups.

    -----

    Before the thanksgiving break, I left both Kennedy and Baikonur up for an extended period, because I was 1) tweaking backups from Kennedy to Baikonur, and 2) I was doing some scrubs.
    Turned it off on Friday. Didn't think much about it - other than about three weeks ago, I'd told the server

    "Sudo Yum Update"
    You can see where this is going.
    Kennedy runs Rocky, which of course is RHEL-based.
    RHEL doesn't have ZFS natively, so you end up using open-ZFS.
    I told Kennedy to update. It did. Silently, building its kernel, without ZFS support.

    OH BUT DEAR READER IT GETS BETTER.

    Booting the machine, Samba goes "OK, I have THESE SHARES. It is THE LAW that I must MAKE THESE SHARES AVAILABLE". And Samba, being the pit of plague filled pestilence that it is, goes "I MUST SHARE THESE" and then goes "HUH, I CAN'T READ THESE SO LA LA LA LA I WILL MAKE THEM ANYWAY"
    So, I logged in to the server, expecting files, and saw nothing. None of the 700TiB of files were there . NONE. No data, nothing. The share was there, it just wansn't mapped.

    sigh

    After ten minutes, I realized that the new RHEL kernel doesn't have ZFS modules yet that work with it, so... I rolled back 😉

    And what have we learned children?

    ALWAYS READ RELEASE NOTES and ALWAYS CHECK COMPATIBILITY before doing SERVER UPGRADES.

  3. A cautionary tale:

    #Linux #RHEL #VideoServer

    So, at @show we have two #45Drives servers... one is a storinator, running our main video production disk set, with about 700 TiB of drives. The second is a much older (pre-storinator) storage pod, with severely limited I/O but about 400 TiB for the urgent "DO NOT DELETE" stuff on it.

    The first is called "Kennedy". It has shares on it named after the Shuttles.

    The second is called "Baikonur" it has one share - Buran. It's used for backups.

    -----

    Before the thanksgiving break, I left both Kennedy and Baikonur up for an extended period, because I was 1) tweaking backups from Kennedy to Baikonur, and 2) I was doing some scrubs.
    Turned it off on Friday. Didn't think much about it - other than about three weeks ago, I'd told the server

    "Sudo Yum Update"
    You can see where this is going.
    Kennedy runs Rocky, which of course is RHEL-based.
    RHEL doesn't have ZFS natively, so you end up using open-ZFS.
    I told Kennedy to update. It did. Silently, building its kernel, without ZFS support.

    OH BUT DEAR READER IT GETS BETTER.

    Booting the machine, Samba goes "OK, I have THESE SHARES. It is THE LAW that I must MAKE THESE SHARES AVAILABLE". And Samba, being the pit of plague filled pestilence that it is, goes "I MUST SHARE THESE" and then goes "HUH, I CAN'T READ THESE SO LA LA LA LA I WILL MAKE THEM ANYWAY"
    So, I logged in to the server, expecting files, and saw nothing. None of the 700TiB of files were there . NONE. No data, nothing. The share was there, it just wansn't mapped.

    sigh

    After ten minutes, I realized that the new RHEL kernel doesn't have ZFS modules yet that work with it, so... I rolled back 😉

    And what have we learned children?

    ALWAYS READ RELEASE NOTES and ALWAYS CHECK COMPATIBILITY before doing SERVER UPGRADES.

  4. A cautionary tale:

    #Linux #RHEL #VideoServer

    So, at @show we have two #45Drives servers... one is a storinator, running our main video production disk set, with about 700 TiB of drives. The second is a much older (pre-storinator) storage pod, with severely limited I/O but about 400 TiB for the urgent "DO NOT DELETE" stuff on it.

    The first is called "Kennedy". It has shares on it named after the Shuttles.

    The second is called "Baikonur" it has one share - Buran. It's used for backups.

    -----

    Before the thanksgiving break, I left both Kennedy and Baikonur up for an extended period, because I was 1) tweaking backups from Kennedy to Baikonur, and 2) I was doing some scrubs.
    Turned it off on Friday. Didn't think much about it - other than about three weeks ago, I'd told the server

    "Sudo Yum Update"
    You can see where this is going.
    Kennedy runs Rocky, which of course is RHEL-based.
    RHEL doesn't have ZFS natively, so you end up using open-ZFS.
    I told Kennedy to update. It did. Silently, building its kernel, without ZFS support.

    OH BUT DEAR READER IT GETS BETTER.

    Booting the machine, Samba goes "OK, I have THESE SHARES. It is THE LAW that I must MAKE THESE SHARES AVAILABLE". And Samba, being the pit of plague filled pestilence that it is, goes "I MUST SHARE THESE" and then goes "HUH, I CAN'T READ THESE SO LA LA LA LA I WILL MAKE THEM ANYWAY"
    So, I logged in to the server, expecting files, and saw nothing. None of the 700TiB of files were there . NONE. No data, nothing. The share was there, it just wansn't mapped.

    sigh

    After ten minutes, I realized that the new RHEL kernel doesn't have ZFS modules yet that work with it, so... I rolled back 😉

    And what have we learned children?

    ALWAYS READ RELEASE NOTES and ALWAYS CHECK COMPATIBILITY before doing SERVER UPGRADES.

  5. A cautionary tale:

    #Linux #RHEL #VideoServer

    So, at @show we have two #45Drives servers... one is a storinator, running our main video production disk set, with about 700 TiB of drives. The second is a much older (pre-storinator) storage pod, with severely limited I/O but about 400 TiB for the urgent "DO NOT DELETE" stuff on it.

    The first is called "Kennedy". It has shares on it named after the Shuttles.

    The second is called "Baikonur" it has one share - Buran. It's used for backups.

    -----

    Before the thanksgiving break, I left both Kennedy and Baikonur up for an extended period, because I was 1) tweaking backups from Kennedy to Baikonur, and 2) I was doing some scrubs.
    Turned it off on Friday. Didn't think much about it - other than about three weeks ago, I'd told the server

    "Sudo Yum Update"
    You can see where this is going.
    Kennedy runs Rocky, which of course is RHEL-based.
    RHEL doesn't have ZFS natively, so you end up using open-ZFS.
    I told Kennedy to update. It did. Silently, building its kernel, without ZFS support.

    OH BUT DEAR READER IT GETS BETTER.

    Booting the machine, Samba goes "OK, I have THESE SHARES. It is THE LAW that I must MAKE THESE SHARES AVAILABLE". And Samba, being the pit of plague filled pestilence that it is, goes "I MUST SHARE THESE" and then goes "HUH, I CAN'T READ THESE SO LA LA LA LA I WILL MAKE THEM ANYWAY"
    So, I logged in to the server, expecting files, and saw nothing. None of the 700TiB of files were there . NONE. No data, nothing. The share was there, it just wansn't mapped.

    sigh

    After ten minutes, I realized that the new RHEL kernel doesn't have ZFS modules yet that work with it, so... I rolled back 😉

    And what have we learned children?

    ALWAYS READ RELEASE NOTES and ALWAYS CHECK COMPATIBILITY before doing SERVER UPGRADES.

  6. A cautionary tale:

    #Linux #RHEL #VideoServer

    So, at @show we have two #45Drives servers... one is a storinator, running our main video production disk set, with about 700 TiB of drives. The second is a much older (pre-storinator) storage pod, with severely limited I/O but about 400 TiB for the urgent "DO NOT DELETE" stuff on it.

    The first is called "Kennedy". It has shares on it named after the Shuttles.

    The second is called "Baikonur" it has one share - Buran. It's used for backups.

    -----

    Before the thanksgiving break, I left both Kennedy and Baikonur up for an extended period, because I was 1) tweaking backups from Kennedy to Baikonur, and 2) I was doing some scrubs.
    Turned it off on Friday. Didn't think much about it - other than about three weeks ago, I'd told the server

    "Sudo Yum Update"
    You can see where this is going.
    Kennedy runs Rocky, which of course is RHEL-based.
    RHEL doesn't have ZFS natively, so you end up using open-ZFS.
    I told Kennedy to update. It did. Silently, building its kernel, without ZFS support.

    OH BUT DEAR READER IT GETS BETTER.

    Booting the machine, Samba goes "OK, I have THESE SHARES. It is THE LAW that I must MAKE THESE SHARES AVAILABLE". And Samba, being the pit of plague filled pestilence that it is, goes "I MUST SHARE THESE" and then goes "HUH, I CAN'T READ THESE SO LA LA LA LA I WILL MAKE THEM ANYWAY"
    So, I logged in to the server, expecting files, and saw nothing. None of the 700TiB of files were there . NONE. No data, nothing. The share was there, it just wansn't mapped.

    sigh

    After ten minutes, I realized that the new RHEL kernel doesn't have ZFS modules yet that work with it, so... I rolled back 😉

    And what have we learned children?

    ALWAYS READ RELEASE NOTES and ALWAYS CHECK COMPATIBILITY before doing SERVER UPGRADES.

  7. apple.news/ASe4PO-R1QCGA_dILMd
    Future Synology storage systems will require Synology branded mass storage.

    I’ve never been a fan of these Taiwanese storage systems simply because file systems and redundancy technology could not be ascertained pre-sale.

    Dismal Manor Gang has 2 TrueNAS Mini+ and a 45homelab.com (Storinator mob, storage for BackBlaze) hl4 4 slot available from bare metal to built & burned in Zen4 systems.

    #Synology #45homelab #45drives #backblaze #rockylinux #HoustonUI #cockpit

  8. Ok. So.
    Bad = 2
    Good = 6
    Looks like new #45Drives #HL15 gets 192GB of RAM on an Intel 10th i9 with 18 cores.

  9. I should also note that the old server power supply let out the magic smoke at the very end of last week. I have a redundant setup, so it carried on working, but emitted the annoying beep from hell until I put a *spare* PSU in.

    I *do* have two spare PSUs, but they are old, cranky, and I'd rather have one that's new and certified and under warranty than rely on some janky ones I purchased off ebay.

    Urg.

    I need to earn more pennies.

    #Server #Computer #45Drives #Data

  10. I just had to spend $1097.90 on a new power supply for our server.

    $1097.90.

    The last time I paid for one it was early in 2023 and it cost me $750.

    Dang.

    #Server #Computer #Contentcreator #45Drives

  11. It was disappointing that the first 45Drives Creator's Summit included only white, cis males (heretofore referenced as w/c/m).

    And, they are bringing the exact same folks back for their 2nd summit.

    Hard. Fscking. Eyeroll.

    nb: I don't have an issue with most of the creators that took part of the first summit and follow/support one of them. I'm also well aware that most of the IT/tech-centric creators are generally w/c/m, but at least an effort could have been made to not make it all w/c/m!

    #45Drives #Tech #Diversity

  12. :rocket: A huge thank you to @45Drives for their generous support of @rocky_linux! :penguin: Your contributions help us continue building and innovating in the open-source community; plus, it's awesome to see your powerful hardware running Rocky Linux! :floppy_disk: :wrench:

  13. Great news for one of the first, most enthusiastic sponsors of the Rocky Enterprise Software Foundation. Welcome to the US, ! buff.ly/3Rtewkl

  14. Homelab NAS upgrade done (well, phase 1). Moved the NAS into the HL15 case from 45Drives and I absolutely love it. Granted, it *could* use a few more drives, but I'll deal with that issue later. The NAS pulls double duty: serves files via SMB/NFS which are all on the spinners living on the 10GbE network, and iSCSI duties on an NVMe array on the 40GbE network. #homelab #storage #45Drives

  15. Just upgraded my HBA in my #unraid server to a 9305-16i and now my case looks a lot cleaner and I can fit 3 more drives. #homelab #selfhosted #45homelab #HL15 #45drives

  16. 🎂 11 Days until Rocky Linux's Birthday. Have you found us on the chat server yet? chat.rockylinux.org/ Search for channel 12 Days of Rockmas. Today we are crowdsourcing a playlist for software update crunch time. Might include tunes from the original creation of Rocky Linux!

  17. After a week of using and testing the HL15, I finally released my in-depth review of this new storage server.

    Does it meet the HomeLab community needs?

    youtube.com/watch?v=QGSaj5TYUB

    #homelab #storage #storage server #hl15 #45drives #45homelab

  18. Ok so I just left for #kubecon and my wife sends me this picture saying “glad you left yet?” 🫠

    Going to be a long week! Huge thanks to #45drives for supporting independent media! Review coming to the self hosted podcast soon and a boatload of content to my YouTube channel. 🙃

  19. I took a trip with 3 other Tech YouTubers to 45 Drives Headquarters to see the new 45 HomeLab HL15 and other devices during their first ever Creator Summit to discuss storage! We take a look at lots of Storinators, the HL15 HomeLab, all flash Stornados, and even the Storinator Jr.!

    youtube.com/watch?v=CUvtDV6_Ac

    #45drives #45homelab #homelab #hl15 #storage

  20. Hey all! I am heading up to Nova Scotia for a storage summit next week hosted by 45 Drives with some other creators.
    What questions would you like answered about storage, 45 Drives, Storinators, or even Sydney, Nova Scotia? 🍁

    #storage #45drives #ceph #homelab #servers #opensource #hardware #homeserver #enterprise

  21. Came back from the #NissanAriya_e4orce launch event with just under 900 GB of video and found a new 2TB of footage on my desk from @BeanieCam, who spent Thursday and Friday filming the B roll for the #KiaEV6GT.

    That’s basically 3TB in four days. This week we have a review to film (another 1.5 TB I’d guess…)

    We’re going to need a new #HardDrive array. #45Drives #Linux #ContentCreation #BehindTheScenes