wildfire305

I am unable to figure out how to search the 41 pages of the post for the information I'm looking for. Can you explain how to properly use the tool to run a manual verify? I have this set to run on the 15th and it alerted me this morning to 10 corrupted files on a share that I had excluded (I excluded it after the automatic hash creation had run on the share). After reading the extremely helpful tooltips in the tool, I realize now that I needed to run the clear command after excluding the directory share. I ran that and everything is green checkmarks. Now I want to run a verify again so I get a clean report. Is it the "check export" button? Bonus info: The share I excluded was rapidly changing data from system backups that I knew did not need to be verified and didn't want to waste resources on. Those directories change multiple times a day. That's the share that reported the 10 errors which I'm confident the files changed since they were hashed.

Once you flash the firmware is it durable? I mean to say is it once and done? it doesn't revert back on its own or have bugs?

What little research I've done looks like I may need to perform a complicated firmware flash procedure to get it into IT mode. I'm willing to go for it since I have nothing to lose.

I have a Dell h310 (I think) card laying around (it was sent to me by mistake) It has two internal ports. I don't have any more room inside the Dell t5810 case for more disks. I would like to use that card and convert it to external using a slot adapter. And build or buy an external enclosure but it's unfamiliar territory for me. It looks like an area where I could easily buy the wrong thing and waste money on something I can't use. Is there any guidance on how to set those up. Do you have any suggestions on where I can look to gain that knowledge? I really really do want to stop using the esata enclosures because I know it is my main bottleneck.

It has no independent cable. It's in an external esata enclosure and the other two disks are fine. I would assume a bad esata cable would cause issues with all the disks in the enclosure. I could try a different slot, I have one free. cvg02-diagnostics-20211014-1219.zip

Realizing they are not color coded in this forum, I'm referring to the frozen and flush errors.

