dalmaar

I finally had a chance to try the procedures and It has worked perfectly, no data loss (other than the file I was originally writing, but I was doing a copy so I still have the file). I think this was all due to a faulty SATA cable, at least so far no errors. Will be keeping a close eye on this drive/ thanks for the help

Update... Thanks for the pointer, I never clicked that manual link before. 🙄 Unfortunately I was called out of town, will give those procedures a try when I get back.

Having an issue with one of my unraid boxes. This unraid box has been running without issue for years, I admit it has been so stable I am rusty on procedures when something does go wrong. I effort to prepare to upgrade, I was cleaning up files getting ready for parity check, etc involved transferring files to/from Disk 6. It started spewing errors. Google and this forum suggested they were are pointing to a possible sata cable issue, clean shutdown, swap the cable. Bring it back up and that disk is in emulation mode (yellow icon), but disk share not showing up, (maybe a disk issue at this point?) I could not get the array up and had to do a SYNC (or something like that, I did NOT format disk). ~16 hrs later it finished and during that time I saw a few notifications pop up the GUI about some smart parameters reset to zero. after it was done without errors the disk is now in green but has status "Unmountable: Wrong or no file system". I can see all the disk shares but not disk6. Jul 29 12:17:58 Tower2 kernel: mdcmd (38): check correct Jul 29 12:17:58 Tower2 kernel: md: recovery thread: recon D6 ... Jul 30 03:40:01 Tower2 crond[1066]: exit status 3 from user root /usr/local/sbin/mover &> /dev/null Jul 30 04:39:07 Tower2 kernel: md: sync done. time=58869sec Jul 30 04:39:07 Tower2 kernel: md: recovery thread: exit status: 0 Included the diagnostics zip file, but saw these in the logfile: Jul 29 11:59:03 Tower2 kernel: XFS (md6): Corruption warning: Metadata has LSN (1:89786) ahead of current LSN (1:89698). Please unmount and run xfs_repair (>= v4.3) to resolve. Jul 29 11:59:03 Tower2 kernel: XFS (md6): log mount/recovery failed: error -22 Jul 29 11:59:03 Tower2 kernel: XFS (md6): log mount failed Jul 29 11:59:03 Tower2 root: mount: /mnt/disk6: wrong fs type, bad option, bad superblock on /dev/md6, missing codepage or helper program, or other error. Jul 29 11:59:03 Tower2 root: dmesg(1) may have more information after failed mount system call. Jul 29 11:59:03 Tower2 emhttpd: shcmd (104): exit status: 32 Jul 29 11:59:03 Tower2 emhttpd: /mnt/disk6 mount error: Wrong or no file system Jul 29 11:59:03 Tower2 emhttpd: shcmd (105): umount /mnt/disk6 Jul 29 11:59:03 Tower2 root: umount: /mnt/disk6: not mounted. At this point I am unclear as what to do next, unfamiliar with the xfs_repair tool, or the process to get it started. I was hoping to get it to emulation mode until replacement drive arrives. At this point I am not doing anything with server, no file transfers or reboot/shutdowns. \ Staying powered up in this state, Any help appreciated. tower2-diagnostics-20230730-0604.zip

All, Follow up post, after upgrading to 4G all is well, clean upgrade. Dalmaar

Appears my very first old dual core raid box is finally showing it's age, It only has 2G memory and is not enough to uncompress the upgrade to 6.7.2, rootfs runs out of space. I think I have 2 2G sticks in a junk box some place, or I can attempt a manual install on the flash drive, probably just put in the memory. I will post results, if anybody runs into similar issue, probably not many folks running an Unraid with 2G. Dalmaar

