RobbieH

Sorry I left that out, drive is GPT. It is in VMWare ESXi 6.5 and the VM has been upgraded to v13. Hard drive is on a SCSI controller (this is common in VMWare). It is on SCSI 1:3, the two 5TB drives are on 1:1 and 1:2. It shows the proper size everywhere in VMWare Client, but not in Windows. I saw that Tom's article too, but it had nothing to do with this problem unfortunately. But, I did try them. In the real motherboard BIOS, it is on AHCI. All the settings other than the SCSI channel are the same as the 5TB, but this one simply isn't working right. I may pull it and try it on my W10 box and see what happens. But, for now, I'm going to fiddle with the SCSI controller settings.

I'm not sure where else to ask, you all seem to be the type of people that live out on the edge like I do. I have a Windows 7 VM running in VMWare 6.5. The system currently has two 5TB WD Red drives that I use in a DrivePool for storage. Opening "Computer" shows the two drives as 4.54 TB, all is well. So, I want to add an 8TB Archive drive. I set up the RDM in VMWare the same exact way I set up the 5TB drives. VMWare sees the drive as a capacity of 7.28 TB. In the Windows 7's VM settings, it also sees the drive there as 7.28 TB, and I have all the settings the same as how I configured the 5TB drives. BUT I go into W7 Disk Management and it shows the drive as only being 1307.91 GB. I've tried everything I can think of to get this drive to show as 8TB but nothing. Oh, and it's that way even when Unallocated. I did set it up as GPT (as are the 5TB drives) but still it's just 1.3TB.

Sure enough, the new version cleared the errors. I'm not saying there is nothing wrong with the drive, but marking them as unchecked and letting Scanner do its thing removed the "damaged" status from the Scanner dashboard.

First off, thanks! I should have told you, this is a WD Red 5TB that I've had in there for about a year. Will Scanner continue to tell me that the drive is damaged no matter what I do? I just ordered a 8TB SMR drive to replace it with for now, since I've been wanting to mess with them anyway. From what I read here a while back, it should be fine for storing my rips for playback.

Hey Christopher, I've run into a problem that's showing itself in a way I've never seen before, or maybe it has been so long since I've had a problem I don't remember what to do correctly. First, I'm on 2.5.2.3103 Beta I have a hard drive that is reporting it is unable to read 104 sectors. I've deleted the corrupted files and rescanned, nothing is coming up with errors now. I set the readable blocks unchecked, and the unreadable blocks unchecked, and let it rescan. But, it is still reporting 104 unreadable sectors. I thought there was a way to mark these as unusable and go along my way, but I do not seem to be able to get to this point. Is there a way to do this?

Did you go down to post 70? I use Drivepool and Scanner (they are two different products) and love them. But, I have no use for Clouddrive. Thought on Windows storage spaces?

Questions pop up occasionally over on the AVS Forum. Like this one. Scroll to post 70 http://www.avsforum.com/forum/26-home-theater-computers/2430098-what-does-htpc-mean-you-3.html

I record live TV to mine all the time. I have 5 tuners, and there are likely times that at least 4 of them are recording. Windows 7 in an ESXi 5.5 VM Recordings go to a pair of WD Red drives. 1 HDHR Prime 1 HDHR Extend

Chris, You used to have a write-up somewhere on here that described the differences (really the advantages) of DrivePool over Storage Spaces. I can't find it now. Do you know where it is, or can you re-paste it here?

Be very careful, do not consider DrivePool a backup solution. If you delete files or if you have files get corrupted on the primary drive, they will be the same on the pool drive. A backup will save you in the event you accidentally delete or corrupt files, DrivePool will not. This is not a knock at DP or RAID solutions, it's just the truth. I am a huge DP fan, but please do not consider it to be a backup solution.

You can still create an autoexec.bat that runs at bootup. You can enter a "del c:\temp\*.* /s" that will catch most of the files. Of course set the path to match what you have for your real temp file. And I will concur, if you have space on the boot HDD, you can successfully expand the boot partition. Another solution, which I use when setting up my corporate systems, is to never install programs to C:.

