Error during boot up.

classic Classic list List threaded Threaded
25 messages Options
12
Reply | Threaded
Open this post in threaded view
|

Error during boot up.

Dale-46
Howdy,

I just installed a new video card.  After a couple weeks of USPS
dragging it around, it finally came in.  Anyway, I got it installed and
was booting up.  I noticed somewhere between the kernel part and it
going through the runlevel part, there was something that failed.  I saw
a little red colored text and the word failed but I found one bad thing
about a really fast CPU.  It scrolls by so fast, I can't tell what it
is.  It is almost a blur when it scrolls up.  It's not a service because
rc-status shows all green.  I'm not sure that lists everything tho since
it seems a little light on the number of services. 

At some point way back, I recall there being a logger that picks up the
area between when dmesg is logging and when syslog or friends start
logging to the message file.  I think this is where the error is.  I
can't find tool now.  I also can't find anything else in /var/log
either.  Am I wrong on having this or did it die off in the tree and got
removed?  If so, is there something that picks up that area of the boot
up process as far as errors go?  My system seems to work fine but I'd
like to know what that error was.  It may cause a problem at some point
and could even be the problem with that random reboot I had in another
thread. 

Thanks.

Dale

:-)  :-) 

P. S.  I did reseat all the power cables to the mobo while I was
swapping video cards.  Hoping that may help with that weird reboot thing
I had going on.  BTW, it hasn't happened since the one I started the
thread about either.  Weird. 

Reply | Threaded
Open this post in threaded view
|

Re: Error during boot up.

J. Roeleveld
On December 20, 2018 4:41:26 AM UTC, Dale <[hidden email]> wrote:
Howdy,

I just installed a new video card.  After a couple weeks of USPS
dragging it around, it finally came in.  Anyway, I got it installed and
was booting up.  I noticed somewhere between the kernel part and it
going through the runlevel part, there was something that failed.  I saw
a little red colored text and the word failed but I found one bad thing
about a really fast CPU.  It scrolls by so fast, I can't tell what it
is.  It is almost a blur when it scrolls up.  It's not a service because
rc-status shows all green.  I'm not sure that lists everything tho since
it seems a little light on the number of services. 

At some point way back, I recall there being a logger that picks up the
area between when dmesg is logging and when syslog or friends start
logging to the message file.  I think this is where the error is.  I
can't find tool now.  I also can't find anything else in /var/log
either.  Am I wrong on having this or did it die off in the tree and got
removed?  If so, is there something that picks up that area of the boot
up process as far as errors go?  My system seems to work fine but I'd
like to know what that error was.  It may cause a problem at some point
and could even be the problem with that random reboot I had in another
thread. 

Thanks.

Dale

:-)  :-) 

P. S.  I did reseat all the power cables to the mobo while I was
swapping video cards.  Hoping that may help with that weird reboot thing
I had going on.  BTW, it hasn't happened since the one I started the
thread about either.  Weird. 


In "rc.conf" there is an option to log to /var/log/rc.log or similar.
Not near a working system, so can't check actual option.

--
Joost
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
Reply | Threaded
Open this post in threaded view
|

Re: Error during boot up.

Dale-46
J. Roeleveld wrote:
On December 20, 2018 4:41:26 AM UTC, Dale [hidden email] wrote:
Howdy,

I just installed a new video card.  After a couple weeks of USPS
dragging it around, it finally came in.  Anyway, I got it installed and
was booting up.  I noticed somewhere between the kernel part and it
going through the runlevel part, there was something that failed.  I saw
a little red colored text and the word failed but I found one bad thing
about a really fast CPU.  It scrolls by so fast, I can't tell what it
is.  It is almost a blur when it scrolls up.  It's not a service because
rc-status shows all green.  I'm not sure that lists everything tho since
it seems a little light on the number of services. 

At some point way back, I recall there being a logger that picks up the
area between when dmesg is logging and when syslog or friends start
logging to the message file.  I think this is where the error is.  I
can't find tool now.  I also can't find anything else in /var/log
either.  Am I wrong on having this or did it die off in the tree and got
removed?  If so, is there something that picks up that area of the boot
up process as far as errors go?  My system seems to work fine but I'd
like to know what that error was.  It may cause a problem at some point
and could even be the problem with that random reboot I had in another
thread. 