Can anyone interpret this log for me? 6 disks in the array including the parity and this is the only one with errors in the log. No errors on the main screen, no smart failures, no issues with the data. Just these errors in the log. It is in an external esata four bay box with two other disks that report no errors in the array. ErrorWarningSystemArray Oct 10 20:42:50 CVG02 kernel: ata10: SATA max UDMA/133 abar m8192@0xf7180000 port 0xf7180180 irq 40 Oct 10 20:42:50 CVG02 kernel: ata10: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Oct 10 20:42:50 CVG02 kernel: ata10.00: ATA-8: SAMSUNG HD204UI, S2H7J9AZA00533, 1AQ10001, max UDMA/133 Oct 10 20:42:50 CVG02 kernel: ata10.00: 3907029168 sectors, multi 0: LBA48 NCQ (depth 32), AA Oct 10 20:42:50 CVG02 kernel: ata10.00: configured for UDMA/133 Oct 10 20:42:50 CVG02 kernel: sd 10:0:0:0: [sdg] 3907029168 512-byte logical blocks: (2.00 TB/1.82 TiB) Oct 10 20:42:50 CVG02 kernel: sd 10:0:0:0: [sdg] Write Protect is off Oct 10 20:42:50 CVG02 kernel: sd 10:0:0:0: [sdg] Mode Sense: 00 3a 00 00 Oct 10 20:42:50 CVG02 kernel: sd 10:0:0:0: [sdg] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Oct 10 20:42:50 CVG02 kernel: sdg: sdg1 Oct 10 20:42:50 CVG02 kernel: sd 10:0:0:0: [sdg] Attached SCSI disk Oct 10 20:44:15 CVG02 emhttpd: SAMSUNG_HD204UI_S2H7J9AZA00533 (sdg) 512 3907029168 Oct 10 20:44:16 CVG02 emhttpd: read SMART /dev/sdg Oct 10 20:44:59 CVG02 emhttpd: read SMART /dev/sdg Oct 10 20:45:29 CVG02 emhttpd: SAMSUNG_HD204UI_S2H7J9AZA00533 (sdg) 512 3907029168 Oct 10 20:45:29 CVG02 kernel: mdcmd (6): import 5 sdg 64 1953514552 1 SAMSUNG_HD204UI_S2H7J9AZA00533 Oct 10 20:45:29 CVG02 kernel: md: import disk5: (sdg) SAMSUNG_HD204UI_S2H7J9AZA00533 size: 1953514552 erased Oct 10 20:45:29 CVG02 emhttpd: read SMART /dev/sdg Oct 10 20:46:20 CVG02 emhttpd: writing MBR on disk (sdg) with partition 1 offset 64, erased: 0 Oct 10 20:46:20 CVG02 emhttpd: re-reading (sdg) partition table Oct 10 20:46:21 CVG02 kernel: sdg: sdg1 Oct 10 20:46:21 CVG02 kernel: sdg: sdg1 Oct 10 23:32:51 CVG02 kernel: ata10.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen Oct 10 23:32:51 CVG02 kernel: ata10.00: failed command: FLUSH CACHE EXT Oct 10 23:32:51 CVG02 kernel: ata10.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 13 Oct 10 23:32:51 CVG02 kernel: ata10.00: status: { DRDY } Oct 10 23:32:51 CVG02 kernel: ata10: hard resetting link Oct 10 23:32:51 CVG02 kernel: ata10: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Oct 10 23:32:51 CVG02 kernel: ata10.00: configured for UDMA/133 Oct 10 23:32:51 CVG02 kernel: ata10.00: retrying FLUSH 0xea Emask 0x4 Oct 10 23:32:51 CVG02 kernel: ata10: EH complete Oct 10 23:38:10 CVG02 kernel: ata10.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen Oct 10 23:38:10 CVG02 kernel: ata10.00: failed command: FLUSH CACHE EXT Oct 10 23:38:10 CVG02 kernel: ata10.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 24 Oct 10 23:38:10 CVG02 kernel: ata10.00: status: { DRDY } Oct 10 23:38:10 CVG02 kernel: ata10: hard resetting link Oct 10 23:38:11 CVG02 kernel: ata10: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Oct 10 23:38:11 CVG02 kernel: ata10.00: configured for UDMA/133 Oct 10 23:38:11 CVG02 kernel: ata10.00: retrying FLUSH 0xea Emask 0x4 Oct 10 23:38:11 CVG02 kernel: ata10: EH complete Oct 11 00:27:32 CVG02 kernel: ata10.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen Oct 11 00:27:32 CVG02 kernel: ata10.00: failed command: FLUSH CACHE EXT Oct 11 00:27:32 CVG02 kernel: ata10.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 20 Oct 11 00:27:32 CVG02 kernel: ata10.00: status: { DRDY } Oct 11 00:27:32 CVG02 kernel: ata10: hard resetting link Oct 11 00:27:32 CVG02 kernel: ata10: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Oct 11 00:27:32 CVG02 kernel: ata10.00: configured for UDMA/133 Oct 11 00:27:32 CVG02 kernel: ata10.00: retrying FLUSH 0xea Emask 0x4 Oct 11 00:27:32 CVG02 kernel: ata10: EH complete Oct 11 01:29:27 CVG02 kernel: ata10.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen Oct 11 01:29:27 CVG02 kernel: ata10.00: failed command: FLUSH CACHE EXT Oct 11 01:29:27 CVG02 kernel: ata10.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 18 Oct 11 01:29:27 CVG02 kernel: ata10.00: status: { DRDY } Oct 11 01:29:27 CVG02 kernel: ata10: hard resetting link Oct 11 01:29:27 CVG02 kernel: ata10: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Oct 11 01:29:27 CVG02 kernel: ata10.00: configured for UDMA/133 Oct 11 01:29:27 CVG02 kernel: ata10.00: retrying FLUSH 0xea Emask 0x4 Oct 11 01:29:27 CVG02 kernel: ata10: EH complete Oct 11 01:41:44 CVG02 kernel: ata10.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen Oct 11 01:41:44 CVG02 kernel: ata10.00: failed command: FLUSH CACHE EXT Oct 11 01:41:44 CVG02 kernel: ata10.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 17 Oct 11 01:41:44 CVG02 kernel: ata10.00: status: { DRDY } Oct 11 01:41:44 CVG02 kernel: ata10: hard resetting link Oct 11 01:41:44 CVG02 kernel: ata10: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Oct 11 01:41:44 CVG02 kernel: ata10.00: configured for UDMA/133 Oct 11 01:41:44 CVG02 kernel: ata10.00: retrying FLUSH 0xea Emask 0x4 Oct 11 01:41:44 CVG02 kernel: ata10: EH complete Oct 11 01:42:45 CVG02 kernel: ata10.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen Oct 11 01:42:45 CVG02 kernel: ata10.00: failed command: FLUSH CACHE EXT Oct 11 01:42:45 CVG02 kernel: ata10.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 26 Oct 11 01:42:45 CVG02 kernel: ata10.00: status: { DRDY } Oct 11 01:42:45 CVG02 kernel: ata10: hard resetting link Oct 11 01:42:46 CVG02 kernel: ata10: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Oct 11 01:42:46 CVG02 kernel: ata10.00: configured for UDMA/133 Oct 11 01:42:46 CVG02 kernel: ata10.00: retrying FLUSH 0xea Emask 0x4 Oct 11 01:42:46 CVG02 kernel: ata10: EH complete Oct 11 01:49:31 CVG02 kernel: ata10.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen Oct 11 01:49:31 CVG02 kernel: ata10.00: failed command: FLUSH CACHE EXT Oct 11 01:49:31 CVG02 kernel: ata10.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 7 Oct 11 01:49:31 CVG02 kernel: ata10.00: status: { DRDY } Oct 11 01:49:31 CVG02 kernel: ata10: hard resetting link Oct 11 01:49:31 CVG02 kernel: ata10: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Oct 11 01:49:31 CVG02 kernel: ata10.00: configured for UDMA/133 Oct 11 01:49:31 CVG02 kernel: ata10.00: retrying FLUSH 0xea Emask 0x4 Oct 11 01:49:31 CVG02 kernel: ata10: EH complete Oct 11 01:55:35 CVG02 kernel: ata10.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen Oct 11 01:55:35 CVG02 kernel: ata10.00: failed command: FLUSH CACHE EXT Oct 11 01:55:35 CVG02 kernel: ata10.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 16 Oct 11 01:55:35 CVG02 kernel: ata10.00: status: { DRDY } Oct 11 01:55:35 CVG02 kernel: ata10: hard resetting link Oct 11 01:55:36 CVG02 kernel: ata10: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Oct 11 01:55:36 CVG02 kernel: ata10.00: configured for UDMA/133 Oct 11 01:55:36 CVG02 kernel: ata10.00: retrying FLUSH 0xea Emask 0x4 Oct 11 01:55:36 CVG02 kernel: ata10: EH complete Oct 11 05:42:03 CVG02 kernel: ata10: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Oct 11 05:42:09 CVG02 kernel: ata10.00: qc timeout (cmd 0x27) Oct 11 05:42:09 CVG02 kernel: ata10.00: failed to read native max address (err_mask=0x4) Oct 11 05:42:09 CVG02 kernel: ata10.00: HPA support seems broken, skipping HPA handling Oct 11 05:42:09 CVG02 kernel: ata10.00: revalidation failed (errno=-5) Oct 11 05:42:09 CVG02 kernel: ata10: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Oct 11 05:42:09 CVG02 kernel: ata10.00: configured for UDMA/133 Oct 11 06:57:56 CVG02 emhttpd: spinning down /dev/sdg Oct 11 07:48:17 CVG02 emhttpd: read SMART /dev/sdg Oct 11 08:50:57 CVG02 emhttpd: spinning down /dev/sdg Oct 11 09:01:09 CVG02 emhttpd: read SMART /dev/sdg Oct 11 10:13:01 CVG02 emhttpd: spinning down /dev/sdg Oct 11 12:05:17 CVG02 emhttpd: read SMART /dev/sdg Oct 11 14:03:31 CVG02 emhttpd: spinning down /dev/sdg Oct 11 15:00:08 CVG02 emhttpd: read SMART /dev/sdg Oct 11 16:07:01 CVG02 emhttpd: spinning down /dev/sdg Oct 11 16:36:50 CVG02 emhttpd: read SMART /dev/sdg Oct 11 17:58:58 CVG02 kernel: ata10.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen Oct 11 17:58:58 CVG02 kernel: ata10.00: failed command: FLUSH CACHE EXT Oct 11 17:58:58 CVG02 kernel: ata10.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 5 Oct 11 17:58:58 CVG02 kernel: ata10.00: status: { DRDY } Oct 11 17:58:58 CVG02 kernel: ata10: hard resetting link Oct 11 17:58:59 CVG02 kernel: ata10: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Oct 11 17:58:59 CVG02 kernel: ata10.00: configured for UDMA/133 Oct 11 17:58:59 CVG02 kernel: ata10.00: retrying FLUSH 0xea Emask 0x4 Oct 11 17:58:59 CVG02 kernel: ata10: EH complete Oct 11 18:05:52 CVG02 kernel: ata10.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen Oct 11 18:05:52 CVG02 kernel: ata10.00: failed command: FLUSH CACHE EXT Oct 11 18:05:52 CVG02 kernel: ata10.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 23 Oct 11 18:05:52 CVG02 kernel: ata10.00: status: { DRDY } Oct 11 18:05:52 CVG02 kernel: ata10: hard resetting link Oct 11 18:05:52 CVG02 kernel: ata10: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Oct 11 18:05:52 CVG02 kernel: ata10.00: configured for UDMA/133 Oct 11 18:05:52 CVG02 kernel: ata10.00: retrying FLUSH 0xea Emask 0x4 Oct 11 18:05:52 CVG02 kernel: ata10: EH complete Oct 11 19:14:03 CVG02 emhttpd: spinning down /dev/sdg Oct 11 20:18:06 CVG02 emhttpd: read SMART /dev/sdg Oct 11 21:20:19 CVG02 emhttpd: spinning down /dev/sdg Oct 11 21:52:38 CVG02 emhttpd: read SMART /dev/sdg Oct 11 21:57:20 CVG02 emhttpd: read SMART /dev/sdg Oct 11 21:59:34 CVG02 emhttpd: spinning down /dev/sdg Oct 11 22:26:33 CVG02 emhttpd: read SMART /dev/sdg Oct 11 22:53:57 CVG02 kernel: ata10.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen Oct 11 22:53:57 CVG02 kernel: ata10.00: failed command: FLUSH CACHE EXT Oct 11 22:53:57 CVG02 kernel: ata10.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 8 Oct 11 22:53:57 CVG02 kernel: ata10.00: status: { DRDY } Oct 11 22:53:57 CVG02 kernel: ata10: hard resetting link Oct 11 22:53:57 CVG02 kernel: ata10: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Oct 11 22:53:57 CVG02 kernel: ata10.00: configured for UDMA/133 Oct 11 22:53:57 CVG02 kernel: ata10.00: retrying FLUSH 0xea Emask 0x4 Oct 11 22:53:57 CVG02 kernel: ata10: EH complete Oct 11 23:56:31 CVG02 emhttpd: spinning down /dev/sdg Oct 12 02:00:42 CVG02 emhttpd: read SMART /dev/sdg Oct 12 03:45:12 CVG02 emhttpd: spinning down /dev/sdg Oct 12 03:55:21 CVG02 emhttpd: read SMART /dev/sdg Oct 12 05:46:06 CVG02 emhttpd: spinning down /dev/sdg Oct 12 06:23:57 CVG02 emhttpd: read SMART /dev/sdg Oct 12 07:25:36 CVG02 emhttpd: spinning down /dev/sdg Oct 12 08:01:19 CVG02 emhttpd: read SMART /dev/sdg Oct 12 10:34:58 CVG02 emhttpd: spinning down /dev/sdg Oct 12 12:05:02 CVG02 emhttpd: read SMART /dev/sdg Oct 12 14:24:11 CVG02 emhttpd: spinning down /dev/sdg Oct 12 14:31:18 CVG02 emhttpd: read SMART /dev/sdg Oct 12 15:33:47 CVG02 emhttpd: spinning down /dev/sdg Oct 12 17:16:46 CVG02 emhttpd: read SMART /dev/sdg Oct 13 01:38:48 CVG02 emhttpd: spinning down /dev/sdg Oct 13 02:32:06 CVG02 emhttpd: read SMART /dev/sdg Oct 13 06:39:44 CVG02 emhttpd: spinning down /dev/sdg Oct 13 07:37:18 CVG02 emhttpd: read SMART /dev/sdg Oct 13 09:09:14 CVG02 emhttpd: spinning down /dev/sdg Oct 13 10:28:07 CVG02 emhttpd: read SMART /dev/sdg Oct 13 14:01:20 CVG02 emhttpd: spinning down /dev/sdg Oct 13 15:39:55 CVG02 emhttpd: read SMART /dev/sdg Oct 13 16:43:03 CVG02 emhttpd: spinning down /dev/sdg Oct 13 17:46:17 CVG02 emhttpd: read SMART /dev/sdg Oct 13 18:48:47 CVG02 emhttpd: spinning down /dev/sdg Oct 13 20:41:40 CVG02 emhttpd: read SMART /dev/sdg Oct 13 22:02:20 CVG02 emhttpd: spinning down /dev/sdg Oct 13 22:24:03 CVG02 emhttpd: read SMART /dev/sdg Oct 13 23:54:40 CVG02 emhttpd: spinning down /dev/sdg Oct 14 01:43:30 CVG02 emhttpd: read SMART /dev/sdg Oct 14 03:04:13 CVG02 emhttpd: spinning down /dev/sdg Oct 14 03:55:43 CVG02 emhttpd: read SMART /dev/sdg Oct 14 05:47:14 CVG02 emhttpd: spinning down /dev/sdg Oct 14 06:46:40 CVG02 emhttpd: read SMART /dev/sdg Oct 14 07:48:34 CVG02 emhttpd: spinning down /dev/sdg Oct 14 09:00:32 CVG02 emhttpd: read SMART /dev/sdg Oct 14 10:28:13 CVG02 emhttpd: spinning down /dev/sdg Oct 14 11:48:16 CVG02 emhttpd: read SMART /dev/sdg DONE

