New answers tagged hard-drive
Yes, the capacity will grow in btrfs when you replace the drives with bigger ones. But make sure you always have backups! While the RAID0/1 code is not nearly as buggy as the RAID5/6 code in btrfs (as of 07/2016), your device replacement would not be the first one to go horrible wrong.
Perhaps the issue is caused by incompatible versions of CIFS/SMB. On one of the Win10 systems that fail to connect, please try the following: Run appwiz.cpl (The add/remove programs wizard). Click "Turn Windows features on or off" Enable "SMB 1.0/CIFS File Sharing Support" Make sure to close all File Explorer instances, then try to re-connect.
I use diskinfo tool to get accurate and current information about the hard disk attached to my office laptops, desktop and servers. its portable and handle tool. I followed under URL to reach this tool: https://www.windowstechupdates.com/how-to-check-hard-drive-real-age/
One disk at a time. Let each drive rebuild successfully, then replace the next drive. That's all. (replacing all disks at the same time == data loss - don't do that!)
Everything I can find points to the fact that the only "Supported" WinPE environment for this hardware is WinPE 10. Official Link Requirements Below are the requirements to install Windows 7 with the m2 SSD. "RAID On" enabled in BIOS. "UEFI Boot with Legacy Option ROM enabled" in BIOS. Windows PE 10.0.10586 Intel Rapid Storage 14.5....
Having those errors across multiple drives seems to indicate a backplane/controller/cabling problem more than a disk or RAM issue.
People generally speak about bit rot in regards to RAID rebuilds, as it is the worst time to encounter a unrecoverable read error. Issues with rebuilds can generally be boiled down to 3 areas. hardware failure (during a rebuild), user error, and poor maintenance. I have seen lots of users try to "recover" a RAID volume, and just make things worse for ...
My general rule of thumb is that if the errors are continuing to rise unexpectedly, the disk needs replaced; if it's static, there might have been some transient condition that caused the error, and the system's not reproducing the conditions that caused problems. A few checksum errors doesn't necessarily indicate anything bad mechanically with the drive (...
DVR drives are tuned for sequential IO workloads. Random IO speeds will suffer if you use these, but depending on your load and IO profile, this may not be a problem.
/dev/sdc2 failed. It will need to be replaced.
Very often "External" HDDs are reported with wrong size, if the size of the HDD exceeds the supported maximum size of the usb bridge. if the external hhd is an bundled enclosure you can ignore my answer, if it is something like a docking station this could be your problem. try a different enclosure that supports 3tb hdds and up...
Well I tried it and it worked. Turns out new revisions of SAS are compatible with hardware supporting only an older revision of SAS. (though they do not get the higher throughput supported) I'm not aware of any capacity ceiling on older SAS hardware. I did stick with the same brand Seagate, though I wouldn't be surprised if any brand of SAS drive would work....
Top 50 recent answers are included