Thanks.

Dale

:-)  :-) 

P. S.  I did reseat all the power cables to the mobo while I was
swapping video cards.  Hoping that may help with that weird reboot thing
I had going on.  BTW, it hasn't happened since the one I started the
thread about either.  Weird. 


In "rc.conf" there is an option to log to /var/log/rc.log or similar.
Not near a working system, so can't check actual option.

--
Joost
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.


That gave me the clue I needed.  I was looking for a package.  No wonder I couldn't find it.  It was disabled in rc.conf for some reason and based on the last date of the log file, it has been for a while, which is why I thought something got cleaned out or something.  I now have this set:



# NOTE: Linux systems require the devfs service to be started before
# logging can take place and as such cannot log the sysinit runlevel.
rc_logger="YES"

# Through rc_log_path you can specify a custom log file.
# The default value is: /var/log/rc.log
rc_log_path="/var/log/rc.log"
 

Thanks for the help.  When I boot next time, maybe it will log the error and I can see what is going on. 

Dale

:-)  :-) 
Reply | Threaded
Open this post in threaded view
|

Re: Error during boot up.

Peter Humphrey-3
On Thursday, 20 December 2018 08:12:43 GMT Dale wrote:

> Thanks for the help.  When I boot next time, maybe it will log the error
> and I can see what is going on.

You could also try CTRL-S to pause the screen update and CTRL-Q to let it
continue.

--
Regards,
Peter.




Reply | Threaded
Open this post in threaded view
|

Re: Error during boot up.

J. Roeleveld
On Thursday, December 20, 2018 11:04:55 AM CET Peter Humphrey wrote:
> On Thursday, 20 December 2018 08:12:43 GMT Dale wrote:
> > Thanks for the help.  When I boot next time, maybe it will log the error
> > and I can see what is going on.
>
> You could also try CTRL-S to pause the screen update and CTRL-Q to let it
> continue.

In my experience, this never works when it happens in the beginning as it's
near impossible to time it right.

--
Joost




Reply | Threaded
Open this post in threaded view
|

Re: Error during boot up.

J. Roeleveld
In reply to this post by Dale-46
On Thursday, December 20, 2018 9:12:43 AM CET Dale wrote:

> J. Roeleveld wrote:
> > On December 20, 2018 4:41:26 AM UTC, Dale <[hidden email]> wrote:
> >     Howdy,
> >    
> >     I just installed a new video card.  After a couple weeks of USPS
> >     dragging it around, it finally came in.  Anyway, I got it installed
> >     and
> >     was booting up.  I noticed somewhere between the kernel part and it
> >     going through the runlevel part, there was something that failed.  I
> >     saw
> >     a little red colored text and the word failed but I found one bad
> >     thing
> >     about a really fast CPU.  It scrolls by so fast, I can't tell what it
> >     is.  It is almost a blur when it scrolls up.  It's not a service
> >     because
> >     rc-status shows all green.  I'm not sure that lists everything tho
> >     since
> >     it seems a little light on the number of services.
> >    
> >     At some point way back, I recall there being a logger that picks up
> >     the
> >     area between when dmesg is logging and when syslog or friends start
> >     logging to the message file.  I think this is where the error is.  I
> >     can't find tool now.  I also can't find anything else in /var/log
> >     either.  Am I wrong on having this or did it die off in the tree and
> >     got
> >     removed?  If so, is there something that picks up that area of the
> >     boot
> >     up process as far as errors go?  My system seems to work fine but I'd
> >     like to know what that error was.  It may cause a problem at some
> >     point
> >     and could even be the problem with that random reboot I had in another
> >     thread.
> >    
> >     Thanks.
> >    
> >     Dale
> >    
> >     :-)  :-)
> >    
> >     P. S.  I did reseat all the power cables to the mobo while I was
> >     swapping video cards.  Hoping that may help with that weird reboot
> >     thing
> >     I had going on.  BTW, it hasn't happened since the one I started the
> >     thread about either.  Weird.
> >
> > In "rc.conf" there is an option to log to /var/log/rc.log or similar.
> > Not near a working system, so can't check actual option.
> >
> > --
> > Joost
>
> That gave me the clue I needed.  I was looking for a package.  No wonder
> I couldn't find it.  It was disabled in rc.conf for some reason