Agreed. I have also had to tell my apc I replaced that battery using the windows app.

Thanks for the quick response. It's nice to know you guys have thought through these scenarios. I have two parity. Does that change anything?

Hypothetically, if a drive failed on the 30th and a parity check was scheduled for the next morning, what would happen? By default, "Wite corrections to parity" is left turned on in this hypothetical scenario, and no user intervention is possible. Will the parity check destroy the data, will it stop and not run, what is the programmed response to this scenario?

oops I realized I posted this on a solved thread. Sorry, I'll make a new one.

Question related to this: If a drive failed on the 30th and a parity check was scheduled for the next morning, what would happen? Edit: by default correcting parity check is left turned on in this hypothetical scenario, and no user intervention is possible. Will the parity check destroy the data, will it stop and not run, what is the programmed response to this scenario?

Bump... Anyone have any comments on this idea. My theory is that I can point snapraid to the mnt/disk1, etc. Area and use just one more drive as a snapshot backup/parity 3. Then I wouldn't have to use a whole bunch of drives to make a backup of my system. (yes, I also already have full backups and cloud backups.)

The error I get when trying to add a channel is "405 Method not allowed" syntax I'm using is https://www.youtube.com/c/PracticalEngineeringChannel with or without a trailing backslash it fails. But I managed to add one channel this way, it just won't add more.

