• 8 Posts
  • 146 Comments
Joined 2 years ago
cake
Cake day: August 15th, 2023

help-circle







  • Why hasn’t the market dropped yet with all the fuckery going on in DC? Because the impact of said fuckery has not occurred yet.

    This is s completely incorrect take on the stock market.

    Rule #1 of the stock market is that none understands how it responds to inputs.

    Rule #2 is that it attempts to factor in future expectations, so if you wait for something to happen, the impact is already accounted for in the price if the stock.

    Market frenzy, people piling on when FOMO takes over, etc all make it impossible to have any level of certainty. So it’s a valid question to ask why all of the current fuckery has not translated into market chaos.





  • hdparm wouldn’t let me run the security-erase or security-erase-enhanced commands. It was indicating an IO failure. I thought maybe that was due to me not giving the drive a file system so I went back to Disks and gave it one, but still no luck. When I give it a file system the drive mounts though, so no actual hardware issues that I can see.

    I found a thread on another site about using dd to remove the last 1-10MB of a RAID disk in order to make their RAID appliance see the drives as unconfigured. That’s basically what I’m trying to do here so I followed those instructions but this Mediasonic bay is still not coming to life with the old drives. I might be at the point of sending it back and looking for something else.

    Just for completeness, the command used to wipe the end of the drive is as follows where you specify the amount to wipe using the “mb” variable and you change /dev/sdX to the correct drive. From a thread on Stack Exchange.

    disk=/dev/sdX && mb=10 && dd if=/dev/zero of=$disk bs=512 count=$(( 2048 * $mb )) seek=$(( $(blockdev --getsz $disk) - 2048 * $mb ))


  • I’ve never used this before so I’m not sure what to make of it. I am currently letting it analyze one of the disks and it’s seeing a lot of HFS+ blocks (I assume that’s what it’s reporting) and a handful of ext4. That makes sense I guess, since I’m not wiping the drive, just trying to delete any partition info and/or formatting.

    The only thing that seems like it might affect how the disk looks when inserted is cylinder geometry but I don’t know enough about that to even guess at what to do with it. Is there something I should be looking for in testdisk?






  • I took a bit to reply because I wanted to wait for the next update to Mullvad. I just installed it this morning and even though I haven’t re-started the program, my network connection is dafaulting to go through the Mullvad wireguard servers which is letting everything work. I’m not sure why I have so many copies of the same wg0-mullvad server in my list so that seems suspicious.

    Here are the resolv.conf and systemd/resolved.conf files… really nothing unique other than calling back to 127.0.0.53 for the nameserver like I showed before. My desktop has the same settings and nameserver though. The only difference is that Mullvad on my desktop is not using wireguard servers, so maybe that is causing the issue on my Surface?

    resolv.conf
    # This is /run/systemd/resolve/stub-resolv.conf managed by man:systemd-resolved(8).
    # Do not edit.
    #
    # This file might be symlinked as /etc/resolv.conf. If you're looking at
    # /etc/resolv.conf and seeing this text, you have followed the symlink.
    #
    # This is a dynamic resolv.conf file for connecting local clients to the
    # internal DNS stub resolver of systemd-resolved. This file lists all
    # configured search domains.
    #
    # Run "resolvectl status" to see details about the uplink DNS servers
    # currently in use.
    #
    # Third party programs should typically not access this file directly, but only
    # through the symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a
    # different way, replace this symlink by a static file or a different symlink.
    #
    # See man:systemd-resolved.service(8) for details about the supported modes of
    # operation for /etc/resolv.conf.
    
    nameserver 127.0.0.53
    options edns0 trust-ad
    search .
    
    systemd/resolved.conf
    #  This file is part of systemd.
    #
    #  systemd is free software; you can redistribute it and/or modify it under the
    #  terms of the GNU Lesser General Public License as published by the Free
    #  Software Foundation; either version 2.1 of the License, or (at your option)
    #  any later version.
    #
    # Entries in this file show the compile time defaults. Local configuration
    # should be created by either modifying this file (or a copy of it placed in
    # /etc/ if the original file is shipped in /usr/), or by creating "drop-ins" in
    # the /etc/systemd/resolved.conf.d/ directory. The latter is generally
    # recommended. Defaults can be restored by simply deleting the main
    # configuration file and all drop-ins located in /etc/.
    #
    # Use 'systemd-analyze cat-config systemd/resolved.conf' to display the full config.
    #
    # See resolved.conf(5) for details.
    
    [Resolve]
    # Some examples of DNS servers which may be used for DNS= and FallbackDNS=:
    # Cloudflare: 1.1.1.1#cloudflare-dns.com 1.0.0.1#cloudflare-dns.com 2606:4700:4700::1111#cloudflare-dns.com 2606:4700:4700::10
    01#cloudflare-dns.com
    # Google:     8.8.8.8#dns.google 8.8.4.4#dns.google 2001:4860:4860::8888#dns.google 2001:4860:4860::8844#dns.google
    # Quad9:      9.9.9.9#dns.quad9.net 149.112.112.112#dns.quad9.net 2620:fe::fe#dns.quad9.net 2620:fe::9#dns.quad9.net
    #DNS=
    #FallbackDNS=
    #Domains=
    #DNSSEC=no
    #DNSOverTLS=no
    #MulticastDNS=no
    #LLMNR=no
    #Cache=no-negative
    #CacheFromLocalhost=no
    #DNSStubListener=yes
    #DNSStubListenerExtra=
    #ReadEtcHosts=yes
    #ResolveUnicastSingleLabel=no
    #StaleRetentionSec=0