ldasilva

is that a norco 4020/rpc-4020 did it come with those trays? or did you do some after market stuff to it? i ask cuz my backplanes have died not sure what to do with it

yeah the backup share was it the cache drive just has 2 vms on it which im not using/dont care i just wanted to make sure the main array was backup i got a little worried i new the cache drive didnt have any mirroring was ok with that thanks itimpi and MAM59

tower-diagnostics-20221213-1928.ziphow do i go about fixing some or all files unprotected share error i cant seem to figure out what the error is thanks

Brand: Western Digital Caviar Green Model: WDC WD20EADS-00R6B0 Approximate age at failure: 2y, 5m, 23d, 0h Drive in warranty: No 1 Raw read error rate 0x002f 200 200 051 Pre-fail Always Never 0 3 Spin up time 0x0027 150 146 021 Pre-fail Always Never 9491 4 Start stop count 0x0032 096 096 000 Old age Always Never 4964 5 Reallocated sector count 0x0033 168 168 140 Pre-fail Always Never 251 7 Seek error rate 0x002e 200 200 000 Old age Always Never 0 9 Power on hours 0x0032 071 071 000 Old age Always Never 21769 (2y, 5m, 23d, 1h) 10 Spin retry count 0x0032 100 100 000 Old age Always Never 0 11 Calibration retry count 0x0032 100 253 000 Old age Always Never 0 12 Power cycle count 0x0032 100 100 000 Old age Always Never 66 192 Power-off retract count 0x0032 200 200 000 Old age Always Never 47 193 Load cycle count 0x0032 162 162 000 Old age Always Never 116914 194 Temperature celsius 0x0022 122 089 000 Old age Always Never 30 196 Reallocated event count 0x0032 001 001 000 Old age Always Never 208 197 Current pending sector 0x0032 200 199 000 Old age Always Never 6 198 Offline uncorrectable 0x0030 200 199 000 Old age Offline Never 0 199 UDMA CRC error count 0x0032 200 200 000 Old age Always Never 1 200 Multi zone error rate 0x0008 200 167 000 Old age Offline Never 0 Brand: Seagate Model: ST2000DL003-9VT166 Approximate age at failure: 4y, 2m, 7d, 3h Drive in warranty: No 1 Raw read error rate 0x000f 117 099 006 Pre-fail Always Never 147668272 3 Spin up time 0x0003 090 076 000 Pre-fail Always Never 0 4 Start stop count 0x0032 093 093 020 Old age Always Never 7611 5 Reallocated sector count 0x0033 100 100 036 Pre-fail Always Never 0 7 Seek error rate 0x000f 084 065 030 Pre-fail Always Never 284656557 9 Power on hours 0x0032 059 058 000 Old age Always Never 36723 (4y, 2m, 7d, 3h) 10 Spin retry count 0x0013 100 100 097 Pre-fail Always Never 0 12 Power cycle count 0x0032 100 100 020 Old age Always Never 65 183 Runtime bad block 0x0032 100 100 000 Old age Always Never 0 184 End-to-end error 0x0032 100 100 099 Old age Always Never 0 187 Reported uncorrect 0x0032 089 089 000 Old age Always Never 11 188 Command timeout 0x0032 100 100 000 Old age Always Never 0 189 High fly writes 0x003a 100 100 000 Old age Always Never 0 190 Airflow temperature cel 0x0022 074 059 045 Old age Always Never 26 (min/max 21/27) 191 G-sense error rate 0x0032 100 100 000 Old age Always Never 0 192 Power-off retract count 0x0032 100 100 000 Old age Always Never 56 193 Load cycle count 0x0032 097 097 000 Old age Always Never 7945 194 Temperature celsius 0x0022 026 041 000 Old age Always Never 26 (0 21 0 0 0) 195 Hardware ECC recovered 0x001a 030 015 000 Old age Always Never 147668272 197 Current pending sector 0x0012 100 100 000 Old age Always Never 0 198 Offline uncorrectable 0x0010 100 100 000 Old age Offline Never 0 199 UDMA CRC error count 0x003e 200 200 000 Old age Always Never 0 240 Head flying hours 0x0000 100 253 000 Old age Offline Never 281294588092845 241 Total lbas written 0x0000 100 253 000 Old age Offline Never 2329080217 242 Total lbas read 0x0000 100 253 000 Old age Offline Never 879719883

thanks RobJ i attached it so which ones should i look out for? ST2000DL003-9VT166_5YD4H4Z-20160607-1910.txt

