zerohour

@CHBMB Thank you so much! Updating the docker didn't work so I had to remove and then reboot server. But it finally worked. Very fast support, on a busy weekend. Thanks!

Getting the same problem. If I open the nginx log (/appdata/grocy/log/nginx) I get: 2019/05/11 19:56:40 [error] 299#299: *21 FastCGI sent in stderr: "PHP message: PHP Warning: file_put_contents(/app/grocy/data/viewcache/280834de7e8f30ba6d5b5ffd2e411299adf3057f.php): failed to open stream: No such file or directory in /app/grocy/vendor/illuminate/filesystem/Filesystem.php on line 122 PHP message: PHP Warning: include(/app/grocy/data/viewcache/280834de7e8f30ba6d5b5ffd2e411299adf3057f.php): failed to open stream: No such file or directory in /app/grocy/vendor/illuminate/view/Engines/PhpEngine.php on line 43 PHP message: PHP Warning: include(): Failed opening '/app/grocy/data/viewcache/280834de7e8f30ba6d5b5ffd2e411299adf3057f.php' for inclusion (include_path='.:/usr/share/php7') in /app/grocy/vendor/illuminate/view/Engines/PhpEngine.php on line 43" while reading response header from upstream, client: 192.168.0.191, server: _, request: "GET /login HTTP/1.1", upstream: "fastcgi://127.0.0.1:9000", host: "192.168.0.10:9283" 2019/05/11 19:56:46 [error] 299#299: *17 FastCGI sent in stderr: "PHP message: PHP Warning: file_put_contents(/app/grocy/data/viewcache/280834de7e8f30ba6d5b5ffd2e411299adf3057f.php): failed to open stream: No such file or directory in /app/grocy/vendor/illuminate/filesystem/Filesystem.php on line 122 PHP message: PHP Warning: include(/app/grocy/data/viewcache/280834de7e8f30ba6d5b5ffd2e411299adf3057f.php): failed to open stream: No such file or directory in /app/grocy/vendor/illuminate/view/Engines/PhpEngine.php on line 43 PHP message: PHP Warning: include(): Failed opening '/app/grocy/data/viewcache/280834de7e8f30ba6d5b5ffd2e411299adf3057f.php' for inclusion (include_path='.:/usr/share/php7') in /app/grocy/vendor/illuminate/view/Engines/PhpEngine.php on line 43" while reading response header from upstream, client: 192.168.0.191, server: _, request: "GET /login HTTP/1.1", upstream: "fastcgi://127.0.0.1:9000", host: "192.168.0.10:9283", referrer: "http://192.168.0.10/Docker"

Fixed! I added: avahi:x:61:214:Avahi Daemon User:/dev/null:/bin/false avahi-autoipd:x:62:62:Avahi AutoIP Daemon User:/dev/null:/bin/false to /boot/config/passwd and it fixed the issue immediately. Even fixed my media box problem. Thanks.

I'm having the exact same problem with mine. I also believe this issue causes my media box to freeze whenever I try to stream. Anyone have any info about it? Frank, have you tried 6.3? It might fix the problem, but I always wait for stable releases.

Here's two of the same disks, similar age. Syslog attached. Disk2 = drive which failed to mount. Obviously some failures, looks like they're related to the checksum Disk1 - Same type of disk, everything seems okay with it syslog-2013-05-31.zip

Okay, I checked it (properly) they all seem okay. I added my replacement party disk, started the array and now it looks like disk2 isn't mounting and says it's 'Unformated'. Has a bunch of the errors below: May 30 23:14:40 Tower kernel: ata7.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 (Errors) May 30 23:14:40 Tower kernel: ata7.00: BMDMA stat 0x24 (Drive related) May 30 23:14:40 Tower kernel: ata7.00: failed command: READ DMA (Minor Issues) May 30 23:14:40 Tower kernel: ata7.00: cmd c8/00:08:d7:00:01/00:00:00:00:00/e0 tag 0 dma 4096 in (Drive related) May 30 23:14:40 Tower kernel: res 51/40:00:d8:00:01/40:00:00:00:00/00 Emask 0x9 (media error) (Errors) May 30 23:14:40 Tower kernel: ata7.00: status: { DRDY ERR } (Drive related) May 30 23:14:40 Tower kernel: ata7.00: error: { UNC } (Errors) May 30 23:14:40 Tower kernel: ata7.00: configured for UDMA/33 (Drive related) May 30 23:14:40 Tower kernel: ata7: EH complete (Drive related) Is this disk toast?