By default, it is disabled. My guess is that you accidentally overwrote that
setting at some point.

> and
> based on the last date of the log file, it has been for a while, which
> is why I thought something got cleaned out or something.  I now have
> this set:
>
>
>
> # NOTE: Linux systems require the devfs service to be started before
> # logging can take place and as such cannot log the sysinit runlevel.
> rc_logger="YES"
>
> # Through rc_log_path you can specify a custom log file.
> # The default value is: /var/log/rc.log
> rc_log_path="/var/log/rc.log"
>  
>
> Thanks for the help.  When I boot next time, maybe it will log the error
> and I can see what is going on.

Make sure that path is mounted soon. Eg, that it isn't on a seperate
mountpoint.

--
Joost




Reply | Threaded
Open this post in threaded view
|

Re: Error during boot up.

Dale-46
In reply to this post by Peter Humphrey-3
Peter Humphrey wrote:
> On Thursday, 20 December 2018 08:12:43 GMT Dale wrote:
>
>> Thanks for the help.  When I boot next time, maybe it will log the error
>> and I can see what is going on.
> You could also try CTRL-S to pause the screen update and CTRL-Q to let it
> continue.
>


I did try page up, up arrow and such.  I was trying to get at least one
or two keywords to look into.  Thing is, it is so fast. My old 4 core
booted pretty quick but this new 8 core with faster clock speeds is
seriously fast.  It goes from the kernel starting to load to sddm
starting in seconds.  I'm not sure if the extra memory helps at that
point or not but the faster and extra cores sure does.  I'll try to
remember that ctrl s.  I just better have my fingers ready.  lol 

If I had a sdd drive for the OS to be on, I guess it would be even
faster.  vvrrrmmmmm vvvrrrmmmmm!!!!

Dale

:-)  :-) 

Reply | Threaded
Open this post in threaded view
|

Re: Error during boot up.

J. Roeleveld
On December 20, 2018 11:45:29 AM UTC, Dale <[hidden email]> wrote:
Peter Humphrey wrote:
On Thursday, 20 December 2018 08:12:43 GMT Dale wrote:

Thanks for the help. When I boot next time, maybe it will log the error
and I can see what is going on.
You could also try CTRL-S to pause the screen update and CTRL-Q to let it
continue.



I did try page up, up arrow and such.  I was trying to get at least one
or two keywords to look into.  Thing is, it is so fast. My old 4 core
booted pretty quick but this new 8 core with faster clock speeds is
seriously fast.  It goes from the kernel starting to load to sddm
starting in seconds.  I'm not sure if the extra memory helps at that
point or not but the faster and extra cores sure does.  I'll try to
remember that ctrl s.  I just better have my fingers ready.  lol 

If I had a sdd drive for the OS to be on, I guess it would be even
faster.  vvrrrmmmmm vvvrrrmmmmm!!!!

Dale

:-)  :-) 


Next upgrade idea:
- mainboard with NVME slot
- NVME drive for your OS.

Your CPU and memory will be the next bottleneck :)


--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
Reply | Threaded
Open this post in threaded view
|

Re: Error during boot up.

Dale-46
J. Roeleveld wrote:
On December 20, 2018 11:45:29 AM UTC, Dale [hidden email] wrote:
Peter Humphrey wrote:
On Thursday, 20 December 2018 08:12:43 GMT Dale wrote:
Thanks for the help. When I boot next time, maybe it will log the error and I can see what is going on.
You could also try CTRL-S to pause the screen update and CTRL-Q to let it continue.
I did try page up, up arrow and such.  I was trying to get at least one or two keywords to look into.  Thing is, it is so fast. My old 4 core booted pretty quick but this new 8 core with faster clock speeds is seriously fast.  It goes from the kernel starting to load to sddm starting in seconds.  I'm not sure if the extra memory helps at that point or not but the faster and extra cores sure does.  I'll try to remember that ctrl s.  I just better have my fingers ready.  lol  If I had a sdd drive for the OS to be on, I guess it would be even faster.  vvrrrmmmmm vvvrrrmmmmm!!!! Dale :-)  :-) 