Having an Issue upgrading from 6.6.1 to 6.71. or 6.7.2. Using the tools>update OS, after selecting upgrade to 6.7.1 I get the following on popup log plugin: updating: unRAIDServer.plg plugin: downloading: https://s3.amazonaws.com/dnld.lime-technology.com/stable/unRAIDServer-6.7.2-x86_64.zip ... done plugin: downloading: https://s3.amazonaws.com/dnld.lime-technology.com/stable/unRAIDServer-6.7.2-x86_64.md5 ... done Archive: /tmp/unRAIDServer.zip creating: /tmp/unRAIDServer/EFI-/ creating: /tmp/unRAIDServer/EFI-/boot/ inflating: /tmp/unRAIDServer/EFI-/boot/bootx64.efi inflating: /tmp/unRAIDServer/EFI-/boot/ldlinux.e64 inflating: /tmp/unRAIDServer/EFI-/boot/libcom32.c32 inflating: /tmp/unRAIDServer/EFI-/boot/libutil.c32 inflating: /tmp/unRAIDServer/EFI-/boot/mboot.c32 inflating: /tmp/unRAIDServer/EFI-/boot/menu.c32 inflating: /tmp/unRAIDServer/EFI-/boot/syslinux.cfg inflating: /tmp/unRAIDServer/bzfirmware inflating: /tmp/unRAIDServer/bzfirmware.sha256 inflating: /tmp/unRAIDServer/bzimage inflating: /tmp/unRAIDServer/bzimage.sha256 inflating: /tmp/unRAIDServer/bzmodules inflating: /tmp/unRAIDServer/bzmodules.sha256 inflating: /tmp/unRAIDServer/bzroot inflating: /tmp/unRAIDServer/bzroot-gui unzip error 0 plugin: run failed: /bin/bash retval: 1 It seems to have an error? and exits without upgrading, tried a clean reboot. Nothing in sys log, via GUI Log (no highlighted text). After reboot all seems ok., I assuming nothing was changed. I must be missing something? Any help appreciated. Dalmaar

Thanks for the feedback. I did see that thread but dismissed it because my other unraid box on the same network is working fine. If I understand it that has to do with the router and both unraid boxes are using the same router.

I just realized the screen shot showing "Use SSH" set to NO is actually set to AUTO, I must have grabbed it to soon. Dalmaar

Hello, I m having an issue with one of my unraid boxes I hope is a simple fix, any help is appreciated. I have 2 unraid boxes on the same network, both running 6.6.1. While preparing to upgrade to the latest version I noticed errors in the log from one of my unraid boxes every 10 -20 mins or so: Nov 25 11:23:39 Tower nginx: 2018/11/25 11:23:39 [error] 3212#3212: OCSP_check_validity() failed (SSL: error:2707307D:OCSP routines:OCSP_check_validity:status expired) while requesting certificate status, responder: ocsp.int-x3.letsencrypt.org,peer: 104.91.166.209:80, certificate: "/etc/ssl/certs/unraid_bundle.pem" Appears to be indicating my certification has expired, and it can not renew, and indeed it did expire on Nov 16. I then clicked the "renew" button and nothing. No log, nothing. I can download plugin upgrades and the other unraid box is fine, as I can see my cert is good for jan 06 2019 and I did nothing to cause that it renewed automatically. After looking at some forum topics I try shutting SSH off. apply, restart, set to auto, with the same results. Tried a different browser, cleared cookies, then I tried these commands: rm /boot/config/ssl/certs/certificate_bundle.pem /etc/rc.d/rc.nginx reload They appear to work, now my renew button has changed to provision (like when I first upgraded to the version that supported certificates). Click provision and again absolutely nothing. This unraid box has been up for years (first running v4) and is a very simple low powered NAS. No docker, no VMs running dual core CPU with 2G memory, and riserfs formatted disks. The often tail the log and it is quiet other that informational messages and these warnings. At this time this machine can not acquire a cert, but everything else appears ok, I am not sure what might help so I included the identification and network setting screen shots. Side question: can I upgrade to 6.6.5 with only 2G? I will not be running any dockers or VMs, the "fix common problems" plugin flags this as a warning.

