fiore00713

Not sure if I should be revitalizing this thread or starting a new one. I'm still having intermittent issues with this even after completing a rebuild of the system. I DID manage to catch an error in the log window coinciding with a lockup this morning. It would appear that it may be a configuration issue, but I'm not 100% sure how to interpret this. If anyone can make heads or tails of this and at least get me down the right path As an aside, I have VMs currently disabled (disk failure, waiting on RMA) I also have a replacement 10g NIC I was going to work on replacing when I had the chance, should it be a hardware issue on the NIC (one of the only things I haven't yet replaced) Excerpt from the log window attached unraid_error_capture.txt

I ran for 19 days before experiencing the issue again. I thought for a moment that it may have been oddly related to a Win11 VM I had but the lockup proved that wrong. In reviewing the syslog it appears that there may be some info captures but I'm not entirely certain how to interpret it if anyone is able to assist in my efforts unraid-diagnostics-20221207-1743.zip

Nothing there from the time when the system would have encountered an issue. I was first tipped off by a ping monitor on my NGINX and there was no corresponding logs that were mirrored to the flash drive from that time. I had logs from overnight when backups and docker updates ran, and then subsequently after I had to hard-reset the system but nothing in-between to help me track down anything.

Hey All, I've been trying to track down an issue that's plagued me since updating my system to 6.11 I'm running into instances where my serer is becoming completely locked up and unresponsive Dockers appear to crash as my NGINX ping test is the first to report a problem if I'm not around Web interface, SSH, IPMI console and local console are all a no go. The only way that I've found to recover is by a hard reset. I've turned on syslog mirroring to the flash drive but this appears to be happening in such a way that that's not even writing I've got a few dockers that are running with a eth0 interface and I had previously disabled all but my PiHole instance, following this most recent occurrence I've disabled that one for good measure too Looking to see where I may have something jacked up at. One addition oddity is that I've got some old network interfaces that get listed as "do not exist" during boot I had looked at the network config file but did not find the references there, if that may be causing an issue somewhere? unraid-diagnostics-20221104-1611.zip

I'm seeing a very similar set of issues as @jafi and @capt.shitface when trying to update from 21.0.5 to 21.0.7 (at this time) and something caught my eye... I'm curious if you're seeing the same thing, if it matters or if I'm going down the wrong path I've noticed that my /data path permissions are not set for 'abc' 'abc' but rather 'nobody' 'users' I was trying to compare with a friend of mine but we're a bit at a loss. I'm not sure if the permissions are screwing me up or if it's just something else I'm not catching For reference; I first tried running the update via the gui but it failed for... honestly I cannot remember but it was on the step for "Move new files in place" I've tried subsequently to run updater.phar and am running into similar difficulties Part of me is curious if it's permissions based but I'm not certain If anyone can assist or point me in a different direction it'd be appreciated

@ich777 thanks for the response I am currently running in Legacy mode, not UEFI I checked the BIOS but (unless I'm seriously not digging hard enough) couldn't find anything related to BAR support

Trying to sort out getting my P2000 to fire up with the latest update. Trying to determine if it's some setting in unRAID I've managed to get bunked up, BIOS or something else? Running on an ASRockRack X470D4U, I just updated to the latest BIOS and IPMI firmware Updated to 6.9.0 and installed the NVIDIA Driver plugin Seeing the "NVIDIA-SMI" failed message below; I confirmed the card works by hooking up a monitor to the system and was receiving output. I'm seeing the device recognized within System Devices and it's not assigned currently I'm ultimately looking to assign this to my Plex container as I had before upgrading my hardware (I've got it so I'd like to utilize it) Any assistance appreciated unraid-diagnostics-20210302-2253.zip

Reboot worked, booted into safe mode and everything started up okay Rebooted into normal and array started up as normal, shares are there, things seem happy so far Sorry for the panic-post but I appreciate your quick assistance

Is there a 'safe' method for making the array stop? It's still sitting at starting with no updates in the log and the normal stop button is greyed out

Morning all, I'm having a rough start to this week and things this morning are just compounding it I woke up this morning to my unRAID being very grumpy. VMs had crashed, dockers stopped, and as I'm looking through things I found that my system listed no shares, uh-oh, but it still showed the data in use on the array. Immediate fears alleviated some. Checking the system log I saw some 'out of memory' errors and I fear I threw too much of a queue at my YouTube-DL container and it's caused a slew of issues. I stopped whatever dockers thought they were running from the webUI, stopped and restarted the array but the shares still showed as missing. So I tried a reboot. Everything went through the startup without issue, until I went to start my array. It's been sitting at 'starting array' for about 15 minutes now and I'm starting to grow weary. I'm attaching two diagnostics. One from before the reboot and another from after. I'm leaving things sit for now as I don't want to poke at it too much more than I already have. Any input appreciated. unraid-diagnostics-20200519-0906.zip unraid-diagnostics-20200519-0840.zip

Hey All, Trying to sort out an issue I'm experiencing after moving to some new hardware. I've got a P2000 I had been utilizing in my old system. I just recently upgraded the board/cpu/memory and am re-using some of the PCIe cards in the new configuration, one of which is the P2000. The new build is a 3950X in a ASRock Rack X470D4U Everything appears to be working correctly as far as the PCIe cards go, however I can't seem to get the P2000 to pull back in like it had been previously. Prior to swapping everything out I rolled back to 6.8.2 stock, and removed the additional configurations in the docker container that were pointing to the NVIDIA device. My system boots, and I can see the P2000 under Tools > System Devices I have tried reinstalling both 6.8.2 as well as 6.8.3 with the NVIDIA drivers and I see the same error for both: Running 'nvidia-smi' I see the same error in the console and the below error in the system log: The one thing I haven't tried is passing it to a VM yet, though I know this bypasses the need for the NVIDIA driver as it relates to the docker container so it may be a moot point to test. Reading back a bit it seems a few people have had similar issues but either haven't resolved it or I'm missing their fix. Anyone able to provide a little further insight into this I'd appreciate it Also attaching a diagnostic unraid-diagnostics-20200428-1346.zip

A huge THANK YOU to @Squid and @johnnie.black for your assistance with my issue. The clear process finally completed and I was able to reboot, format and get the array back online and the shares to show up. That being said, once I made sure everything appeared to be in working order I rolled back to 6.7.2 (after taking backups) and will run at that for the time being. I look forward to 6.8 stable as it seemed to have some great new stuff! Thanks again

Sorry, my thought process when I said normal should have been really phrased as a 'known issue' and that it should resolve itself once the clear is completed. I am thinking correctly in regards to, once the clear finishes, everything should go back to normal?

So this is "normal" until the disk is finished clearing? I've been breezing through my backup config and looking at what's living on the flash drive now and was ripping my hair out because everything looks visually the same. That being said, I have two disks being added to the array currently; 23 and 24, ideally these are going at the same rate? So when the clear process is done in about 11-12hrs I should be golden (maybe after a reboot?) I think I'll have some lingering issues with paths for my docker.img and libvirt.img as they're complaining about paths but dockers I can nuke and correct and libvirt I can pull form a good backup I just... Thought everything was going well after I fixed my Cache issue, and then my night went to shit XD As always I appreciate your feedback @Squid - I'm not as well versed in Linux as I probably should be but I try <,<'

Something I just realized in trying to research in hopes of finding an answer; I took a flash backup earlier in the day before I screwed with anything. Would it be advantageous to try and write a new flash drive using this backup? Would there be any possible ill-effects of this?

I went through the process of reformatting my Cache drive following a weird issue I encountered After I got that fixed and was working to get things set back up, everything seemed okay. I added two additional drives to my array and now I'm having some major issues. My Shares are showing "There are no exportable user shares". Data usage is showing okay so I know it's still there but somehow something's gone poof and I'm trying to not freak out XD Diags attached Please help unraid-diagnostics-20191031-2352.zip

So for what it's worth I rebooted and now one of them says they're missing >_>

Is there a 'best practice' way you'd recommend to do this?

Long story short some sort of oops happened last night and one of my drives was removed from the Cache pool. Figured no big deal, re-add the second drive, start the array and it would go to work. It appears to have done so, but I'm also suspecting something might be going on that's not so right. My log is flooded with: Oct 29 15:47:39 unRAID kernel: BTRFS info (device sdad1): found 1 extents The size of the cache pool is reporting incorrectly as 1.5tb (this has been changing since last night) and running btrfs fi usage -T /mnt/cache looks a little odd to me but I'm not versed enough to know what exactly might be up I feel like I may need to run a rebalance to get things back to RAID1 happy status but I wanted to get some input first before I went willy-nilly screwing around with it. Diags attached. Thank You unraid-diagnostics-20191029-2249.zip

Hey all, Taking my first stab at installing a P2000 in my rig and it's giving me all sorts of fuss. I'm currently running 6.8rc4. Went through the plugin and installed the nvidia version of rc4, rebooted prior to installed the GPU and was getting kernel panic errors. end kernel panic - not syncing: VFS: unable to mount root fs on unknown-block(0,0) I was able to revert back and get booted, so I tried the approach of installing the GPU, then going through the update processes, same troubles. I reverted back to 6.8rc3 and rc1 and the issue persists. I'm not sure why it's giving me such an issue, I'm not terribly well versed in the Linux side of things but if anyone has some recommendations on what to try I'd appreciate it.

I had a previous incident where I was getting hardware errors reported by Fix Common Problems If I'm reading my logs correctly I'm having them again, but a different stick? Just wanted to get another set of eyes on this to sanity check me unraid-diagnostics-20190923-2220.zip Thanks

Taking a quick breeze through syslog it looks like it's isolated to Chan#0_DIMM#0, would you agree? I'll try reseating that stick today and see what happens, worse case I can pickup a new stick. I appreciate your quick response!

Woke up to a sad error from Fix Common Problems this morning stating my server had detected hardware errors. Full disclosure, I upgraded my processors early last week, though I'm pretty sure I ran Fix Common Problems and it didn't give me any troubles, it's been a long week and I could be mistaken. Any assistance would be appreciated. unraid-diagnostics-20190609-1412.zip

Awesome, that seems to have done the trick. Many thanks

unraid-diagnostics-20181010-1815.zip Attached