Next upgrade idea:
- mainboard with NVME slot
- NVME drive for your OS.

Your CPU and memory will be the next bottleneck :)


--
Sent from my Android device with K-9 Mail. Please excuse my brevity.


Yea.  I looked into rebuilding from scratch, less the case of course.  I'm just not sure it would be worth the speed increase.  The biggest things I needed, more drive space and more memory.  The CPU was just on sale.  Hard to beat $75.00 for a 8 core CPU running at over 4GHz.  Right now, it's plenty fast.  I may consider it after I do some other things tho.  I plan to do a emerge -e world before to long.  I wanted to let the new CPU compound sort of get set in. 

I might add, the new video card is way overpowered for what I do.  LOL  Most of the time, it maxes out at about 10% of its power and less than 10% for memory usage.  I really can't tell much difference from my old 220 to this new 650 series.  The biggest difference, the 650 runs much cooler.  I just hope it doesn't get bored and go to sleep.  ;-)  Oh, when I run glxgears at full screen, it still only goes to about 60%.  It warms up a little but not a whole lot.

Now to go see what a NVME drive is.  I don't recall ever hearing of those.  Sounds interesting.

Dale

:-)  :-) 
Reply | Threaded
Open this post in threaded view
|

Re: Error during boot up.

Nikos Chantziaras-2
In reply to this post by Dale-46
On 20/12/2018 06:41, Dale wrote:
> Howdy,
>
> I just installed a new video card.  After a couple weeks of USPS
> dragging it around, it finally came in.  Anyway, I got it installed and
> was booting up.  I noticed somewhere between the kernel part and it
> going through the runlevel part, there was something that failed.  I saw
> a little red colored text and the word failed but I found one bad thing
> about a really fast CPU.  It scrolls by so fast, I can't tell what it
> is.

You should probably add the "quiet" option to your kernel command line
in Grub. It will silence all useless noise, and should (I think) only
print errors if they occur.

Worth a try.


Reply | Threaded
Open this post in threaded view
|

Re: Error during boot up.

Dale-46
Nikos Chantziaras wrote:

> On 20/12/2018 06:41, Dale wrote:
>> Howdy,
>>
>> I just installed a new video card.  After a couple weeks of USPS
>> dragging it around, it finally came in.  Anyway, I got it installed and
>> was booting up.  I noticed somewhere between the kernel part and it
>> going through the runlevel part, there was something that failed.  I saw
>> a little red colored text and the word failed but I found one bad thing
>> about a really fast CPU.  It scrolls by so fast, I can't tell what it
>> is.
>
> You should probably add the "quiet" option to your kernel command line
> in Grub. It will silence all useless noise, and should (I think) only
> print errors if they occur.
>
> Worth a try.
>
>
>


I don't think it would help.  It's the speed that is the problem. It was
almost impossible to read anything with my old CPU. It's nothing but a
blur with this new one.  Mostly, I saw red letters and what looked like
the word "error". 

If it will log the error, that is best because I can copy and paste it
into a search engine and find out what it means and how to fix it, if I
don't figure it out on my own.  May help someone else reading this tho.  ;-)

Thanks.

Dale

:-)  :-) 

Reply | Threaded
Open this post in threaded view
|

Re: Error during boot up.

Grant Edwards-6
On 2018-12-20, Dale <[hidden email]> wrote:

> I don't think it would help.  It's the speed that is the problem. It was
> almost impossible to read anything with my old CPU. It's nothing but a
> blur with this new one.  Mostly, I saw red letters and what looked like
> the word "error". 
>
> If it will log the error, that is best because I can copy and paste it
> into a search engine and find out what it means and how to fix it, if I
> don't figure it out on my own.  May help someone else reading this tho.  ;-)

