mayhem2408

According to MSIs website, BIOS V19 and higher support the Ryzen 9 3900x. I am running the latest V1D. I have not tried another OS but will see what I can do. This PC has no DVD drive so OS from USB only. I'll try Ubuntu Live tonight.

I have just upgraded my unraid server to an AMD Ryzen 9 3900x. The problem I am having is that I power up the PC, unraid starts to load and within seconds I get a black screen and the hardware resets and starts all over again. This is an endless loop. Prior to this I was running an AMD Ryzen 7 2700 on the same motherboard and it was working fine. The motherboard is an MSI B450 Gaming Plus motherboard and has the latest 7B86v1D Bios that supports the 3000 series CPUs If I remove the Ryzen 9 3900x and reinstall the Ryzen 7 2700, unraid boots just fine. Below is a link to the video of the bootup process, at attached is a still screenshot of the last thing I see before the hardware resets. https://youtu.be/Fr7Bm8Ijzao Has anyone had seen this before and know of a possible cause. Do I have a faulty CPU, or maybe the motherboard, although up to date, doesn't support the CPU correctly.

I tried running "xfs_fsr -t 18000" without specifying a /dev/md? so that it would start an automatic defrag of all xfs drives for 5 hours. I noticed it started defraging /mnt/disk1 instead of /dev/md1. Is it safe to let it continue on /mnt/disk1 ? I've noticed that if I specify /dev/md1 in the command line, it ignores the -t command (Which is normal apparently)

Thanks for the guide. I have been having a lot of buffering problems with some of my movies of late. So I decided to check fragmentation. OMG. I was told that Linux file systems don't suffer from fragmentation like NTFS. They can't be more wrong. One of my drives is 99.87% fragmentation. That is the worst fragmentation I have ever seen, on any system. This was is a 2TB drive with 350GB free. Can anyone explain why the fragmentation is so bad? 2TB HDD, 350GB Free, 99.86% Fragmentation root@Tower:~# xfs_db -r /dev/md6 xfs_db> frag actual 462546, ideal 636, fragmentation factor 99.86% Note, this number is largely meaningless. Files on this filesystem average 727.27 extents per file xfs_db> frag -d actual 27, ideal 26, fragmentation factor 3.70% Note, this number is largely meaningless. Files on this filesystem average 1.04 extents per file xfs_db> frag -f actual 462519, ideal 610, fragmentation factor 99.87% Note, this number is largely meaningless. Files on this filesystem average 758.23 extents per file xfs_db> 2TB HDD, 320GB Free, 99.33% Fragmentation root@Tower:~# xfs_db -r /dev/md5 xfs_db> frag actual 2299335, ideal 15320, fragmentation factor 99.33% Note, this number is largely meaningless. Files on this filesystem average 150.09 extents per file xfs_db> frag -d actual 522, ideal 460, fragmentation factor 11.88% Note, this number is largely meaningless. Files on this filesystem average 1.13 extents per file xfs_db> frag -f actual 2298813, ideal 14860, fragmentation factor 99.35% Note, this number is largely meaningless. Files on this filesystem average 154.70 extents per file xfs_db> 6TB HDD, 600GB Free, 95.48% Fragmentation root@Tower:~# xfs_db -r /dev/md4 xfs_db> frag actual 15899, ideal 718, fragmentation factor 95.48% Note, this number is largely meaningless. Files on this filesystem average 22.14 extents per file xfs_db> frag -d actual 33, ideal 28, fragmentation factor 15.15% Note, this number is largely meaningless. Files on this filesystem average 1.18 extents per file xfs_db> frag -f actual 15866, ideal 690, fragmentation factor 95.65% Note, this number is largely meaningless. Files on this filesystem average 22.99 extents per file xfs_db> 6TB HDD, 400GB Free, 98.56% Fragmentation root@Tower:~# xfs_db -r /dev/md3 xfs_db> frag actual 500672, ideal 7220, fragmentation factor 98.56% Note, this number is largely meaningless. Files on this filesystem average 69.35 extents per file xfs_db> frag -d actual 391, ideal 370, fragmentation factor 5.37% Note, this number is largely meaningless. Files on this filesystem average 1.06 extents per file xfs_db> frag -f actual 500281, ideal 6850, fragmentation factor 98.63% Note, this number is largely meaningless. Files on this filesystem average 73.03 extents per file xfs_db> 2TB HDD, 350GB Free, 76.99% Fragmentation root@Tower:~# xfs_db -r /dev/md2 xfs_db> frag actual 153132, ideal 35233, fragmentation factor 76.99% Note, this number is largely meaningless. Files on this filesystem average 4.35 extents per file xfs_db> frag -d actual 1374, ideal 1354, fragmentation factor 1.46% Note, this number is largely meaningless. Files on this filesystem average 1.01 extents per file xfs_db> frag -f actual 151758, ideal 33879, fragmentation factor 77.68% Note, this number is largely meaningless. Files on this filesystem average 4.48 extents per file xfs_db> 6TB HDD, 1.1TB Free, 36.5% Fragmentation (Contains all my AppData, dockers, ect and some Movies) root@Tower:~# xfs_db -r /dev/md1 xfs_db> frag actual 2846177, ideal 1807222, fragmentation factor 36.50% Note, this number is largely meaningless. Files on this filesystem average 1.57 extents per file xfs_db> frag -d actual 53083, ideal 40568, fragmentation factor 23.58% Note, this number is largely meaningless. Files on this filesystem average 1.31 extents per file xfs_db> frag -f actual 2793094, ideal 1766654, fragmentation factor 36.75% Note, this number is largely meaningless. Files on this filesystem average 1.58 extents per file xfs_db> 2TB HDD, 600GB Free, 3.96% Fragmentation (This is the newest drive on the server) root@Tower:~# xfs_db -r /dev/md7 xfs_db> frag actual 2954, ideal 2837, fragmentation factor 3.96% Note, this number is largely meaningless. Files on this filesystem average 1.04 extents per file xfs_db> frag -d actual 122, ideal 109, fragmentation factor 10.66% Note, this number is largely meaningless. Files on this filesystem average 1.12 extents per file xfs_db> frag -f actual 2832, ideal 2728, fragmentation factor 3.67% Note, this number is largely meaningless. Files on this filesystem average 1.04 extents per file xfs_db>

