Welcome! Log In Create A New Profile

Advanced

Yet Another cannot boot thread

Posted by dinjo 
Re: Yet Another cannot boot thread
November 01, 2013 03:09AM
I was more concerned with this warning in dmesg have changed usbrootfs to use ext3 now.
[   35.595458] alg: hash: Test 1 failed for mv-hmac-sha1
[   35.603134] 00000000: 0c aa 9f d5 37 c3 79 3a 91 d9 21 5f 42 2b 2c 24a

In regards to swap file despite having 512MB not even 6-7MB MB is getting used

root@debian:/etc/init.d# free -m
             total       used       free     shared    buffers     cached
Mem:           120        116          3          0          3         84
-/+ buffers/cache:         29         91
Swap:          511          0        511

root@debian:/etc/init.d# sysctl  vm.swappiness
vm.swappiness = 60

Should I change swappiness if yes then how much ?



Edited 1 time(s). Last edit at 11/01/2013 03:10AM by dinjo.
Re: Yet Another cannot boot thread
November 02, 2013 12:22AM
dinjo Wrote:
-------------------------------------------------------
> I was more concerned with this warning in dmesg
> have changed usbrootfs to use ext3 now.
>
> [   35.595458] alg: hash: Test 1 failed for
> mv-hmac-sha1
> [   35.603134] 00000000: 0c aa 9f d5 37 c3 79 3a
> 91 d9 21 5f 42 2b 2c 24a
>

This is the kernel bug for cryptodev HW acceleration. I have yet to find a patch for it. I recalled someone posted about this here in the forum, but could not find it.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Re: Yet Another cannot boot thread
November 02, 2013 01:33AM
Its fine unless its a known thing
Re: Yet Another cannot boot thread
November 02, 2013 03:24AM
Yes. It's a known bug. As log as your openssl works, I don't think it's matters.

If anybody is aware that this does cause problem with openssl, please post.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Re: Yet Another cannot boot thread
November 07, 2013 04:26AM
I can't get the netconsole in edit mode i.e when i hit enter it does not shows me prompt instead it keeps on loading
Re: Yet Another cannot boot thread
November 07, 2013 11:54AM
For the second nc command, instead of
nc -u 192.168.1.100 6666

try
nc -up 6666 192.168.1.100 6666

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Re: Yet Another cannot boot thread
November 08, 2013 03:58AM
yes i have been using that command itself , also i saw some other threads where some other people were also not able to get into edit mode in net console.
Re: Yet Another cannot boot thread
November 16, 2013 10:03PM
Seems like netconsole does not come up until 33 seconds maybe thats the reason the previous log are not shown
[   23.121018] sd 0:0:0:0: [sda] Attached SCSI disk
[   23.136067] sd 0:0:0:0: Attached scsi generic sg0 type 0
[   33.626464] netpoll: netconsole: local port 6666
[   33.631114] netpoll: netconsole: local IPv4 address 192.168.1.110
[   33.637304] netpoll: netconsole: interface 'eth0'
[   33.642029] netpoll: netconsole: remote port 6666
[   33.646869] netpoll: netconsole: remote IPv4 address 192.168.1.104
Re: Yet Another cannot boot thread
November 17, 2013 12:07AM
dinjo,

Your HDD or kernel is taking too long to boot up. It took 23 seconds before the disk is fully recognized, and then at that time it took another 10 seconds for netconsole to run. And eth0 was already up by this time. As comparison, mine takes about 6 seconds on the GoFlex Net (instead of 23), and eth0 was not up yet at that time.

A sure way to tell what's really going on is to connect serial console and observe the kernel booting activities.

Here is the hint in your dmesg showed where was that 17 second gap:
[    0.000000] Preemptible hierarchical RCU implementation.
[    0.000000] NR_IRQS:114
[    0.000000] sched_clock: 32 bits at 200MHz, resolution 5ns, wraps every 21474ms
[    0.000000] Console: colour dummy device 80x30
[   17.793460] Calibrating delay loop... 1191.11 BogoMIPS (lpj=5955584)
[   17.883251] pid_max: default: 32768 minimum: 301
[   17.883353] Security Framework initialized