With most more modern motherboards this is probably not an option, but
when I'm troubleshooting that sort of thing, I tell the kernel to use
a serial console. I connect something to the serial port that logs the
data to a file (usually a second Linux machine running C-Kermit, but
there are untold other options), and Bob's your uncle.

With GRUB, you can usually hit <some character> to stop autoboot, then
<some other character> to edit the default boot options to add the
"console=" incantation.

If you really want to geek out, you can configure GRUB to use the
serial console also (but that's not really needed for your situation).

So far, I've been able to avoid buying a motherboard without at least
one plain-old-UART on it.  These days you usually have to provide your
own ribbon-cable-DB9 bracket, but it's still a lifesaver for obscure
kernel problems.

Another option is 'netconsole':

   https://wiki.archlinux.org/index.php/Netconsole

It doesn't kick in as early as a serial-console does, but it it might
be early enough if the NIC driver and netconsole drivers are compiled
into the kernel as opposed to being a loadable module.

--
Grant Edwards               grant.b.edwards        Yow! Everybody is going
                                  at               somewhere!!  It's probably
                              gmail.com            a garage sale or a disaster
                                                   Movie!!


Reply | Threaded
Open this post in threaded view
|

Re: Error during boot up.

Bill Kenworthy
On 21/12/18 5:37 am, Grant Edwards wrote:

> On 2018-12-20, Dale <[hidden email]> wrote:
>
>> I don't think it would help.  It's the speed that is the problem. It was
>> almost impossible to read anything with my old CPU. It's nothing but a
>> blur with this new one.  Mostly, I saw red letters and what looked like
>> the word "error". 
>>
>> If it will log the error, that is best because I can copy and paste it
>> into a search engine and find out what it means and how to fix it, if I
>> don't figure it out on my own.  May help someone else reading this tho.  ;-)
> With most more modern motherboards this is probably not an option, but
> when I'm troubleshooting that sort of thing, I tell the kernel to use
> a serial console. I connect something to the serial port that logs the
> data to a file (usually a second Linux machine running C-Kermit, but
> there are untold other options), and Bob's your uncle.
>
> With GRUB, you can usually hit <some character> to stop autoboot, then
> <some other character> to edit the default boot options to add the
> "console=" incantation.
>
> If you really want to geek out, you can configure GRUB to use the
> serial console also (but that's not really needed for your situation).
>
> So far, I've been able to avoid buying a motherboard without at least
> one plain-old-UART on it.  These days you usually have to provide your
> own ribbon-cable-DB9 bracket, but it's still a lifesaver for obscure
> kernel problems.
>
> Another option is 'netconsole':
>
>    https://wiki.archlinux.org/index.php/Netconsole
>
> It doesn't kick in as early as a serial-console does, but it it might
> be early enough if the NIC driver and netconsole drivers are compiled
> into the kernel as opposed to being a loadable module.
>
Tried this? /etc/rc.conf

# rc_logger launches a logging daemon to log the entire rc process to
# /var/log/rc.log
# NOTE: Linux systems require the devfs service to be started before
# logging can take place and as such cannot log the sysinit runlevel.
rc_logger="YES"

# Through rc_log_path you can specify a custom log file.
# The default value is: /var/log/rc.log
rc_log_path="/var/log/rc.log"

BillK



Reply | Threaded
Open this post in threaded view
|

Re: Error during boot up.

Neil Bothwick
In reply to this post by Dale-46
On Thu, 20 Dec 2018 15:13:37 -0600, Dale wrote:

> I don't think it would help.  It's the speed that is the problem. It was
> almost impossible to read anything with my old CPU. It's nothing but a
> blur with this new one.  Mostly, I saw red letters and what looked like
> the word "error". 

Record a video of the screen while booting and play it back in slow
motion. It's low tech but it works with all errors, even those from
GRUB ;-)


--
Neil Bothwick

Joystick: (n.) a device essential for performing business tasks and
training exercises esp. favored by pilots, tank commanders, riverboat
          gamblers, and medieval warlords.

attachment0 (849 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Error during boot up.

Dale-46
Neil Bothwick wrote:

> On Thu, 20 Dec 2018 15:13:37 -0600, Dale wrote:
>
>> I don't think it would help.  It's the speed that is the problem. It was
>> almost impossible to read anything with my old CPU. It's nothing but a
>> blur with this new one.  Mostly, I saw red letters and what looked like
>> the word "error". 
> Record a video of the screen while booting and play it back in slow
> motion. It's low tech but it works with all errors, even those from
> GRUB ;-)
>
>


The only video camera I have is one built into my still picture camera. 
I can tell you, it ain't much resolution wise.  It might help but at the
speed things are scrolling up and how basic that camera's video function
is, I don't know.  Might be worth a shot tho. 

What gets me, error or not, the system is running fine.  I haven't
noticed anything not working either.  No clue what it could be.  I got
another part coming in tomorrow so I'll likely have to shutdown in the
next couple days.  I'm just about ready to start rearranging my hard
drives and such.

While at it.  I have most of my hard drives in front of the large 230mm
front fan in my case.  I have a Cooler Master HAF 932.  One drive is up
on the top part, no fan there but it has plenty of air holes and a tiny
amount of air gets sucked in and over the drive(s).  The drive runs at
86F.  My other drives that are in front of that fan runs a little
cooler, 77F.  That little bit warmer won't affect the life of the drive
will it?  From what I've read, some run just fine even when over 100F. 
Just checking.  If needed, I can get a fan mounted in there somehow.  I
have to say, I like the cooling on this case.  Those large fans can move
some air. 

Thanks.

Dale

:-)  :-) 