well, the second parity check finished (without corrections) and went well... Last checked on Mon 12 Dec 2016 08:52:49 PM CST (today), finding 0 errors. Duration: unavailable (no parity-check entries logged) Logfile... Dec 12 05:31:16 Tower2 kernel: mdcmd (482): check NOCORRECT Dec 12 05:31:16 Tower2 kernel: md: recovery thread woken up ... Dec 12 05:31:16 Tower2 kernel: md: recovery thread checking parity... Dec 12 05:31:16 Tower2 kernel: md: using 1536k window, over a total of 7814026532 blocks. Dec 12 20:52:49 Tower2 kernel: md: sync done. time=55293sec Dec 12 20:52:49 Tower2 kernel: md: recovery thread sync completion status: 0 No changes in the smart report, I guess at this point I will just keep an eye on this drive. I already have another drive on order, was going to expand the array.

Thanks for the reply, No, I do not have file checksums in place. Should I now do another parity check without correction? I will definitely watch this drive I always have a tail running on the logfile. Dalmaar

Hello, looking for some advice on how to proceed after parity check. I have never gotten any kind of errors on this unraid box until now. I did a parity check (with write corrections) and while it finished close to previous parity check times, it finished with sync errors. Last checked on Sun 11 Dec 2016 10:10:08 PM CST (today), finding 988 errors. Duration: 15 hours, 31 minutes, 38 seconds. Average speed: 143.1 MB/s after examining the logfile, I can see what might be a more serious issue? After a bunch of "correcting parity" logs entries followed by a read error block (see snippet below), this happened one more time and near at the end of the parity check. ---------------------------------------------------------------------------------- (Begin LOGFILE SNIPPET) . . Dec 11 21:56:05 Tower2 kernel: md: correcting parity, sector=15482671128 Dec 11 21:56:05 Tower2 kernel: md: correcting parity, sector=15482671136 Dec 11 21:56:05 Tower2 kernel: md: correcting parity, sector=15482671144 Dec 11 21:56:05 Tower2 kernel: md: correcting parity, sector=15482671152 Dec 11 21:56:05 Tower2 kernel: md: correcting parity, sector=15482671160 Dec 11 21:56:05 Tower2 kernel: md: correcting parity, sector=15482671168 Dec 11 21:56:05 Tower2 kernel: md: correcting parity, sector=15482671176 Dec 11 21:56:05 Tower2 kernel: md: correcting parity, stopped logging Dec 11 21:56:11 Tower2 kernel: ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Dec 11 21:56:11 Tower2 kernel: ata5.00: irq_stat 0x40000001 Dec 11 21:56:11 Tower2 kernel: ata5.00: failed command: READ DMA EXT Dec 11 21:56:11 Tower2 kernel: ata5.00: cmd 25/00:90:10:b8:dc/00:03:9a:03:00/e0 tag 5 dma 466944 in Dec 11 21:56:11 Tower2 kernel: res 51/40:00:c8:b8:dc/00:00:9a:03:00/00 Emask 0x9 (media error) Dec 11 21:56:11 Tower2 kernel: ata5.00: status: { DRDY ERR } Dec 11 21:56:11 Tower2 kernel: ata5.00: error: { UNC } Dec 11 21:56:11 Tower2 kernel: ata5.00: configured for UDMA/133 Dec 11 21:56:11 Tower2 kernel: sd 5:0:0:0: [sdf] tag#5 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 Dec 11 21:56:11 Tower2 kernel: sd 5:0:0:0: [sdf] tag#5 Sense Key : 0x3 [current] [descriptor] Dec 11 21:56:11 Tower2 kernel: sd 5:0:0:0: [sdf] tag#5 ASC=0x11 ASCQ=0x4 Dec 11 21:56:11 Tower2 kernel: sd 5:0:0:0: [sdf] tag#5 CDB: opcode=0x88 88 00 00 00 00 03 9a dc b8 10 00 00 03 90 00 00 Dec 11 21:56:11 Tower2 kernel: blk_update_request: I/O error, dev sdf, sector 15483058376 Dec 11 21:56:11 Tower2 kernel: ata5: EH complete Dec 11 21:56:11 Tower2 kernel: md: disk4 read error, sector=15483058312 Dec 11 21:56:11 Tower2 kernel: md: disk4 read error, sector=15483058320 Dec 11 21:56:11 Tower2 kernel: md: disk4 read error, sector=15483058328 Dec 11 21:56:11 Tower2 kernel: md: disk4 read error, sector=15483058336 . . Dec 11 21:56:11 Tower2 kernel: md: disk4 read error, sector=15483059032 Dec 11 21:56:14 Tower2 kernel: ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Dec 11 21:56:14 Tower2 kernel: ata5.00: irq_stat 0x40000001 Dec 11 21:56:14 Tower2 kernel: ata5.00: failed command: READ DMA EXT Dec 11 21:56:14 Tower2 kernel: ata5.00: cmd 25/00:40:a0:bb:dc/00:05:9a:03:00/e0 tag 8 dma 688128 in Dec 11 21:56:14 Tower2 kernel: res 51/40:00:a0:bb:dc/00:00:9a:03:00/00 Emask 0x9 (media error) Dec 11 21:56:14 Tower2 kernel: ata5.00: status: { DRDY ERR } Dec 11 21:56:14 Tower2 kernel: ata5.00: error: { UNC } Dec 11 21:56:14 Tower2 kernel: ata5.00: configured for UDMA/133 Dec 11 21:56:14 Tower2 kernel: sd 5:0:0:0: [sdf] tag#8 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 Dec 11 21:56:14 Tower2 kernel: sd 5:0:0:0: [sdf] tag#8 Sense Key : 0x3 [current] [descriptor] Dec 11 21:56:14 Tower2 kernel: sd 5:0:0:0: [sdf] tag#8 ASC=0x11 ASCQ=0x4 Dec 11 21:56:14 Tower2 kernel: sd 5:0:0:0: [sdf] tag#8 CDB: opcode=0x88 88 00 00 00 00 03 9a dc bb a0 00 00 05 40 00 00 Dec 11 21:56:14 Tower2 kernel: blk_update_request: I/O error, dev sdf, sector 15483059104 Dec 11 21:56:14 Tower2 kernel: md: disk4 read error, sector=15483059040 . . Dec 11 22:10:08 Tower2 kernel: md: sync done. time=55898sec Dec 11 22:10:08 Tower2 kernel: md: recovery thread sync completion status: 0 (End LOGFILE SNIPPET) ------------------------------------------------------------------------------------- The SMART report on drive 4 shows 0 reallocated and pending sectors. 5 Reallocated sector count 0x0033 100 100 010 Pre-fail Always Never 0 197 Current pending sector 0x0012 100 100 000 Old age Always Never 0 but one SMART value I have never noticed before, this one marked in yellow as a warning. I have not kept records and not sure if this was there before the parity check. 187 Reported uncorrect 0x0032 098 098 000 Old age Always Never 2 I usually just leave the array alone during the parity check, but accidentally started a copy to this raid box (thought I was writing to my other unraid box), and I aborted the copy after I realized I was on the wrong unraid box. However the copy was going to disk2 (not disk 4 where the errors occurred). My question is how to proceed, I can try another parity check, but if this seems more serious I can start looking into replacement. I have never seen any drive on this array red ball. Or does this appear like some glitch that happened? I have the server behind UPS and did not detect any power issues or anything, did I "cause" this with my copy to the array during parity check? System Specs: unRAID system: unRAID server Pro, version 6.1.9 (not upgraded to current version yet ) Motherboard: Gigabyte Technology Co., Ltd. - F2A88XM-D3H Processor: AMD A10-7850K Radeon R7, 12 Compute Cores 4C+8G @ 3.7 GHz HVM: Enabled IOMMU: Enabled Memory: 16 GB (max. installable capacity 16 GB) Array: 4 data - 8TB Seagate archive (Shingle) drives 1 parity - 8TB Seagate archive (Shingle) drive Not running anything to spectacular, just a basic NAS. Thanks, any help/advice is appreciated Dalmaar