there doesnt seem much info about this i just got hit with this a few weeks ago any input on this? looks like blackbaze says if they see anything besides 0 they replace it i have a drive pre-clearing now so i will most likely replace it . . 1 Raw read error rate 0x000f 111 099 006 Pre-fail Always Never 33453960 3 Spin up time 0x0003 093 076 000 Pre-fail Always Never 0 4 Start stop count 0x0032 093 093 020 Old age Always Never 7418 5 Reallocated sector count 0x0033 100 100 036 Pre-fail Always Never 0 7 Seek error rate 0x000f 084 065 030 Pre-fail Always Never 282676411 9 Power on hours 0x0032 060 060 000 Old age Always Never 35225 (4y, 6d, 17h) 10 Spin retry count 0x0013 100 100 097 Pre-fail Always Never 0 12 Power cycle count 0x0032 100 100 020 Old age Always Never 61 183 Runtime bad block 0x0032 100 100 000 Old age Always Never 0 184 End-to-end error 0x0032 100 100 099 Old age Always Never 0 187 Reported uncorrect 0x0032 089 089 000 Old age Always Never 11 188 Command timeout 0x0032 100 100 000 Old age Always Never 0 189 High fly writes 0x003a 100 100 000 Old age Always Never 0 190 Airflow temperature cel 0x0022 070 059 045 Old age Always Never 30 (min/max 26/33) 191 G-sense error rate 0x0032 100 100 000 Old age Always Never 0 192 Power-off retract count 0x0032 100 100 000 Old age Always Never 53 193 Load cycle count 0x0032 097 097 000 Old age Always Never 7752 194 Temperature celsius 0x0022 030 041 000 Old age Always Never 30 (0 21 0 0 0) 195 Hardware ECC recovered 0x001a 015 015 000 Old age Always Never 33453960 197 Current pending sector 0x0012 100 100 000 Old age Always Never 0 198 Offline uncorrectable 0x0010 100 100 000 Old age Offline Never 0 199 UDMA CRC error count 0x003e 200 200 000 Old age Always Never 0 240 Head flying hours 0x0000 100 253 000 Old age Offline Never 265059611713651 241 Total lbas written 0x0000 100 253 000 Old age Offline Never 1777833167 242 Total lbas read 0x0000 100 253 000 Old age Offline Never 1581356104

just a update looks like its done doing its thing and stable once again i didnt see any files in lost and found so i either lost a few or it was able to fix everything and i didnt lose anything thank you Robj and trurl Squid

thanks

thanks

yeah looks like i goofed later after trying to research when searching i wasn't on the main page im doing the check disk filesystems like robj said i did so far reiserfsck --check /dev/md2 and the output told me to run reiserfsck --rebuild-tree /dev/md2 as of right now i am just waiting for it to complete before it started it said there would be a lost+and+found folder where is that located after this is done? big thank you to Robj and trurl

so i upgraded to v6.1.9 from v5 disk2 has REISERFS error (device md2): vs-7000 i was searching the forum but didnt see that error thanks lee May 29 14:03:54 Tower rpc.mountd[3138]: Version 1.2.8 starting May 29 14:03:54 Tower emhttp: Starting Docker... May 29 14:03:54 Tower logger: /usr/bin/docker not enabled May 29 14:03:55 Tower avahi-daemon[2106]: Service "Tower" (/services/smb.service) successfully established. May 29 14:04:34 Tower shfs/user: shfs_readdir: fstatat: jcg-other-stuff (13) Permission denied May 29 14:04:34 Tower shfs/user: shfs_readdir: readdir_r: /mnt/disk2/backup/old-vhs-movies-tapes/hi8-tapes (13) Permission denied May 29 14:04:34 Tower shfs/user: shfs_readdir: fstatat: jcg-other-stuff (13) Permission denied May 29 14:04:34 Tower shfs/user: shfs_readdir: readdir_r: /mnt/disk2/backup/old-vhs-movies-tapes/hi8-tapes (13) Permission denied May 29 14:06:00 Tower emhttp: cmd: /usr/local/emhttp/plugins/dynamix/scripts/newperms /mnt/disk2 May 29 14:06:14 Tower kernel: REISERFS warning (device md2): vs-13075 reiserfs_read_locked_inode: dead inode read from disk [118103 118104 0x0 SD]. This is likely to be race with knfsd. Ignore May 29 14:06:14 Tower kernel: REISERFS warning (device md2): vs-13075 reiserfs_read_locked_inode: dead inode read from disk [118103 118109 0x0 SD]. This is likely to be race with knfsd. Ignore May 29 14:06:14 Tower kernel: REISERFS warning (device md2): vs-13075 reiserfs_read_locked_inode: dead inode read from disk [118103 118110 0x0 SD]. This is likely to be race with knfsd. Ignore May 29 14:06:14 Tower kernel: REISERFS warning (device md2): vs-13075 reiserfs_read_locked_inode: dead inode read from disk [118103 118108 0x0 SD]. This is likely to be race with knfsd. Ignore May 29 14:06:14 Tower kernel: REISERFS warning (device md2): vs-13075 reiserfs_read_locked_inode: dead inode read from disk [118103 118105 0x0 SD]. This is likely to be race with knfsd. Ignore May 29 14:06:37 Tower kernel: REISERFS error (device md2): vs-7000 search_by_entry_key: search_by_key returned item position == 0 May 29 14:06:37 Tower kernel: REISERFS (device md2): Remounting filesystem read-only May 29 14:06:37 Tower kernel: REISERFS error (device md2): vs-7000 search_by_entry_key: search_by_key returned item position == 0 May 29 14:06:37 Tower kernel: REISERFS error (device md2): vs-7000 search_by_entry_key: search_by_key returned item position == 0 May 29 14:06:37 Tower kernel: REISERFS error (device md2): vs-7000 search_by_entry_key: search_by_key returned item position == 0 May 29 14:06:37 Tower kernel: REISERFS error (device md2): vs-7000 search_by_entry_key: search_by_key returned item position == 0

