richardb

Okay, did more digging. There is (or was ) a disk 12 that had failed completely: wasn't even powering up. I have replaced it, but when I now try and rebuild, it gets about 10% of the way through, then disk 3 starts giving errors all of the time, and it doesn't seem to respond. So I can't rebuild the array as is, and I seem to have one disk that has an intermittent failure when I try. Is there any hope here, or is it time to nuke the whole thing and start again?

Okay, this is the thing that is frustrating me. I just rebooted the system, and disk 3 is fine. No errors, reading okay. I ran a SMART short self-test, and it reports no errors: "SMART overall-health self-assessment test result: PASSED". It does report that the drive is pre-fail on read error rates and is "old age" on others, but there is certainly no indication that it is failing completely as the log files suggest. Is it about ready to be swapped out? Perhaps, but it ain't dead yet. This is after a reboot and no changes in cable, etc. On disk 12: I have no idea on that. There are no other disks on the system except for a 1TB drive that is passed directly to a media center VM to write captured media files to. I haven't taken any disks out recently. It's a phantom. I guess I can try putting in another drive and rebuilding with that, but this is exactly the kind of stuff that is making me very nervous about this. I mean, disks failing I can understand. Disks failing, then seeming to be fine after a reboot, but another disk appearing? That scares me. Fortunately, everything is backed up in the cloud, and I am in the middle of replacing this system with a simpler one with fewer (bigger) drives running something other than UnRaid.

No response on this? Pity, as I have just realized that this problem has caused corruption and data loss. I guess I'll be dumping UnRaid and moving to something that doesn't have strange bugs that randomly dump a chunk of my data.

Okay, so here is the diagnostic log. This time the system stayed up, but the log file is showing 100%, and I suspect it will dump the shares shortly. Last mesg in the syslog was the same: "Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 131883040 bytes) in /usr/local/emhttp/plugins/dynamix/include/DefaultPageLayout.php(383) : eval()'d code on line 73" I think it is something to do with a parity check. The system was running one because it completely rebooted overnight for some reason. bernard-diagnostics-20170705-1406.zip

Okay, I will keep an eye out for it and do that when it happens again.

Hmm, so this just happened again. This time I wasn't doing anythng: the system was just running normally, then the shares vanished. The system kept running, but there were no shares available or listed on the shares interface page. The last error in the syslog was Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 131874848 bytes) in /usr/local/emhttp/plugins/dynamix/include/DefaultPageLayout.php(383) : eval()'d code on line 73 Any ideas?

Okay, figured this out. One of my drives had a loose power cable, which was causing intermittent write failures. This then filled the log file with warnings, and the log partition was full. Rather disappointing that something as simple as that could bring the whole system down, though: that seems like something that should be caught and dealt with without this kind of consequences.

Hey all, having a problem with my Unraid system: my shares keep vanishing. I am running 6.3.5 on a system with 2X Xeon CPUs and 32GB of RAM. Recently, I have noticed a problem where my file shares vanish. They just no longer show up on the network, and are no longer listed on the shares page. If I go into the command line and navigate to /mnt/user, I get the following error: /bin/ls: reading directory '.': Input/output error A reboot usually seems to deal with this problem, but it is happening more frequently. It has happened twice today, and is proving to be a significant problem for this system. I see this in the system log: Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 131768352 bytes) in /usr/local/emhttp/plugins/dynamix/include/DefaultPageLayout.php(383) : eval()'d code on line 73 Any ideas?

NO !! This is what can cause the "user share copy bug" and result in lost data. Disk share to disk share is fine; or a user share to ANOTHER user share is okay. Ah, this makes sense. This is probably the easiest approach, as copying 8TB to another system is going to take a long time. I'll create another share (which excludes the drives I want to remove), copy it there, then move it back to the original. With verification, of course :-).

Excellent, thanks. I will give that a go. I also realized that I can change the disk settings for user shares after they are created to exclude drives. However, that doesn't seem to move the data off the drive. I guess that only covers new data?

Can you give me some pointers on this? I haven't assigned shares to specific disks, and I don't see an option to change where the data is placed after the share is created. How would I move the data onto another disk?

That's what I thought, but I was hoping for a more, erm, elegant solution. Rest assured I won't be rushing into anything.

It's mainly about using them elsewhere. I already have them set to a fairly aggressive power-down, so the system runs at fairly low power when it isn't crunching. But I appreciate the thought ;-)

Hey all, I have a slightly unusual question: I want to remove several disks from my array. I have been doing some rationalization on my system, and I realized that I have more space than I need: I have 32TB, but am only using about 8TB most of the time. So, I'd like to remove some of the drives to save power, simplify the system and use them elsewhere or keep them as cold spares. However, I can't find any specific instructions on this. My initial thought is that it is probably a process of remove drive, rebuild array, rinse and repeat. Is that the case, or is there a less aggressive way to mark a drive for removal and shift the data off?

Afraid I got rather frustrated and did a hard reboot (AKA pull the plug)m especially as this is the second time in a week the system has had a non-responsive lock up like this that required serious surgery to repair. I did have to rebuild the array afterwards, but no data lost. New shutdown commands noted for future reference, though.