nfriedly

Ok, I had two more freezes. Yesterday's was a bit different - it happened in the afternoon, they keyboard lights didn't blink, and when I rebooted it, it told me that the CPU was over temperature. This made me realize that the fan in the AOI cooler had died. (The pump was still working though.) That might be the root cause of the whole mess. I swapped it with a case fan and rebooted. It kicked off a parity check and seemed to be working when I went to bed. I thought maybe I had fixed the issue. This morning it was back to the same type of crash that had happened before yesterday with the keyboard lights blinking. I'm attaching the syslog and syslog-previous, but my suspicion now is that something is got permanently damaged by the CPU overheating. --------- Update: (April 22) maybe it was just overheating. It's been a month and a half, and aside from the one crash that happened the night after replacing the fan, it's been rock solid. I ordered an HBA card, and was waiting for it to arrive so that I could use a different CPU & motherboard with fewer SATA ports. But now that it's arrived, I'm not sure I actually need it. Oh well. I'll probably swap it out anyways. syslog syslog-previous

Ok, I turned on Mirror syslog to flash, I'll post another update after the next freeze. I see it says a copy of the syslog is stored in the logs folder on the flash drive - what's the right way to retrieve that file? Is it exposed in the web UI or over the network, or should I just plug the flash drive into another computer?

I put my server together about 6 years ago and it's been really solid until recently. However, 4 times in the last ~month I've found it completely frozen, not responding to network requests (file shares, docker images, the admin web UI), and not responding to keyboard or mouse inputs at the physical machine. When this happens, the numlock light on the keyboard turns off and the caps lock and scroll lock lights start blinking. It seems to be getting more frequent, with the most recent two freezes happening after only a day or two of uptime. The screen shows whatever was happening at the moment it froze, so I've left `htop` open once, and `dmesg --follow` the next time, but neither have anything too obvious. htop shows shfs using about 10% CPU and transmission using another 15% across two processes; dmesg shows only two recent messages: md: sync done. time=60938sec md: recovery thread: exit status 0 I'm not sure what those mean, but "exit status 0" sounds like "not a crash". I'm also attaching an anonymized diagnostics bundle. The CPU, MB, and RAM (i7-2600K, Asus P8P67 Pro, & 2x8GB Kingston HyperX Fury DDR3-1866) are all recycled from the desktop PC I built about 15 years ago, so my first thought is that maybe one of them is going out. But I'd still like to understand what's happening better. Also, all of 4 freezes have happened in the middle of the night, which makes me think it might be some scheduled thing that's triggering it. [Edit] One other thing that comes to mind is that I switched the cache drive from a SATA SSD to an NVMe SSD a couple of months ago. I initially messed up the file owners when copying everything over to the new SSD, which broke some of my docker images, but I think I have it straightened out now. Does anyone here have any ideas what the root cause might be? unraid-diagnostics-20240226-1418.zip

In my case, none of these were true - I'm on a personal account and I've had 2FA enabled for years - but it still wouldn't show me the App Passwords option. I poked around for a while and eventually found that the url https://myaccount.google.com/apppasswords works even though it doesn't show up in the security settings. After that, when I did finally get google to give me an app password, I tried just copy-pasting it to unraid, but that got an authentication error. Eventually I realized that even though the password was really 16-characters, google had put spaces after every 4 characters for readability (or whatever), so when I copy-pasted I got extra spaces that weren't part of the password. I had to paste it into a notepad, delete the spaces, then copy it into unraid.

That was it! uBlock Origin said nothing was blocked, but disabling it and refreshing brought my shares back! Thank you! I still want to know how I was able to write 400gb of data to an unmountable drive, but everything seems to be working now.

Does unraid automatically format a drive in the process of clearing it and adding it to the array? My current best guess is that that didn't happen - the drive was never formatted - but for some reason it let me write data to the drive anyways. Then, after rebooting, the data is there, but the "headers" or whatever it needs to identify the format isn't there. I'm going to try formatting it and just copy the data over again. Update: Yep, formatting & rebooting fixed my 4th drive. The Shares tab in the Unraid UI is still empty. However, and I didn't think to check this before, but my shares do show up if I look at the network from another computer. Aside from the Shares UI, everything seems to be working. Edit: A couple of other things I noticed: the dashboard says "Share count: 9", but doesn't list any of them. And, if I go to create a new share, the "Read settings from" menu shows all of my shares.

Here you go unraid-diagnostics-20190715-1910.zip

Hi folks. I added a 4th data drive to my Unraid array yesterday, and I let it do it's clear thing. I have the default FS set to BTRFS, so I expect that's how it was formatted. My other drives were XFS because that was the default when I first added them. So that could be part of the trouble. Anyways, I added the drive, let it clear overnight, created a new share with only the new drive (no cache), and started sending data to it. I think I got around 400GB transferred over before I happened to look in the UI and notice that the FS column said "auto" and the Size/Used/Free column said "Unmountable: Unsupported Partition Layout". This was obviously at least partially incorrect as it was mounted. However, I wanted to add one more drive, so I went ahead and shut down to do that, then I had to upgraid my unraid license for the new drive, then I added the next drive to the array. It's clearing now. But, the drive I added yesterday still says it's unmountable, only now it's actually not mounted. And, to make matters worse, my shares page is now empty. There was only one other important share, and it was (probably) set to use all drives in the array, so that might be why it's hiding all of them from me; I'm not sure. What I'd like help with is 1) How do I get my shares back? 2) How do I make yesterday's drive mountable? Preferably without loosing the 400gb, although I can get it back if I have to. 3) What happened and how do I prevent it from happening again?