Thanks for the speedy reply. You're right! D'oh, new it had to be something since they all were like that.

Hi, I've been having off and on drive issues for the last 6 months! About a month ago one of my drives failed and it ended up that the drive wasn't on my parity, or my parity was completely invalid. After replacing the drive, and replacing the lost data (help from a friend) I rebuilt my parity disk. It built fine. Then I ran a parity check because I wasn't confident in my parity at all. It came through with 0. So I ran it again! (Yes, I'm a little paranoid at this point) and everything came back clean once again. A few weeks later, after using a possibly bad power supply for a few days (in the RMA process) my parity disk was disabled. I've RMA'd that disk since and I'm preclearing. While I was preclearing, I got a LOT of errors in my syslog. See attached. Basically a whole lot of: May 30 05:51:53 Tower kernel: md: diskX read error (Errors) May 30 05:51:53 Tower kernel: handle_stripe read error: 2434475536/2, count: 1 (Errors) X = disk2/9 I also noticed that the disks where that occurring was in the "not protected" part of the unmenu Main screen, and it looked like it spun down. I then stopped the array. With my array off, I ran reiserfsck --check and It said there was no superblock. After checking a few other drives using reiserfsck it's a bigger problem that I thought (Out of 12 disks) 11 disks: superblock cannot be found 1 disk: Bad root block 0. (which is not disk2 or 9 in the above syslog) It recommends I run --rebuild-sb, which is fine, but I think it's VERY weird that ALL my disks have a superblock issue. What's going on? My disk is nearly finished preclearing and I'd rather not do a parity check if all my other data disks are bad. Using unraid 5.0-rc11. Any help would be appreciated, thanks! syslog-2013-05-30.zip

Hey all, I'm looking for the best solution.. I've been fighting a LOT of dead drives with my server. I've since bought a new PSU but I'm still recovering. Basically, I had two simultaneous drive failures at the same time, a 2TB and 500GB. I manged to save the data by reading it through linux so that's good. The data is stored on another disk but I'm waiting to get my array up 100% before I get the data back on it. The 2TB drive failed first so I had that replaced and while that was going in the 500GB died. I put in another 500GB but it had failed as well so my backup-backup plan was my 750GB. I precleared the drive and the new 2TB and they all passed. I than put them in my array, added the devices and went to format them as they showed up unformated. This also failed; getting the bread: Cannot read the block (0): (Input/output error). on BOTH disks. Attached is the syslog. The first time I pre-cleared the drive was on my old PSU. Pre-clear didn't seem to pick up the block (0) issue, I guess it just looks at the before/after conditions and if nothing has changed it believes it's okay. Is this how it works? So, my array is running right now pretty much 'unprotected' since I can't do a rebuild if another disk fails so what's the best way out of this? I'm going to RMA the disks as quickly as possible, and hopefully that fixes it but is there any other ideas? Can I just delete the two disks (using initconfig), rebuild the parity based on the current drive and prey nothing dies on the rebuild and add them both later? There is no data to be rebuilt on the two disks, I'd rather just add them in. Thanks syslog-2011-12-20.zip

This was right after the rebuild so 15 drives making heat... It's at 29 C right now.

Thanks Joe, I checked the rest of the drives and none of the other drives are above 0 for the two attributes you posted, whew. I suspected it was my parity drive but I wasn't sure what the deal was with the controller resetting.

