80-90% of the boot ups, my rig crashing and immediately reboots in the begining of the boot procedure, always at the same stage which is

 

Unpacking initramfs...

 

In those 10-20%, when it is booting successfully I have no problem at all afterwards during operation.

I suspected this to be a RAM issue, but the memtest is passed without any error.

Could someone please point me to the right direction where should I look into? (Maybe my flashdrive is dying? )

You can test another flash just to rule out any other bios or hardware issues.

 

You can  also try downloading a new copy of the distribution you are using.

Then update the files on the flash drive.

 

Which distribution are you using, maybe you can do an md5sum on a windows machine and compare it to another forum member.

 

http://www.etree.org/md5com.html

my Beta8 sums are

 

root@Atlas /boot #md5sum bzimageb bzrootb

8b11aa568877489879f6b0f07fee630c  bzimageb

7508c78402cb80588a928089d8bb60ac  bzrootb

 

This will just prove/disprove if there is a corruption of your bzroot/bzimage.

 

 

Thanks for the feedback!

 

Hmmmm... I've just plugged the flashdrive into my desktop PC to create a fresh backup of it and it was freezing during the first copying, then was OK on the second try. Something is definitely not OK with that flash.

 

I am now going to try my unRAID machine with an other flash...

Thanks for the feedback!

 

Hmmmm... I've just plugged the flashdrive into my desktop PC to create a fresh backup of it and it was freezing during the first copying, then was OK on the second try. Something is definitely not OK with that flash.

 

I am now going to try my unRAID machine with an other flash...

 

Try running a checkdisk on the flash drive to see if it finds anything and fixes it.  You could try doing a full format (none quick version) to see if that can fix anything.  Obviously this will erase the data on the flash so get as much of the stuff off of it as you can.

Just finished the test with the other flash, was flawless...

 

Now I am looking into this.

Uhhh... I am not sure I will even trust this flash any more, but my pro licence is stick to this...

Just finished the test with the other flash, was flawless...

 

Now I am looking into this.

Uhhh... I am not sure I will even trust this flash any more, but my pro licence is stick to this...

 

Send Tom and email.  He has, to my knowledge , been very understanding in situations like this.

Thanks prostuff1!

 

I continously had reading/writing issues to the flash, so finally I formatted it.

Following to this, I was able to restore my unraid to the flash, although there were small stutters during copying.

 

Now it seems OK, finger crossed.

I've not experienced problems yet, but my syslog is continously includes the following notice after mover finished:

This is also seems to spun up all the drives. This happens all day, not just randomly. So do you think I should go for changing this flash?

 

Thank you!

 

Nov 22 03:40:01 Tower logger: mover started

Nov 22 03:41:07 Tower logger: mover finished

Nov 22 04:11:18 Tower emhttp: shcmd (77): /usr/sbin/hdparm -y /dev/sdh >/dev/null

Nov 22 04:11:18 Tower emhttp: shcmd (78): /usr/sbin/hdparm -y /dev/sdd >/dev/null

Nov 22 04:11:19 Tower emhttp: shcmd (79): /usr/sbin/hdparm -y /dev/sdj >/dev/null

Nov 22 04:11:20 Tower emhttp: shcmd (80): /usr/sbin/hdparm -y /dev/sda >/dev/null

Nov 22 04:11:20 Tower emhttp: shcmd (81): /usr/sbin/hdparm -y /dev/sdc >/dev/null

Nov 22 04:11:21 Tower emhttp: shcmd (82): /usr/sbin/hdparm -y /dev/sdb >/dev/null

Nov 22 04:11:22 Tower emhttp: shcmd (83): /usr/sbin/hdparm -y /dev/sdg >/dev/null

Nov 22 04:11:22 Tower emhttp: shcmd (84): /usr/sbin/hdparm -y /dev/sdf >/dev/null

Nov 22 04:11:23 Tower emhttp: shcmd (85): /usr/sbin/hdparm -y /dev/sdk >/dev/null

Nov 22 04:41:05 Tower kernel: usb 2-2: reset high speed USB device using ehci_hcd and address 2

Nov 22 04:41:05 Tower kernel: usb 2-2: reset high speed USB device using ehci_hcd and address 2

Nov 22 04:41:05 Tower kernel: usb 2-2: device descriptor read/64, error -71

Nov 22 05:11:24 Tower emhttp: shcmd (86): /usr/sbin/hdparm -y /dev/sda >/dev/null

Nov 22 05:11:25 Tower emhttp: shcmd (87): /usr/sbin/hdparm -y /dev/sdb >/dev/null

Nov 22 05:12:26 Tower emhttp: shcmd (88): /usr/sbin/hdparm -y /dev/sdh >/dev/null

Nov 22 05:12:26 Tower emhttp: shcmd (89): /usr/sbin/hdparm -y /dev/sdd >/dev/null

Nov 22 05:12:27 Tower emhttp: shcmd (90): /usr/sbin/hdparm -y /dev/sdj >/dev/null

Nov 22 05:12:28 Tower emhttp: shcmd (91): /usr/sbin/hdparm -y /dev/sdc >/dev/null

Nov 22 05:12:28 Tower emhttp: shcmd (92): /usr/sbin/hdparm -y /dev/sdg >/dev/null

Nov 22 05:12:29 Tower emhttp: shcmd (93): /usr/sbin/hdparm -y /dev/sdf >/dev/null

Nov 22 05:12:30 Tower emhttp: shcmd (94): /usr/sbin/hdparm -y /dev/sdk >/dev/null

I tried Googling "device descriptor read 64 error 71 usb", and discovered this error is rather common out there.  A couple of threads I found interesting are below:

 

  http://lists-archives.org/linux-usb-devel/00012-error-71-during-loading-pehci-ehci-usb-driver.html

  http://ubuntuforums.org/archive/index.php/t-797789.html

 

There was also a hint that a newer kernel release *might* help, so you might try the latest unRAID release.

 

The fact that it is spinning up all the drives is really really strange!  I would definitely try different USB ports first, and then a different flash drive.