FearlessUser

I am not a smart man. This was one of those "user error" thing's I've heard so much about. I had 3 USB drives that were all the same, but I swore I only had 2. One was empty, and the other one that gave me error above is what I used to flash the HBA in my server to IT mode. The 3rd drive that I should have been using was in an anti-static bag. The drives are those Kingston Data Traveler drives that are silver, matching perfectly with an anti-static bag. The first 7 times I looked at the bag, I thought it was empty. My wife even went through that box and thought the bag was empty. 9th time is the charm I guess. Moral of the story: you're not using the right drive. Check all the anti-static bags, even the ones you think are empty. And make a backup before you move cross country. It's not a good idea to not have a backup.

Just found this old post that I'll try tomorrow. Something came up and I can't work on this anymore tonight. If anyone else has other ideas, feel free to add them. I'll get back on this after work tomorrow

It moves on to the next items in the boot order. It's a dual NIC motherboard with PXE. It looks for something on both NICs and fails because I don't have it connected to the network yet. That and I'm not set up for PXE. Then it tells me to insert the boot device and hit any key. If I put the USB drive back in, it tries to go through the PXE setup again, so it looks like it's stuck looking for that at this point until I shut it down

I moved cross country about a month ago. I'm not sure if it mattered, but I spent a bit of time making sure to label where every cable and drive was plugged in when I tore it down, and made sure everything was hooked back up the same way now that I'm finally getting around to setting the server back up at the new house. The picture below is what I get when I boot it up. The USB drive is recognized by Windows just fine, and it has no issues when I run a checkdisk on it. What am I missing here? It's still set to boot from the USB drive in the BIOS, that hasn't changed. The BIOS sees the USB drive by brand and name, so it seems like the drive is fine. I made the USB key back in May of 2019, and whatever version of unraid was available at the time. I've rebooted it several times over the years for OS updates and adding new drives. When I took it down, it said the uptime was something like 305 days, so it's been about a year since it was booted up last. The last OS update I did took the server to either 6.7 or 6.8, something like that. Could the mismatch between what's on the stick and something else cause this problem?

I have some 1tb Adata drives and have the issue. I figured it was because they are kind of cheaper drives. I bought some 860s to swap them out with. If I don't use them here, I have plenty of places to use them

So, turns out it was the same issue as the white label shucked drives. I put on a molex to sata power adapter, that cleared it right up. Curse you, WD...

Starting up my first unRAID server. I have a couple of SSDs, some 12tb Seagate drives, and a 12tb Ultrastar. The SSDs and Seagate drives show up fine. The Ultrastar is a bigger problem. It's not showing up to assign at all. Tried a few different known working locations with sata and power cables, but this drive keeps eluding unRAID. Figured it was a bad drive, so I connected it with a sata to usb adapter to my PC. It showed up fine. Put it back in the server, nothing. Connected it to the server with the adapter, it shows up fine. I'm at a loss. Diagnostics attached, I'm not really sure what to look for. As of now, its in the case connected via sata