• Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About reapola

  • Rank


  • Gender
  • Location

Recent Profile Visitors

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

  1. They (the community devs in question) have stated they weren't communicated behind the scenes as you expected which is where this discussion of unraid vs community developers has erupted from. Glad you've planted your flag though.
  2. Nope, looking seriously at all the main players again - migrated from Readynas pro over 4 years ago which was also propped up by its community as to inbuilt limitations by design or lack of forethought.
  3. Great that integration of 3rd party modules into the kernel is being being helped by people that don't know how that 'works'. @limetech this is a situation of your own making which has just been made worse by your replies. I was looking for a project under our 2nd COVID lockdown and I think you've just given me it.
  4. *moved from hardware Use case: I've been using Unraid for the last 4 years and during that time I've upgraded a few times with the server going from just being used to host media files to being used for gaming/VR and now full circle back to a NAS host with extra capability. Now with the 'new WFH normal' I find myself using my own device more for accessing work services etc and I'm currently finding the Dell SFF endpoint I use lacking. Over the last few days I've been pricing up building another standalone gaming PC but now I'm looking at a full compute re
  5. 1c | 285 | 8448 | 4224 | 128 | 4216 | 323.3 Wish it was that fast! Any comments on the results? The original settings were put in when I built the server in 2016. I'm currently looking at moving to 8/10Gb disks, probably shucking the WD elements as the price of reds are ridiculous! Unraid 6.x Tunables Tester v4.1 by Pauven Tunables Report produced Thu Sep 19 21:27:49 BST 2019 Run on server: Zeus Extra-Long Parity Sync Test Current Values: md_num_stripes=4096, md_sync_w
  6. I'm on my second unraid build after having a readynas pro for years. My last build (see below) set up in 2017 was based off the techspot article that year - At the time the CPUs were £180, ram £200 & motherboard £300 which for a 32thread server was a steal. This year I've been upgrading my gaming PC and now its time to look at the server, so far its been mainly housekeeping to reduce the data usage (currently 70% used) in order to replace the hdds as they are 4/5 years old now running 24/7. Are there any similar
  7. Rolled back to 6.1.9 after hard lock of w10 gaming vm which in turn locked unraid necessitating in a unclean shutdown. Spent the rest of the night getting the server back up to scratch and creating a new w10 vm. I think at this point I'm "out" with 6.2 after the initial hassle of getting it installed upgrade followed by this.
  8. Upgraded to beta 20 and experienced the same label not found error as previous betas. Threw caution to the wind and created a new virgin usb unRAID bootdisk and it started fine. Slight issue with unraid not detecting the filesystem when starting the array resulting in a unmountable drives and brown pants moment. Changing from 'auto' to xfs for each affected drive fixed the issue and avoided me crying lots. I've now set up all the dockers, settings and plugins from scratch and very happy with the polish that's went in to the updated webui - good job! Since i'm having to rem
  9. The problem is happening earlier than your screenshot shows, and your system log attached in previous post is too garbled to read btw: how'd you get that log if you can't mount the usb flash? Did you try some of the other usb ports? Core linux os is loading so ssh is enabled, logged in and scp'd it across - garbled how? File is a tar bz2 of the whole log directory. Attached is the syslog extracted out the archive. Tried all the usb ports, 1 on motherboard for hypervisors, 4 on back, 2 on front and 2 usb3s syslog.txt
  10. In reference to the bug report above, here's the capture from ipmi console. Edit: This is with a freshly formatted usb which was formatted and labelled as per spec using windows epxlorer and not rufus as I was previously using. Reverting back to 6.1.9 fixes the issue so must be kernel or driver related. Motherboard is a SuperMicro X10SL7-F ( and the usb stick is connected to a USB2 port which is as far as I'm aware connected to an Intel® C222 Express PCH controller.
  11. Same issue here with b19 as 18, flash does not mount and therefore OS doesn't load. I've attached a copy of the log dir which should hopefully highlight the issue. Attached file is .tar.bz2 unraid_6.2b19.No_unRAIDlabel_logdir.txt
  12. Other people have reported the same bug in this thread?
  13. Nope, logs posted before are from a physical install with the usb stick originally on the esxi/internal USB port. Tried all the usb controllers and a different usb.
  14. Any update to why the flash can't/ won't mount and subsequently won't boot?
  15. I have two of the recommended flash drives, one of which being the sandisk cruzerfit which this install has the guid tied to. I've taken the files off the drive, formatted with rufus to fat32 with an mbr and label of 'UNRAID' and it still refuses to see the usb drive after the os goes to ram and mount /boot. I've also tried another usb stick to rule out a dodgy usb drive (although both are 3/4weeks old) and moved the usb stick from the esxi/hypervisor usb port underneath the gfx card to one at the rear, which as a by product saves me from swearing trying to get a finger underneath the gtx970