Reply | Threaded
Open this post in threaded view
|

Re: Error during boot up.

Dale-46
In reply to this post by Dale-46
Dale wrote:
J. Roeleveld wrote:
On December 20, 2018 11:45:29 AM UTC, Dale [hidden email] wrote:
Peter Humphrey wrote:

Next upgrade idea:
- mainboard with NVME slot
- NVME drive for your OS.

Your CPU and memory will be the next bottleneck :)


--
Sent from my Android device with K-9 Mail. Please excuse my brevity.


Yea.  I looked into rebuilding from scratch, less the case of course.  I'm just not sure it would be worth the speed increase.  The biggest things I needed, more drive space and more memory.  The CPU was just on sale.  Hard to beat $75.00 for a 8 core CPU running at over 4GHz.  Right now, it's plenty fast.  I may consider it after I do some other things tho.  I plan to do a emerge -e world before to long.  I wanted to let the new CPU compound sort of get set in. 

I might add, the new video card is way overpowered for what I do.  LOL  Most of the time, it maxes out at about 10% of its power and less than 10% for memory usage.  I really can't tell much difference from my old 220 to this new 650 series.  The biggest difference, the 650 runs much cooler.  I just hope it doesn't get bored and go to sleep.  ;-)  Oh, when I run glxgears at full screen, it still only goes to about 60%.  It warms up a little but not a whole lot.

Now to go see what a NVME drive is.  I don't recall ever hearing of those.  Sounds interesting.

Dale

:-)  :-) 


OMG.  Those things are fast.  Those things make a sata drive look like a snail or something and let's not mention the old IDE drives.  Thing is, I've got a 160GB drive for the OS itself right now.  Even a 256GB one of those isn't to bad price wise.  The OS is really all I'd need on that thing anyway.  The sata drives are plenty fast enough for watching videos etc.  I wonder, how much faster would emerges go on those things?  One wouldn't even need portage's work directory on tmpfs with that. 

Wow!!!

Dale

:-)  :-) 
Reply | Threaded
Open this post in threaded view
|

Re: Error during boot up.

J. Roeleveld
On December 21, 2018 12:27:28 AM UTC, Dale <[hidden email]> wrote:
Dale wrote:
J. Roeleveld wrote:
On December 20, 2018 11:45:29 AM UTC, Dale [hidden email] wrote:
Peter Humphrey wrote:

Next upgrade idea:
- mainboard with NVME slot
- NVME drive for your OS.

Your CPU and memory will be the next bottleneck :)


--
Sent from my Android device with K-9 Mail. Please excuse my brevity.


