April 2, 201313 yr First I want to start by saying that I have been using Unraid for years without ANY issue, and I love it. So hats off to you guys for an awesome and stable release product! The problems that I have had lately have been with the Beta5.0 rc12a version. I have experienced kernel panics when building parity 3 times in the past few days. Before updating to 5.0 I had 4.7 running and was able to build parity just fine. The strange thing is that every time this has happened has been sometime after midnight on all three occasions. Now the one thing that may be an issue is that I was using the array to stream content at these times. Also I am running plugins on the system and they where running as well. So this time I have shut down all Plugins and am trying parity check again. This takes a few days though. Does anyone have any thoughts on this one ? Thanks guys ! System Specs are here. Also I have attached a image of the error. 11 Disks in the array at about 9.5 TB - on PCI Sata controllers 2TB Parity drive on the MB Sata ports 750GB Parity drive on the MB Sata ports Intel i3 3.4GHz Sandy Bridge Proc Foxconn H61AP MB 8GB Corsair CMP8GX3M2B1333C9 DDR3 1333 RAM 4- Promise SATA TXA300 controller Cards Plugins Sabnzbd Plex Media Server Sick Beard Couch Potato Transmission
April 2, 201313 yr First I want to start by saying that I have been using Unraid for years without ANY issue, and I love it. So hats off to you guys for an awesome and stable release product! The problems that I have had lately have been with the Beta5.0 rc12a version. I have experienced kernel panics when building parity 3 times in the past few days. Before updating to 5.0 I had 4.7 running and was able to build parity just fine. The strange thing is that every time this has happened has been sometime after midnight on all three occasions. Now the one thing that may be an issue is that I was using the array to stream content at these times. Also I am running plugins on the system and they where running as well. So this time I have shut down all Plugins and am trying parity check again. This takes a few days though. Does anyone have any thoughts on this one ? Thanks guys ! System Specs are here. Also I have attached a image of the error. 11 Disks in the array at about 9.5 TB - on PCI Sata controllers 2TB Parity drive on the MB Sata ports 750GB Parity drive on the MB Sata ports Intel i3 3.4GHz Sandy Bridge Proc Foxconn H61AP MB 8GB Corsair CMP8GX3M2B1333C9 DDR3 1333 RAM 4- Promise SATA TXA300 controller Cards Plugins Sabnzbd Plex Media Server Sick Beard Couch Potato Transmission Without any other details, the fact that your screen shot shows a memory "alloc" (allocation) at the end of the stack trace, might be a clue to indicate you ran out of free memory. Joe L.
April 2, 201313 yr Author So maybe a bad memory module? I will run a memtest overnight and see what happens with that.
April 2, 201313 yr So maybe a bad memory module? I will run a memtest overnight and see what happens with that. Could be that too, but I said not enough "free" memory. (all available memory was already allocated to a running process) Track via free -l Usually you will run out of "low" memory before anything else. Joe L.
April 2, 201313 yr All those plugins can eat a lot of memory. Try disabling them, rebooting, and then building parity.
April 3, 201313 yr Author Ok so I disabled all the plugins yesterday morning when I did the first post. It was bilding parity all day and was fine. I checked it when I went to bed at 11pm last night and it was at about 40%. I woke up this morning and the same kernel panic happened. I am doing a mem test now and will check when I get home. I am at a loss here. It seems that this only happens after midnight. I guess I am reverting back to 4.7 . Unless anyone else has any ideas.
April 3, 201313 yr My 'Guess' would be that something is starting automatically around midnight which causes the kernel panic. Why don't you print a copy of the disk setup (main page) and your share setups. Back up your current flash drive so you can go back to your current setup. Double (and triple) check that you have a copy of your key file. Now wipe your flash drive clean. Install unRAID rc12a from the download. Copy the key file to the proper location. Boot the server. Check and restore the settings. Now see what happens when you rebuilt parity.
April 3, 201313 yr Author Yeah I like that better then rolling back to 4.7. Fresh copy of 5 with no plugins installed. Will try again tonight.
April 4, 201313 yr Author Yep failed again. Also apparently the memtest application does nothing when I run it. I had it running all day yesterday and no passes or progress.
April 4, 201313 yr Author I am going to downgrade to 4.7 tonight, but I am concerned about how to do this because I believe that the files in the config folder are different in 4.7 then they are in 5. I have a screen shot of my dive config so I can put those in the correct place, but I am concerned about my Shares not working correctly because the file structure is different. Do I need to be concerned about the Shares? Or can I recreate them from a screen shot of what disk where included in the shares in version 5?
April 4, 201313 yr Yep failed again. Also apparently the memtest application does nothing when I run it. I had it running all day yesterday and no passes or progress. Need a better description than "Yep failed again." If memtest is not running, that is a serious matter. The memtest application has been around for a generation and is a standalone application that is completely independent of any operating system. It has absolutely nothing to do with unRAID as its only propose is to test one piece of hardware and that hardware is memory. If it is not running, you have a serious hardware issue...
April 4, 201313 yr You can always try downloading an iso from here http://www.memtest.org/ and attempt running it from a CD to ensure it's not something to do with your usb stick.
April 4, 201313 yr If memtest is not running, that is a serious matter. Not necessarily - I don't think that the memtest distributed with unRAID is the latest version. It may be that your hardware is not supported with the current distribution. Obtain the latest memtest image and try with that. This is what I had to do when I built my original DH55TC/i3-530 based system. Edit to add: Failing 'sometime after midnight' makes me wonder whether mover is causing the system to topple over.
April 4, 201313 yr Author Yep failed again. Also apparently the memtest application does nothing when I run it. I had it running all day yesterday and no passes or progress. Need a better description than "Yep failed again." If memtest is not running, that is a serious matter. The memtest application has been around for a generation and is a standalone application that is completely independent of any operating system. It has absolutely nothing to do with unRAID as its only propose is to test one piece of hardware and that hardware is memory. If it is not running, you have a serious hardware issue... What I meant was that the Parity Build Failed again after midnight.
April 4, 201313 yr Author You can always try downloading an iso from here http://www.memtest.org/ and attempt running it from a CD to ensure it's not something to do with your usb stick. Thanks I will download and try that. Based on the release notes for the latest version Supporting Sandy Bridge processors, I am thinking this may be it. I will try after work.
April 4, 201313 yr Author If memtest is not running, that is a serious matter. Not necessarily - I don't think that the memtest distributed with unRAID is the latest version. It may be that your hardware is not supported with the current distribution. Obtain the latest memtest image and try with that. This is what I had to do when I built my original DH55TC/i3-530 based system. Edit to add: Failing 'sometime after midnight' makes me wonder whether mover is causing the system to topple over. Is there a way to disable the mover completely for temporary testing ?
April 4, 201313 yr Is there a way to disable the mover completely for temporary testing ?easy, just rename it so it is not found. mv /usr/local/sbin/mover /usr/local/sbin/mover.old
April 4, 201313 yr Author Strangely enough it looks like there is not a mover file in the directory. Here is a ls from root@Loki:/sbin# ls adjtimex* fsck.ext4dev* mkfs.bfs* resize2fs* agetty* fsck.minix* mkfs.cramfs* resize_reiserfs* arp* fsck.reiserfs@ mkfs.ext2@ rmmod* arping* gdisk* mkfs.ext3@ rmt@ badblocks* genpowerd* mkfs.ext4@ route* blkid* genpowerfail* mkfs.ext4dev@ rpc.portmap* blockdev* gentest* mkfs.minix* rpc.statd* bootlogd* getty* mkfs.reiserfs@ runlevel* cfdisk* halt* mklost+found* scsi_id@ clock@ hdparm* mkreiserfs* setserial* ctrlaltdel* hwclock* mkswap* sfdisk* debugfs* ifconfig* modinfo* sgdisk* debugreiserfs* ifenslave* modprobe* shutdown* depmod* init* mount@ sln* dhcpcd* initscript.sample* mount.cifs* sulogin* dosfsck* insmod* mount.fuse* swapoff@ dumpe2fs* insmod.static* mount.nfs* swapon* e2freefrag* installpkg* nameif* switch_root* e2fsck* ipmaddr* nologin* sysctl* e2image* iptunnel* pidof@ telinit@ e2label@ jaztool@ pivot_root* tune2fs* e2undo* killall5* plipconfig* udevadm* explodepkg* ldconfig* poweroff@ udevd* fdisk* logsave* rarp* umount@ filefrag* losetup* raw* umount.nfs@ findfs* lsmod* rdev* upgradepkg* fsck* makepkg* reboot@ uugetty* fsck.cramfs* mii-tool* reiserfsck* wipefs* fsck.ext2* mkdosfs* reiserfstune* ziptool* fsck.ext3* mke2fs* removepkg* fsck.ext4* mkfs* rescan-scsi-bus*
April 4, 201313 yr Strangely enough it looks like there is not a mover file in the directory. Here is a ls from root@Loki:/sbin# ls adjtimex* fsck.ext4dev* mkfs.bfs* resize2fs* agetty* fsck.minix* mkfs.cramfs* resize_reiserfs* arp* fsck.reiserfs@ mkfs.ext2@ rmmod* arping* gdisk* mkfs.ext3@ rmt@ badblocks* genpowerd* mkfs.ext4@ route* blkid* genpowerfail* mkfs.ext4dev@ rpc.portmap* blockdev* gentest* mkfs.minix* rpc.statd* bootlogd* getty* mkfs.reiserfs@ runlevel* cfdisk* halt* mklost+found* scsi_id@ clock@ hdparm* mkreiserfs* setserial* ctrlaltdel* hwclock* mkswap* sfdisk* debugfs* ifconfig* modinfo* sgdisk* debugreiserfs* ifenslave* modprobe* shutdown* depmod* init* mount@ sln* dhcpcd* initscript.sample* mount.cifs* sulogin* dosfsck* insmod* mount.fuse* swapoff@ dumpe2fs* insmod.static* mount.nfs* swapon* e2freefrag* installpkg* nameif* switch_root* e2fsck* ipmaddr* nologin* sysctl* e2image* iptunnel* pidof@ telinit@ e2label@ jaztool@ pivot_root* tune2fs* e2undo* killall5* plipconfig* udevadm* explodepkg* ldconfig* poweroff@ udevd* fdisk* logsave* rarp* umount@ filefrag* losetup* raw* umount.nfs@ findfs* lsmod* rdev* upgradepkg* fsck* makepkg* reboot@ uugetty* fsck.cramfs* mii-tool* reiserfsck* wipefs* fsck.ext2* mkdosfs* reiserfstune* ziptool* fsck.ext3* mke2fs* removepkg* fsck.ext4* mkfs* rescan-scsi-bus* NOT /sbin, but /usr/local/sbin
April 4, 201313 yr Author Strangely enough it looks like there is not a mover file in the directory. Here is a ls from root@Loki:/sbin# ls adjtimex* fsck.ext4dev* mkfs.bfs* resize2fs* agetty* fsck.minix* mkfs.cramfs* resize_reiserfs* arp* fsck.reiserfs@ mkfs.ext2@ rmmod* arping* gdisk* mkfs.ext3@ rmt@ badblocks* genpowerd* mkfs.ext4@ route* blkid* genpowerfail* mkfs.ext4dev@ rpc.portmap* blockdev* gentest* mkfs.minix* rpc.statd* bootlogd* getty* mkfs.reiserfs@ runlevel* cfdisk* halt* mklost+found* scsi_id@ clock@ hdparm* mkreiserfs* setserial* ctrlaltdel* hwclock* mkswap* sfdisk* debugfs* ifconfig* modinfo* sgdisk* debugreiserfs* ifenslave* modprobe* shutdown* depmod* init* mount@ sln* dhcpcd* initscript.sample* mount.cifs* sulogin* dosfsck* insmod* mount.fuse* swapoff@ dumpe2fs* insmod.static* mount.nfs* swapon* e2freefrag* installpkg* nameif* switch_root* e2fsck* ipmaddr* nologin* sysctl* e2image* iptunnel* pidof@ telinit@ e2label@ jaztool@ pivot_root* tune2fs* e2undo* killall5* plipconfig* udevadm* explodepkg* ldconfig* poweroff@ udevd* fdisk* logsave* rarp* umount@ filefrag* losetup* raw* umount.nfs@ findfs* lsmod* rdev* upgradepkg* fsck* makepkg* reboot@ uugetty* fsck.cramfs* mii-tool* reiserfsck* wipefs* fsck.ext2* mkdosfs* reiserfstune* ziptool* fsck.ext3* mke2fs* removepkg* fsck.ext4* mkfs* rescan-scsi-bus* NOT /sbin, but /usr/local/sbin Sorry about that. Now the mover name is changed. I will give building a try again.
April 4, 201313 yr Is there a way to disable the mover completely for temporary testing ?easy, just rename it so it is not found. mv /usr/local/sbin/mover /usr/local/sbin/mover.old Wouldn't it be easier to go into Settings -> Share settings, and alter the schedule?
April 5, 201313 yr Author So it appears that the mover was the culprit ! After disabling the mover, parity has been building all night with no Kernel Panic. So I think there is something different about the mover in 5.0rc12a then 4.7. I did not have this issue in 4.7. Also it appears that the Memtest version in the 5.0rc12a download is not the latest version from Memtest. Version 4.20 is on their site and supports Sandy Bridge CPUs. Memtest on the stick says version 4.10. Thanks for the help guys !
Archived
This topic is now archived and is closed to further replies.