mrbens

Members
  • Posts

    101
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

mrbens's Achievements

Apprentice

Apprentice (3/14)

4

Reputation

  1. Thank you. Swapped out disk 14 for a spare disk I was going to use for backups and moved it to another server to try a Preclear. With all the read errors during the parity-sync, does that mean there's likely to be corrupt files when disk 14 gets rebuilt from parity?
  2. Extended SMART test didn't go too well. Got to around 70% and now the disk has been error disabled after a further 1024 errors. This is about the 8th disk recently to fail. Really don't know what's going on. Attached diagnostics. Please advise if there's anything else to do, but guess it'll need replacing. Thank you. tower-diagnostics-20230121-1623.zip
  3. Another day, another disk failure. Not having the best luck lately. Moved an 8TB disk from my main server to new HP Gen10 Plus Microserver to Preclear to re-use. The disk has been working fine in my main server for years. It had 73 historic UDMA CRC error count already, but as far as I'm aware that's more a cable issue and not anything to get too worried about. Preclear was going fine until about 60% into the post-read when it failed due to reported uncorrect, current pending sector and offline uncorrectable SMART errors. Attached diagnostics. Please advise if there's anything I should do or if the disk will likely need disposing of. Thank you. backup-diagnostics-20230120-1855.zip
  4. Thanks trurl. Parity has about an hour left to finish syncing, then I'll start the extended SMART test. No further errors luckily. Is it worth doing another parity check after the SMART test?
  5. Thanks. How do you remove disks without invalidating parity please?
  6. Hi trurl, thanks for the reply. I did New Config since I was removing a disk to move to another server and also removing 3 disks that had either died or SMART errors were incrementing that I'd copied the data off (https://forums.unraid.net/topic/133224-6115-disk-9-disabled-after-1175-errors/). Is that the correct way to remove disks from the array? Had a few other changes to make at the same time as removing the disks, so since I needed to do New Config sorted it all at once to let parity rebuild: Added second parity. Added a new data disk. Moved a disk physically in the server and on the GUI to another slot. Cables for disk 14 seem securely in. Is there anything you recommend I do with disk 14 such as extended SMART test or check filesystem? When the parity sync finishes, should I do another parity check to see if it completes without errors?
  7. Installed a second parity disk yesterday and the parity sync is currently at 46%. Just got home to see disk 14 has had 327,424 read errors. Doesn't look to be any serious SMART errors. It's connected to a Broadcom 8 Port 6Gbps SAS 9207-8i SGL PCI-E Host Bus Adaptor. Doesn't seem to be any issues with the others disks connected to the controller. Bit worried if it fails as I have no parity at the moment and have had a few disks fail recently. Attached diagnostics. Please advise. tower-diagnostics-20230119-2218.zip
  8. Managed to move most data off the 3 disks. Luckily didn't lose anything important. It was getting a bit scary with all the errors on disk 6 which made it slow to copy the data off disks 6 and 9! Probably got some corrupt files, but luckily the disks are in a share of unimportant files. Currently trying to erase and clear them to dispose of, but 2 of them are taking a very long time due to the errors and keep pausing temporarily. Top one says 35MB/s but only does that for a few seconds before pausing for a while. Is it worth skipping the pre and post read on them, or is it recommended to leave them all to finish normally? The bottom disk is erasing at a really slow speed. Guess there's nothing I can do about that.
  9. Thank you. I'm running it with --rebuild-tree now as it suggested on the read only check. Hope all goes well.
  10. Used the rsync command below to copy 8TB disk 3 (resierfs) to 16TB disk 2 (xfs), so I can move disk 3 to another server, but got an error at the end: rsync -avPX /mnt/disk3/ /mnt/disk2/ sent 7,049,131,125,720 bytes received 195,551 bytes 61,352,544.89 bytes/sec total size is 7,035,745,316,299 speedup is 1.00 rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1336) [sender=3.2.7] Think it's just 13 GB that wouldn't copy, but struggling to find how to check the previous errors to see which files(s) were affected. How do I check this please? The following lines repeated many times in the syslog which seem to be related: Jan 12 02:32:32 Tower kernel: REISERFS error (device md3): vs-5150 search_by_key: invalid format found in block 4027868. Fsck? Jan 12 02:32:32 Tower kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 966 does not match to the expected one 2 There's still 1.5TB free on disk 2. Attached diagnostics. ------------------------------------------------------------------------------------------------------------------------- Currently in the process of converting all my disks to xfs. I'll be adding a new 18TB disk into the disk 3 slot once the 8TB has been removed. Is it better to format the existing resierfs 8TB in slot 3 to xfs, then swap it out for the new 18TB or use New Config to remove the 8TB and add the 18TB into the same slot? I'd think it's best to convert the 8TB to xfs first so just that empty disk has to rebuild instead of having to rebuild the parity leaving the array unprotected for a couple of days but just want to double check. Thank you for any assistance. tower-diagnostics-20230113-1101.zip
  11. Stopped the short SMART test of disk 6 and the rysnc speed improved again. 1,211,924,480 11% 23.21MB/s 0:06:17 After disk 9 has finished copying to disk 1, I could copy disk 10 and then disk 6 to disk 1 too. Disks 6, 9 and 10 are only small old 3TB and 2TB luckily, so don't mind removing them from the array in case they die soon. Disk 10 now on 760 reallocated sectors. Disk 6 hasn't increased from 6304. Stopped the extended test too and rysnc speed briefly went as high as 49MB/s but then stayed around or under 18MB/s on big files since then. For peace of mind I'd rather copy off all the data quicker and can test them later when they are not part of the array. Had 2 disks fail at the same time before and lost one of them completely, the other I could save a lot with ddrescue but it took months and had a lot of corrupt files.
  12. Thanks JorgeB. I've got an extended test running now. itimpi just realised I had notices and warnings disabled and just had notifications for OS updates and alerts. I've enabled them now and worryingly it looks like disk 6 is also having issues with reallocated sectors. I'm currently running rsync -avPX /mnt/disk9/ /mnt/disk1/ to do New Config to remove disk 9 as I've got space on disk 1 for now, but worried about doing that in case disk 6 fails and would leave me without parity to rebuild it. Disk 10 now too: Currently up to 592 reallocated sectors 30 minutes later. No new errors on the Main page. Attached new diagnostics. What would you recommend please? rsync speed has also dropped to under 3MB/s while running a SMART extended test of disk 9 and short test of disk 6. 5,150,177,280 100% 25.63MB/s 0:03:11 (xfr#782, ir-chk=1052/2045) 8,468,856,832 46% 2.60MB/s 1:01:37 It was running about 25MB/s earlier, and I think over 50MB/s previously when copying a different disk to convert to xfs a few days ago when no disks were disabled. I can understand why it's slower now with a disabled disk, but should the SMART checks be slowing it down so much from 25MB/s to 3MB/s? Short SMART seems to be stuck on 90%. Holding off running a test on disk 10 while the server is busy. Once I've finished converting all my disks to xfs I'm adding a second parity as I've had issues with a few disks recently. tower-diagnostics-20230105-0529.zip
  13. Need some assistance please. Disk 9 has been disabled after 1175 read and write errors. SMART not looking good. Attached diagnostics. Does it look like it'll need binning, or is it worth replacing the SATA cable with a new one and trying a preclear to re-add it? Thanks. tower-diagnostics-20230104-1035.zip