And after you do that, put IP addresses in for DNS servers. If you don't know your ISP DNS servers addresses, 8.8.8.8 and 8.8.4.4 are the addresses for Google's public DNS servers. Thanks a lot!!, it took both suggestions and it is now updating properly Dalmaar

Yes. Thanks johnnie.black I can fall back on that if I need to. Before I do that I would like to investigate why the plugin is not upgrading properly. I can wait if anybody has any ideas, not that important to get to v6.1.9 anytime quickly. I only noticed I was back a few releases when I upgraded my first unRAID v4.7 server (yes. v4.7 ), and realized the latest version was up to v6.1.9. Dalmaar

Hello, When I attempt to update from v6.1.6 via "check for updates" on the plugin page, my version v6.1.6 install always says "up-to-date". I have upgraded via this method from a previous version awhile back (6.0.1 I think), and other plugins have updated fine. I am seeing no obvious errors and just this line on the syslog, which seems normal?? Jul 29 22:12:29 Tower emhttp: cmd: /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin checkall I have tried shutting down and temporarily renaming cfg/plugins directory, restarting and attempted to check to updates with only the 2 default plugins and still it thinks v6.1.6 is the latest No other issues with server, pretty simple setup, I do have 2 VMs not being used at the moment and no dockers installed yet. I can do a manual install if needed but rather use the GUI if possible. Is is just as easy as copying over the bzimage and bzroot from the 6.1.9 zip? Thanks, Dalmaar

