localzuk Posted July 12, 2017 Posted July 12, 2017 So, one of the things I've noticed across a number of the schools we have taken on is a prepensity of their previous IT providers to partition a 146GB "Data" disk, which is used for shares/user files etc... Doesn't matter how big the actual disks are, always a 146GB disk. Can anyone answer this riddle for me? Why would you spec a server with 1TB of space and then not partition most of it into use?
mikeprice Posted July 12, 2017 Posted July 12, 2017 Possibly so that if a PC fails and has to be replaced with another with a smaller drive then they know that the 'data disk' will still fit onto the replacements 'data disk' or possibly so that everyone has the same amount of disk space and can't say 'but freddy has a bigger one than me' although why 146 is a mystery
DJ-1701 Posted July 12, 2017 Posted July 12, 2017 although why 146 is a mystery That's easy! It's because 42 is far too small... 1
DavePa Posted July 12, 2017 Posted July 12, 2017 We used to buy HP enterprise HDDs at 146gb capacity, maybe whoever partitioned them was thinking that they may have to replace them with that size spares?
localzuk Posted July 12, 2017 Author Posted July 12, 2017 (edited) I have a suspicion. 146GB is the size of SAS disk. I fear that what they did, when they got a new server, was to clonezilla it all across then fix the drivers... Thing is, the servers have 1TB SATA disks in now. Edited July 12, 2017 by localzuk
DJ-1701 Posted July 12, 2017 Posted July 12, 2017 I have a suspicion. 146GB is the size of SAS disk. I fear that what they did, when they got a new server, was to clonezilla it all across then fix the drivers... Eep... welcome to the great rebuild of 2017? 1
ollyyllo Posted July 12, 2017 Posted July 12, 2017 How big are the other partitions, 110gb or 104gb? They could have used fat images from a 250 or 256 gb drive?
localzuk Posted July 12, 2017 Author Posted July 12, 2017 How big are the other partitions, 110gb or 104gb? They could have used fat images from a 250 or 256 gb drive? 48GB C drive, 500GB "nothing really on it" partition and then the rest is unallocated.
Roberto Posted July 12, 2017 Posted July 12, 2017 (edited) Can anyone answer this riddle for me? Why would you spec a server with 1TB of space and then not partition most of it into use? If it's all the same managed service provider, want to take a bet it employs two consultants who know how to write scripts (whether human documentation or a bunch of powershell say) to do things like clone drives, move data, etc. and eight "consultants" whose specialist technical areas are lifting heavy objects into and out of racks, and how to run a powershell script or follow documentation to the letter. Edited July 12, 2017 by Roberto
john Posted July 12, 2017 Posted July 12, 2017 If they were an external provider it could be a script reader doing as per script and someone wrote the script for SAS Disk and never said if disk is bigger go bigger etc.. ? I do see it at times, anyone still make a partition on the same VHD for the Page File to sit in when its on the same VHD, same SCSI Card, same LUN, SAN etc...
DMcCoy Posted July 12, 2017 Posted July 12, 2017 As an aside, I've found MDT terrible at partitioning things. I got the perfect layout for W10 + recovery etc in the proper order. Only works on a blank drive! Run MDT a second time and it falls over due to trying to install a second time to the wrong partition. At least you don't have to create VMDKs and VHDs in a special way now to align the sectors to an 8k boundary along with all yours LUNs!
john Posted July 12, 2017 Posted July 12, 2017 As an aside, I've found MDT terrible at partitioning things. I got the perfect layout for W10 + recovery etc in the proper order. Only works on a blank drive! Run MDT a second time and it falls over due to trying to install a second time to the wrong partition. At least you don't have to create VMDKs and VHDs in a special way now to align the sectors to an 8k boundary along with all yours LUNs! Did you remeber to tell MDT how you wanted it setup as you can do that in MDT, so when we get new Laptops and Desktops with the crappy recovery and secret stalking partitions MDT just blats the lot and makes one C Drive for us as that is what we tell it.
DMcCoy Posted July 12, 2017 Posted July 12, 2017 Did you remeber to tell MDT how you wanted it setup as you can do that in MDT, so when we get new Laptops and Desktops with the crappy recovery and secret stalking partitions MDT just blats the lot and makes one C Drive for us as that is what we tell it. That's what I did, but it only works on the first go, with a drive with no partitions (or new vhd/diskpart clean). All subsequent attempts see the MDT scripts messing the order up and using the recovery partition as the installation location. It's an MDT script issue with initial drive letter assignment for WinPE things.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now