So first of all, this was a little home project that I setup a number of years ago, all of which was in perfect working order until life got a little busier.
The Server, a basic wee HP ML10v2 was setup with VMware so that I could create vm's as and when I pleased. I used to dabble in computer networking and infrastructure support, but those days have long passed.
Initially, I had a single Server 2012R2 vm which I used as the backend for Plex. And with that, I had assigned a single 4TB drive as the main media store. No RAID (I know, I know).
There server has been powered down the last 3 years and upon booting up, everything was operationally sound, but unfortunately I couldn't log in to my server 2012 vm as I forgot my credentials (Again, I know
).
I therefore created a new, simpler Windows 10 vm in the hope that I could simply migrate the datastore across, but this is where issues began to arise. No matter what way I configured the new vm in ESXI, that is, One Hard Drive to act as c:/ drive, and a second drive, call it d:/, to act as the main storage for Plex files, I couldn't get access to the 3.5TB worth of media I had previously accumulated
() due to 'disk capacity' errors.
After much deliberation, and probably with the fact that im a complete novice when it comes to working inside ESXI, I decided to bite the bullet, unmount the 4TB drive, reformat it, and create a new datastore. But the **** hit the fan last night. Whilst everything had been working well in that I appeared to have setup the new vm correctly, and had worked tirelessly rebuilding my media store with some 450GB worth of media, the vm became unresponsive and within ESXI, I could no longer power it on because it had ran out of space, even though there was plenty of room left on the basic 500GB c:/ drive, and loads of room on the bulk 4TB drive.
I'll drop in some screen shots below for an overview of things. Even though there is two datastore, whenever I try to assign the bulk media store to hard disk two, the vdmc file always defaults to the smaller datastore and I have a feeling this is something to do with it, even though within windows 10, I have pooled the drives in order to access the larger 4TB drive, a screenshot I'll also include.
Ive therefore gone ahead, reformatted all my hard work again, setup a new vm, pool the drives in order to create a second E:/ drive, but I dont want to begin work until I know for sure that I have access to more than 400GB.
NB: When creating the media store this time, I said the drive was larger than what it is in the mad notion that I would be able to increase capacity should I come up against the dame problem. it doesn't sound right to me, but that's why im here looking help before I begin work to rebuild my media library.
Image Screenshot-2024-10-13-at-15-57-03 hosted in ImgBB
ibb.co
Image Screenshot-2024-10-13-at-15-57-33 hosted in ImgBB
ibb.co
Image Screenshot-2024-10-13-at-15-57-46 hosted in ImgBB
ibb.co
Image Screenshot-2024-10-13-at-15-58-14 hosted in ImgBB
ibb.co
Image Screenshot-2024-10-13-at-15-58-30 hosted in ImgBB
ibb.co
Image Screenshot-2024-10-13-at-16-23-55 hosted in ImgBB
ibb.co
Image Screenshot-2024-10-13-at-16-24-03 hosted in ImgBB
ibb.co
