Jump to content

unraidun

Members
  • Content Count

    34
  • Joined

  • Last visited

Community Reputation

0 Neutral

About unraidun

  • Rank
    Advanced Member

Recent Profile Visitors

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

  1. Ermm from the wiki... Guess I need to download from memtests website and make a second bootable flash? *well dang just made a bootable flash using the utility found on memtest.org (http://www.memtest.org/download/5.01/memtest86+-5.01.usb.installer.zip) but it won't boot (just goes straight to bios). Similar to the problem when first setting up UnRaid (it went straight to bios unless I checked the "Allow UEFI Boot" when running the flash tool). Is there somewhere in my bios where I can enable these 'non UEFI boot' devices? I enabled/disabled "Legacy USB Support", enabled/disabled "Fast Boot", but I don't see any other options relating to booting/UEFI...
  2. Every time I select memtest from the boot options, I get one line of text (too fast to read it) then my machine reboots. Google came up with this... https://www.passmark.com/forum/memtest86/40884-memtest-reboots-before-test-begins ...think this is a 'multi processor' issue? My system... Asus TUF Gaming X570-Plus AMD Ryzen 5 1600 16g Corsair Vengence DDR4 RAM Anyone encountered this before?
  3. Yup, able to http in just fine. So the 'Allow UEFI Boot' tick box definitely did the trick (it's a shame it's hidden under the 'customize' section of the wizard). Now I need to figure out why I just get a flashing _ when I boot into GUI mode... *well guess I will mark this topic as solved. Don't really care about GUI mode as long as I can remote in...
  4. OK making some progress. Re ran the flash maker and noticed if you click 'customize' there is an 'Allow UEFI Boot' tick box, so I checked that. Now I can get to the boot screen, but when I select GUI mode, it looks like it's starting, but then just a black screen with a flashing _ . Going to try no GUI mode now to see if I can at least http to it...
  5. Asus TUF Gaming X570-Plus AMD Ryzen 5 1600 16g Corsair Vengence DDR4 RAM Have my usb flash drive as the primary boot device (only device listed). Tried disabling legacy usb support. Tried enabling CSM and setting all options to UEFI (read that worked in another thread). Tried different usb ports (this MB only has 3.0 ports so can't try a 2.0 port). Yet every time I power on my box, it goes straight into bios (after the TUF Gaming logo). Tried running the flash creator "Unraid.USB.Creator.Win32-1.6" (is there no 64 bit version?) on two brand new "SanDisk Cruzer Fit 16 GB". The first time I formatted before running, the second time I just ran the exe. Both times I got 'write successful', at which point I assumed I was done, so I closed the window (I don't need to run 'make bootable' if I use the wizard/app right?). Any ideas?
  6. Does anyone have experience with the new xfs scrub command? Or some other way to preemptively check the health of a file/disk? That seems to be one of the biggest differences between the two file systems. Or perhaps there is some other xfs or btrfs feature I am overlooking? But as I do more research on btrfs, it does seem like most of the bells and whistles it provides are useless for a simple 'write once read many media archive file server'...
  7. So I've spent a lot of time researching the differences between XFS/BTRFS. All of the 'issues'/instability with BTRFS seem to be from years ago, mostly relating to RAID (which isn't a factor for us, right?). There have been a handful of threads here on the forums, but I would expect more discussion when it comes to such an important (irreversible) decision.. The big selling point for me is data validation. Being able to periodically run 'btrfs scrub' just to verify the health of the disks (and system/memory overall) is a huge selling point. The peace of mind you get from that can't be under valued. I was hoping XFS had something similar, and there does seem to be a new 'xfs scrub' command, but does that actually work like BTRFS? Are there even checksums to verify? Or is there some BETTER way to detect if a drive is silently failing/corrupting data with XFS? Bottom line, if you're going to use UnRaid for a large file/media server (seems to be the most common use case), the only two major concerns I have are... 1.) How much wasted space does BTRFS generate (meta data etc...), and 2.) How much slower is BTRFS when reading/writing files. In the context of a file/media server, I have a feeling the answer to both of those questions is : an insignificant amount. Assuming that is all true, can anyone convince me to use XFS instead? Thanks *and just out of curiosity, what is the logic behind forcing us to use BTRFS for the cache drive?
  8. Hrmm ok so I guess that's one major Pro for BTRFS. But file validation aside, are there any other major differences one should consider when deciding on XFS vs BTRFS (for a typical file/media server)? Honestly I'm still leaning towards XFS (I agree with you guys, the chances of the hardware not catching write errors is slim), but I just want to make sure there isn't something else I'm missing...
  9. Anyone else with XFS experience able to comment on this? XFS must have some way to validate files (something like a btrfs scrub command) right?
  10. Hmm that's unfortunate. But in theory, if you have enough information to rebuild an entire disk, don't you also have enough information to rebuild a single file (assuming you know exactly where the bits exist)? So in the meantime, there is NO way to validate a file after doing a copy in XFS? Again, willing to initiate some kind of manual scrub command (doesn't have to be automatic/native to the file system).
  11. For our work archive/media store, we plan on sending files (massive projects, pictures & video, all of which we need to stream over 10g lan) first to a dedicated ‘uploads’ share. Once a file is placed in uploads, the root admin will manually move them (via Krusader) to the main 'Archives' unraid array (perhaps we could use a script to automate this copy, if no files are being renamed/deleted). In theory, once a file is written, it will rarely (if ever) be touched again. The idea being, we can expose 'Archives' to all users (since it’s read only), and not have to worry about accidental deletion, ransomware, etc… So given this specific use case, XFS or BTRFS for the main array? A feature we would like to have is some way to checksum/validate a file (not every read, just on initial write and then manually/periodically), and recover corrupted files from parity (hopefully without rebuilding the entire disk?). Essentially what we’re trying to figure out is, are there any relevant differences (for this case) between the two file systems? I imagine it is not trivial to switch after picking one, so just trying to avoid buyers remorse before committing (currently leaning towards XFS…). Thanks
  12. In my never ending quest for peace of mind, I came across these 'power supply testers'... https://www.amazon.com/Computer-PC-Tester-Connectors-Enclosure/dp/B076CLNPPK/ref=sr_1_3?keywords=power+supply+tester&qid=1579037405&sr=8-3 For only 13 bucks, seems like a good investment? Especially since the ps I plan to use is a reclaimed part from an old gaming rig (3 year old Corsair CX 750m). Blew out the dust this morning, hasn't been powered on in ages... Would a little device like that tell me if my PS is 'good'? And I suppose I could also use it to test these molex->sata cables too eh?
  13. I think you're right. So I guess the game plan is just to use the 'best' recommended name brand (Monoprice) molex->sata adapter (the reviews confirm it is crimped, so should be less likely to fail). https://www.amazon.com/Monoprice-108794-24-Inch-15-Pin-Female/dp/B009GULFJ0 And just do one adapter (4 drives) per molex. On the plus side, using a molex->sata adapter means I won't have to do the 3rd pin mod for all these shucked WD drives
  14. While doing research on how to power all my sata drives, I came across lots of scary stories about molex->sata power adapters catching fire. This guy on youtube made an interesting video about what to avoid when selecting such an adapter... https://www.youtube.com/watch?v=TataDaUNEFc&feature=youtu.be&t=117 *sadly enough, the same guy had one catch fire because he ignored his own advice... https://www.youtube.com/watch?v=EYkof-csPfI *and the cable autopsy -> https://www.youtube.com/watch?v=fAyy_WOSdVc Well that's just great. Now I'm super paranoid. I HAD planned on using a "good" molex->sata power adapter (one recommended by jonathanm and many others), but I'm still nervous... https://www.amazon.com/gp/product/B009GULFJ0/ref=ppx_od_dt_b_asin_title_s00?ie=UTF8&psc=1 Looking for alternatives to molex, I found a company that sells extra 6pin->sata power cables for my Corsair CX 750m ps, so I thought, great, now I don't have to use those molex adapters. But then I thought, wait, is the problem with the molex, or the sata end of the cable? According to the videos I've seen, it sounds like the sata end is the culprit here. If it isn't shielded properly, the arc which causes the fire will happen regardless (molex or not), right? Does that mean the molex->sata adapter I linked IS indeed "safe" because it appears to be properly shielded/terminated? It just seems like even if I use pure sata power cables, I will still need to use a at least one male->female sata power extension cable (the default cable from my ps isn't long enough). And while that may be safer than a janky molex adapter, isn't a one to one sata power extender still a potential fire hazard? Thanks for any insight!
  15. Was about to order two of those COMeap 6pin -> Molex ps cords, and I saw they DO make sata versions (which also claim to be compatible with my Corsair ps)... https://www.amazon.com/COMeap-Adapter-Corsair-Modular-Supply/dp/B0823989PS/ref=sr_1_6_sspa?keywords=comeap+corsair+6+pin+sata&qid=1578972588&s=electronics&sr=1-6-spons&psc=1&spLa=ZW5jcnlwdGVkUXVhbGlmaWVyPUFXSEMxWFROWERHJmVuY3J5cHRlZElkPUEwNTAxMzM5VDFUUVAzUUxFNDk0JmVuY3J5cHRlZEFkSWQ9QTAzNDI1NDFPRTZQMUZUTTRNMUwmd2lkZ2V0TmFtZT1zcF9idGYmYWN0aW9uPWNsaWNrUmVkaXJlY3QmZG9Ob3RMb2dDbGljaz10cnVl So I COULD in theory power everything with pure sata (no molex -> sata adapters), but then my cables won't be long enough to reach the farthest drive bay. My case seems like it's pretty common server dimensions (Rosewill L4500 server chasis). How in the heck do you guys power your far corner drives WITHOUT resorting to daisy chaining/adapters? Would tacking on a simple male->female 3 inch sata extension cable to each port be better/safer than the previous plan (molex->sata)? *sorry didn't mean to hijack this thread, started a new thread regarding this issue/sata port fires...