bidmead

Members
  • Posts

    120
  • Joined

  • Last visited

Everything posted by bidmead

  1. Thanks again, JorgeB. That's really helpful. OK, I've now set the Maxstor format to btrfs and successfully added it to the restarted array. More confusion here, though, as under Main, the drive file system is reported as btrfs but is also being reported as "unmountable, no file system". Apologies for the repeated requests for handholding. The UnRAID WebGUI is magnificently detailed and the clarity of the physical layout is exemplary (QNAP and Synology please note). But the logic is occasionally defeating me. -- Chris
  2. In the screenshot I posted. -- Chris Sent from my CPH1907 using Tapatalk
  3. Ah, OK. Thanks, JorgeB. That makes sense. If I'm going to add the drive to the array (which is my intention) I don't need to format it at this point because the act of adding it will present the formatting opportunity. What I'm less sure about it why the drive is being declared as "missing". As a complete newbie I'm not clear what UnRAID thinks this drive is missing from. Not missing from the array, because it was never in the array. And not missing from the list of unassigned devices because it's still showing up in that list. Can you clear this up for me? -- Chris
  4. Thanks for getting back to me. Ok, I've done what you suggested. The red X disappears and I've refreshed the browser page. But there's no change. The format button is still greyed out and the drive still appears as both unassigned and missing. I intended to add the drive to the array. -- Chris Sent from my CPH1907 using Tapatalk
  5. OK, I've used the Preclear plugin successfully to preclear a 300GB Maxtor drive. The precleared drive shows up under Unassigned devices. There's a button to format it, but it's grey and has lost its link. Below is a list of Missing drives and the Maxtor appears there. Can anyone tell me what's going on here? -- Chris
  6. I'm getting this error in the DriveSpeed logs: "ERROR","127.0.0.1-startStop-1","11/03/2020","10:33:53","","load-extension;Extension [15mcbgnnccbzf.lex] was not found at [/opt/lucee/server/lucee-server/context/extensions/installed/15mcbgnnccbzf.lex];lucee.runtime.exp.ApplicationException: Extension [15mcbgnnccbzf.lex] was not found at [/opt/lucee/server/lucee-server/context/extensions/installed/15mcbgnnccbzf.lex] Can anyone throw light on this? -- Chris
  7. Many thanks for that, John. I didn't know about Highcharts. That's very useful enlightenment. My comments here have been largely a knee-jerk reaction conditioned by flying chalk incidents in boyhood. I apologise if I've raised a hackle or two. I still think Mr Creighton has an indelibly valid point. But at the next seance I shall tell him to calm down. -- Chris
  8. Thanks for the thought, BRiT. No, I've no sense of malicious intent here. I'm only trying to adjust to the mood. I think I've said what I believe could be improved in the description of the units. What's your view on this? -- Chris
  9. I didn't come here to pick a fight. But happy to be piled on by the occupants here if that's the style of discourse. It's a kind of welcome, I suppose. As an IT journalist I'd never get away with using T on its own to denote anything other than a metric tonne (or perhaps a tablespoon). There are well-developed conventions for describing MB/s (or Mb/s---which is it?) and TB (or Tb or TiB---which is it?) and the Internet seems to confirm that there's enough regular adherence to these conventions in drive speed charts to justify the stinging flightpath of Mr Creighton's chalk in the direction of fuzzy units. John Bartlett's done some really excellent work here. Are we saying it's perfect and beyond refinement? -- Chris
  10. My interpretation probably isn't very relevant. It's Mr Creighton and his flying chalk we should be worrying about... More seriously, a chart like this is supposed to convey information with a degree of precision. It's not a Rorschach Inkblot Test. -- Chris
  11. As a (quite genuinely humble in the light of the expertise on display here) newbie to this topic and to UnRAID in general, may I make a plea on behalf of my old and now deceased chemistry master, Mr Creighton, who would regularly throw chalk with high speed and deadly accuracy at any pupil who omitted or misapplied units. He is turning in his grave at the use of "M" on the Y-axis and "G" on the X-axis for these drive speed charts. -- Chris
  12. The request (for WebGUI read-only access) makes sense to me. And I too feel uncomfortable having to log in as "root". I stumbled onto this thread because I've been trying to create a second admin account called, er, admin and have discovered I can't do it. Any account added subsequent to root apparently has to be a user account. I was hoping to run a pair of admin/root accounts simultaneously (but very temporarily) so I could explore the capabilities of one without compromising my ability to get into WebGUI administration. This arose because I added a password to the default root account and then discovered that for some reason I was being denied admin access (of course, there's a simple fix if you're local to the physical server). Does anyone know of some kluge at the command line level that might provide a second admin account (like duplicating and editing the relevant entries in /config/password and associated files)? -- Chris
  13. What's the performance penalty for booting without ACPI? I'm also puzzled about the Asmedia controller being unknown to Linux. Isn't Linux the basis of QTS? -- Chris
  14. I'm still puzzling over this. Perhaps someone with a general knowledge of bootable USB drives might be able to help out here. The Hiren's Boot CD (USB version) that I have here is the one USB drive that boots all the way. I have not been able to create any other USB drive, using any other operating system, that does this. The only unique feature I can identify with this Hiren's USB is that it uses the Windows operating system. All my other attempts (including UnRAID) have involved versions of Linux. I'm attaching a screenshot of the Hiren's directory structure in the hope that someone here might be able to put their finger on why this boots and others don't. If there's any other information that would help with this, do please let me know. Thanks in advance to whoever responds and in any case thanks to all of you reading this. -- Chris
  15. I've written more on the private Tested Technology page to add the result of my inspection of the various USB sticks, recognised and unrecognised by the GA-E45-DS3R BIOS (F4). Spoiler: The conclusion isn't very exciting. But I'd be delighted if forum members could pitch in with suggestions, vague encouragement and/or hoots and whistles of derision at my methodology. Every little helps. -- Chris
  16. Thanks for that, Decto, and thanks for taking the trouble to read the Tested Technology private page. The collection of random USB flash drives, of which only a handful appeared in the piece I wrote, is the swag collected from a quarter century of IT journalism and press events. (The IT career is longer than than but USB turned up late.) If I could find a way to pool them all into a vdev I'd have plenty of room to back up the Internet. I think I've created and tested every possible variant of the UnRAID boot USB. Yes, I'm pretty certain the issue is with the motherboard, not with UnRAID, as you suggest, although being limited just to USB booting is one of the fundamental challenges UnRAID presents here. I'm not sure that downgrading the BIOS from F4 would be my first choice. I'd rather been thinking in terms of upgrading to a later version (F9?). One reason I haven't yet done so is that I'm damned sure we got this thing booting nicely and regularly from a USB stick back when it was a Hackintosh. And on top of that, I'm very curious to know, to get to understand, why we can't do that now. I'm currently scouring through the recognised and unrecognised USBs to try to grok their diffs. (Although the fact that the UnRAID USB that manages to get as far as GRUB isn't among those recognised in the Boot Candidate list suggests I may be barking up the wrong tree here.) I've followed the links you've pointed to (many thanks) and will investigate further tomorrow. -- Chris
  17. Many thanks, Decto. I've taken your advice about skipping the Gigabyte splash screen---it's saved me a lot of time carrying out the repetitive investigation I'm documenting on this unpublished Tested Technology page. I'm writing up the ongoing adventure there to avoid taking up time and space here in this forum. But I'd be very grateful for input from anyone who would care to visit the page and contribute their thoughts. The ultimate aim (looking a little far off at the moment) is to do a series on the development of an UnRAID system, starting with a single drive, expanding that to a dual drive system (data drive + parity drive) and then subsequently to add an SSD cache. Then bung other drives in as available. We have the drives and the SSD, generously donated by Seagate and OWC and I know this nice old Cosmos box can boot from USB. Just can't get it to connect with UnRAID! HALP!!! -- Chris
  18. This motherboard is in a machine we built just over a decade ago as an early Hackintosh. (https://www.theregister.com/2009/08/26/efix_os_x_on_generic_pc/) It could definitely boot from a USB drive then because it had to. I want now to install UnRAID on this same machine. But it seems it can no longer boot from a USB drive. To simplify the issue, apparently the BIOS is no longer able to SEE any USB drives. As the risk of being over-long here and outstaying my welcome as a newbie, I'll lay out where I've got to so far: STATUS 1. Not all the external USB ports on the CoolMaster Cosmos case are actually wired. The ones I've been using are known-good to work with the keyboard. 2. The build currently has a CD-ROM drive and an SSD which I have not installed a bootable operating system on. 3. The SSD shows up as a boot candidate under Advanced BIOS Features/Hard Disk Boot Priority (along with "Bootable Add-in Cards") but not the CD-ROM. However, I can boot from the CD-ROM drive, as tested with an old Hiren's Boot CD. ASSUMPTIONS 1. With the correct BIOS settings the known-good USB ports (see 1. above) should be physically capable of supporting USB flash as drives. 2. Any possible problems beyond the motherboard (eg RAM, CD-Drive, SSD drive, Graphics card, USB format and/or bootability) are irrelevant to the question of whether the BIOS can find the USB drive. 3. A found USB drive won't necessarily show up as a boot candidate (as described in 3. above) but should show up as a potential target for Q-Flash (F8). 4. Setting USB-HDD in the Boot Device List or not won't affect Assumption 3. 5. All the BIOS parameters relevant to this issue are under Integrated Peripherals and the rest can safely be left to the Fail-Safe defaults. So I'm currently messing with the Integrated Peripherals parameters then rebooting and checking Q-Flash. If I should be exploring wider parameters or if there's a better test than this or if any of my assumptions are wrong, do please shout out. -- Chris