• Content Count

  • Joined

  • Last visited

Community Reputation

1 Neutral

About psm321

  • Rank

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Thanks! I see that it does xfs_growfs on every disk it mounts And runs sgdisk to create a new partition table on some subset of disks, seems most likely newly-added ones.
  2. So I've read various pages and see that the recommended method to replace a data drive with a larger one is to simply unassign the old one, assign the new one, and let it rebuild onto it. My question, out of curiosity, is how the filesystem is grown (since there don't seem to be any instructions for it and people seem to say that it "just works"). I would assume that the kernel-level unraid md driver only literally rebuilds the disk image. Does emhttpd throw some magic on top of that that edits the partition table and grows the fs after the rebuild is done or something? Just want to unders
  3. Ok, thanks to some fun kernel hackery, I got myself out of the situation so no longer urgently need an answer. Still curious if there was a different way to go about it though.
  4. I am not by any means an expert at unraid or data recovery -- only replying because nobody has. If somebody more experienced comes along you should probably listen to them instead of me! If you're comfortable with the shell, you could try this script: Note: I haven't tried it and am no expert. General data recovery rules (which you already seem familiar with, but just to reiterate): stop using (writing to) the device that the file was deleted from, and make sure to not try to recover to that
  5. Also, if you're like me and get the "bright idea" to give your vdisks serial numbers in the XML to distinguish them instead of using different sizes and upsetting your OCD, don't be like me and put spaces in the serial number or you'll waste a few hours figuring out that unraid doesn't like that. Probably best to avoid other special characters too and just stick with alphanumerics.
  6. Just a quick note in case somebody else gets stuck on this: I was having trouble getting my VM to see the USB stick, which was plugged into a USB3.0 port. I had to change the emulated controller from the default ehci USB2.0 to be an xhci USB3.0 one (either nec or qemu works, though a quick google seems to show qemu is preferred) to get it to work.
  7. Yes, I realize now that it was stupid to do, but I set md_sync_thresh and md_sync_window to 0 while trying to experiment with why a file move was slow. But now, I can't change those values or stop the parity check because all the various waits etc. in the code are looking for pending counts to be < 0. Just wondering if anybody has ideas for getting out of it other than just doing an unclean shutdown
  8. I just wanted to bump this once before working on a custom container as I'm coming up on renewal. Sorry if I missed a reply somewhere, didn't find one in a quick search.
  9. For anyone else reading this, I did end up ordering an ASM1142 card ( ) and it works fine natively.
  10. You have too many ptys open. Apparently each qemu (VM) uses one up to provide a serial console to the VM. You likely have some combo of 8 total VMs+web terminals+preclears running. Other than closing some of them, the other option would be to allow more ptys to be used for a root login by appending lines like pts/8 pts/9 pts/10 pts/11 etc. into /etc/securetty. Removing /etc/securetty entirely also accomplishes this, but I don't claim to understand the security implications (if any) of doing this.
  11. I'm on my phone so I didn't check all of them, but at least some of the plugins have an individual option for it. The one I used has it and so does the nsone one. err, command-line options, not config file options afaict. That would be too convenient
  12. I would personally suggest trying a longer propogate delay. I was having similar issues with 30 seconds. Unfortunately AFAIK there's not a container variable for this -- I ended up editing something inside the container.
  13. Perhaps it's running and unRAID lost track of it? (not sure if that's possible, I'm new to all this). docker ps | grep "" should tell you what container is using it
  14. netstat -nptl (I believe it's in nerd tools) should show you what's listening on that port