My wife actually buys a bunch of this shit. We’ve got packages arriving from China almost weekly and I hate it.

There’s only been one of her influenced buys that has been any good, but I’d trade it for not having a Chinese garbage dump for a house.

Yeah this is what I’m doing now. I tried all of the tricks but they aren’t working. Unfortunately this dock is USB 2.0 so I think it will take quite a while. These are “only” 3TB drives, but I need to clean 2 of them before I can test. Hopefully sometime next week??? Haha.

Thanks, this looked really promising but didn’t work for me. lvremove said it couldn’t find the volume group and dmraid said that I have an unsupported sector size and it didn’t see any raid disks at me drive location.

I’m currently using dd to write zeros to the drives. I’m not sure how long that will take me on this old USB 2.0 dock.

I want to use RAID 1 but I’ve tried single disk as well.

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?

Sweet Caroline has always existed

I went into the Mullvad settings a bit deeper to see why my Surface might be using wireguard tunnels while my desktop doesn’t. I didn’t see anything related to that, but I did notice that Mullvad has a “Lockdown Mode” which requires you to be connected to Mullvad in order to access the internet. I don’t have that active, but I wonder if it is in that mode anyway. I did a quick enable/disable of it to no avail.

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?

# 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 .

#  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

Butt hurt? Naw.

Disgusted with your parents for raising such an ass? Absolutely.

No, unfortunately. It consistently works when connected to Mullvad on both wireless and cellular networks. It briefly worked without Mullvad after a routine software update but its back to its old ways.

What I should probably do next, just to be thorough, is boot Mint or Tails from USB and see if it all works.

Since I dont keep anything on this device, reinstalling wont be a major pain. Ive just had enough other things going on that this hasn’t bubbled to the top of my list.

Ahh, you haven’t learned anything since the 60’s. Your idiotic ramblings are starting to make sense…

It seems like you think you’re funny… ??

God you’re insufferable

Thanks for the info, I’ll read through the docs and hopefully get this up and running again in the near future. Fortunately, nothing here is mission critical and I can still use the machine with VPN active. Getting resolv.conf back in working order appears to be the right solution.

My nsswitch.conf file looks identical to yours, so nothing to edit there.

I also looked at my resolv.conf and systemd\resolved.conf files.

resolv.conf is a symlink, but is the only file with anything un-commented in the file:

# 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 .

Yes I believe that Mullvad routes you to their DNS server so that explains why it works when connected to VPN. If I attempt an nslookup when NOT connected to VPN it fails and the server it attempts to contact is 127.0.0.53. When I connect to VPN the nslookup succeeds, and it uses the same server address.

I then disconnect from VPN and ping the ip address that I just looked up (I chose etsy) and the ping goes through so this seems to be a DNS lookup issue. Is 127.0.0.53 the right server address? I would expect it to use my DHCP server address of 192.168.x.x format.

Thanks for the tip. If I bypass DNS it does appear to work so that’s likely the problem. I need to figure out why now and I think it has something to do with a local DNS override of some sort.

I checked and everything was still set to the defaults, which makes sense as I didn’t change anything. Regardless, I deleted the connection and re-made it with the same results. No network connectivity outside of my LAN unless I have a VPN active.

Settings are:

Security: WPA/WPA 2 Personal IPV4 using DHCP DNS: Automatic Routes: Automatic IPV6: Active (but unused) with DNS=Auto and Routes=Auto

I did also try resetting the network using the Reset button to no avail.

I may just end up reinstalling the OS if I can’t figure anything out.

Yeah, but Dunkin for coffee??