My last postwent into detail regarding the hunt for a new NAS for my needs. Synology vs Qnap, 10Gb upgradability, 6 or 8 bay, 1 NIC vs 4. I was confused
Anyways, whichever NAS I do go with, will have 10Gb compatability. I have no immediate want nor use for 10Gb but as the prices come down, I will eventually move to it. Even the connectivity between my 10Gb capable NAS and hopefully my server is good enough for me.
That brings me to the server. As you may have read, I have an HP ML150 G6 with two E5540 CPU’s, 96Gb of memory and a HP P410 RAID card. I was wondering if the HP ever came with 10Gb capability and although I can’t find anything direct, I do see that some HP servers in the G6 line had 10Gb options.
I came across a low cost HP 10Gb card on a Google search that seems to be popular among the homelab community. The HP NC523SFP 10Gb 2-port card. Looking at the list of compatible servers here. HP identifies a few ML G6 servers (330,350,370) along with a bunch of other DL and SL series G6 servers. This 10Gb nic appears to be the same as the Qlogic QLE3242 and a newer model compared to the HP NC522SFP.
Initially I did come across the HP NC522SFP(Qlogic QLE3142) but from what I’ve read, it appears to run a bit hot and the NC523SFP seems like a newer version of the card, although I can’t state that for certain.
What I am going to try is to plug this card into my server and see if it will automatically detect it. I’m curious is what VMware will see.
When I installed Vmware ESXi 6.5 on the server, I had difficulty using the HP Proliant specific installation. I would get purple error messages. I’m really curious and interested to see what I can push this server with. Like most of this blog, this is all about my learning and understanding. Things may not work out and others will. I don’t mind the outcome and I will do my best to keep you all in the loop.
I should be installing the card this weekend so I’ll try to provide some feedback as soon as I can.
Since my last relevant post regarding the HP ML150 G6, I’ve been thinking about how to tackle my education on iSCSI/NFS in my home lab environment and also replace my againg 10 year old NAS.
Lets take a step back and let me explain my storage history. About 10 years ago when I beginning to get into IT career wise, I decided to purchase an HP EX490 Mediasmart Server. This little nifty box was one of HP’s products to get their foot into the door of the home NAS market, but the EX490 was a bit more than just a regular NAS.
This unit was great when it launched and I did enjoy it what it did for me. Although, the OS was already outdated on the launch of the server, shortly after WHS v2 was released. I didn’t bother changing the OS due to the hassle and my data so stuck with the ancient v1 release.
I’ve kept this little box full with Western Digital Green 2TB drives, which have performed flawlessly over 10 years without any failures. I still have them and will post SMART data in anther post.
The EX490 was and still is a great little unit for the tasks it was designed for but we can all agree that those specs are on the light side even a few years ago. It can still handle file serving needs in 2019 for somebody that doesn’t have high requirement so I will try to find a new owner for this little box.
I also had the EX490 upgraded from it’s slow Intel Celeron 450 to a Intel E8400 CPU around that time. Look at how both CPUs compare using CPU-World here. I’ve always wanted to purchase the Intel Q9550s but back then the CPU was fairly pricey and the E8400 I had laying around from past desktop builds.
With the memory and cpu upgraded, I did notice the increase in performance and continued using the NAS for a few more years.
About 4 years ago, bored and having the want to tinker with the EX490, I finally decided to purchase the Intel Q9550s from eBay. The processor arrived and it was immediately installed. The performance bump from the E8400 to the Intel Q9550s wasn’t very noticeable for me but I was able to check that off my list. See the comparison here.
Anyways, that is my real first exposure to a home NAS/server unit, purchased sometime around 2009-2010. I have since collected more data and I’ve been on the hunt to replace the aging EX490.
I’ve toyed with the idea of a custom NAS or enterprise SAN (LOLZ) since that is really the closest thing I can somewhat relate to from my work enviroment. I didn’t know much about Terramaster, QNAP or Synology so I started searching around to try and find out which manufacturer will provide me a scalable yet powerful and quality unit. My needs were quite basic really;
Store my personal data, photos and videos from over the years. No brainer
Storage for all my Linux ISOs…
Capable of iSCSI and NFS storage that I could integrate with my HP ML150 G6 to practice storage configurations.
2-4 NICs so I could do NIC teaming and practice failover.
So on April 12th, I purchased the Synology DS1618+. The fancy matte black unit arrived and I was really excited. I compared many of the Synology units, from the DS918+ all the way to the ridiculously priced DS1819+.
I’ve played around with the DS1618+, setting a 4x2TB SHR1, Btrfs configuration for my personal data and 2x3TB RAID-1 EXT4 for what I wanted to use for datastores for VMware. I liked the OS, it was nice and basic. I was a bit surprised that enabling ‘advanced’ mode in the Synology control panel seemed to have displayed up a few more items, but everything still looked fairly basic. Regardless, it looks like a polished OS overall.
What sat wrong with me was the hardware. The processor was decent and the memory capability with ECC capable RAM is fantastic but I didn’t feel that what I paid (1100.00 CAD) was worth it. About two weeks after receiving the Synology, I noticed QNAP had a few nicer offerings. I looked at a few modes and noticed that the hardware features of QNAP are much better than Synology. Doing some searches on Google, most user’s that have used both platforms have the same opinion. Synology for the OS and updates, QNAP for the hardware. Multiple QNAP units incoporate PCIe slots (one or two) but also have intergrated 10Gb NICs. I wanted to like the Synology, so I looked at the bigger brother, the DS1819+. I don’t really want 8 bays but for scalability and being able to have a hot spare and SSD for caching (or SSD’s for VM’s) is a benefit.
The DS1618+ was starting to look like something I was going to return. Browsing on Amazon, I was surprised to see the massive total price difference between the DS1618+ and the DS1819+. My DS1618+ cost me about $1107.xx Canadian currency. The DS1819+ sells for about $1333.xx + tax, which brings it to a total of about $15xx.xx Canadian dollars.
$400.00 bucks for another 2 bays? No way Jose.
So I actively searched for a comparable but better(in my eyes) QNAP unit. I’ve looked at a few which met some of my requirements, such as the QNAP TS-932x, TVS-951X or the TS-963X. I love how they are 9-bay, have 10Gb integrated but for some reason something didn’t appeal to me.
I kept searching and I found one that looked like a small price increase over the DS1618+ but still cheaper than the DS1819+ and had more capabilities and features. The QNAP TS-873. This seems to tick off all my wants. 4 NICs, 8-bay, lower cost than the Synology unit but much better in hardware. The only real downfall I see is that the CPU uses a bit more power (15W more normal use vs the DS1618+) but the overall gains from it at the price point leave Synology in the dust (IMO of course).
Now people will say that the QNAP OS isn’t as refined as the Synology unit. Sure I get that, but that is something that QNAP can improve over the years. The hardware, well I’m stuck with for the period I plan to keep this unit for.
I am not purchasing a NAS to use at home for 2-3 years. I am looking to get something for the long haul. My HP EX490 operated pretty reliably for nearly 10 years and thankfully I had no failures.
Last night I placed an order for the TS-873 and I am excited to see what this unit holds. I did have two QNAP NAS (TS-EC879U-RP) at work so I have some familiarity of the OS already. I say did because one of them randomly failed out of the sudden. Thankfully I was able to use the other one to retrieve my data from the drives. Qnap support was pretty poor and slow. Oh well.
Anyways, that’s the gist of my storage history for the past 9-10 years. I know RAID and the number of bays are NOT backup, so fear not. Any critical data will be uploaded to Backblaze under a personal account. Their pricing seems fairly good and the general feedback about them looks to be positive.
What do you think? Do you think I made a wise choice? What do you look for when purchasing a NAS?
I want to rant. I’ve been working as an IT/Sysadmin for about 2 years now and there are two things that I am haunted by.
Now, I am always learning and I am by no means an expert at windows systems administration. I took on more and more responsibilities that removed me from the ‘IT Support’ role and let me grow into Systems Administration and I continue to learn daily.
Now, not get into specifics, but taking over a AD infrastructure that was neglected by hacks is terrifying. I refer to hacks, as in people that neglect the network, that don’t have a proper vision for documentation and structure and that don’t understand how AD and GPOs work.
Within the IT SysAdmin community “It’s always DNS” is a common phrase and a joke at times. Well god dam, I can’t believe how accurate it is or how powerful DNS is in a network.
You know what irks me? People that use crafty stupid hostnames for critical servers or any server at that. Stupid names such as “Sugar Baby” “Super Man” “Bat Man”, etc… you get the gist.
When you take over a network and have critical servers with stupid naming conventions like that, it can get very easy to shut down the wrong server or make changes because all of the names are so irrelevant. Especially when nothing is documented and you are left to your own to research and investigate carefully.
Not that I’ve had that happen, but I have had a mishap with a DNS record that was named something ridiculous. The server wasn’t even around anymore but a critical server was using that DNS record for a link to an IP in it’s hostfile. Something I never thought to check nor look into.
The other thing that annoys me is the ignorance of not knowing how to properly setup GPO’s and push them out to AD. You do NOT need to enforce everything. Stop doing that. After spending time looking around and cleaning up GPO’s, you wonder what would drive a person to just enforce everything.
Sure, if it’s a critical policy that you want in every OU regardless if it has Inheritance blocking or not but don’t enforce everything just because you are trying to push the policy out faster or believe that it will guarantee that the policy will get to the clients.
I cannot believe that a novice admin is correcting domain wide issue that a senior IT director of many years had made.
I can spend the rest of my afternoon ranting about stuff that I’ve come across but that’s not the point of this post. I wanted to get DNS and GPO’s off my chest only.
I suppose you will find this in any job/career. People that want to take initiative, drive, pride in their work and do the best with what they can. Others will just let things fall into disarray and not bother.
To give some greater context, see my previous post.
When I was initially planning on how to setup these drives, I configured them with the HP P410 RAID utility as a RAID-0 array. I made the decision to not live such a risky lifestyle and blow away the array and configure it for RAID-1. I want to build a solid homelab that will assist me in aspects of systems administration so I didn’t want to risk everything by running the wrong array.
Anyways, when I booted into VMware, I was unable to add the VMFS datastore after setting it to RAID-1.
I received the following error:
“Failed to create VMFS datastore – Cannot change the host configuration”
I did a bit of searching around and tried to re-scan the datastore and get vmwre to detect it but nothing was working. I soon came across the following VMware communities post here, user Cookies04 was on onto something.
The user identified a very familiar scenario to mine.
” From what I have seen and found this error comes from having disks that were part of different arrays and contain some data on them.”
That’s the exact thing that happened to me. RAID-0, some VMware data, then RAID-1.
I proceeded to follow the three easy steps and my issue was solved.
I didn’t really have to post all of this but I wanted to in case somebody were to come across my page and had the same issue.
The interwebz if filled with many many solutions for issues. I’m just adding what’s worked for me.
I don’t spend the amount of time on my home server as I’d like to. After a long day of sitting at my desk at work, dealing with production servers and everything super sensitive, I try to unwind a bit and work at a slow pace. My slow pace this week is my esx datastore.
I’ve spent the past couple of days thinking about how I want to setup the datastore that will contain my virtual machines. Initially I had the HP P410 RAID controller connected to two, WD Green drives in a RAID-o array. I was satisfied with that at first because the drives will run at SATA 2 speeds and hopefully RAID-0 will improve the performance ever so slightly.
Then I got thinking, my goal is to setup a ‘corporate’ environment at home. Multiple domain controllers, WSUS, Sophos Firewall, play with SNMP and PRTG monitoring but that made me realize that I don’t want to build a large environment that will go to waste if one drive was to fail. My ultimate goal is to move onto SSDs and use a more complex raid (RAID 6 or 10) for this server, but that’s down the line when I free up funds and more resources.
Last night, I decided to delete the RAID-0 array, pull out the WD Green drives and install two new-to-me 1TB SAS drives and proper cabling (Mini SAS SFF-8087 to SFF-8482+15P). I briefly talked about the cabling in this previous post.
I purchased a few SAS drives from ebay, not knowing exactly which one would be compatible with the HP P410 raid controller. Most of what I can find on the internet, points to the HP P410 controller not being picky with the brand of drives.
Initially I installed a two Seagate 1TB SAS ST1000NM0045 drives but the RAID utility would not want to see the drives. Thinking it’s the cable, I replaced it with a spare but the outcome was still the same. I did a bit of searching around and found a discussion on serverfault.com, regarding HP Proliant not recognizing EMC SAS drives. One user points out that some drives can be formatted in 520-byte sectors vs 512-byte sectors that you would normally get on normal PC/server class drives.
I haven’t tested that theory but I will. With that said, I decided to install two other drives, which surprisingly worked right away.
The drives that are functioning fine with the HP P410 raid controller are:
Dell Enterprise Plus MK1001TRKB
Seagate Constellation ES.3 ST1000NM0023
Now that I have two drive’s in a RAID-1 array, I loaded into VMware ESXi and proceeded to add a the new VMFS datastore. Adding the datastore gave me some issues, which I’ve documented here.
I have in my possession two SAMSUNG Data Center Series SV843 2.5″ 960GB drives that I purchased about 2 years ago from newegg for a fantastic price. I’ve toyed with using them in this build, but the SSD drives would only work at SATA 2 speeds. Maybe I’ll use them to house my personal data, but I should purchase a few more to do RAID-6 or RAID 1+0.
Regardless of my direction, I am still working out the kinks in my homelab environment.
Ideally, I’d like to find a cheap or reasonably priced NAS that has iSCSI ports. I then would be able create two datastores on the NAS, one for extended VM storage if required and the other for user data.
For those of you that have an older HP ProLiant server that has the HP Onboard Administrator powered by Lights-Out 100 (LO100) and want to gain two additional features, I will provide the key at the bottom.
The two features are: *Virtual Media Access *Virtual KVM
Anyways, incase anybody wants to mess with both features, here is the key:
Application License Key
Current License Key:35DRP-7B3TX-78VVM-7KX4Y-XS74X Current License Key Type:LO100 Advanced INDIVIDUAL
For a full list of specifications, features and configurations, please see the following HP Support article here.
I’m back with the ML150! 2018 was a rough year but now that it’s in the rear view mirrors, I can sit back, reflect and move forward. I started focusing more at work to keep myself busy through a few difficult times and in mid-2018, I was involved in a large network outage that took weeks to rectify with a new network rebuild. That’s another story in itself that I won’t get into.
I’ve finished my home office and I’m eager to continue my projects, the HP ML150 and my tinkering of all electronic and IT related areas.
In my corporate setting, I’ve inherited a three node VMware ESXi cluster, a two node XenServer cluster and one lonely serer running Hyper-V about 2 years ago. The ESXi cluster had its vCSA ‘broken’ as I’ve detailed here. I resolved the vCSA issue and it’s worked great since, but that whole process had me on the edge.
This is the exact reason why I am building this ESXi node at home, so that I can learn and break things in my safe environment.
I bet that if you are visiting my site and have read my previous posts, you may be wondering what I’ve decided to do regarding storage. Storage in general, is a foreign area for me that I’d like to get learn and get better at. Keep on reading…if you want to 🙂
So the ML150 G6? Well I was able to acquire the a HP P410 Raid card with Battery Backed Write Cache and a 512mb cache memory module. My only concern about this card is and was that it will do SATA 3 (6Gbps) speeds on SAS and SATA 2 (3Gpbs) speeds on SATA interfaces. Link to the HP P410 Controller Overview.
Initially I wanted to run a few 500gb SSD’s but that’s been put on hold for now due to the Sata 2 speeds of the RAID controller. I was able to purchase two 1Tb 3.5″ Seagate SAS drives that I wanted to install but I realized that I was missing the correct cabling. I purchased Mini-SAS to SFF-8087 cables, but those are incorrect and will not work with SAS drives.
The image below shows the difference between the SATA interface and the SAS interface. The difference is obvious.
With the wrong cable purchased and wanting to use the SAS drives that I have, I ordered the following cable: Mini SAS 36P SFF-8087 to SFF-8482+15P.
With the SAS cables still being in transit somewhere, I’ve resorted to just using the HP P410 Controller with the original Mini SAS to 4-Sata SFF-8087 cables and two regular SATA WD Green 2TB 7200RPM drives.
While reviewing my storage options, my interest peaked in ZFS and I purchased the highly recommended IBM M1015 RAID aka LSI SAS9220-8i controller. I suspect this is something I will dig into but not just yet. Right now I have to get this server up and running as I want to tackle some VMware projects in the coming weeks.
The physical storage for now is sorted. I installed VMware ESXi 6.5 Build 4564106 onto a USB flash drive that is plugged directly onto the motherboard of the server. No need to utilize any raid controller ports nor sata ports for a small hypervisor install.
Booting the server, I entered the HP P410 controller configuration and setup RAID-0 (NO RAID) with the two, 2TB drives. This is a lab. I can afford the loss of a drive/data. This server and this datastore will not hold any of my critical data and is only a test environment.
Raid-0 will provide me with striping and that’s fine by me as I want the most speed possible in my given situation.
I had planned to install ESXi on a smaller , non protruding USB Flash drive from the manufacturer Verbatim (16gb USB2). The ESXi installation would near 75% and crash with a timeout error. After trying a few times and trying different USB ports, it turns out the flash drive was the issue. I used a completely different brand flash drive to host the ESXi installation and it worked on the first try.
Here are two snips of my VMware ESXi management interface.
That’s about it for tonight. The ESXi install took way too long because of that oddly performing flash drive.
Long term plans are to bring in a NAS with an iSCSI interface so that I can mimic an external datastore that is not directly attached to the server. I will be building my lab-corporate environment that consists of a few Domain controllers that will run a select number of features. I would like mess with DHCP split scopes, WSUS, iron out some GPO skills and mess around with VMware.
I would like to setup vCSA here at home and possibly another node to build a 2-node cluster, but that’s not yet.
From my recent blog post regarding setting up vCenter, I had difficulties locating the area to apply the vCenter license. From what I found on the internet, it was referenced that you should go to the Host that contains the vCenter/VCSA VM, click on the VM and click on Configure. Maybe VMware changed it in version 6.7 but I could not find the same area for license registration under the VM itself.
Under the VCSA VM –> Configure –> Settings, I should see a ‘License’ section. I could not find anything of that sort. I logged in as my admin account and my personal admin account, both that have the license role and that feature was still not available.
Frustrated, I did some looking around within the vSphere client and I found the area to do this.
You need to click on the ‘top’ FQDN vCenter identifier on the left hand side of the window, which houses your Datacenter and the nodes inside.
Once you click on it, you will see the following,
As you see, now selecting the VCSA and going to the Configure section and under Settings, we now see Licensing as an option. Now in my case, I’ve already applied the license but I’m going over where I went to do this.
You would select the Assign License button to proceed with entering your key into vCenter.
Under the Assign License window, you will have two options. To select an existing license or new license. You can import the license from your License section from the admin page or you can type in your license if you haven’t already done so. I’ve already uploaded my licenses to the Administration License section, which I will show next.
Now what I have done initially was gone into the Administration section –> Licensing –> Licenses and typed in the VMware vCenter Server 6 Essential vCenter license key. When I did this, the usage of the vCenter license was set to 0 and capacity was set to 1. This was because I never assigned the license to the vCenter itself. I did this in the Assign License window as seen above.
The last and final screenshot above shows the Administrator License window which identifies my License(s) and their state and capacity.
To note: When I was in the process of importing each host, the license for those hosts registered automatically here. I did not have to enter the VMware vSphere 6 Essentials Plus License. Those just followed with each host/node into vCenter.
I’ll come out and say it, I’m not an expert or a confident user of virtualization and more specifically VMware products. Over the last bit, I’ve taken on a more senior and technical lead position at my job and that involves more to do with the infrastructure side of things and not as much ‘customer facing’. I’ve played around with VMware Workstation and Oracle VirtualBox but I haven’t done a hole lot in regards to ESXi, vCenter and the works.
I needed to ‘pull up my big boy pants’ and start learning as much as I can in the short time frame about our production ESXi cluster, trying to understand the configuration and anything that may be wrong with it.
When my department slowly withered away until it was only me, I’ve heard that our vCenter is broken and that management of the cluster is not possible. Not having VMware support, I was really concerned about this broken system and how it would negatively affect our production and highly critical cluster. I started doing some reading and came to realize that vCenter (VCSA) is only a central mangement feature. Rather than using vSphere client to manage each invidivual node/host, vCenter allows you to manage the hosts all together (in a cluster) and enabled a few features, including High Availability (HA) and vMotion (allowing to move VM’s from host to host without downtime).
Knowing this, I spent any downtime I had reading up about vCenter and VCSA. I looked at different installation methods (Windows vs Linux) the pros and cons of each. vCenter can be installed on top of a Windows installation or it can be configured on a Linux machine and often referred to VCSA (vCenter Server Appliance).
My first question was regarding what vCenter/VCSA can I use with my cluster? Luckly, I came across a page on VMware site that helps identify the version of ESXi and what version of vCenter is compatible.
With that sorted, I downloaded the most recent version of vCenter 6.7U1. I choose to download the Linux installation rather than mess with Windows and use up a license for it.
Now with the .ISO downloaded, I searched high and low to find a good step by step guide on how to complete this install. I already shut down the old vCenter VM that was previously created by our IT staff, which was having issued and filling it’s storage with logs. Rather than try to troubleshoot it, I wanted to start with a fresh install.
I came across this fantastic link that helped me tremendously for setting up and installing my VCSA. The notes and screenshots helped a novice like myself through this process.
As this was a live production setup, I was always fearful of something occurring but unfortunately I don’t have the resources to do it any other way.
Anyways, I felt that I wanted to share this quick post and the link to the site that helped me through this process. Good articles go a long way in helping others out and that is one thing I want to focus with this blog site. To provide good information that I discover or come across.
It feels like it’s been a while since my last post here. A recap from the previous WQHD T430s post, the AUO screen that I received had a light bleed defect in it. It wasn’t a huge problem but for the cost of a new screen, I wanted a display with no defects. I returned the screen and decided to test my luck with the LG LP140QH1SPB1 display.
I was really excited that this time around everything would be smooth like butter. I was wrong.
Let’s start off with the fitment of the LG LP140QH1 SPB1 compared to the AUO B140QAN01.5 panel.
The top mounting points on both panels fit perfectly. Both panels can utilize the factory top screw mounting points without issues.
The bottom two panel mount points on both displays don’t fit but the AUO display is much closer to fitting then the LG panel. Unfortuinately I didn’t take pictures of the AUO display but take my word. With some precision and a dremel, you could slighly widen the AUO bottom mount holes and they should work fine.
The LG display required me to shave off some extra plastic that prevent the panel from sitting flush in the housing.
Let’s look at a few images I took while installing the LG panel.
The first image shows two things. All four mounting points on the bezel housing have two ways of securing the panel in place(see red arrow). The first method is the screw. The second method is a plastic nipple that is right beside the screw point. This nipple helps allign and seat the panel into it’s spot, allowing the screw to be threaded in properly. The AUO panel, each mounting tab has two wholes. The LG panel only has one hole per mount point.
The second issue shown in the first image is marked in the yellow arrow. There was a tiny plastic piece that was used in securing the front display bezel. With that plastic clip, I was unable to lay the display down as it was pushing up against the panel circuit board. I had to remove it and with that out of the way, the circuit board didn’t have pressure on it.
The second image, with the yellow box shows the plastic clip that I had to break off.
The third image shows the usual mounting points (2 securing methods per mount).
The fourth image shows a better angle of the left mount point that was discussed in the first image.
The two images above are of the right side. The right side also presented almost the same problems with seating the panel into the display housing.
The image on the left shows outlined in a red box the plastic nipple that is used for the secondary securing method. This had to be removed also for the panel to sit as flush as possible.
The right image shows the panel sitting much closer to the mount point, with that plastic nipple removed. Sorry about the low quality photos and angles. I do what I can with what I have.
Now that we have the panel sitting properly, I decided to turn on the T430s and see how the panel works. Before we get further into this, I want to make a note that I did turn on the display initially before doing any modifications. The display looked fine but I didn’t test it with anything white open on the screen, which tends to show imperfections I find.
With that laptop loaded into Windows 10, I opened up This PC and was disappointed with my finding.
Looking at the panel with a white background, you can see white marks on the panel in multiple spots. This sucked bad. I went over all the connections and made sure nothing was causing this. I even removed the front display bezel but it didn’t help. This wasn’t an issue of the panel being sandwiched too tight in the housing. It was just another screen defect.
I use the factory Windows 10 dark blue/black background and upon loading up, you wouldn’t notice this instantly. Eventually it would become visible through regular operation.
Well that’s it for now. I shipped the panel back yet again to this other ebay seller. I had a complete refund of the screen (including return shipping fee) and now I’m back to where I started.
I’m concerned about buying the AUO B140QAN01.5 screen and I won’t buy the LG one anymore. I’ve contacted the seller of the AUO screen that I purchased before, asking if they got a new shipment of panels. The response I received:
We’re sorry to tell you that this model screen is new,all have a little light leakage on the middle of the left and right side.
We asked many of our suplier,they all said this screen have this problem.
Thanks for your time and patience.
Have a good day!
Looking at this post here, I may just purchase the AUO B140QAN01.1 and give that a whirl.