Yea.  I looked into rebuilding from scratch, less the case of course.  I'm just not sure it would be worth the speed increase.  The biggest things I needed, more drive space and more memory.  The CPU was just on sale.  Hard to beat $75.00 for a 8 core CPU running at over 4GHz.  Right now, it's plenty fast.  I may consider it after I do some other things tho.  I plan to do a emerge -e world before to long.  I wanted to let the new CPU compound sort of get set in. 

I might add, the new video card is way overpowered for what I do.  LOL  Most of the time, it maxes out at about 10% of its power and less than 10% for memory usage.  I really can't tell much difference from my old 220 to this new 650 series.  The biggest difference, the 650 runs much cooler.  I just hope it doesn't get bored and go to sleep.  ;-)  Oh, when I run glxgears at full screen, it still only goes to about 60%.  It warms up a little but not a whole lot.

Now to go see what a NVME drive is.  I don't recall ever hearing of those.  Sounds interesting.

Dale

:-)  :-) 


OMG.  Those things are fast.  Those things make a sata drive look like a snail or something and let's not mention the old IDE drives.  Thing is, I've got a 160GB drive for the OS itself right now.  Even a 256GB one of those isn't to bad price wise.  The OS is really all I'd need on that thing anyway.  The sata drives are plenty fast enough for watching videos etc.  I wonder, how much faster would emerges go on those things?  One wouldn't even need portage's work directory on tmpfs with that. 

Wow!!!

Dale

:-)  :-) 

Considering that they, like all SSDs have a limited write cycle, I only use mine for the compiled software. I still use a tmpfs for compiling.

--
Joost

--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
Reply | Threaded
Open this post in threaded view
|

Re: Error during boot up.

J. Roeleveld
In reply to this post by Dale-46
On December 21, 2018 12:21:35 AM UTC, Dale <[hidden email]> wrote:
Neil Bothwick wrote:
On Thu, 20 Dec 2018 15:13:37 -0600, Dale wrote:

I don't think it would help.  It's the speed that is the problem. It was
almost impossible to read anything with my old CPU. It's nothing but a
blur with this new one.  Mostly, I saw red letters and what looked like
the word "error". 
Record a video of the screen while booting and play it back in slow
motion. It's low tech but it works with all errors, even those from
GRUB ;-)




The only video camera I have is one built into my still picture camera. 
I can tell you, it ain't much resolution wise.  It might help but at the
speed things are scrolling up and how basic that camera's video function
is, I don't know.  Might be worth a shot tho. 

What gets me, error or not, the system is running fine.  I haven't
noticed anything not working either.  No clue what it could be.  I got
another part coming in tomorrow so I'll likely have to shutdown in the
next couple days.  I'm just about ready to start rearranging my hard
drives and such.

While at it.  I have most of my hard drives in front of the large 230mm
front fan in my case.  I have a Cooler Master HAF 932.  One drive is up
on the top part, no fan there but it has plenty of air holes and a tiny
amount of air gets sucked in and over the drive(s).  The drive runs at
86F.  My other drives that are in front of that fan runs a little
cooler, 77F.  That little bit warmer won't affect the life of the drive
will it?  From what I've read, some run just fine even when over 100F. 
Just checking.  If needed, I can get a fan mounted in there somehow.  I
have to say, I like the cooling on this case.  Those large fans can move
some air. 

Thanks.

Dale

:-)  :-) 


Temperature fluctuations are what kills equipment. If the temperature stays constant within the safe range, then it should be fine.

--
Joost
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
Reply | Threaded
Open this post in threaded view
|

Re: Error during boot up.

Peter Humphrey-3
In reply to this post by J. Roeleveld
On Friday, 21 December 2018 08:28:25 GMT J. Roeleveld wrote:

> Considering that they, like all SSDs have a limited write cycle, I only use
> mine for the compiled software. I still use a tmpfs for compiling.

This box has a Samsung SM951 256GB NVMe drive, and it's 21 months old. It runs
BOINC projects 24/7/52 on all CPU 12 cores and is apparently as good as the
day it arrived. I do use a tmpfs for compiling though.