thanks rob i think my problem was the excludes i added that after i ran out of space thinking it wouldnt use that drive any more for new files more files showed up but now i have a new problem i upgraded to v6 ill post in v6 thread but problem is below . . . . May 29 14:03:54 Tower logger: /usr/sbin/rpc.mountd May 29 14:03:54 Tower emhttp: shcmd (74): /etc/rc.d/rc.atalk status May 29 14:03:54 Tower rpc.mountd[3138]: Version 1.2.8 starting May 29 14:03:54 Tower emhttp: Starting Docker... May 29 14:03:54 Tower logger: /usr/bin/docker not enabled May 29 14:03:55 Tower avahi-daemon[2106]: Service "Tower" (/services/smb.service) successfully established. May 29 14:04:34 Tower shfs/user: shfs_readdir: fstatat: jcg-other-stuff (13) Permission denied May 29 14:04:34 Tower shfs/user: shfs_readdir: readdir_r: /mnt/disk2/backup/old-vhs-movies-tapes/hi8-tapes (13) Permission denied May 29 14:04:34 Tower shfs/user: shfs_readdir: fstatat: jcg-other-stuff (13) Permission denied May 29 14:04:34 Tower shfs/user: shfs_readdir: readdir_r: /mnt/disk2/backup/old-vhs-movies-tapes/hi8-tapes (13) Permission denied May 29 14:06:00 Tower emhttp: cmd: /usr/local/emhttp/plugins/dynamix/scripts/newperms /mnt/disk2 May 29 14:06:14 Tower kernel: REISERFS warning (device md2): vs-13075 reiserfs_read_locked_inode: dead inode read from disk [118103 118104 0x0 SD]. This is likely to be race with knfsd. Ignore May 29 14:06:14 Tower kernel: REISERFS warning (device md2): vs-13075 reiserfs_read_locked_inode: dead inode read from disk [118103 118109 0x0 SD]. This is likely to be race with knfsd. Ignore May 29 14:06:14 Tower kernel: REISERFS warning (device md2): vs-13075 reiserfs_read_locked_inode: dead inode read from disk [118103 118110 0x0 SD]. This is likely to be race with knfsd. Ignore May 29 14:06:14 Tower kernel: REISERFS warning (device md2): vs-13075 reiserfs_read_locked_inode: dead inode read from disk [118103 118108 0x0 SD]. This is likely to be race with knfsd. Ignore May 29 14:06:14 Tower kernel: REISERFS warning (device md2): vs-13075 reiserfs_read_locked_inode: dead inode read from disk [118103 118105 0x0 SD]. This is likely to be race with knfsd. Ignore May 29 14:06:37 Tower kernel: REISERFS error (device md2): vs-7000 search_by_entry_key: search_by_key returned item position == 0 May 29 14:06:37 Tower kernel: REISERFS (device md2): Remounting filesystem read-only May 29 14:06:37 Tower kernel: REISERFS error (device md2): vs-7000 search_by_entry_key: search_by_key returned item position == 0 May 29 14:06:37 Tower kernel: REISERFS error (device md2): vs-7000 search_by_entry_key: search_by_key returned item position == 0

hi guys im a bit lost on what to do i been searching the forum and seen a few people with the same problem but the fixs they did doesnt seem to work i am missing files under user share but browsing to disk(x) shows files it all started when the drive got maxed out so i moved a few gbs off it to another drive for some free space i then added another 2tb drive into the mix i checked the log file i didnt see any errors i am using version 5.0 anyone point me to the right spot to fix this i was checking the wiki Thanks unraid-log-file-5-28-16.txt

right now i have it backing up to crash-plan which is my offsite and have a extra drive outside of the unraid for the important data copyed which is 2 copys i was looking for a 3rd which be right on unraid on its own disk

i was thinking of extra extra redundancy i already have crashplan installed.... i was also thinking of only backing up data that i didnt want to lose i guess it would be a half ass raid 6 in case something went wrong with the other drives i might have 50tbs of data but only want to backup 1-2tbs to the excluded disk