feins

Members
  • Posts

    137
  • Joined

  • Last visited

Posts posted by feins

  1. On 8/18/2023 at 4:49 PM, Lolight said:

    In many cases manually tweaking BIOS settings might yield significant idle power savings, like enabling the motherboard's power saving mode, enabling all available CPU C-States, disabling unused circuitry and setting PCIE DMI power saving to enabled.

    Lenovo Bios already enable Power saving mode disable any peripheral thats not in used like sound device serial and PS2 port.

    That's why was thinking to get something newer most likely will have better efficiency, since most of the time the server are under idle mode just Radarr and Sonarr are running at the back. Just that donno which one should go for also need to think of RoI as well.

  2. I'd say they have very similar idle efficiency, in general.
    But there are ways to optimize a particular system for maximum savings.
     
    But it's more of a try-n-see endeavor due to the unlimited variety of hardware configurations.
    https://docs.google.com/spreadsheets/d/1LHvT2fRp7I6Hf18LcSzsNnjp10VI-odvwZpQZKv_NCI/edit#gid=0
     
    You might want to check this thread:
     
     

    Thanks for the info.
    I’ve tried powertop before but it screw up the system more than reduce power consumption. So I’ve remove powertop at the end after trying to tweak it but fail to get it stable.


    Sent from my iPhone using Tapatalk
  3. 10 hours ago, Lolight said:

    Depends on your use case.

    If buying new or used only for media streaming (no VMs):

     

    New:

    multiple stream 4K transcoding in Plex, Jellyfin or Emby - the i5 12500 (non-F SKU) selected for its more powerful iGPU.

    direct play or light transcoding - the i3 12100 (non-F)

     

    Used:

    Any Intel Core non-F 10th gen. (same iGPU across the product line).

    I dont mind New or Used.

     

    Basically the most important is for Plex 4K HDR Transcoding with Dolby TrueHD Dolby Atmos.

    Most of the time its been idle or direct play/Stream, the transcode only for mobile device to save data or sometime just dont know why Plex just transcode for no reason.

    As now each month 80% of the electricity bill are from here as can see while the server idling at 100+W as such was thinking a efficiency wat to reduce it is the most important.

    Was thinking of going new which going to spend a few thousand or trying to source something a gen generation back but still give similar result would be fine.

    I only know that the recent gen 13 i5 are very efficient CPU with quite some data floating around that it drawn very min amount of power during idling but i cant find any data regarding the Gen 9 to Gen 12 Processor's actual idle power consumption. As if can get the Gen9 processor that had the same idling power that will save quite a amount as there are alot of used processor and board on line.

     

    image.thumb.png.bc4878bfa6a0757ee22f115ba8f4683d.png

  4. Are you going all new hardware, including the case?
     
    12-13 gen are fully supported.

    I got a Coolermaster Cosmos Storm.
    It’s a pretty old casing but it’s still a very good case.
    Compare to the gen9-13 which processor you would prefer?


    Sent from my iPhone using Tapatalk
  5. I’m thinking of going to upgrade my current build to lower the power consumption.

    At mean time I’m running unraid on my Lenovo Thinkstation P500 with 9 drive in total and 128gb of ddr4 ECC Ram. HBA card, And Xeon E5-2698-V3 processor and P2000 GPU, as now idle with 8drive spin down and nearly 0 CPU activity, GPU idle mode I had a power consumption around 100-130W.

     

    I’ve been searching around on the forum but can’t find the answer that I’m looking for as what’s the latest processor that unraid support so I won’t get the wrong processor as I notice previously someone mention that the 12-13gen Intel cpu are not recommended.

    Can someone recommend some hardware for me to go about.

    Thanks in advance.

     

     

    Sent from my iPhone using Tapatalk

  6. 44 minutes ago, JorgeB said:
    Jul  7 18:22:08 TS-P500 kernel: sd 3:0:0:0: [sdd] tag#5 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=DRIVER_OK cmd_age=0s
    Jul  7 18:22:08 TS-P500 kernel: sd 3:0:0:0: [sdd] tag#5 CDB: opcode=0x28 28 00 00 00 00 00 00 00 20 00
    Jul  7 18:22:08 TS-P500 kernel: I/O error, dev sdd, sector 0 op 0x0:(READ) flags 0x80700 phys_seg 4 prio class 2
    Jul  7 18:22:08 TS-P500 kernel: sd 3:0:0:0: [sdd] tag#6 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=DRIVER_OK cmd_age=0s
    Jul  7 18:22:08 TS-P500 kernel: sd 3:0:0:0: [sdd] tag#6 CDB: opcode=0x28 28 00 00 00 00 00 00 00 08 00
    Jul  7 18:22:08 TS-P500 kernel: I/O error, dev sdd, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
    Jul  7 18:22:08 TS-P500 kernel: Buffer I/O error on dev sdd, logical block 0, async page read

     

    Still issues on a different controller, assuming the cables are also not the same could just be a failing device.

    I just replace the cable with another.

    Attach latest Diagnostic.

    ts-p500-diagnostics-20230707-2307.zip

  7. 58 minutes ago, JorgeB said:
    Jul  7 16:56:54 TS-P500 kernel: ata3.00: exception Emask 0x10 SAct 0xc0000 SErr 0x400101 action 0x6 frozen
    Jul  7 16:56:54 TS-P500 kernel: ata3.00: irq_stat 0x08000000, interface fatal error
    Jul  7 16:56:54 TS-P500 kernel: ata3: SError: { RecovData UnrecovData Handshk }
    Jul  7 16:56:54 TS-P500 kernel: ata3.00: failed command: WRITE FPDMA QUEUED
    Jul  7 16:56:54 TS-P500 kernel: ata3.00: cmd 61/fe:90:92:6d:78/09:00:74:00:00/40 tag 18 ncq dma 1309696 ou
    Jul  7 16:56:54 TS-P500 kernel:         res 40/00:9c:90:77:78/00:00:74:00:00/40 Emask 0x10 (ATA bus error)
    Jul  7 16:56:54 TS-P500 kernel: ata3.00: status: { DRDY }
    Jul  7 16:56:54 TS-P500 kernel: ata3.00: failed command: WRITE FPDMA QUEUED
    Jul  7 16:56:54 TS-P500 kernel: ata3.00: cmd 61/02:98:90:77:78/06:00:74:00:00/40 tag 19 ncq dma 787456 out
    Jul  7 16:56:54 TS-P500 kernel:         res 40/00:9c:90:77:78/00:00:74:00:00/40 Emask 0x10 (ATA bus error)
    Jul  7 16:56:54 TS-P500 kernel: ata3.00: status: { DRDY }
    Jul  7 16:56:54 TS-P500 kernel: ata3: hard resetting link

     

    There's a problem with the device, try new cables or SATA port.

    Ive just Tried relocated the cable and SATA port already. Here are the Check Filesystem Status without -n output.

     

    image.thumb.png.ff281525dcf039143aebf47cc32cdadd.png

  8. I got one of my Drive become Unmountable: Unsupported or no file system after i reallocated it from onboard SATA to PCIE SATA.

    Also i did a gracefully shutdown but after boot up the parity doing resync and i dont dare to force shutdown to check on the Unsupport Drive connection.

    Since i had to wait for 2days for the Parity to complete Sync i've attach the Diagnostic file, hope someone could find out what might be the issue. Unraid was quite robust previously seems like there much fragile since 6.12 update.

  9. 22 hours ago, jasonjulius1122 said:

    If that not works you can also check out this trouble shooting easy steps:

    Check and secure all cables.

    Restart the server.

    Enable Disk 2 if it's disabled.

    Initiate the rebuild process.

    The thing is that since the New 8TB drive was rebuild 3.2% when i try the method above, it don't rebuild but instead it Resync to Parity which much worst since the data in the new 8TB are not valid. Since my old Disk 2 4TB data are still valid what've done is i do a new config. So i could replace the 4TB and wont get a deny that only same size or larger size error and resync the Parity and then replace the new drive and perform a rebuild again.

    I'm not sure is this a good way of doing it. But sofar its seems working and now the rebuild already nearly 50%.

  10. Thanks guys for the update.

    What I've done is after power up the Disk 1 are back online so means previously the issue mostly is the cable. But just donno why the error happen after the rebuild was running after 30min.

    So since my old Disk 2 4TB data are valid. i remove the Disk 2 8TB and then New Config so i could mount back the old Disk 2 4TB

    Enable Maintenance mode and start the server.

    Let it rebuild the parity from the Array.

    After completed the parity sync test all application and date are all okie.

    Then remove the old Disk 2 4TB again and upgrade to the new Disk 2 8TB drive and rebuild the Array again.

     

     

  11. Today i was upgrading one of the Array 4TB HDD to a 8TB.

    Server bootup and add the new 8TB to replace my Disk 2.

    During rebuild Unraid prompt Disk 1 Fail, the rebuild just halt at 3.2%.

    Ive force to shutdown the server try to re secure all power cable and sata cable.

    Boot the server up and Disk 1 are back online.

    Notice that Disk 2 are now list as disable and the rebuild didn't continue.

    What should i do now.

    ts-p500-diagnostics-20230702-2255.zip

  12. 19 hours ago, JorgeB said:
    With all that log spam cannot see anything about why docker is failing, is this a new error? Also look for a BIOS update.


    No new bios update last update was Dec 2021.
    Seems 1st time I’ve encounter this error.
    Still had like 12hr more for the parity to sync.
    I’ve try everything it’s just won’t respond.

     

    This morning I notice that the Parity has completed sync with no error.

    Ive move the appdata, domain and system share back to the Cache and reboot the server and the system are bootup and the docker are up and running.

    Bit i notice something during boot that there is an error from the output as

    rm: missing operand
    Try 'rm --help' for more information.

    mv: cannot stat '/usr/local/bin/mover': No such file or directory

    And the server was pause waiting for quite sometime before proceed.

    Latest diagnostic file attached.
    ts-p500-diagnostics-20230701-1415.zip
    Sent from my iPhone using Tapatalk

  13. Dear All, i need some help.

    Today i was trying to replace my Parity to a larger Drive from 4TB to 8TB.

    I've move all my files and folder from Cache to the Array and everything is completed moved and shutdown the server as normal.

    After i replace the Parity, boot up and assign the new HDD to parity and start the server and i notice the parity is rebuilding.

    I try to enable docker and notice that's an error Docker Fail to Start.

    Also when i open the syslog i notice its full of error Intel PCH root port ACS workaround enabled.

    I was thinking to try to shutdown the server and check if anything loose or a reboot might solve the error but,

    I try to pause the parity rebuild and also try to cancel the rebuild also not responding.

    ts-p500-diagnostics-20230630-1721.zip

    image.thumb.png.b0f568536e11f247bf99389001ddbd4f.png

    image.thumb.png.64b52567a17c9de2857eb2b7852441b5.png

  14. Today i notice there are some Error from my Unraid Log with "segfault" and I'm not sure what is it and how to fix it.

    Could anyone could help me on this?

     

    Jun 26 20:55:44 TS-P500 kernel: device vethbdfdcf4 entered promiscuous mode
    Jun 26 20:55:45 TS-P500 kernel: eth0: renamed from veth6d0393d
    Jun 26 20:55:45 TS-P500 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethbdfdcf4: link becomes ready
    Jun 26 20:55:45 TS-P500 kernel: docker0: port 6(vethbdfdcf4) entered blocking state
    Jun 26 20:55:45 TS-P500 kernel: docker0: port 6(vethbdfdcf4) entered forwarding state
    Jun 26 20:55:45 TS-P500 rc.docker: binhex-radarr: started succesfully!
    Jun 26 20:55:47 TS-P500 rc.docker: Plex-Media-Server: started succesfully!
    Jun 26 20:56:07 TS-P500 kernel: wireguard: WireGuard 1.0.0 loaded. See www.wireguard.com for information.
    Jun 26 20:56:07 TS-P500 kernel: wireguard: Copyright (C) 2015-2019 Jason A. Donenfeld <[email protected]>. All Rights Reserved.
    Jun 26 20:56:30 TS-P500 webGUI: Successful login user root from 10.10.2.182
    Jun 26 20:59:29 TS-P500 kernel: PMS ReqHandler[20860]: segfault at 14732f192eac ip 00001473214d5d81 sp 0000147325d69ec0 error 4 in libnvcuvid.so.535.54.03[1473214bf000+af6000] likely on CPU 4 (core 4, socket 0)
    Jun 26 20:59:29 TS-P500 kernel: Code: 00 00 00 00 00 0f 1f 40 00 41 54 55 49 89 f2 53 48 89 d5 31 c0 48 89 cb b9 21 00 00 00 41 b9 08 01 00 00 48 81 ec 10 01 00 00 <8b> 96 0c 6c 00 00 8b b6 f8 6b 00 00 48 89 e7 49 89 e4 f3 48 ab 4d
    Jun 26 21:05:00 TS-P500 root: Fix Common Problems Version 2023.04.26
    Jun 26 21:39:49 TS-P500 emhttpd: spinning down /dev/sdj
    Jun 26 21:39:49 TS-P500 emhttpd: spinning down /dev/sdh
    Jun 26 21:39:49 TS-P500 emhttpd: spinning down /dev/sdg
    Jun 26 21:39:49 TS-P500 emhttpd: spinning down /dev/sdc
    Jun 26 21:39:49 TS-P500 emhttpd: spinning down /dev/sdi
    Jun 26 21:58:32 TS-P500 emhttpd: read SMART /dev/sdh
    Jun 26 21:59:06 TS-P500 emhttpd: read SMART /dev/sdg
    Jun 26 21:59:15 TS-P500 emhttpd: read SMART /dev/sdi
    Jun 26 22:00:37 TS-P500 emhttpd: read SMART /dev/sdj
    Jun 26 22:00:37 TS-P500 emhttpd: read SMART /dev/sdc
    Jun 26 22:24:28 TS-P500 kernel: Plex Transcoder[31343]: segfault at 28 ip 000014e28424c1c2 sp 00007ffd8dae45f0 error 4 in libavformat.so.59[14e2840cb000+1fe000] likely on CPU 4 (core 4, socket 0)
    Jun 26 22:24:28 TS-P500 kernel: Code: 89 ef e8 f1 a8 07 00 45 31 ed 85 c0 41 0f 94 c5 45 85 e4 74 60 83 bb 80 05 00 00 00 74 57 48 8b ab 70 05 00 00 48 89 6c 24 08 <48> 8b 7d 28 e8 65 a5 07 00 eb 62 48 8b bb 80 00 00 00 8b 93 7c 05
    Jun 26 22:24:30 TS-P500 kernel: Plex Transcoder[31430]: segfault at 28 ip 0000147f0e84c1c2 sp 00007ffc0b213480 error 4 in libavformat.so.59[147f0e6cb000+1fe000] likely on CPU 26 (core 10, socket 0)
    Jun 26 22:24:30 TS-P500 kernel: Code: 89 ef e8 f1 a8 07 00 45 31 ed 85 c0 41 0f 94 c5 45 85 e4 74 60 83 bb 80 05 00 00 00 74 57 48 8b ab 70 05 00 00 48 89 6c 24 08 <48> 8b 7d 28 e8 65 a5 07 00 eb 62 48 8b bb 80 00 00 00 8b 93 7c 05
    Jun 26 22:24:59 TS-P500 kernel: PMS ReqHandler[31973]: segfault at 14b24806ec3c ip 000014b24ab2fd81 sp 000014b2459f8ec0 error 4 in libnvcuvid.so.535.54.03[14b24ab19000+af6000] likely on CPU 20 (core 4, socket 0)
    Jun 26 22:24:59 TS-P500 kernel: Code: 00 00 00 00 00 0f 1f 40 00 41 54 55 49 89 f2 53 48 89 d5 31 c0 48 89 cb b9 21 00 00 00 41 b9 08 01 00 00 48 81 ec 10 01 00 00 <8b> 96 0c 6c 00 00 8b b6 f8 6b 00 00 48 89 e7 49 89 e4 f3 48 ab 4d
    Jun 26 22:31:08 TS-P500 emhttpd: spinning down /dev/sdj
    Jun 26 22:31:08 TS-P500 emhttpd: spinning down /dev/sdh

     

    image.thumb.png.4c3d41e1ccfdca27712a2eae7a33edae.png

    ts-p500-diagnostics-20230627-1245.zip