I recently ran out of space on my Homelab ESXi running on my HP DL380 G7 server, so it’s time to add some more storage. First, I checked the list of supported drives known not to have the thermal runaway issue on the DL380 and similar models. I have a couple of WD Blacks right now, but the model numbers on those are hit and miss, some models work, some don’t, and I couldn’t find the exactly same model number on sale again (the working model I have is WD7500BPKX). I noticed though there’s a longer list of WD Blue drives that are known to work ok, and looking on Amazon I found some refurb 1TB drives for $40. Since this is just a hobby server and I don’t need to store anything critical on there, this sounded like a good deal.
I needed a couple of extra drive caddies too, here’s what I picked up:
2x KKmoon HHD Tray Bracket For HP G7 2.5″ Drive Caddy SAS SATA 371593-001 DL380 DL370 DL360 G5 G6 G7″
2x WD Blue 1TB Mobile Hard Disk Drive – 5400 RPM SATA 6 Gb/s 128MB Cache 2.5 Inch – WD10SPZX (Certified Refurbished)
The WD drives arrived same day from Amazon – they were in sealed bags but obviously not the original packaging as they were refurbs. They were also wrapped in plenty of bubblewrap which was plenty adequate to protect them during shipping, and shipped in a Jiffy bag:
The HP server drive caddies arrived the following Monday (ordered on Saturday). Again, packaged well, in a box and in a Jiffy bag:
While testing a React frontend for my SudokuSolver Lambda, I kept getting this error when calling the Lambda using superagent from React:
RequestId: 35934232-xxx Process exited before completing request
Testing from Postman it completed as expected.
This error message means what it says, the Lambda quit before it completed executing.
There are 2 possible paths through my SudokuSolver:
The input puzzle has a single, unique solution
The input has more than one possible solution
If there is more than one solution, the Solver finds the first solution and then exits. Yes, it does a System.exit(). There’s the cause of my problem. I was testing from Postman with a puzzle with a single solution, but the test from my React app only had a couple of values in the grid.
read and understand what the error message means. Once you understand what it’s telling you, ask how and where this applies to your code
when changing variable aspects of your test, don’t change too many at one time. If possible only make one change, so if something is unexpected you’ll know it’s as a result of that change (in my case I changed my test data from Postman to the React app and so wasn’t comparing the results with the same inputs. The issue was unrelated to React or superagent, it was completely related to my test data)
It’s been rumored for a while now that a new upcoming Mac Pro, likely to be announced at WWDC 2019, will be ‘modular’. The last generation Mac Pro, usually referred to as the ‘trashcan’ because it looks just like a trash can, is anything but modular compared to previous generations.
This is what my 2008 Mac Pro looks like in the inside:
I have a mix of SSDs and HDDs in there, and I boot MacOS, Windows 10, Linux and run Proxmox to virtualize the hardware. I have 2 GPUs, one Mac native AMD and one generic nvidia .
I don’t think ‘modular’ means the same as expandable. My 2008 Mac Pro does everything I need as a daily driver desktop, and if I need it to do something different I can easily pull parts out and put new parts in.
I want the new Mac Pro to be as expandable as this, but I think ‘modular’ more likely refers to an ability to link multiple units together to add capacity and features, but that sounds like an expensive approach, and nowhere near as flexible as the expandability of prior generation Mac Pros. Fingers crossed, I’m looking forward to see what will be announced, but I don’t think the new Mac Pro will be as expandable as the previous generations.