I use foldersyncpro on my androids for local ftp backup every night to the server. Very simple and I can easily modify it temporarily to go to a different ftp or multiple ftps.

@UnBeastRaid I find b2 very easy to use with Duplicati. If you do some research on Glacier and find it easy to use with Duplicati or other, let me know, I might switch or do both.

I'm using 2 parity for three data disks. A full set of offline backups updated weekly-ish manually using a windows box (for a different storage media/file system), a second offline backup as ZFS. The personal data is in encrypted veracrypt containers in case of cyber theft or actual theft. And B2 for the irreplaceable stuff. If you have a friend willing to host an offsite backup in exchange for an offsite backup for their stuff, that can be free. But if you both live in the same geographic area, you're not protected from a massive natural disaster. I tried that, but my parents' internet bandwidth was unable to support timely backups.

Oh wow glacier is a tiny bit cheaper. I didn't know about that one. How does it compare to using backblaze?

Backblaze b2 using a duplicati docker is the cheapest of all. Or a mirror backup to a windows desktop os using storage spaces or drivepool + snapraid for backblaze unlimited $7 a month. Those are the cheapest options. Someone made a backblaze unlimited docker, but it's really hinky and I wouldn't trust it after I tried it for five minutes.

It did not change the permissions on the folders in question. I know that is exactly what it is for, but it didn't work. Manually chmod 777 the folders did correct the problem I was experiencing.

