Farrukh

Members
  • Posts

    6
  • Joined

  • Last visited

Farrukh's Achievements

Noob

Noob (1/14)

0

Reputation

  1. Good job and thanks I will try this out. I believe you are right about the AES-NI requirement but I think we should be good for 2.5. For now they have removed the requirements for it. Here is the article I was reading. https://www.netgate.com/blog/pfsense-2-5-0-development-snapshots-now-available.html
  2. I am using RAW for my pfsense vdisk. After upgrading to 6.8 I thought that my vdisk got corrupted. Happened to me once before hence I suspected the vdisk. I was going through process of elimination to see what will get the vm to get pass the 100% stuck state. This is what I did: Force stop pfsense vm Using cli cd /mnt/user/domain/pfsense/ mv vdisk1.img vdisk1.old (keep RAW based vdisk) touch vdisk1.img (create a file called vdisk. This is not RAW or Qcow2. This is just to get the vm to start) Even though this got me pass the 100% stuck state it doesn't matter since this mean there is no disk drive attached to the vm.
  3. Same issue here. Went from 6.7.2 stable to 6.8. Pfsense vm stuck at 100% during initial boot. Went back to 6.7.2 for now. I do apologise for not having any diagnostics to help the cause. However, I did find something interesting during my troubleshooting. I suspected the issue was with the vdisks. Hence I started playing around with the vdisks and noticed if I create just a dummy file by using <touch vdisk1.img>. I was able to get pass the 100% hang state. Now obviously this won't work since that vdisk1.img is not really a vdisk but this test seems to confirm my suspicion. Oh well 6.9 will probably address it I am hoping.
  4. Hi, I am trying to troubleshoot my server it seems to be hanging after about 30 to 45 days of flawless working. This issue initially started around 2017 September. I have tried various UNRAID updates and replaced hardware such as NIC, SATA Drive and GPU. I have looked at logs and stats during and after the 30 to 45 day before crash and found nothing out of the ordinary. For the most recent kernel panic, I have collected logs using plugin Fix Common Problem and attached the logs with this post. Here are the following things I have done to narrow this fault down: 1) Performed multiple memtest for 24+ hours without errors. 2) Performed xfs filesystem check with -nv (please find the results attached). I think the results are good but I could be wrong. 3) Performed btrfs scrub on my cache pool with no errors. I am not sure at this point what is causing it to hang such unpredictably. Unfortunately I don't have the kernel panic screenshot for this particular instance since I am out of town. However, I have attached a couple from the last 2 failures. The screenshots are from March and May. Unfortunately, I am out of town till August 30th. Hence, I wont have physical access to my server but I will be able to remotely collect and perform most diagnostic tasks. Any help regarding this would be awesome M/B: MSI - Z97 PC Mate(MS-7850) CPU: Intel® Core™ i7-4790 CPU @ 3.60GHz HVM: Enabled IOMMU: Enabled Cache: 256 kB, 1024 kB, 8192 kB Memory: 24 GB (max. installable capacity 32 GB) Network: bond0: IEEE 802.3ad Dynamic link aggregation, mtu 1500 eth0: 1000 Mb/s, full duplex, mtu 1500 eth1: 1000 Mb/s, full duplex, mtu 1500 PARITY: 8TB Seagate DISK1: 4TB Seagate DISK2: 4TB Seagate DISK3: 8TB Seagate DISK4: 4TB Seagate CACHE: 240GB Intel CACHE1: 256GB Samsung pro CACHE2: 256GB Samsung pro Disk1.txt Disk2.txt Disk3.txt Disk4.txt sigma-nas-diagnostics-20180817-0029.zip sigma-nas-diagnostics-20180817-0059.zip sigma-nas-diagnostics-20180817-0129.zip sigma-nas-diagnostics-20180817-0159.zip sigma-nas-diagnostics-20180817-0229.zip
  5. Hi, Can some help me decipher the following Call Trace? I am guessing that this maybe related to memory just from looking at the messages. I have attached the diagnostics.zip file for more system information. Any help would be greatly appreciated. Thank you. Fix Common Problem reported the following Call Trace: Aug 31 16:01:51 Sigma-NAS kernel: DataFileSync: page allocation stalls for 11034ms, order:0, mode:0x24201ca(GFP_HIGHUSER_MOVABLE|__GFP_COLD) Aug 31 16:01:51 Sigma-NAS kernel: CPU: 4 PID: 9141 Comm: DataFileSync Not tainted 4.9.30-unRAID #1 Aug 31 16:01:51 Sigma-NAS kernel: Hardware name: MSI MS-7850, BIOS V4.11 02/16/2016 Aug 31 16:01:51 Sigma-NAS kernel: ffffc9001531fb28 ffffffff813a4a1b 0000000000000001 0000000000000000 Aug 31 16:01:51 Sigma-NAS kernel: ffffc9001531fbb8 ffffffff810cb5b1 024201ca2fdf8b80 ffffffff8193d4e2 Aug 31 16:01:51 Sigma-NAS kernel: ffffc9001531fb50 ffffffff00000010 ffffc9001531fbc8 ffffc9001531fb68 Aug 31 16:01:51 Sigma-NAS kernel: Call Trace: Aug 31 16:01:51 Sigma-NAS kernel: [<ffffffff813a4a1b>] dump_stack+0x61/0x7e Aug 31 16:01:51 Sigma-NAS kernel: [<ffffffff810cb5b1>] warn_alloc+0x102/0x116 Aug 31 16:01:51 Sigma-NAS kernel: [<ffffffff810cbb67>] __alloc_pages_nodemask+0x541/0xc71 Aug 31 16:01:51 Sigma-NAS kernel: [<ffffffff810d0d55>] ? __do_page_cache_readahead+0x1ed/0x21f Aug 31 16:01:51 Sigma-NAS kernel: [<ffffffff81102d82>] alloc_pages_current+0xbe/0xe8 Aug 31 16:01:51 Sigma-NAS kernel: [<ffffffff810c4d78>] __page_cache_alloc+0x89/0x9f Aug 31 16:01:51 Sigma-NAS kernel: [<ffffffff810c6971>] filemap_fault+0x23d/0x458 Aug 31 16:01:51 Sigma-NAS kernel: [<ffffffff810e8f38>] __do_fault+0x68/0xbb Aug 31 16:01:51 Sigma-NAS kernel: [<ffffffff810edf55>] handle_mm_fault+0x6b1/0xf96 Aug 31 16:01:51 Sigma-NAS kernel: [<ffffffff8167c00e>] ? __schedule+0x2b1/0x46a Aug 31 16:01:51 Sigma-NAS kernel: [<ffffffff81091741>] ? hrtimer_try_to_cancel+0x13/0x81 Aug 31 16:01:51 Sigma-NAS kernel: [<ffffffff81042252>] __do_page_fault+0x24a/0x3ed Aug 31 16:01:51 Sigma-NAS kernel: [<ffffffff81042438>] do_page_fault+0x22/0x27 Aug 31 16:01:51 Sigma-NAS kernel: [<ffffffff81680f18>] page_fault+0x28/0x30 Aug 31 16:01:51 Sigma-NAS kernel: Mem-Info: Aug 31 16:01:51 Sigma-NAS kernel: active_anon:817911 inactive_anon:15937 isolated_anon:0 Aug 31 16:01:51 Sigma-NAS kernel: active_file:3861771 inactive_file:1149105 isolated_file:1434 Aug 31 16:01:51 Sigma-NAS kernel: unevictable:0 dirty:1145560 writeback:1378 unstable:0 Aug 31 16:01:51 Sigma-NAS kernel: slab_reclaimable:87654 slab_unreclaimable:92101 Aug 31 16:01:51 Sigma-NAS kernel: mapped:22688 shmem:128230 pagetables:6804 bounce:0 Aug 31 16:01:51 Sigma-NAS kernel: free:58483 free_pcp:0 free_cma:0 Aug 31 16:01:51 Sigma-NAS kernel: Node 0 active_anon:3271644kB inactive_anon:63748kB active_file:15447084kB inactive_file:4596420kB unevictable:0kB isolated(anon):0kB isolated(file):5736kB mapped:90752kB dirty:4582240kB writeback:5512kB shmem:512920kB shmem_thp: 0kB shmem_pmdmapped: 0kB anon_thp: 1693696kB writeback_tmp:0kB unstable:0kB pages_scanned:416 all_unreclaimable? no Aug 31 16:01:51 Sigma-NAS kernel: Node 0 DMA free:15888kB min:84kB low:104kB high:124kB active_anon:0kB inactive_anon:0kB active_file:0kB inactive_file:0kB unevictable:0kB writepending:0kB present:15972kB managed:15888kB mlocked:0kB slab_reclaimable:0kB slab_unreclaimable:0kB kernel_stack:0kB pagetables:0kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB Aug 31 16:01:51 Sigma-NAS kernel: lowmem_reserve[]: 0 3040 23900 23900 Aug 31 16:01:51 Sigma-NAS kernel: Node 0 DMA32 free:100496kB min:17180kB low:21472kB high:25764kB active_anon:210308kB inactive_anon:0kB active_file:2130796kB inactive_file:720496kB unevictable:0kB writepending:716840kB present:3273776kB managed:3263780kB mlocked:0kB slab_reclaimable:66200kB slab_unreclaimable:14352kB kernel_stack:224kB pagetables:408kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB Aug 31 16:01:51 Sigma-NAS kernel: lowmem_reserve[]: 0 0 20860 20860 Aug 31 16:01:51 Sigma-NAS kernel: Node 0 Normal free:117548kB min:117896kB low:147368kB high:176840kB active_anon:3061336kB inactive_anon:63748kB active_file:13316384kB inactive_file:3876656kB unevictable:0kB writepending:3871208kB present:21755904kB managed:21361504kB mlocked:0kB slab_reclaimable:284416kB slab_unreclaimable:354052kB kernel_stack:30608kB pagetables:26808kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB Aug 31 16:01:51 Sigma-NAS kernel: lowmem_reserve[]: 0 0 0 0 Aug 31 16:01:51 Sigma-NAS kernel: Node 0 DMA: 0*4kB 0*8kB 1*16kB (U) 0*32kB 2*64kB (U) 1*128kB (U) 1*256kB (U) 0*512kB 1*1024kB (U) 1*2048kB (U) 3*4096kB (M) = 15888kB Aug 31 16:01:51 Sigma-NAS kernel: Node 0 DMA32: 260*4kB (UME) 423*8kB (UME) 2257*16kB (UME) 97*32kB (UME) 54*64kB (UME) 65*128kB (UME) 64*256kB (UME) 28*512kB (UME) 7*1024kB (M) 2*2048kB (M) 1*4096kB (M) = 101496kB Aug 31 16:01:51 Sigma-NAS kernel: Node 0 Normal: 7426*4kB (UMEH) 4415*8kB (UMEH) 2429*16kB (UMEH) 107*32kB (UMEH) 71*64kB (MH) 31*128kB (H) 11*256kB (H) 0*512kB 0*1024kB 0*2048kB 0*4096kB = 118640kB Aug 31 16:01:51 Sigma-NAS kernel: 5140740 total pagecache pages Aug 31 16:01:51 Sigma-NAS kernel: 0 pages in swap cache Aug 31 16:01:51 Sigma-NAS kernel: Swap cache stats: add 0, delete 0, find 0/0 Aug 31 16:01:51 Sigma-NAS kernel: Free swap = 0kB Aug 31 16:01:51 Sigma-NAS kernel: Total swap = 0kB Aug 31 16:01:51 Sigma-NAS kernel: 6261413 pages RAM Aug 31 16:01:51 Sigma-NAS kernel: 0 pages HighMem/MovableOnly Aug 31 16:01:51 Sigma-NAS kernel: 101120 pages reserved sigma-nas-diagnostics-20170904-1326.zip