I'm trying to fix my HPA drives and while rebuilding the drive I've started getting a lot of these messages. The error would happen only a few times when I do a full parity check, but right now every time I do a rebuild/parity check my syslog looks like someone got murdered. The result of the rebuild: Parity updated 2196 times to address sync errors. My syslog: Apr 20 21:10:04 Tower kernel: ata1.00: failed command: READ DMA EXT (Minor Issues) Apr 20 21:10:04 Tower kernel: ata1.00: cmd 25/00:00:7f:63:00/00:04:3a:00:00/e0 tag 0 dma 524288 in (Drive related) Apr 20 21:10:04 Tower kernel: res 51/40:cf:9f:65:00/40:01:3a:00:00/e0 Emask 0x9 (media error) (Errors) Apr 20 21:10:04 Tower kernel: ata1.00: status: { DRDY ERR } (Drive related) Apr 20 21:10:04 Tower kernel: ata1.00: error: { UNC } (Errors) Apr 20 21:10:04 Tower kernel: ata1.00: configured for UDMA/133 (Drive related) Apr 20 21:10:04 Tower kernel: ata1: EH complete (Drive related) Apr 20 21:10:06 Tower kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 (Errors) Apr 20 21:10:06 Tower kernel: ata1.00: BMDMA stat 0x25 (Drive related) Apr 20 21:10:06 Tower kernel: ata1.00: failed command: READ DMA EXT (Minor Issues) Apr 20 21:10:06 Tower kernel: ata1.00: cmd 25/00:00:7f:63:00/00:04:3a:00:00/e0 tag 0 dma 524288 in (Drive related) Apr 20 21:10:06 Tower kernel: res 51/40:cf:9f:65:00/40:01:3a:00:00/e0 Emask 0x9 (media error) (Errors) Apr 20 21:10:06 Tower kernel: ata1.00: status: { DRDY ERR } (Drive related) Apr 20 21:10:06 Tower kernel: ata1.00: error: { UNC } (Errors) Apr 20 21:10:06 Tower kernel: ata1.00: configured for UDMA/133 (Drive related) Apr 20 21:10:06 Tower kernel: sd 1:0:0:0: [sda] Unhandled sense code (Drive related) Apr 20 21:10:06 Tower kernel: sd 1:0:0:0: [sda] Result: hostbyte=0x00 driverbyte=0x08 (System) Apr 20 21:10:06 Tower kernel: sd 1:0:0:0: [sda] Sense Key : 0x3 [current] [descriptor] (Drive related) Apr 20 21:10:06 Tower kernel: Descriptor sense data with sense descriptors (in hex): Apr 20 21:10:06 Tower kernel: 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00 Apr 20 21:10:06 Tower kernel: 3a 00 65 9f Apr 20 21:10:06 Tower kernel: sd 1:0:0:0: [sda] ASC=0x11 ASCQ=0x4 (Drive related) Apr 20 21:10:06 Tower kernel: sd 1:0:0:0: [sda] CDB: cdb[0]=0x28: 28 00 3a 00 63 7f 00 04 00 00 (Drive related) Apr 20 21:10:06 Tower kernel: end_request: I/O error, dev sda, sector 973104543 (Errors) Apr 20 21:10:06 Tower kernel: ata1: EH complete (Drive related) Apr 20 21:10:06 Tower kernel: md: disk0 read error (Errors) Apr 20 21:10:06 Tower kernel: handle_stripe read error: 973104480/0, count: 1 (Errors) Apr 20 21:10:06 Tower kernel: md: disk0 read error (Errors) Apr 20 21:10:06 Tower kernel: handle_stripe read error: 973104488/0, count: 1 (Errors) Apr 20 21:10:06 Tower kernel: md: disk0 read error (Errors) Apr 20 21:10:06 Tower kernel: handle_stripe read error: 973104496/0, count: 1 (Errors) The handle_stripe read error goes on for hundreds of lines and the first bunch of errors repeat several times. I'm not sure if this is my drive or the controller itself causing the issue. Does ata1 refer to the drive on the controller or my motherboard? sda is my parity drive and it doesn't show any errors in SMARTtest Here's the attributes result for the drive SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 35747 3 Spin_Up_Time 0x0027 040 040 021 Pre-fail Always - 15000 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 551 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 9 Power_On_Hours 0x0032 089 089 000 Old_age Always - 8191 10 Spin_Retry_Count 0x0032 100 100 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 35 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 25 193 Load_Cycle_Count 0x0032 190 190 000 Old_age Always - 32762 194 Temperature_Celsius 0x0022 099 081 000 Old_age Always - 53 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 196 196 000 Old_age Always - 1425 198 Offline_Uncorrectable 0x0030 197 194 000 Old_age Offline - 1111 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 165 001 000 Old_age Offline - 7022 Any help would be appreciated.