Thanks all for the replies... I am thinking it is in the controller inside the enclosures also, or win7 is not operating properly (wow there is some shocking news). Of course to use >2tb I need win7. I have a different USB3 card (for one of my other box) I might try just to satisfy myself that I tried all options. When I put these drives in my Unraid server, I should not expect this problem? I will be able to set the spindown time like I can now with my samsungs and WDs? Thanks

Hello, I got lucky and scored a few Hitachi drives locally last week before the prices spiked to much, these are the first Hitachi drives I have ever owned. I picked up: internal HDS5C3030ALA630 5400rpm green ($109) external USB3 touro pro which has a HDS723030ALA640 7200rpm for $139 (figured I could open the case and take the drive out if I wanted). I was actually not expecting a 7200 rpm, but I can put to good use I am not quite ready to put these into my Unraid server as I am current out of physical space (and ports) and in the middle of upgrading to larger case, etc. So I put the internal in a USB3 case and the external was good to go, and plugged them into my Win7 box. Transfer rates are excellent on both drives, as expected 7200 is faster and hotter. Now the question........finally Both of these drives go to sleep in like 10-15 mins of no activity, and I have not been able to control/adjust this time, it is way to short for everyday use IMHO. I have a few older WD elements (5400 green, probably EADS or something) and they also sleep, but after like 30 mins. I do not remember reading any issues with Hitachi drives sleep issue on these boards in Unraid so I thought it might be a win7 issue. I emailed Hitachi and did get a response. they claim "The drive doesn't have a built in sleep or spin down feature enabled. It is designed to support the Windows settings for power saving". I changed every friggin power setting I could find in win7, even on the USB3 cards and nothing changed. I thought maybe the USB3 card is doing this, so I moved one Hitachi drives off the card and onto a normal USB2 plug. Same thing happens. They have a utility tool that looks like it can control an "idle setting" on the drive but it claims to not with with 3TB drive The last email with Hitachi... "We are still working on updating our tools but the drive shouldn't need to be atlered. It sounds more like there is a a defect in this particular drive and it is going to sleep on its own. Maybe it has some corrupted firmware from the warehouse when it was built. If you just got it, definitely bring it back for a replacement" c'mon, 2 different lines of drive, and both are corrupt? sounds like BS to me....and returning is always a pain. Anybody else have similar experience with these drives in win7? I hope no sleep issues with Unraid. Anybody know how to change this setting, or if such a setting exists. I am looking into a program keep the drive alive by writing some blank file or something but this seems like a total kludge. Thanks for any help.