gamer1pc
-
Posts
20 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by gamer1pc
-
-
This is the error: "Your server has run out of memory, and processes (potentially required) are being killed off. You should post your diagnostics and ask for assistance on the Unraid forums"
I have included my diagnostics as well. If anyone could please let me know if my server is fine, it seems to be fine on RAM as well with only ~37% usage.
-
21 minutes ago, JorgeB said:
Run a scrub on the pool, check that all errors are corrected, after that delete and re-create the docker image.
I ran a scrub and came out with no errors found, should I checkmark "repair corrupted blocks"?
-
I've also added these parameters to my flash configuration: nvme_core.default_ps_max_latency_us=0 pcie_aspm=off
After reading around the forums and for some it fixed it but it hasn't for mine. I've attached and image of the errors and diagnostics as well. Any help is appreciated as I seem to not be able to find a solution around.
-
@brimnac Thanks for the reply I'll give it a try
-
Anyone know how I can add this to the config/command line c=LTC,mc=FIRO. I need it in order for the pool to convert my FIRO to LTC. Thanks in advanced for the help
-
I was able to restore everything back to normal on wednesday and everything was fine on Thursday, but this Friday afternoon. Parity got disabled and other disks were put to grey status as the picture shows. I couldn't stop the array since it was stuck so I had to do a hard shutdown. Could it be just a coincidence and had bad luck or does the diagnostics show the same thing again?
-
Well thinking I was fine, I had to stop the array and the other cache became corrupted as well as I started it up again. I have a question regarding the recovery options you linked. Do these have to be performed while the array is started in normal mode, maintenance mode or not have the array started? Thanks in advanced
-
Yeah the second Cache 2 disk was a mirror of Cache disk so I just swap them. Thank you once again for explaining what happened
-
Hi, I upgraded the OS to 6.9rc2 after the data rebuild. Then rebooted and started the array, and now the Cache disks are showing as "Unmountable: No file system", I have attached the diagnostics and a picture. Should I reboot again and see if they get mounted this time?
-
I'm going to update to 6.9 to see if it resolves these problems then. Just need to wait for the parity data rebuild to finish. Thanks for the advice
-
My parity disk became disabled and I started a parity check, but stopped it as I realized there's no point to it. I have a feeling it might be the sata cables or the sata controller on the motherboard as it happened to disk1 a day before and unraid hangs on "stopping array" for hours when I wanted to shutdown to inspect disk1. Which forced me to force shutdown the server. I have posted the diagnostics file before restarting. I really appreciate anyone who helps me figure this out.
-
(SOLVED) I was able to test out the USB in the slots on the back instead of infront of the case and it worked. So my guess is that the driver wasn't loading for the USB controller on the front panel.
-
It's a USB 3.0 stick and I've tried booting from either the USB 2.0 port and USB 3.0 port. I also made sure it's booting into legacy mode so it won't go into UEFI. I tried the command and only showed tmpfs. So I believe it should at least show disk 1, but like you said earlier it doesn't seem to mount it. It's really strange behavior.
-
I tried it again and same thing, and like how it mentioned earlier that the USB does work on my other computer, I was even able to make the zip file and it saved on the flash drive. Could a setting on the BIOS be breaking it?
-
First thing to check - are you sure that the USB stick is formatted as FAT32. If it is not the GUI will not come up.
In terms of getting help it is much more useful if you post the full diagnostics ZIP file which contains much more than the syslog. From a putty session you can get this by using the 'diagnostics' command which will put it into the 'logs' folder on the USB stick (i.e. /boot/logs from putty.
Here is what it looks like, I believe more stuff should be showing up besides just the config folder http://i.imgur.com/k5XgqGU.png
-
I would also like to add that my /boot doesn't show what I have in my usb which is the img file and those txt files, so for some reason it only shows the config folder
-
Yeah it's formatted as FAT32, and I did that but it doesn't seem to save. How do I make it so it saves to the flash drive instead of on the RAM?
-
(SOLVED) I was able to test out the USB in the slots on the back instead of infront of the case and it worked. So my guess is that the driver wasn't loading for the USB controller on the front panel.
So I have UnRAID 6.1.9 on a 32GB USB. It boots up fine but when I try to access the server by either the IP or domain name it won't let me get in, but I can use Putty to access it for some reason. I'll put the syslog below, I had to delete some text because of the 20000 character limit, so I chose what I thought was important, if it doesn't have what you need to find out, I uploaded it to paste bin here: http://pastebin.com/3W9EVKHq. One thing I want to mention is that when I tried to boot from another computer it booted up fine and was able to access the Web GUI, but when it boots in my server I can't access the Web GUI.
Mar 8 16:10:06 Tower kernel: NET: Registered protocol family 2 Mar 8 16:10:06 Tower kernel: TCP established hash table entries: 131072 (order: 8, 1048576 bytes) Mar 8 16:10:06 Tower kernel: TCP bind hash table entries: 65536 (order: 8, 1048576 bytes) Mar 8 16:10:06 Tower kernel: TCP: Hash tables configured (established 131072 bind 65536) Mar 8 16:10:06 Tower kernel: UDP hash table entries: 8192 (order: 6, 262144 bytes) Mar 8 16:10:06 Tower kernel: UDP-Lite hash table entries: 8192 (order: 6, 262144 bytes) Mar 8 16:10:06 Tower kernel: NET: Registered protocol family 1 Mar 8 16:10:06 Tower kernel: RPC: Registered named UNIX socket transport module. Mar 8 16:10:06 Tower kernel: RPC: Registered udp transport module. Mar 8 16:10:06 Tower kernel: RPC: Registered tcp transport module. Mar 8 16:10:06 Tower kernel: RPC: Registered tcp NFSv4.1 backchannel transport module. Mar 8 16:10:06 Tower kernel: Netfilter messages via NETLINK v0.30. Mar 8 16:10:06 Tower kernel: nfnl_acct: registering with nfnetlink. Mar 8 16:10:06 Tower kernel: nf_conntrack version 0.5.0 (65536 buckets, 262144 max) Mar 8 16:10:06 Tower kernel: nf_tables: (c) 2007-2009 Patrick McHardy <[email protected]> Mar 8 16:10:06 Tower kernel: nf_tables_compat: (c) 2012 Pablo Neira Ayuso <[email protected]> Mar 8 16:10:06 Tower kernel: xt_time: kernel timezone is -0000 Mar 8 16:10:06 Tower kernel: ipip: IPv4 over IPv4 tunneling driver Mar 8 16:10:06 Tower kernel: gre: GRE over IPv4 demultiplexor driver Mar 8 16:10:06 Tower kernel: ip_gre: GRE over IPv4 tunneling driver Mar 8 16:10:06 Tower kernel: IPv4 over IPsec tunneling driver Mar 8 16:10:06 Tower kernel: NET: Registered protocol family 17 Mar 8 16:10:06 Tower kernel: bridge: automatic filtering via arp/ip/ip6tables has been deprecated. Update your scripts to load br_netfilter if you need this. Mar 8 16:10:06 Tower kernel: Bridge firewalling registered Mar 8 16:10:06 Tower kernel: 9pnet: Installing 9P2000 support Mar 8 16:10:06 Tower kernel: Key type dns_resolver registered Mar 8 16:10:06 Tower kernel: registered taskstats version 1 Mar 8 16:10:06 Tower kernel: Btrfs loaded Mar 8 16:10:06 Tower kernel: rtc_cmos 00:04: setting system clock to 2016-03-09 00:09:31 UTC (1457482171) Mar 8 16:10:06 Tower kernel: Freeing unused kernel memory: 916K (ffffffff8188f000 - ffffffff81974000) Mar 8 16:10:06 Tower kernel: acpi-cpufreq: overriding BIOS provided _PSD data Mar 8 16:10:06 Tower kernel: ahci 0000:00:11.0: version 3.0 Mar 8 16:10:06 Tower kernel: r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded Mar 8 16:10:06 Tower kernel: r8169 0000:03:00.0: can't disable ASPM; OS doesn't have ASPM control Mar 8 16:10:06 Tower kernel: ahci 0000:00:11.0: AHCI 0001.0200 32 slots 4 ports 6 Gbps 0xf impl SATA mode Mar 8 16:10:06 Tower kernel: ahci 0000:00:11.0: flags: 64bit ncq sntf ilck pm led clo pmp pio slum part Mar 8 16:10:06 Tower kernel: scsi host0: ahci Mar 8 16:10:06 Tower kernel: r8169 0000:03:00.0 eth0: RTL8168evl/8111evl at 0xffffc90001c0e000, 74:d4:35:58:b3:5b, XID 0c900880 IRQ 29 Mar 8 16:10:06 Tower kernel: r8169 0000:03:00.0 eth0: jumbo features [frames: 9200 bytes, tx checksumming: ko] Mar 8 16:10:06 Tower kernel: scsi host1: ahci Mar 8 16:10:06 Tower kernel: scsi host2: ahci Mar 8 16:10:06 Tower kernel: scsi host3: ahci Mar 8 16:10:06 Tower kernel: ata1: SATA max UDMA/133 abar m1024@0xfeb0b000 port 0xfeb0b100 irq 19 Mar 8 16:10:06 Tower kernel: ata2: SATA max UDMA/133 abar m1024@0xfeb0b000 port 0xfeb0b180 irq 19 Mar 8 16:10:06 Tower kernel: ata3: SATA max UDMA/133 abar m1024@0xfeb0b000 port 0xfeb0b200 irq 19 Mar 8 16:10:06 Tower kernel: ata4: SATA max UDMA/133 abar m1024@0xfeb0b000 port 0xfeb0b280 irq 19 Mar 8 16:10:06 Tower kernel: piix4_smbus 0000:00:14.0: SMBus Host Controller at 0xb00, revision 0 Mar 8 16:10:06 Tower kernel: piix4_smbus 0000:00:14.0: Auxiliary SMBus Host Controller at 0xb20 Mar 8 16:10:06 Tower kernel: scsi host4: pata_atiixp Mar 8 16:10:06 Tower kernel: scsi host5: pata_atiixp Mar 8 16:10:06 Tower kernel: ata5: PATA max UDMA/100 cmd 0x1f0 ctl 0x3f6 bmdma 0xf000 irq 14 Mar 8 16:10:06 Tower kernel: ata6: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma 0xf008 irq 15 Mar 8 16:10:06 Tower kernel: ata5.00: ATA-9: ADATA SP550, 2F5220007125, O0803B5a, max UDMA/133 Mar 8 16:10:06 Tower kernel: ata5.00: 937703088 sectors, multi 2: LBA48 NCQ (depth 0/32) Mar 8 16:10:06 Tower kernel: ata5.00: limited to UDMA/33 due to 40-wire cable Mar 8 16:10:06 Tower kernel: ata5.00: configured for UDMA/33 Mar 8 16:10:06 Tower kernel: ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Mar 8 16:10:06 Tower kernel: ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Mar 8 16:10:06 Tower kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Mar 8 16:10:06 Tower kernel: ata4: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Mar 8 16:10:06 Tower kernel: ata2.00: ATA-8: HGST HDN724040ALE640, PK1334PEHPA1ZS, MJAOA5E0, max UDMA/133 Mar 8 16:10:06 Tower kernel: ata2.00: 7814037168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA Mar 8 16:10:06 Tower kernel: ata3.00: ATA-8: HGST HDN724040ALE640, PK1334PEHNHT3S, MJAOA5E0, max UDMA/133 Mar 8 16:10:06 Tower kernel: ata3.00: 7814037168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA Mar 8 16:10:06 Tower kernel: ata4.00: ATA-9: ADATA SP550, 2F5220006843, O0803B5a, max UDMA/133 Mar 8 16:10:06 Tower kernel: ata4.00: 937703088 sectors, multi 2: LBA48 NCQ (depth 31/32), AA Mar 8 16:10:06 Tower kernel: ata1.00: ATA-8: HGST HDN724040ALE640, PK1334PEHPD7JS, MJAOA5E0, max UDMA/133 Mar 8 16:10:06 Tower kernel: ata1.00: 7814037168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA Mar 8 16:10:06 Tower kernel: ata4.00: configured for UDMA/133 Mar 8 16:10:06 Tower kernel: ata3.00: configured for UDMA/133 Mar 8 16:10:06 Tower kernel: ata2.00: configured for UDMA/133 Mar 8 16:10:06 Tower kernel: ata1.00: configured for UDMA/133 Mar 8 16:10:06 Tower kernel: scsi 0:0:0:0: Direct-Access ATA HGST HDN724040AL A5E0 PQ: 0 ANSI: 5 Mar 8 16:10:06 Tower kernel: sd 0:0:0:0: [sda] 7814037168 512-byte logical blocks: (4.00 TB/3.64 TiB) Mar 8 16:10:06 Tower kernel: sd 0:0:0:0: Attached scsi generic sg0 type 0 Mar 8 16:10:06 Tower kernel: sd 0:0:0:0: [sda] 4096-byte physical blocks Mar 8 16:10:06 Tower kernel: scsi 1:0:0:0: Direct-Access ATA HGST HDN724040AL A5E0 PQ: 0 ANSI: 5 Mar 8 16:10:06 Tower kernel: sd 0:0:0:0: [sda] Write Protect is off Mar 8 16:10:06 Tower kernel: sd 1:0:0:0: [sdb] 7814037168 512-byte logical blocks: (4.00 TB/3.64 TiB) Mar 8 16:10:06 Tower kernel: sd 1:0:0:0: [sdb] 4096-byte physical blocks Mar 8 16:10:06 Tower kernel: sd 1:0:0:0: Attached scsi generic sg1 type 0 Mar 8 16:10:06 Tower kernel: sd 1:0:0:0: [sdb] Write Protect is off Mar 8 16:10:06 Tower kernel: sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00 Mar 8 16:10:06 Tower kernel: sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Mar 8 16:10:06 Tower kernel: scsi 2:0:0:0: Direct-Access ATA HGST HDN724040AL A5E0 PQ: 0 ANSI: 5 Mar 8 16:10:06 Tower kernel: sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 Mar 8 16:10:06 Tower kernel: sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Mar 8 16:10:06 Tower kernel: sd 2:0:0:0: [sdc] 7814037168 512-byte logical blocks: (4.00 TB/3.64 TiB) Mar 8 16:10:06 Tower kernel: sd 2:0:0:0: [sdc] 4096-byte physical blocks Mar 8 16:10:06 Tower kernel: sd 2:0:0:0: Attached scsi generic sg2 type 0 Mar 8 16:10:06 Tower kernel: sd 2:0:0:0: [sdc] Write Protect is off Mar 8 16:10:06 Tower kernel: sd 2:0:0:0: [sdc] Mode Sense: 00 3a 00 00 Mar 8 16:10:06 Tower kernel: sd 2:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Mar 8 16:10:06 Tower kernel: scsi 3:0:0:0: Direct-Access ATA ADATA SP550 3B5a PQ: 0 ANSI: 5 Mar 8 16:10:06 Tower kernel: sd 3:0:0:0: [sdd] 937703088 512-byte logical blocks: (480 GB/447 GiB) Mar 8 16:10:06 Tower kernel: sd 3:0:0:0: Attached scsi generic sg3 type 0 Mar 8 16:10:06 Tower kernel: sd 3:0:0:0: [sdd] Write Protect is off Mar 8 16:10:06 Tower kernel: sd 3:0:0:0: [sdd] Mode Sense: 00 3a 00 00 Mar 8 16:10:06 Tower kernel: sd 3:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Mar 8 16:10:06 Tower kernel: scsi 4:0:0:0: Direct-Access ATA ADATA SP550 3B5a PQ: 0 ANSI: 5 Mar 8 16:10:06 Tower kernel: sd 4:0:0:0: [sde] 937703088 512-byte logical blocks: (480 GB/447 GiB) Mar 8 16:10:06 Tower kernel: sd 4:0:0:0: Attached scsi generic sg4 type 0 Mar 8 16:10:06 Tower kernel: sd 4:0:0:0: [sde] Write Protect is off Mar 8 16:10:06 Tower kernel: sd 4:0:0:0: [sde] Mode Sense: 00 3a 00 00 Mar 8 16:10:06 Tower kernel: sd 4:0:0:0: [sde] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Mar 8 16:10:06 Tower kernel: sd 3:0:0:0: [sdd] Attached SCSI disk Mar 8 16:10:06 Tower kernel: sd 4:0:0:0: [sde] Attached SCSI disk Mar 8 16:10:06 Tower kernel: sd 1:0:0:0: [sdb] Attached SCSI disk Mar 8 16:10:06 Tower kernel: sd 2:0:0:0: [sdc] Attached SCSI disk Mar 8 16:10:06 Tower kernel: sd 0:0:0:0: [sda] Attached SCSI disk Mar 8 16:10:06 Tower kernel: random: dd urandom read with 126 bits of entropy available Mar 8 16:10:06 Tower kernel: random: nonblocking pool is initialized Mar 8 16:10:09 Tower logger: /etc/rc.d/rc.inet1: List of interfaces: 'eth0' Mar 8 16:10:09 Tower logger: /etc/rc.d/rc.inet1: /sbin/ifconfig lo 127.0.0.1 Mar 8 16:10:09 Tower logger: /etc/rc.d/rc.inet1: /sbin/route add -net 127.0.0.0 netmask 255.0.0.0 lo Mar 8 16:10:09 Tower logger: /etc/rc.d/rc.inet1: /usr/bin/timeout 60 /sbin/dhcpcd -w -t 10 -h Tower -d -L eth0 Mar 8 16:10:09 Tower dhcpcd[1346]: dhcpcd-6.8.1 starting Mar 8 16:10:09 Tower dhcpcd[1346]: eth0: executing `/lib/dhcpcd/dhcpcd-run-hooks' PREINIT Mar 8 16:10:09 Tower dhcpcd[1346]: eth0: executing `/lib/dhcpcd/dhcpcd-run-hooks' NOCARRIER Mar 8 16:10:09 Tower dhcpcd[1346]: eth0: waiting for carrier Mar 8 16:10:09 Tower kernel: r8169 0000:03:00.0 eth0: link down Mar 8 16:10:09 Tower kernel: r8169 0000:03:00.0 eth0: link down Mar 8 16:10:12 Tower dhcpcd[1346]: eth0: carrier acquired Mar 8 16:10:12 Tower kernel: r8169 0000:03:00.0 eth0: link up Mar 8 16:10:12 Tower dhcpcd[1346]: eth0: executing `/lib/dhcpcd/dhcpcd-run-hooks' CARRIER Mar 8 16:10:12 Tower dhcpcd[1346]: eth0: delaying IPv4 for 0.7 seconds Mar 8 16:10:13 Tower dhcpcd[1346]: eth0: using ClientID 01:74:d4:35:58:b3:5b Mar 8 16:10:13 Tower dhcpcd[1346]: eth0: soliciting a DHCP lease Mar 8 16:10:13 Tower dhcpcd[1346]: eth0: sending DISCOVER (xid 0x5494da0d), next in 3.7 seconds Mar 8 16:10:13 Tower dhcpcd[1346]: eth0: offered 192.168.1.6 from 192.168.1.1 Mar 8 16:10:13 Tower dhcpcd[1346]: eth0: sending REQUEST (xid 0x5494da0d), next in 3.3 seconds Mar 8 16:10:13 Tower dhcpcd[1346]: eth0: acknowledged 192.168.1.6 from 192.168.1.1 Mar 8 16:10:13 Tower dhcpcd[1346]: eth0: probing for 192.168.1.6 Mar 8 16:10:13 Tower dhcpcd[1346]: eth0: ARP probing 192.168.1.6 (1 of 3), next in 1.8 seconds Mar 8 16:10:15 Tower dhcpcd[1346]: eth0: ARP probing 192.168.1.6 (2 of 3), next in 1.7 seconds Mar 8 16:10:17 Tower dhcpcd[1346]: eth0: ARP probing 192.168.1.6 (3 of 3), next in 2.0 seconds Mar 8 16:10:19 Tower dhcpcd[1346]: eth0: leased 192.168.1.6 for 86400 seconds Mar 8 16:10:19 Tower dhcpcd[1346]: eth0: renew in 43200 seconds, rebind in 75600 seconds Mar 8 16:10:19 Tower dhcpcd[1346]: eth0: writing lease `/var/lib/dhcpcd/dhcpcd-eth0.lease' Mar 8 16:10:19 Tower dhcpcd[1346]: eth0: adding IP address 192.168.1.6/24 Mar 8 16:10:19 Tower dhcpcd[1346]: eth0: adding route to 192.168.1.0/24 Mar 8 16:10:19 Tower dhcpcd[1346]: eth0: adding default route via 192.168.1.1 Mar 8 16:10:19 Tower dhcpcd[1346]: eth0: executing `/lib/dhcpcd/dhcpcd-run-hooks' BOUND Mar 8 16:10:19 Tower dhcpcd[1346]: forking to background Mar 8 16:10:19 Tower dhcpcd[1346]: forked to background, child pid 1384 Mar 8 16:10:19 Tower dhcpcd[1384]: eth0: ARP announcing 192.168.1.6 (1 of 2), next in 2.0 seconds Mar 8 16:10:19 Tower rpc.statd[1398]: Version 1.2.8 starting Mar 8 16:10:19 Tower sm-notify[1399]: Version 1.2.8 starting Mar 8 16:10:19 Tower rpc.statd[1398]: Failed to read /var/lib/nfs/state: Success Mar 8 16:10:19 Tower rpc.statd[1398]: Initializing NSM state Mar 8 16:10:19 Tower sshd[1418]: Server listening on 0.0.0.0 port 22. Mar 8 16:10:19 Tower acpid: cannot open input layer Mar 8 16:10:19 Tower acpid: starting up with netlink and the input layer Mar 8 16:10:19 Tower acpid: 1 rule loaded Mar 8 16:10:19 Tower acpid: waiting for events: event logging is off Mar 8 16:10:19 Tower crond[1443]: /usr/sbin/crond 4.5 dillon's cron daemon, started with loglevel notice Mar 8 16:10:21 Tower dhcpcd[1384]: eth0: ARP announcing 192.168.1.6 (2 of 2) Mar 8 16:12:54 Tower sshd[1786]: Accepted none for root from 192.168.1.2 port 52621 ssh2
-
Like the title says, is it suppose to appear some where else besides under USB for devices?
Got this error, but everything seems fine. Not sure if it's okay to continue.
in General Support
Posted
Thank you so much for your reply, I really appreciate it. I will take a look at this plugin and limit the RAM on my VM