That seems to have done the trick. Somewhere along the line, part of my media library seems to have been (automatically?) moved to the third disk, which explains why it ran out of space before I was expecting it to. Thanks for the help!

Ok, without the -n, It gave me this: Phase 1 - find and verify superblock... couldn't verify primary superblock - not enough secondary superblocks with matching geometry !!! attempting to find secondary superblock... .......................................found candidate secondary superblock... verified secondary superblock... writing modified primary superblock sb realtime bitmap inode 18446744073709551615 (NULLFSINO) inconsistent with calculated value 129 resetting superblock realtime bitmap ino pointer to 129 sb realtime summary inode 18446744073709551615 (NULLFSINO) inconsistent with calculated value 130 resetting superblock realtime summary ino pointer to 130 Phase 2 - using internal log - zero log... - scan filesystem freespace and inode maps... sb_icount 0, counted 3651520 sb_ifree 0, counted 176 sb_fdblocks 732208915, counted 957649 - found root inode chunk Phase 3 - for each AG... - scan and clear agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 - agno = 2 - agno = 1 - agno = 3 Phase 5 - rebuild AG headers and trees... - reset superblock... Phase 6 - check inode connectivity... - resetting contents of realtime bitmap and summary inodes - traversing filesystem ... - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify and correct link counts... Note - stripe unit (0) and width (0) were copied from a backup superblock. Please reset with mount -o sunit=,swidth= if necessary done So, I think that means it fixed something. What's the best next move? Just restart the array without maintenance mode? Or do I need to worry about parity being wrong? Also, does anyone have any idea how the drive got into the broken state? That's my bigger concern. Thank you for the help! (And patience!)

Ok, here's the output: Phase 1 - find and verify superblock... couldn't verify primary superblock - not enough secondary superblocks with matching geometry !!! attempting to find secondary superblock... .......................................found candidate secondary superblock... verified secondary superblock... would write modified primary superblock Primary superblock would have been modified. Cannot proceed further in no_modify mode. Exiting now.

Hi folks. First up: I have backups of my data, so I haven't actually lost anything. I just want to know what happened and how to avoid it in the future. I have a drive in my array, disk 3, that I had done a command-line rsync to send data to it. I didn't realize that I was trying to send a little bit more data than would fit on the drive. So, it's 100% full and the rsync failed to complete. No big deal, just wasted time. I figured I'd clean it up later. Not sure if that's relevant, but it might be. I shut down my system and added more RAM a couple of days ago. It was a clean shutdown via the web UI, and I waited for the system to completely power down before swapping out the RAM. I booted it back up, but then had to leave, so I didn't really inspect it that closely. I'm not sure if it was reporting the drive as full or not formatted at that point. This morning I logged in to look at things more closely and found the drive reporting as not formatted. I tried a reboot (via the web UI) but that didn't change anything. I dumped the diagnostics, but I'm fairly new to unraid, so I'm not even sure what I should be looking for. As far as I can tell, it's not acting like any errors happened, it's just acting as if I had never formatted the drive in the first place. The SMART reallocated sector count has a raw value of 8, but it's been that way for a while, so I'm not sure if that's related. unraid-diagnostics-20181220-1253.zip

Cool, thank you! For others (and myself in 6 months), here are some links: Nerd Pack (includes tmux): - source, including current list of packages is at https://github.com/dmacias72/unRAID-NerdPack Dev Pack: - source: https://github.com/dmacias72/unRAID-DevPack Also, for reference: just installing the plugin doesn't actually do anything, you have to then open the plugin's settings, turn the tools you want "on" and then hit Apply to actually install things like tmux. In my case, after that, running tmux fails with "open terminal failed: missing or unsuitable terminal: xterm-256color" - however, running "TERM=xterm tmux" does work, but then it had other issues (like `more` doesn't output the correct number of lines, and [backspace] inserts a space.) I gave up on tmux and switched to screen, which was also installable via the Nerd Pack. I prefer tmux, but screen actually works, so it'll do for now.

Hi, I'm brand new to unraid. I know most things should be done in VMs and/or Docker, but I just want to have a few tools like tmux installed in the base system. I tried yum, apt-get, apk, and pkgtool, but none of them were installed. I also tried building tmux from source, but there's no make or g++ either. I feel like there's gotta be something that I'm missing (?)

Hi, I'm brand new to Unraid, so I might just be missing something obvious, but I'm trying to follow the instructions at https://wiki.unraid.net/index.php/UnRAID_6/VM_Management#Step_4:_Edit_the_XML_for_your_virtual_machine to import my existing windows drive, and I don't see an "Edit XML" option when I click on the VM icon. I only see Start, Logs, Edit, and two Remove options. Clicking Edit doesn't seem to bring up anything XML-related either. Any suggestions? Update: found it on the drive: in /etc/libvirt/qemu/ - next issue is that I'm importing an nvme drive. I'm trying to follow the instructions below to get that working: