Jump to content

ldrax

Members
  • Content Count

    52
  • Joined

  • Last visited

Community Reputation

0 Neutral

About ldrax

  • Rank
    Advanced Member

Converted

  • Gender
    Undisclosed
  1. Never mind me. There is apparently a whole new world with GPU passthrough with VM on unRAID. I'll go read them up.
  2. Is the VM able to use the GPU directly? Not sure the term, hardware passthrough?
  3. Hi everyone, I'm just wondering what is the use case of having a mid (or high)-end GPU on unraid build? I have recently upgraded my build with higher specs, that is i7 3770 with Z77 board (they were great specs in their times). These days, used GTX 980, 980Ti, 1060 or RX580 can be had at very reasonable price. Normally the question will be, can I use this for purpose A or B or C. But it's reversed-question, for what purpose X,Y,Z can I use this for? Thank you!
  4. I recently reformatted my disk1 from ReiserFS to XFS, and then I did rsync -avPX /mnt/disk4/ /mnt/disk1 When it's done I ran the xfs_db - frag-f, to my surprise the fragmentation level is 27%, I was kind of hoping to see 0%. Does rsync write some temporary files somewhere on destination drive, and then delete it after completion? Other than that, I'm not sure what might cause the rather significant fragmentation.
  5. Right now I'm running 4 concurrent file copy operations. Command used: rsync -avPX /source /destination Parity: disabled (unassigned) Thread 1: from disk 3 -> 2 Thread 2: from disk 4 -> 1 Thread 3: from disk 7 -> 8 Thread 4: from disk 9 -> 5 I'm only getting about 30MB/s for each of these 4. Tried both recontruct write and Auto on Disk Settings, results are the same, but I figure since parity is disabled, this doesn't matter. If I run just 2 operations, speed of each would be around 45 - 55 MB/s. The disks are connected to SATA ports on motherboard and some to LSI 8i RAID card (PCIE3 x4). Does this mean that as a whole, my entire build's disk bandwidth is only about 100-120 MB/s ? A while back I did an rsync from most of these disks, one disk at a time, to another unRAID build, the max speed was around 120MB/s, but I figure that's the max of my gigabit LAN speed.
  6. Autofan questions. Q1 I understand that autofan is controlling speed by pwm. Is it also working with 3-pin fans header with no PWM, that is, will it do voltage-based speed control using pin #3? If not, is there such plugin? Q2 I'm wondering about the issue of minimum PWM. I clicked DETECT next to "Minimum PWM value:" settings a few times, but the field remains blank. Meanwhile, syslog is reporting 0 rpm at certain PWM values, logs below. Is this all fine or do I need to adjust something somewhere? Oct 27 05:38:09 Tower autofan: Highest disk temp is 40C, adjusting fan speed from: 189 (74% @ 2265rpm) to: 145 (56% @ 1771rpm) Oct 27 05:43:14 Tower autofan: Highest disk temp is 39C, adjusting fan speed from: 145 (56% @ 1767rpm) to: 123 (48% @ 1500rpm) Oct 27 06:08:23 Tower autofan: Highest disk temp is 38C, adjusting fan speed from: 123 (48% @ 1500rpm) to: 101 (39% @ 0rpm) Oct 27 06:13:28 Tower autofan: Highest disk temp is 34C, adjusting fan speed from: 101 (39% @ 0rpm) to: OFF (0% @ 0rpm) Oct 27 06:23:33 Tower autofan: Highest disk temp is 36C, adjusting fan speed from: OFF (0% @ 0rpm) to: 57 (22% @ 0rpm) Oct 27 06:33:38 Tower autofan: Highest disk temp is 37C, adjusting fan speed from: 57 (22% @ 0rpm) to: 79 (30% @ 0rpm) Oct 27 06:48:43 Tower autofan: Highest disk temp is 38C, adjusting fan speed from: 79 (30% @ 0rpm) to: 101 (39% @ 0rpm) Oct 27 07:03:49 Tower autofan: Highest disk temp is 0C, adjusting fan speed from: 101 (39% @ 0rpm) to: OFF (0% @ 0rpm) Oct 27 07:28:54 Tower autofan: Highest disk temp is 39C, adjusting fan speed from: OFF (0% @ 0rpm) to: 123 (48% @ 0rpm) Oct 27 07:33:59 Tower autofan: Highest disk temp is 37C, adjusting fan speed from: 123 (48% @ 1513rpm) to: 79 (30% @ 0rpm) Oct 27 07:44:04 Tower autofan: Highest disk temp is 38C, adjusting fan speed from: 79 (30% @ 0rpm) to: 101 (39% @ 0rpm) Oct 27 07:54:10 Tower autofan: Highest disk temp is 39C, adjusting fan speed from: 101 (39% @ 0rpm) to: 123 (48% @ 1500rpm) Oct 27 07:59:15 Tower autofan: Highest disk temp is 37C, adjusting fan speed from: 123 (48% @ 1510rpm) to: 79 (30% @ 0rpm) Oct 27 08:04:20 Tower autofan: Highest disk temp is 38C, adjusting fan speed from: 79 (30% @ 0rpm) to: 101 (39% @ 0rpm) Oct 27 08:14:25 Tower autofan: Highest disk temp is 39C, adjusting fan speed from: 101 (39% @ 0rpm) to: 123 (48% @ 1496rpm) Oct 27 08:19:30 Tower autofan: Highest disk temp is 37C, adjusting fan speed from: 123 (48% @ 1510rpm) to: 79 (30% @ 0rpm) Oct 27 08:24:35 Tower autofan: Highest disk temp is 38C, adjusting fan speed from: 79 (30% @ 0rpm) to: 101 (39% @ 0rpm) Oct 27 08:34:40 Tower autofan: Highest disk temp is 39C, adjusting fan speed from: 101 (39% @ 0rpm) to: 123 (48% @ 1490rpm) Oct 27 08:39:45 Tower autofan: Highest disk temp is 37C, adjusting fan speed from: 123 (48% @ 1510rpm) to: 79 (30% @ 0rpm) Oct 27 08:44:51 Tower autofan: Highest disk temp is 38C, adjusting fan speed from: 79 (30% @ 0rpm) to: 101 (39% @ 0rpm) Oct 27 08:54:56 Tower autofan: Highest disk temp is 39C, adjusting fan speed from: 101 (39% @ 0rpm) to: 123 (48% @ 1486rpm) Oct 27 09:00:01 Tower autofan: Highest disk temp is 37C, adjusting fan speed from: 123 (48% @ 1510rpm) to: 79 (30% @ 0rpm) Oct 27 09:05:06 Tower autofan: Highest disk temp is 38C, adjusting fan speed from: 79 (30% @ 0rpm) to: 101 (39% @ 0rpm) Oct 27 09:15:11 Tower autofan: Highest disk temp is 39C, adjusting fan speed from: 101 (39% @ 0rpm) to: 123 (48% @ 1503rpm) Oct 27 09:20:16 Tower autofan: Highest disk temp is 37C, adjusting fan speed from: 123 (48% @ 1510rpm) to: 79 (30% @ 0rpm) Oct 27 09:25:21 Tower autofan: Highest disk temp is 38C, adjusting fan speed from: 79 (30% @ 0rpm) to: 101 (39% @ 0rpm)
  7. I've been re-reading this guide: https://wiki.unraid.net/File_System_Conversion I have 11 data disks array currently in ReiserFS, and 1 parity. The 'most recommended' option in that guide is "Mirror each disk with rsync, preserving parity method". I've been mulling over whether to use "Share based with inclusions, no parity" method. I have the option to move 4-disks worth of data to another build, with no need to transfer it back, hence I should be able, I think, to convert 4 disks in one go using 4 screen sessions. All user shares have inclusions set, but honestly if it's too much of a trouble to keep this config, I don't mind losing all shares config. Would like to have second opinion on what I figure the steps would be: 1. Empty 4 disks (say, 1-4) by moving all data from them to another NAS. 2. Stop array, change partition type of disk 1-4 to XFS. 3. Unassign parity disk. 4. Start array, disk 1-4 will be formatted to XFS, data on these will be lost. 5. Copy data from disk 5-8 to newly formatted disk 1-4, respectively. 6. Verify data in disk 1-4. 7. Stop array, change partition type of disk 5-8 to XFS. 8. Start array, disk 5-8 will be formatted to XFS, data on these will be lost. 9. Copy data from disk 9-11 to newly formatted disk 5-7. 10. Verify data in disk 5-7. 11. Stop array, change partition of disks 9-11 to XFS. 12. Assign the parity disk back. 13. Start array, disks 9-11 will be formatted to XFS, parity will be built. I hope there is no issue unforeseen with this plan.
  8. Just an update for my case, it turned out that the 300W SFX (SSP-300SFB Active PFC F3, http://www2.seasonic.com/product/ssp-300sfb/) that I got wasn't enough to power 7 drives (5x 7200rpm, 2x5400rpm). The PSU has 1 cable with 1 Molex connector, and 1 cable with 3 SATA connectors. Trial 1: The 1 Molex was splitted into 3 Molex and connected to the hotswap backplane. While 2 SATA connectors were powering the 2 bottom drives. Trial 2: The 1 Molex was used to power 4 drives, while the other 3 drives were powered by SATA connectors. In both trials, I experienced 'power reset' on random drives, usually not long after I press the parity check or sync/rebuild button. I changed the PSU to Seasonic 500W (ATX) and then to Corsair SFX 600W, the problem didn't appear on either of these PSUs, fingers crossed.
  9. Just an update, truly enough, checksum on the whole disk reveals a bunch of mismatch, in addition to XFS filesystem corruption. The checksum was performed after xfs_repair. On the read error issue, after some painstaking troubleshooting involving many different solutions, I finally, I think, pinned down the cause to be inadequate power supply.
  10. I have 6x3TB (5 data) disks array which I want to replace with 4x6TB (yes 3TB gain, but eventually I'll be adding more 6TBs). From duration point of view, I'm pondering between a) 1x1 replacement procedure (redundancy preserved) Requires rebuilding 5x6TB for approx total 5x12 hours = 60hrs vs b) new config from the scratch (redundancy-voided) followed by manual copy of each original drive (using rsync). Requires copying 5x3TB for approx total 5x6 hours = 30hrs. Shorter time and probably benefit from the resulting defrag-ed state?
  11. Pretty satisfied now with 9-11 C cooler temps after I installed the 3000rpm ippc fans.
  12. Not trying to wake up an old thread, but I was inspired by this thread and got a 1x140 (intake) and 1x120(exhaust) of the said noctua ippc 3000rpm, and in general they bring down the temperature of my 6x7200rpm drives by 9-11 degree during parity check, with both fans controlled by Asus motherboard Q-fan thingy (silent mode), so far it spins the fans max at +- 2000rpm, and yeah the noise not ideal but I can live with it for now.
  13. Yeah these cables are brand new (although that doesn't guarantee anything). Actually what happened was that I decided to get a brand new LSI card complete with 2x4SATA breakout cables. And unraid immediately disabled disk3, and upon slotting in new drive and doing rebuild-sync, disk1 throwing those read errors. But not sure if it's cable issue now, because for many hours later until the rebuild finished, no further errors showing up. As for cooling, I'm a bit frustrated with trying to house 6x7200 drives in Lian Li PC-Q25. Short of replacing it with a bigger casing, I'm going to throw last dice in trying a couple of 'jet engine' 3000rpm ippc case fans, as I read from other thread here. I'll see how it goes once they're here.
  14. Hi johnnie.black, After watching the rebuild for a while and seeing there was no further error, I decided to let the rebuild finish. And it did so without any increment of the read errors. So what I have now is the new disk3 that's been rebuilt using the parity and combination read of 4 other drives, 1 drive of which churned out those huge read errors count during the rebuild. I think I'll try to do a checksum comparison or dry-run rsync from the original disk3 (which I believe is still healthy though incorrectly disabled by unRAID).
  15. Hi guys, Looks like I hadn't much luck with my unRAID machines lately. Been having a string of different issues on my 2 builds. Long story short, I'm replacing disk3, out of 6 disks array (1 parity + 5 data drives). Within half an hour of rebuilding, disk1 thrown huge counts of read errors. Screenshot and diagnostics attached. I have preceded this replace/rebuild process with a quick SMART short self test on all drives, all returning 'Complete without error', including on the 7th drive (the original disk3 that I'm replacing, but this is for another topic). Should i cancel this rebuild now, and if so, what's next for me? Letting the rebuild to finish, would still in the end leave room of doubt of data integrity due to those read errors during rebuild. I'm at loss what to do. Thank you!