Performing the above command led me to a list of 6 directories with the same strange permissions. One of them contained some unimportant data. So I decided to chmod 777 it. That changed the permissions to match all the others: owner: nobody, group: users with read write execute permissions and now everything works correctly in that directory over the samba share. Is it safe to perform that to the other five directories and not worry about how they became read only unless it happens again?

ls -l -h -R | grep dr- Answered my own question after RTFM.

A surface level inspection showed only three folders are affected by these permissions and only at their base. All subdirectories inside the wonkily permissioned base folder are normal. Pictures, Music, Home Videos. I dove into several subdirectories and manually listed permissions (I don't know the syntax to get it to tell me what I want to know in one shot). These are accessed by Plex and Jellyfin. Those apps also access the Movies folder which has normal permissions. I'm not saying those apps are causing the problem, just that they are the first thing I thought of that shares commonality. Those three folders in question are within the media subfolder of the main share Pool. I have some symbolic links to those folders in another share called media. That was used to control specific user access permissions to the media folder - didn't want the kids having the ability to delete or read access to the whole pool. "Home videos" however does not have a symbolic link in the media share - so we can probably rule out that as a cause. Can someone share the command syntax to tell me "if directories recursively have read only permissions and not show other results"? dir /p /s /a:r is what I'm used to (I grew up on dos).

Please see the attached Diagnostics. Parity check finished with zero errors. cvg02-diagnostics-20210926-1104.zip

I will get back to you on this. I deleted the docker and removed the folder from appdata and reinstalled it and it cleared the error. I got to the webpage ui for the app and I couldn't get the syntax correct to download my channel. I will post the results after I finish dealing with a permission issue.