I had a RAID 5 array with (3) Seagate ST336752LC drives. Firmware version 0002 on the original drives. The RAID controller shows them having 34941MB each.
One drive failed, so I ordered another ST336752LC drive. This one has a *newer* firmware and measures up a whopping 200MB *smaller* than the original drives.
This is preventing the RAID BIOS from adding the new drive to the array.
The known defect list is about 3 times larger (1100, as opposed to 200 - 400 on the other drives), but even a variation of 200 defects between the other drives doesn't change the drive size by even 1MB.
Download seatools for DOS from Seagate's site and set the drive size to be maximum, the drive you have has probably been OEM'd to someone who set the size smaller. OEMs who use several disk vendors will
Network Monitoring is essential to ensure that computer systems and network devices are running. Use PRTG to monitor LANs, servers, websites, applications and devices, bandwidth, virtual environments, remote systems, IoT, and many more. PRTG is easy to set up & use.
First I will try to share a design of a Veeam Backup Infrastructure without Direct NFS Access backup.
Note: Direct NFS Access backup transport mechanism is only available in Veeam v9
In above I try to design the Veeam Backup flow between i…
In this Micro Tutorial viewers will learn how to use Windows Server Backup to create full image of their system. Tutorial shows how to install Windows Server Backup Feature on Windows 2012R2 and how to configure scheduled Bare Metal Recovery backup.…
In this Micro Tutorial viewers will learn how to restore single file or folder from Bare Metal backup image of their system. Tutorial shows how to restore files and folders from system backup. Often it is not needed to restore entire system when onl…