I can plug the 3TB drives in to my USB dock and they work, so I don't think the drives are broken (I have 4 and they're brand new, none of them work in the NAS) (And it's not because I am impatient, it won't move even 1% for several hours at the step where it's formatting). If I do as you suggest and power up the NAS without disks AFTER I installed the newest hardware and then start the configuration process again it will just get stuck at the formatting harddrive step. As soon as I pull out the drive, my NAS will start responding again. When I insert one of my 3TB drives the NAS just becomes unresponsive, the drive I just plugged in won't show up in volume management and if I try to go to another page and back to volume management i'll just get a blank page. Here I'll see my 2TB drive and everything is great. I then connect to the manager and go to volume management. Well, I have tried many times As I mentioned in another thread also, if I power up the NAS and then insert my 2TB drive, install the newest firmware, it works fine. Now replug the 3 TB disk to the NAS, and run over the confguratin process again. Try removing the partition table, or wipe the 3 TB disk using the manufacturer tools. As you had installed a 2 TB drive to working status, and uploading a recent firmware version during this process, the firmware was updated in the meantime. I'm puzzled by this, but I can imagine various reasons why the Seatools for DOS isn't recognizing the drive.Daviate wrote:But slap any 2TB drive in and it works very well i think there is something wrong in the firmware and 3TB drives Might happen the initial factory firmware in the Flash applied a wrong partition scheme when trying the first time. Is there some other utility that will allow me to thoroughly test these drives before installing my 2012 R2 Essentials OS? A utility that boots from CD? Perhaps there is something I "need to do" with the drive before Seatools recognizes it, but if Acronis shows it, so should Seatools. There are various reasons this could occur other than something wrong with the drive. Seatools, booting from CD, does its system scan and doesn't recognize the drive. Acronis Disk Director 11 update 2 recognizes the drive, allow me to initialize and format it, and shows that it is "healthy" as a basic, primary volume. The BIOS and system POST recognizes the Seagate drive. I'm testing each drive by connecting only one of them at a time to the motherboard. I wanted to test each of the new NAS drives before installing the OS. And whatever opinion respondents have of the Seagate drives, I've had no problem at all with these NAS drives in the WHS server. I purchased two new Seagate NAS 2TB drives for the build, anticipating that I'd move the existing four drives of the WHS system to the new server eventually. Today, I fired up the system for the first time after fretting over fan connections, airflow, cable-management, etc. It may sound sort of hinky - not buying a "server motherboard" or a Xeon processor - but I'm using an i5-3470 processor and a spare Z68/Gen3 motherboard fitted with 16GB of (non-ECC!!) XMS RAM. For the OS - Win Server 2012 R2 Essentials. I'm building a server to eventually replace my WHS-2011 configuration. I may have several question in more than one forum that begins with this paragraph:
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |