Jump to content

cinereus

Members
  • Posts

    485
  • Joined

  • Last visited

Everything posted by cinereus

  1. Haha thanks. Seems a bit of an oversight. Couldn't it be run in a VM somehow? Or at least log the results to the USB it's running from? I'm not really able to buy a VGA monitor and VGA cable to leave running for checking 128 GB RAM.
  2. Also seems you missed a trailing slash I think?
  3. From experience, rclone is the best way to move large amounts of data between NASes. I've had issues with rsync and other methods before. What's the best practice to set up either the old NAS as a remote or the new NAS as a remote with rclone? SMB shares? Obviously data transfer speed is an issue as we're talking tens of TB. What user should I be running it as (and how)?
  4. Is there any way to run memtest with no monitor?
  5. Deluge, Transmission or Rutorrent? Which performs best with large numbers of torrents?
  6. Currently available for just £385 + 7% TCB discount from WD.
  7. Any idea how to get System Temp to work (on Unraid 6.8.3 • Supermicro SuperServer 6027R-E1R12T (rev 03.54) • X9DRH-7TF V1.02) The first time I installed it immediately after clicking detecting and it finding the nct7904 I had a whole bunch of sensors detecting but the second I clicked Done they all disappeared and I'm left with this: My sensors seem to be found okay (although my fan speeds suddenly disappeared from netstat): root@fs:~# sensors coretemp-isa-0000 Adapter: ISA adapter Package id 0: +33.0°C (high = +74.0°C, crit = +84.0°C) Core 0: +27.0°C (high = +74.0°C, crit = +84.0°C) Core 1: +33.0°C (high = +74.0°C, crit = +84.0°C) Core 2: +27.0°C (high = +74.0°C, crit = +84.0°C) Core 3: +26.0°C (high = +74.0°C, crit = +84.0°C) Core 4: +28.0°C (high = +74.0°C, crit = +84.0°C) Core 5: +27.0°C (high = +74.0°C, crit = +84.0°C) Core 6: +29.0°C (high = +74.0°C, crit = +84.0°C) Core 7: +28.0°C (high = +74.0°C, crit = +84.0°C) coretemp-isa-0001 Adapter: ISA adapter Package id 1: +30.0°C (high = +74.0°C, crit = +84.0°C) Core 0: +30.0°C (high = +74.0°C, crit = +84.0°C) Core 1: +28.0°C (high = +74.0°C, crit = +84.0°C) Core 2: +24.0°C (high = +74.0°C, crit = +84.0°C) Core 3: +28.0°C (high = +74.0°C, crit = +84.0°C) Core 4: +26.0°C (high = +74.0°C, crit = +84.0°C) Core 5: +29.0°C (high = +74.0°C, crit = +84.0°C) Core 6: +30.0°C (high = +74.0°C, crit = +84.0°C) Core 7: +28.0°C (high = +74.0°C, crit = +84.0°C) Now no matter what I try (reinstalling from scratch, any permutation of Detect and Load/Unload drivers), I can't get any sensors to show whatsoever. How do I get this to work on my hardware?
  8. I have a problem. I have a Supermicro SuperServer 6027R-E1R12T running a PWS-920P-SQ PSU and X9DRH-7TF V1.02 motherboard. The fans are very loud so I wanted to control fan speed so installed IPMI. Once installed I went to Fan Control, turned it on to Yes and then clicked apply. Instantly, the fan speed ramped up to be deafeningly loud. The server is in a very noise-sensitive location so I immediately toggled it off and clicked apply again but the fan speed remained the same. I uninstalled IPMI and still had the same issue. I then rebooted and had the same issue as soon as unRAID initialised. So I went for the final option and made a new USB drive for unRAID but as soon as the system loads unRAID the fans spin up to max. I've read the note about Supermicro boards in the OP I can't have it this loud for long enough to boot up, install plug ins and then mess about with the settings. I just want to go back to default fan speeds with a completely fresh install. How can I reset the fans to the default settings after whatever IPMI has done to mess them up? I'm starting from a completely fresh install of unRAID. Managed to fix it. Even though the server is on 192.168.0.52, did a scan and would a web server running on 192.168.0.53 which allowed me to log in and manually change the BIOS fan speed. Somehow IPMI had permanently altered this setting!
  9. I know. I'm entering for a 14 GB hard drive, not a 14 TB one. It's also not a GB vs GiB issue as you can simply test by using other amounts. Again, it gives incorrect figures for examples using 14 GB and other numbers I didn't note down. If it can't get 14 GB right I'm worried about it getting numbers in TB wrong too.
  10. Really? It doesn't seem to work for odd sized drives. e.g. 14 GB
×
×
  • Create New...