Dale is right - it's astonishingly fast. I read somewhere that its write speed
is 8 times that of an ordinary SSD. Kernel compilation takes just over 2
minutes (2.5 for the 4.19 series). To think that I used to leave the then much
smaller kernel to compile overnight...

I want to fit a couple of ordinary SSDs as well, but I'm snookered by -
countersunk mounting screws! The ones I have stand about 1mm proud, which is
enough to stop the housing sliding home. I know - I should make the effort to
find some better screws.

--
Regards,
Peter.




Reply | Threaded
Open this post in threaded view
|

Re: Error during boot up.

Dale-46
In reply to this post by J. Roeleveld
J. Roeleveld wrote:
On December 21, 2018 12:27:28 AM UTC, Dale [hidden email] wrote:
Dale wrote:
J. Roeleveld wrote:
On December 20, 2018 11:45:29 AM UTC, Dale [hidden email] wrote:
Peter Humphrey wrote:

Next upgrade idea:
- mainboard with NVME slot
- NVME drive for your OS.

Your CPU and memory will be the next bottleneck :)


--
Sent from my Android device with K-9 Mail. Please excuse my brevity.


Yea.  I looked into rebuilding from scratch, less the case of course.  I'm just not sure it would be worth the speed increase.  The biggest things I needed, more drive space and more memory.  The CPU was just on sale.  Hard to beat $75.00 for a 8 core CPU running at over 4GHz.  Right now, it's plenty fast.  I may consider it after I do some other things tho.  I plan to do a emerge -e world before to long.  I wanted to let the new CPU compound sort of get set in. 

I might add, the new video card is way overpowered for what I do.  LOL  Most of the time, it maxes out at about 10% of its power and less than 10% for memory usage.  I really can't tell much difference from my old 220 to this new 650 series.  The biggest difference, the 650 runs much cooler.  I just hope it doesn't get bored and go to sleep.  ;-)  Oh, when I run glxgears at full screen, it still only goes to about 60%.  It warms up a little but not a whole lot.

Now to go see what a NVME drive is.  I don't recall ever hearing of those.  Sounds interesting.

Dale

:-)  :-) 


OMG.  Those things are fast.  Those things make a sata drive look like a snail or something and let's not mention the old IDE drives.  Thing is, I've got a 160GB drive for the OS itself right now.  Even a 256GB one of those isn't to bad price wise.  The OS is really all I'd need on that thing anyway.  The sata drives are plenty fast enough for watching videos etc.  I wonder, how much faster would emerges go on those things?  One wouldn't even need portage's work directory on tmpfs with that. 

Wow!!!

Dale

:-)  :-) 

Considering that they, like all SSDs have a limited write cycle, I only use mine for the compiled software. I still use a tmpfs for compiling.

--
Joost

--
Sent from my Android device with K-9 Mail. Please excuse my brevity.


Yea, good idea.  Forgot about that.  Question.  I update usually once a week here.  With my Mom keeping me busy, sometimes I don't get to do that.  I mostly try to update a day or two after KDE sends a email that there is a big release.  Given that, would the wear and tear on one of these drives be really small?  In other words, one of these drives would last a really long time, right?  If I get one of these, I'd put portage's work directory on tmpfs, /home on another set of drives.  I could even put /var somewhere else since logs change a lot, I guess.  Would that setup reduce wear to the point it would be negligible?  Anything else that would be best elsewhere?

I've read a little, mostly on this list, about them wearing out but I haven't kept up with improvements.  I figure they may have improved them somehow as well. 

That is a neat setup tho.  I have a empty PCI slot that is a X8 I think.  I use the X16 for my video card but the X8 could be used for a second video card or maybe one of these drives.  Either way, those slots are supposed to be very fast with data.  Looking at the pics of them, it seems some need the larger slots, like X8 or X16.  I noticed some would fit on the smaller slots, maybe a X4 or something.  I'd think the X8 drives would be faster than a X4 tho. 

This is a neat idea.  I'm finding it interesting.  It may not be right away but I'm giving this some deep thought here.  The cost is not bad at all.  My current spinning rust OS drive has a lot of hours on it. 

Dale

:-)  :-)
12