I had a bunch of the STx000DMxxx drives, and of course they were the 3TB model. Out of all of them, I have one still alive. I use it as a duplication drive only. Because DrivePool is so configurable, it is pretty easy to set them to only hold duplication data. In this case, as long as I only lose the Seagate, I can always pop another in and DP will re-duplicate to the new drive, and I haven't lost any data. One thing - Seagate and Samsung merged at some point (someone please correct me if this is incorrect) and I found a Seagate patch for a few Samsung drives I had that were racking up LCC, and that had already been replaced under warranty. I had to jump through some hoops to make the flash stick as the normal method stated that my firmware was not compatible with the drive I was trying to flash. Well, sure enough the LCC stopped racking up, but after about a year these drives failed too. So, in this case, I'm not sure that head parking had anything to do with the failures. I have heard some rumors (I can't validate) that the LCC on the WD Green has something to do with failures. One thing I do know, is that WD has declined some warranties on the green drives with high LCC count with them stating the drives were used outside of stated capacity or something like that. They are not intended to be used in "always on" PCs, which is kind of funny because that is where a green drive might actually show some minor benefit.

It is always something fun. So, I maxed out my boot SSD, and moved my machines to a new SSD. I still don't have the ability to directly create an RDM to my physical drives, but now I can't even create manual VMDKs like I have in the past. I just get the following error: Failed to create virtual disk: Function not implemented (2490377) I have no idea what I have done here, but I really want to get these servers back up and running. Nevermind, I finally remembered what I was doing wrong on creating the RDM's manually. Forgot to put the target volume name in.

August 26, 2014, through the web portal, was the last one. I found the receipt in my email. I helped a friend with his returns too, his were in a NAS, but Seagate said "no" on those, but the NAS manufacturer took care of it. Same time period.

Interesting, the ST3000DM001 drives I shelled were exchanged by Seagate when they failed, outside of the case. I guess YMMV. Being someone that's in very large data centers as part of my job, and someone that works with these very large companies, there is one more thing about enterprise drives that was left out. Now, I'm talking the drives you get when you purchase servers or SANs, not some company buying a bunch of bare drives. When these drives fail, the common practice is for them to be replaced and the failed drive NOT RETURNED. That way the customer may dispose of the failed drive as their policies require, and they have the ability to track the location of the drive all the way through destruction.

Boy, that's the truth. Google Wemo. I have a pile of Linksys routers I don't use, because they are horrible. I should have known better, I was never a Linksys fan, not before, during, or after Cisco ownership. I have some Asus routers that have worked pretty well for me. I have a Zyxel that's a piece of junk, and an Ubiquiti AP that seems to work pretty well but the Java management app stinks and it uses a proprietary POE+, which I did not know until I got it. Sorry if I got off topic, I could rant about crappy wifi routers/APs for hours. BACK ON TOPIC: What are you trying to solve for? I looked back through the thread and didn't find any mention of what you need in your router.

I use Emby on my local/wired devices and Plex on my tablets, phones, and when remote. One of the things I like about Plex is the ability to "Sync". What this does is pre-transcode the file, then place the file locally on my tablet. I have a 64GB MicroSD card in my tablet, and if I select low quality, I can get a BUNCH of movies and TV shows on the tablet. And, great thing is, on a 7" tablet, the low setting looks perfect. You can install both Plex and Emby server applications on your server with no issues.

As Chris said, I use the USB port in the middle of my motherboard for the boot drive for ESXi. I use a 16gb drive, which is kind of overkill, but it was on the HCL.

I'd put it this way, if you don't know why you need multiple NICs, then you probably don't need them.

Funny, all this time I had mine on 4GB because I thought that was the limit. I guess it was for WHS v1. I have 6 NICs in my server, and currently 5 of them are in use. The 6th one will be soon, and another one (at least) within the next few months. Pretty easy with a 4 port NIC. To go over these: pfSense Firewall - one port for internet side and one for home side Windows Server Essentials - One port for the home network, one for video surveillance cameras Windows 7 - One port for home network All "machines" in VMWare. Soon I'll be spinning off a DMZ with a dedicated web server and some other junk, I need to hook up the management port for the motherboard, and I want to separate out the management port for VMWare. So that's 3 more NICs.

Repair did fix the issue. Not sure what you mean by run an install then restore. I just put the wiped drive in, boot off USB, then tell it to restore the entire C physical disk, as in I don't select individual partitions. Pretty strange that this happened, I've never had it fail before. But, it's fixed. It is the only working WMC computer I have right now - the W7 VM won't switch to Rovi so the guide is blank and the recordings won't work, and the PC I'm typing on now won't finish the PlayReady setup. At least this PC I'm on now isn't all that important, I don't mind wiping WMC off of it and starting from scratch.

I'm at a loss here. The problem with me is I like to find the root cause of my issues. I know I could probably boot off my W7 disk and do a repair, but I want to know why my restore isn't working on its own. I've done this from WHS 1 and 2 with no issues before, don't know what is wrong this time. Scenario: Windows 7 Ultimate 64, i3 processor, SSD boot drive. Machine has been acting funny as if something were wrong with the drive, so I took it out, erased it, ran a full surface test, etc. Did not find any issues, but it's not the first time I've seen an SSD be finicky. Create recovery thumb drive from WSE 2012. Boot from thumb drive, run full recovery, recovery succeeds every time. Reboot, and I get "Missing bootldr". I did my searches as best I could on Google, but I can't find anyone with a similar issue. Since a lot of us here run WSE or WHS, I was hoping someone had some experience with this. I don't want to run recovery until I know what happened.

Use Western Digital's application WDIDLE3 to set the head park to "never". NOTE, you are flashing the drive, and there's always a chance of something going wrong. Make sure you have backups. http://support.wdc.com/product/download.asp?groupid=609&sid=113 I had some drives that Scanner was warning me about the heat on. Then I started getting warnings about other drives in the pool. Turns out the two original drives I was getting the warnings on were failing, and for whatever reason just before they died they started making my other drives overheat. I'd take it as a warning sign if you have a drive with a high load count overheating.

Sorry, I didn't mean to imply only Intel boards had the feature. HP has ILO, etc. I have just had really good luck with Intel boards in the past, so that was the major reason I went with Intel. Oh, and it was on the ESXi HCL.

Part of the reason I got the Intel server board.