OK. Got mine working fine on unraid. Had to make a few other changes. 1/ Edit file /opt/lampp/lampp Line 197 will read "if testport 80" Change it to what ever port you want. I changed mine to "if testport 888" 2a/ Edit file /opt/lampp/etc/httpd.conf Line 52 will read "Listen 80" Change it to the same port you used in the lampp file. I changed mine to "Listen 888" 2b/ Same file, go to line 205 Line 205 will read "ServerName localhost" Add the port at the end. I changed mine to "ServerName localhost:888" From here you will be able to start the apache server using the "./lampp start" command However you will not be able to configure the MySQL server using the myphpadmin page as you get an access denied error So you need to change the following. 3/ Edit file /opt/lampp/etc/extra/httpd-xampp.conf Line 14-19 will read # since XAMPP 1.4.3 <Directory "/opt/lampp/phpmyadmin"> AllowOverride AuthConfig Limit Order allow,deny Allow from all </Directory> Change it to # since XAMPP 1.4.3 <Directory "/opt/lampp/phpmyadmin"> AllowOverride AuthConfig Limit Order allow,deny Allow from all Require all granted # ADDED LINE </Directory> So far it is all working for me. Let me know how you go.

UPDATE: V1.6.7-4 - 2013-02-13 - More fixes to the config screen

UPDATE: 2013-02-05 1.6.7-2jr - Added cache_pressure to the config screen

That should be easy, I'll work on it today and post an update

Thanks speeding_ant and BRiT Based on that info, a 64bit only version would be fine. The 32bit version would only be useful for older CPU configs. But I'm guessing more and more people are wanting to install more and more plugins and the older CPU configs are a dying bread. Otherwise there would be no question of even needing a 64bit version as unRAID by itself doesn't come close to hitting the limits of 32bit. Although to be honest, My Work PC is only 32bit Windows 7 Pro (Company requirement/restriction). My development PC for unRAID in running in a VM and is limited to 32bit Guest because of the 32bit Host. This would mean no unRAID testing during my down time in the office. Not a deal breaker though.

Would I be correct in saying that a 64bit version will require 64bit library's. My limited understanding of the Linux kernel is that 32bit apps and librarys will not run on a 64bit kernel. Unlike Windows which can run 32bit apps in the 64bit OS. Is this correct. If it is correct, I will need 32bit for quiet some time to come.

Update: Plugin has been updated to include cache_dirs V1.6.7

I am trying to update some files on the USB boot drive, but every file is coming up as a read-only system file. If I try to delete from midnight commander, it throws up a "Cannot delete file "......." Read-only file system (30). If I try to delete from the windows share, the file disappears, but when I refresh the file reappears. This happens with every file I have tried. I also wanted to replace the bzimage and bzroot files with the RC10 version, but I can't overwrite them because of a Destination Folder Access Denied error in windows. Does anyone have any clues as to what has gone wrong.

Released V0.7 of the plugin. Link is in the first post

Released V0.6 of the plugin.

Please see the first post for a link to the updated version to fix the problem