My dmesg shows:
[    0.000000] sched_clock: 32 bits at 200MHz, resolution 5ns, wraps every 21474ms
[    0.000000] Console: colour dummy device 80x30
[    1.293016] Calibrating delay loop... 1191.11 BogoMIPS (lpj=5955584)
[    1.382806] pid_max: default: 32768 minimum: 301

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 1 time(s). Last edit at 11/17/2013 12:14AM by bodhi.
Re: Yet Another cannot boot thread
November 17, 2013 05:08AM
Big thumbs up from me for your persistance, bodhi!
If this ever gets resolved, dinjo should at least treat you with a free beer or something similar (http://startupstats.com/startup-trend-beer-2012-03/). ;-)
Re: Yet Another cannot boot thread
November 18, 2013 01:11AM
ingmar_k,

> (http://startupstats.com/startup-trend-beer-2012-03/). ;-)

:)) thanks for the interesting link.

I suspected that dinjo's rootfs is taking more time to mount then normal.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 1 time(s). Last edit at 11/18/2013 01:13AM by bodhi.
Re: Yet Another cannot boot thread
November 21, 2013 05:09AM
Hmm,.. not sure why its a delay but I'll just let it go but i could not figure out why its not allowing me to go to command mode in netconsole i.e its in readonly mode.

I cannot get my second partition to get mounted it has different label and i guess rootfs should get mounted and should boot but as soon as i add in fstab goflex does not boot , does anyone has a sample working fstab ?

Also for turnning off device i do shutdown now -h or poweroff but it gets turned off in 2 seconds is it getting shutdown correctly ?
Re: Yet Another cannot boot thread
November 21, 2013 04:01PM
dinjo Wrote:
-------------------------------------------------------
> Hmm,.. not sure why its a delay but I'll just let
> it go but i could not figure out why its not
> allowing me to go to command mode in netconsole
> i.e its in readonly mode.

It meant your netconsole server nc or socat... Is not working correctly. The box side is working. Tried different programs?

>
> I cannot get my second partition to get mounted it
> has different label and i guess rootfs should get
> mounted and should boot but as soon as i add in
> fstab goflex does not boot , does anyone has a
> sample working fstab ?

Dont mount in fstab. Add a mount command in /etc/rc.local.

> Also for turnning off device i do shutdown now -h
> or poweroff but it gets turned off in 2 seconds is
> it getting shutdown correctly ?

If the HDD is attached, it will take longer to go down completely. So wait 10 seconds.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Re: Yet Another cannot boot thread
November 22, 2013 02:40AM
I'm currently mounting HDD from rc.local but i want it to automount since i wanted all process to have clean startup and clean shutdown(update-rc,d) which at the moment may not be happening , ex- The drive may not get mounted but a torrent client would start and would fail saying no data is found since HDD is not mounted at that time.
Re: Yet Another cannot boot thread
November 22, 2013 04:46PM
dinjo,

What is you /etc/fstab looks like?

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Re: Yet Another cannot boot thread
November 22, 2013 09:10PM
root@debian:~# cat -v -e -t /etc/fstab
# /etc/fstab: static file system information.$
#$
# <file system> <mount point>   <type>  <options>       <dump>  <pass>$
/dev/root      /               ext3    noatime,errors=remount-ro 0 1$
tmpfs          /tmp            tmpfs   defaults          0       0$
/dev/sda2      /media/Data     ext3    noatime           0       0$
Re: Yet Another cannot boot thread
November 23, 2013 01:56AM
Hmm. not sure what was wrong earlier the other drive seems working now.
Author:

Your Email:


Subject:


Spam prevention:
Please, enter the code that you see below in the input field. This is for blocking bots that try to post this form automatically. If the code is hard to read, then just try to guess it right. If you enter the wrong code, a new image is created and you get another chance to enter it right.
Message: