Fimware issue with TVS-672XT on 4.5.1.1456 build 20201015
-
- Getting the hang of things
- Posts: 60
- Joined: Fri May 29, 2020 5:46 pm
Re: Fimware issue with TVS-672XT on 4.5.1.1456 build 20201015
I had the same problem. My friend from forum.qnap.net.pl is working on this problem, I am his guinea pig - so far he has helped. he is currently working on qkpg, when it's ready - I'll let you know.
-
- Getting the hang of things
- Posts: 60
- Joined: Fri May 29, 2020 5:46 pm
-
- New here
- Posts: 8
- Joined: Sat Dec 01, 2018 2:43 pm
Re: Fimware issue with TVS-672XT on 4.5.1.1456 build 20201015
I was relieved to find this post. I thought I was losin' it a bit.
Running 4.5.1.1461 build 20201020, and wondered about a bunch of problems.
- no CPU load in Resource Center or in the Dashboard
- no Mem usage in RC or the dashboard
- no process list in RC.
- felt sluggish, not what I expected.
I had just upgraded to an i5-9400, so this was not what I expected. Also upgraded it to 32GB of RAM.
From clues in this post, poked around at the CLI and found I had over 200 gpuhal_app's running after only about 10 hours since my last boot.
I went brute-force, moved /etc/init.d/init_gpu.sh and /sbin/gpuhal_app to /, then whacked all the gpuhal's with
# ps -aelf | grep "/sbin/gpuhal_app" | awk '{print $1}' | xargs kill
(Yes, I know I could have used 'cut'. I'm rusty.)
Watched my CPU load fall from 90 to 3.5! Woop! And my HBS backup streams from my other NAS nearly quadrupled in throughput.
Looking forward to gpuhal_app being able to properly probe the new GPU on this 9th gen i5.
Running 4.5.1.1461 build 20201020, and wondered about a bunch of problems.
- no CPU load in Resource Center or in the Dashboard
- no Mem usage in RC or the dashboard
- no process list in RC.
- felt sluggish, not what I expected.
I had just upgraded to an i5-9400, so this was not what I expected. Also upgraded it to 32GB of RAM.
From clues in this post, poked around at the CLI and found I had over 200 gpuhal_app's running after only about 10 hours since my last boot.
I went brute-force, moved /etc/init.d/init_gpu.sh and /sbin/gpuhal_app to /, then whacked all the gpuhal's with
# ps -aelf | grep "/sbin/gpuhal_app" | awk '{print $1}' | xargs kill
(Yes, I know I could have used 'cut'. I'm rusty.)
Watched my CPU load fall from 90 to 3.5! Woop! And my HBS backup streams from my other NAS nearly quadrupled in throughput.
Looking forward to gpuhal_app being able to properly probe the new GPU on this 9th gen i5.
--
TVS-472XT i5-9400, 32GB RAM, mirrored Samsung 970 Evo+ 1TB NVMe M.2 cache, 4x16TB Seagate Exos.
TS-873 32GB ECC RAM, Corsair MX300 1TB M.2 cache, Intel X520-SR2 10GbE optical to MikroTik CRS305, 7x10TB Ironwolves.
TS-431P collecting dust.
TVS-472XT i5-9400, 32GB RAM, mirrored Samsung 970 Evo+ 1TB NVMe M.2 cache, 4x16TB Seagate Exos.
TS-873 32GB ECC RAM, Corsair MX300 1TB M.2 cache, Intel X520-SR2 10GbE optical to MikroTik CRS305, 7x10TB Ironwolves.
TS-431P collecting dust.
- OneCD
- Guru
- Posts: 12147
- Joined: Sun Aug 21, 2016 10:48 am
- Location: "... there, behind that sofa!"
Re: Fimware issue with TVS-672XT on 4.5.1.1456 build 20201015
Code: Select all
killall gpuhal_app
-
- Starting out
- Posts: 34
- Joined: Sun Nov 08, 2009 10:47 am
Re: Fimware issue with TVS-672XT on 4.5.1.1456 build 20201015
Hi OneCD,OneCD wrote: ↑Fri Oct 23, 2020 11:17 am... would also work, and is much faster to type.Code: Select all
killall gpuhal_app
Pls explain a bit, what is the problem when we upgrade the CPU to i9-9900 etc, why is there a need to run: killall gpuhal_app ?
Will it help if we put this... killall gpuhal_app ... in autostart.sh ?
I guess even it will help, by running once, we still need to continue to execute this command: killall gpuhal_app ... periodically? Any ways to go about this
Thanks
From: HalfCD
QNAP TVS-672xt, BIOS version:Q012AT13, EC version: Q016E014
CPU: Intel Core i9-9900. Turbo boost switched to Power saving mode, max. frequency=79% (courtesy of user: ramx2), cooled by stock heat sink.
RAM: G Skill (Intl) 16GB x 2 = 32GB
GPU add-on card: none
HDD storage: Seagate IronWolf 12TB x 4 | 7200 RPM | SATA 6Gb/s (RAID 10, better than RAID5 as no need to wait hours for RAID sync especially when abnormal shutdowns)
SSD storage: 860 EVO 1TB x 2 (RAID 1)
SSD cache (M.2): 970 EVO PLUS NVMe 1TB x 2 (RAID 1)
PSU: Stock
CPU: Intel Core i9-9900. Turbo boost switched to Power saving mode, max. frequency=79% (courtesy of user: ramx2), cooled by stock heat sink.
RAM: G Skill (Intl) 16GB x 2 = 32GB
GPU add-on card: none
HDD storage: Seagate IronWolf 12TB x 4 | 7200 RPM | SATA 6Gb/s (RAID 10, better than RAID5 as no need to wait hours for RAID sync especially when abnormal shutdowns)
SSD storage: 860 EVO 1TB x 2 (RAID 1)
SSD cache (M.2): 970 EVO PLUS NVMe 1TB x 2 (RAID 1)
PSU: Stock
-
- Getting the hang of things
- Posts: 60
- Joined: Fri May 29, 2020 5:46 pm
Re: Fimware issue with TVS-672XT on 4.5.1.1456 build 20201015
don't you better buy a package of fakegpuhal for 2 euro? And have peace of mind?
- rafale
- Easy as a breeze
- Posts: 350
- Joined: Tue May 12, 2015 1:53 pm
Re: Fimware issue with TVS-672XT on 4.5.1.1456 build 20201015
Not meaning to be cheap but... No, I would much prefer knowing what is going on and fix it myself rather than downloading an obscur package. Especially when the problem is caused by some firmware changes one can avoid by not upgrading. This does not give me peace of mind.
Server: TVS-872XT i9 9900 ES, 64GB DDR4 2666MHz, intel X550-T2, Asus RTX3070 Dual OC (On pico PSU), 2x Phison E12 1TB M.2, 4x Micron 5210 7.68TB, 4x WD Purple 4TB
Backup NAS: TS-473 20GB DDR4 2400MHz, Mellanox ConnectX3, 2x Samsung PM871b 256GB M.2, 4x WD Red 8TB
Former units: TVS-1282, TS-871, TS-469
Backup NAS: TS-473 20GB DDR4 2400MHz, Mellanox ConnectX3, 2x Samsung PM871b 256GB M.2, 4x WD Red 8TB
Former units: TVS-1282, TS-871, TS-469
- OneCD
- Guru
- Posts: 12147
- Joined: Sun Aug 21, 2016 10:48 am
- Location: "... there, behind that sofa!"
Re: Fimware issue with TVS-672XT on 4.5.1.1456 build 20201015
Hey @joobeng.
The best person to answer this would be @sadrik, as this is their solution.joobeng wrote: ↑Fri Oct 23, 2020 9:09 pmPls explain a bit, what is the problem when we upgrade the CPU to i9-9900 etc, why is there a need to run: killall gpuhal_app ?OneCD wrote: ↑Fri Oct 23, 2020 11:17 am... would also work, and is much faster to type.Code: Select all
killall gpuhal_app
Will it help if we put this... killall gpuhal_app ... in autostart.sh ?
-
- Starting out
- Posts: 34
- Joined: Sun Nov 08, 2009 10:47 am
Re: Fimware issue with TVS-672XT on 4.5.1.1456 build 20201015
Ok. Not familiar with this. Will probably wait.OneCD wrote: ↑Sat Oct 24, 2020 1:37 am Hey @joobeng.The best person to answer this would be @sadrik, as this is their solution.joobeng wrote: ↑Fri Oct 23, 2020 9:09 pmPls explain a bit, what is the problem when we upgrade the CPU to i9-9900 etc, why is there a need to run: killall gpuhal_app ?OneCD wrote: ↑Fri Oct 23, 2020 11:17 am... would also work, and is much faster to type.Code: Select all
killall gpuhal_app
Will it help if we put this... killall gpuhal_app ... in autostart.sh ?
QNAP TVS-672xt, BIOS version:Q012AT13, EC version: Q016E014
CPU: Intel Core i9-9900. Turbo boost switched to Power saving mode, max. frequency=79% (courtesy of user: ramx2), cooled by stock heat sink.
RAM: G Skill (Intl) 16GB x 2 = 32GB
GPU add-on card: none
HDD storage: Seagate IronWolf 12TB x 4 | 7200 RPM | SATA 6Gb/s (RAID 10, better than RAID5 as no need to wait hours for RAID sync especially when abnormal shutdowns)
SSD storage: 860 EVO 1TB x 2 (RAID 1)
SSD cache (M.2): 970 EVO PLUS NVMe 1TB x 2 (RAID 1)
PSU: Stock
CPU: Intel Core i9-9900. Turbo boost switched to Power saving mode, max. frequency=79% (courtesy of user: ramx2), cooled by stock heat sink.
RAM: G Skill (Intl) 16GB x 2 = 32GB
GPU add-on card: none
HDD storage: Seagate IronWolf 12TB x 4 | 7200 RPM | SATA 6Gb/s (RAID 10, better than RAID5 as no need to wait hours for RAID sync especially when abnormal shutdowns)
SSD storage: 860 EVO 1TB x 2 (RAID 1)
SSD cache (M.2): 970 EVO PLUS NVMe 1TB x 2 (RAID 1)
PSU: Stock
-
- New here
- Posts: 8
- Joined: Sat Dec 01, 2018 2:43 pm
Re: Fimware issue with TVS-672XT on 4.5.1.1456 build 20201015
Sure, except I could not tell which killall command that was; on some OSs, killall is tantamount to a shutdown with extreme prejudice. I wasn't going to trust it!OneCD wrote: ↑Fri Oct 23, 2020 11:17 am... would also work, and is much faster to type.Code: Select all
killall gpuhal_app
--
TVS-472XT i5-9400, 32GB RAM, mirrored Samsung 970 Evo+ 1TB NVMe M.2 cache, 4x16TB Seagate Exos.
TS-873 32GB ECC RAM, Corsair MX300 1TB M.2 cache, Intel X520-SR2 10GbE optical to MikroTik CRS305, 7x10TB Ironwolves.
TS-431P collecting dust.
TVS-472XT i5-9400, 32GB RAM, mirrored Samsung 970 Evo+ 1TB NVMe M.2 cache, 4x16TB Seagate Exos.
TS-873 32GB ECC RAM, Corsair MX300 1TB M.2 cache, Intel X520-SR2 10GbE optical to MikroTik CRS305, 7x10TB Ironwolves.
TS-431P collecting dust.
-
- New here
- Posts: 8
- Joined: Sat Dec 01, 2018 2:43 pm
Re: Fimware issue with TVS-672XT on 4.5.1.1456 build 20201015
I don't know why the current release of the firmware gets hung up on probing the built-in Intel GPU. My system was spawning hundreds of those processes, raising my system load to over 80 (having it down around the number of cores you have is desirable!).OneCD wrote: ↑Sat Oct 24, 2020 1:37 am Hey @joobeng.The best person to answer this would be @sadrik, as this is their solution.joobeng wrote: ↑Fri Oct 23, 2020 9:09 pmPls explain a bit, what is the problem when we upgrade the CPU to i9-9900 etc, why is there a need to run: killall gpuhal_app ?OneCD wrote: ↑Fri Oct 23, 2020 11:17 am... would also work, and is much faster to type.Code: Select all
killall gpuhal_app
Will it help if we put this... killall gpuhal_app ... in autostart.sh ?
You can either downgrade to your old supported CPU and its diminutive core count, or go brute force and slaughter the gpu probe temporarily like I did. Your call.
Yes, my system will not be leveraging its GPU, presumably for transcoding, hybridstation, and whatever else it would like to. But I wanted those cores for virtualisation.
I see a new build has been released. I will look at that tomorrow.
--
TVS-472XT i5-9400, 32GB RAM, mirrored Samsung 970 Evo+ 1TB NVMe M.2 cache, 4x16TB Seagate Exos.
TS-873 32GB ECC RAM, Corsair MX300 1TB M.2 cache, Intel X520-SR2 10GbE optical to MikroTik CRS305, 7x10TB Ironwolves.
TS-431P collecting dust.
TVS-472XT i5-9400, 32GB RAM, mirrored Samsung 970 Evo+ 1TB NVMe M.2 cache, 4x16TB Seagate Exos.
TS-873 32GB ECC RAM, Corsair MX300 1TB M.2 cache, Intel X520-SR2 10GbE optical to MikroTik CRS305, 7x10TB Ironwolves.
TS-431P collecting dust.
- OneCD
- Guru
- Posts: 12147
- Joined: Sun Aug 21, 2016 10:48 am
- Location: "... there, behind that sofa!"
Re: Fimware issue with TVS-672XT on 4.5.1.1456 build 20201015
On which OS does 'killall' behave that way?
-
- New here
- Posts: 8
- Joined: Sat Dec 01, 2018 2:43 pm
Re: Fimware issue with TVS-672XT on 4.5.1.1456 build 20201015
Solaris for one. I’ve see it on a few others over the years too, with unfortunate results. Without man pages on the Qnap, hard to trust what it’ll do!
https://xorl.wordpress.com/2011/10/19/a ... s-killall/
--
TVS-472XT i5-9400, 32GB RAM, mirrored Samsung 970 Evo+ 1TB NVMe M.2 cache, 4x16TB Seagate Exos.
TS-873 32GB ECC RAM, Corsair MX300 1TB M.2 cache, Intel X520-SR2 10GbE optical to MikroTik CRS305, 7x10TB Ironwolves.
TS-431P collecting dust.
TVS-472XT i5-9400, 32GB RAM, mirrored Samsung 970 Evo+ 1TB NVMe M.2 cache, 4x16TB Seagate Exos.
TS-873 32GB ECC RAM, Corsair MX300 1TB M.2 cache, Intel X520-SR2 10GbE optical to MikroTik CRS305, 7x10TB Ironwolves.
TS-431P collecting dust.
- OneCD
- Guru
- Posts: 12147
- Joined: Sun Aug 21, 2016 10:48 am
- Location: "... there, behind that sofa!"
Re: Fimware issue with TVS-672XT on 4.5.1.1456 build 20201015
I'll have to remember that one.
QTS includes QNAP's own compilation of BusyBox utilities, but lately, they've been switching-over to GNU utilities instead. I suspect the devs were tired of being hamstrung by BusyBox.
-
- Know my way around
- Posts: 167
- Joined: Sat Jun 02, 2018 3:56 am
Re: Fimware issue with TVS-672XT on 4.5.1.1456 build 20201015
Well a note, the final firmware 4.5.1.1465 build 20201024 caused my nas to reboot without notice while copying files with qfile from an external drive to the raid array.
I had to downgrade to 4.5.1.1461 build 20201020 which it’s not doing that at all!!
I had to downgrade to 4.5.1.1461 build 20201020 which it’s not doing that at all!!
QNAP TVS-672XT:
CPU: Intel Core I9-9900K, Turbo boost ON and cooled by passive copper heat sink.
RAM: 32GB x 2 Crucial DDR4 2666Mhz
GPU 1: EVGA RTX 3060
HDD: WESTERN DIGITAL Ultrastar® DC HC520 12TB x 6 | 7200 RPM | SATA 6Gb/s | PMR|
SSD: Lexar NVME 500GB for QTS
SSD: Intel Optane 500GB H10 for RAID Cache
PSU: Enhance Flex 600W ENP-7660B
CPU: Intel Core I9-9900K, Turbo boost ON and cooled by passive copper heat sink.
RAM: 32GB x 2 Crucial DDR4 2666Mhz
GPU 1: EVGA RTX 3060
HDD: WESTERN DIGITAL Ultrastar® DC HC520 12TB x 6 | 7200 RPM | SATA 6Gb/s | PMR|
SSD: Lexar NVME 500GB for QTS
SSD: Intel Optane 500GB H10 for RAID Cache
PSU: Enhance Flex 600W ENP-7660B