onesis-users Mailing List for oneSIS
Brought to you by:
jjengla
Menu
▾
▴
onesis-users — General discussion about oneSIS.
You can subscribe to this list here.
| 2004 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
(9) |
Dec
(1) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2005 |
Jan
|
Feb
(4) |
Mar
|
Apr
(3) |
May
(2) |
Jun
(1) |
Jul
(1) |
Aug
(5) |
Sep
(2) |
Oct
(1) |
Nov
(1) |
Dec
(32) |
| 2006 |
Jan
(2) |
Feb
(26) |
Mar
(2) |
Apr
(13) |
May
(7) |
Jun
(2) |
Jul
(27) |
Aug
(36) |
Sep
(17) |
Oct
(2) |
Nov
|
Dec
(16) |
| 2007 |
Jan
(11) |
Feb
(6) |
Mar
(26) |
Apr
(14) |
May
|
Jun
(2) |
Jul
|
Aug
(17) |
Sep
(3) |
Oct
|
Nov
(12) |
Dec
(15) |
| 2008 |
Jan
(10) |
Feb
(12) |
Mar
(1) |
Apr
|
May
(7) |
Jun
(1) |
Jul
(19) |
Aug
(4) |
Sep
(3) |
Oct
(7) |
Nov
|
Dec
(12) |
| 2009 |
Jan
(7) |
Feb
(6) |
Mar
(22) |
Apr
(19) |
May
(31) |
Jun
(23) |
Jul
(7) |
Aug
(11) |
Sep
(10) |
Oct
(4) |
Nov
(5) |
Dec
(17) |
| 2010 |
Jan
(31) |
Feb
(27) |
Mar
(25) |
Apr
|
May
(10) |
Jun
(6) |
Jul
(4) |
Aug
(11) |
Sep
(10) |
Oct
(8) |
Nov
(6) |
Dec
(6) |
| 2011 |
Jan
|
Feb
(2) |
Mar
(21) |
Apr
(12) |
May
(2) |
Jun
(9) |
Jul
(3) |
Aug
|
Sep
(7) |
Oct
(8) |
Nov
|
Dec
(2) |
| 2012 |
Jan
(18) |
Feb
(14) |
Mar
(11) |
Apr
|
May
|
Jun
|
Jul
(19) |
Aug
(12) |
Sep
(10) |
Oct
(3) |
Nov
(2) |
Dec
|
| 2013 |
Jan
|
Feb
(7) |
Mar
|
Apr
|
May
(24) |
Jun
(19) |
Jul
(17) |
Aug
|
Sep
(20) |
Oct
(12) |
Nov
(8) |
Dec
|
| 2014 |
Jan
|
Feb
(5) |
Mar
(8) |
Apr
(13) |
May
|
Jun
(6) |
Jul
(3) |
Aug
(4) |
Sep
(17) |
Oct
(4) |
Nov
(7) |
Dec
(3) |
| 2015 |
Jan
(1) |
Feb
(2) |
Mar
|
Apr
|
May
(8) |
Jun
|
Jul
(3) |
Aug
|
Sep
(2) |
Oct
(11) |
Nov
|
Dec
(4) |
| 2016 |
Jan
(1) |
Feb
(17) |
Mar
|
Apr
|
May
|
Jun
(8) |
Jul
|
Aug
(14) |
Sep
(18) |
Oct
(3) |
Nov
|
Dec
|
| 2017 |
Jan
|
Feb
(1) |
Mar
(7) |
Apr
|
May
(9) |
Jun
(5) |
Jul
|
Aug
(1) |
Sep
|
Oct
(3) |
Nov
|
Dec
|
| 2018 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(5) |
Dec
|
| 2019 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2020 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2023 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Smith, M. <mat...@ub...> - 2023-07-07 18:04:35
|
Hi there, I’m spamming y’all to see, if given the recent happenings, there is anyone on this list running Debian as the OS for an academic HPC cluster. I’m part of a group, CaRCC people network<https://carcc.org/people-network/systems-facing-track/>, that puts together monthly talks and discussions that take place monthly. We’re looking to secure a topic for our September Systems-facing call, and I’m curious if there is anyone on this list who is in this position and would be comfortable speaking to it. Apologies if this isn’t the right list but I’m just following the Onesis landing pages instructions for a “contact” email 😊 Thank you in advance, -M -- Matthew Smith (He, Him, His<https://equity.ubc.ca/resources/gender-diversity/pronouns/>) Manager, Research Systems Vice President Research & Innovation | Advanced Research Computing The University of British Columbia | Vancouver Campus | Musqueam Traditional Territory Phone 604 827 5138 | Cell 604 671 9470 mat...@ub...<mailto:mat...@ub...> http://www.arc.ubc.ca<http://www.arc.ubc.ca/> |
|
From: Volkmar G. <vol...@un...> - 2020-01-17 12:43:08
|
Hi all, after sticking to a system image for more than 2 years now, it was time to upgrade. While upgrading I noticed that sfdisk behaviour has changed from util-linux-2.26 to util-linux-2.33.2. The current version requires additional spacing between logical partitions to accomodate for partition table information on disk. The attached patch to oneSIS.pm takes 2 blocks away from each logical partition, leaving the gap sfdisk or parted require. It does not include any additional sanity checking. It assumes that partitions will be much larger than 2 blocks and the missing blocks will not make a huge difference. Maybe this patch will be helpful to some others trying to upgrade their systems, too. Best, Volkmar |
|
From: Bobby L. <uls...@gm...> - 2019-01-19 10:57:21
|
Consider Makefile adjustment:
${srcdir}/mk-isoimage-oneSIS to ${srcdir}/contrib/mk-isoimage-oneSIS
Or moving mk-isoimage-oneSIS back to ${srcdir}
That’ll fix one bug.
Also fantastic project!
With Thanks
Bobby
|
|
From: Eric <thi...@ao...> - 2018-11-19 20:30:37
|
It shows one remote NFS location for the root file system (which is r/o) that maps to "/" and 30-40 entries for one remote NFS snapshot location which maps to a r/w directory or file on the blade. e.g., <nfs_server>:/opt/cluster/image/root / <nfs_server>:/opt/cluster/image/snapshot /etc/motd <nfs_server>:/opt/cluster/image/snapshot /var/spool/cron/ <nfs_server>:/opt/cluster/image/snapshot /etc/passwd <nfs_server>:/opt/cluster/image/snapshot /var/log/audit/ ... -----Original Message----- From: Josh England <jj...@gm...> To: think3mm <thi...@ao...> Cc: OneSIS User List <one...@li...> Sent: Mon, Nov 19, 2018 1:27 pm Subject: Re: [oneSIS-users] Modifiying a Diskless NFS Root Without Rebooting What does 'df' look like on your client? -JE On Mon, Nov 19, 2018 at 10:14 AM Eric <thi...@ao...> wrote: I could understand if the directory we want to create the file in was already mounted r/w, but it is not (so where's the cache?). I guess what I'm asking: is there a way to manually replicate the PXE NFSroot mount for a single file outside of the boot process on a running system? Thanks, EM -----Original Message----- From: Josh England <jj...@gm...> To: think3mm <thi...@ao...> Cc: OneSIS User List <one...@li...> Sent: Mon, Nov 19, 2018 12:36 pm Subject: Re: [oneSIS-users] Modifiying a Diskless NFS Root Without Rebooting This is just an NFS mount with normal caching behavior. It should never require a reboot to refresh the client. You can play tricks on the client-side such as calling opendir and closedir on the parent directory of a file to invalidates the NFS cache, but there are also many NFS tunables to play with. Here is a link that might help:https://www.avidandrew.com/understanding-nfs-caching.html -JE On Mon, Nov 19, 2018 at 5:59 AM Eric via oneSIS-users <one...@li...> wrote: Does anyone know under RHEL 6 how to add a single file to a disk-less NFSroot and refresh the client such that the file shows up without rebooting? In our situation, we have several disk-less blades PXE booting from DHCP on that server and also hosts read-only NFS "root" and read/write "snapshot" file systems. The snapshot image spacehas a separate sub-directory for each client (blade) in the cluster, and any file or directory in the snapshot space get mounted read/write to the corresponding root file system for that blade Again, we would like to add a single file to the snapshot r/w space on the server for a given blade, and refresh the NFSroot mount on the client while it's running, without having to reboot. E.g., the image directory on the server, /opt/.image/rhel6_4, might contain entries like:/opt/image/RHEL6_4/snapshot/blade1/etc/motd /opt/image/RHEL6_4/snapshot/blade1/etc/sysconfig /opt/image/RHEL6_4/snapshot/blade1/etc/passwd /opt/image/RHEL6_4/snapshot/blade1/var/log/audit /opt/image/RHEL6_4/snapshot/blade2/etc/motd /opt/image/RHEL6_4/snapshot/blade2/etc/sysconfig /opt/image/RHEL6_4/snapshot/blade2/etc/passwd /opt/image/RHEL6_4/snapshot/blade2/var/log/audit /opt/image/RHEL6_4/root/etc/opt/image/RHEL6_4/root/sbin/opt/image/RHEL6_4/root/dev/opt/image/RHEL6_4/root/usr/opt/image/RHEL6_4/root/var.... Ex., we want to add a file to ./bladeN/snapshot, say:/opt/image/RHEL6_4/snapshot/bladeN/usr/local/etc/visudo ...and mount that to bladeN without rebooting. Is this possible? _______________________________________________ oneSIS-users mailing list one...@li... https://lists.sourceforge.net/lists/listinfo/onesis-users |
|
From: Josh E. <jj...@gm...> - 2018-11-19 18:27:33
|
What does 'df' look like on your client? -JE On Mon, Nov 19, 2018 at 10:14 AM Eric <thi...@ao...> wrote: > I could understand if the directory we want to create the file in was > already mounted r/w, but it is not (so where's the cache?). I guess what > I'm asking: is there a way to manually replicate the PXE NFSroot mount for > a single file outside of the boot process on a running system? > > Thanks, > EM > > > -----Original Message----- > From: Josh England <jj...@gm...> > To: think3mm <thi...@ao...> > Cc: OneSIS User List <one...@li...> > Sent: Mon, Nov 19, 2018 12:36 pm > Subject: Re: [oneSIS-users] Modifiying a Diskless NFS Root Without > Rebooting > > This is just an NFS mount with normal caching behavior. It should never > require a reboot to refresh the client. You can play tricks on the > client-side such as calling opendir and closedir on the parent directory of > a file to invalidates the NFS cache, but there are also many NFS tunables > to play with. Here is a link that might help: > https://www.avidandrew.com/understanding-nfs-caching.html > > -JE > > > On Mon, Nov 19, 2018 at 5:59 AM Eric via oneSIS-users < > one...@li...> wrote: > > Does anyone know under RHEL 6 how to add a single file to a disk-less > NFSroot and refresh the client such that the file shows up without > rebooting? In our situation, we have several disk-less blades PXE booting > from DHCP on that server and also hosts read-only NFS "root" and read/write > "snapshot" file systems. The snapshot image space has a separate > sub-directory for each client (blade) in the cluster, and any *file or > directory* in the snapshot space get mounted read/write to the > corresponding root file system for that blade > > Again, we would like to add a single file to the snapshot r/w space on the > server for a given blade, and refresh the NFSroot mount on the client while > it's running, without having to reboot. > > E.g., the image directory on the server, /opt/.image/rhel6_4, might > contain entries like: > /opt/image/RHEL6_4/snapshot/blade1/etc/motd > /opt/image/RHEL6_4/snapshot/blade1/etc/sysconfig > /opt/image/RHEL6_4/snapshot/blade1/etc/passwd > /opt/image/RHEL6_4/snapshot/blade1/var/log/audit > /opt/image/RHEL6_4/snapshot/blade2/etc/motd > /opt/image/RHEL6_4/snapshot/blade2/etc/sysconfig > /opt/image/RHEL6_4/snapshot/blade2/etc/passwd > /opt/image/RHEL6_4/snapshot/blade2/var/log/audit > /opt/image/RHEL6_4/root/etc > /opt/image/RHEL6_4/root/sbin > /opt/image/RHEL6_4/root/dev > /opt/image/RHEL6_4/root/usr > /opt/image/RHEL6_4/root/var. > . > . > . > > Ex., we want to add a file to ./blade*N*/snapshot, say: > /opt/image/RHEL6_4/snapshot/blade*N*/usr/local/etc/visudo > > ...and mount that to blade*N* without rebooting. Is this possible? > _______________________________________________ > oneSIS-users mailing list > one...@li... > https://lists.sourceforge.net/lists/listinfo/onesis-users > > |
|
From: Eric <thi...@ao...> - 2018-11-19 18:15:01
|
I could understand if the directory we want to create the file in was already mounted r/w, but it is not (so where's the cache?). I guess what I'm asking: is there a way to manually replicate the PXE NFSroot mount for a single file outside of the boot process on a running system? Thanks, EM -----Original Message----- From: Josh England <jj...@gm...> To: think3mm <thi...@ao...> Cc: OneSIS User List <one...@li...> Sent: Mon, Nov 19, 2018 12:36 pm Subject: Re: [oneSIS-users] Modifiying a Diskless NFS Root Without Rebooting This is just an NFS mount with normal caching behavior. It should never require a reboot to refresh the client. You can play tricks on the client-side such as calling opendir and closedir on the parent directory of a file to invalidates the NFS cache, but there are also many NFS tunables to play with. Here is a link that might help:https://www.avidandrew.com/understanding-nfs-caching.html -JE On Mon, Nov 19, 2018 at 5:59 AM Eric via oneSIS-users <one...@li...> wrote: Does anyone know under RHEL 6 how to add a single file to a disk-less NFSroot and refresh the client such that the file shows up without rebooting? In our situation, we have several disk-less blades PXE booting from DHCP on that server and also hosts read-only NFS "root" and read/write "snapshot" file systems. The snapshot image spacehas a separate sub-directory for each client (blade) in the cluster, and any file or directory in the snapshot space get mounted read/write to the corresponding root file system for that blade Again, we would like to add a single file to the snapshot r/w space on the server for a given blade, and refresh the NFSroot mount on the client while it's running, without having to reboot. E.g., the image directory on the server, /opt/.image/rhel6_4, might contain entries like:/opt/image/RHEL6_4/snapshot/blade1/etc/motd /opt/image/RHEL6_4/snapshot/blade1/etc/sysconfig /opt/image/RHEL6_4/snapshot/blade1/etc/passwd /opt/image/RHEL6_4/snapshot/blade1/var/log/audit /opt/image/RHEL6_4/snapshot/blade2/etc/motd /opt/image/RHEL6_4/snapshot/blade2/etc/sysconfig /opt/image/RHEL6_4/snapshot/blade2/etc/passwd /opt/image/RHEL6_4/snapshot/blade2/var/log/audit /opt/image/RHEL6_4/root/etc/opt/image/RHEL6_4/root/sbin/opt/image/RHEL6_4/root/dev/opt/image/RHEL6_4/root/usr/opt/image/RHEL6_4/root/var.... Ex., we want to add a file to ./bladeN/snapshot, say:/opt/image/RHEL6_4/snapshot/bladeN/usr/local/etc/visudo ...and mount that to bladeN without rebooting. Is this possible? _______________________________________________ oneSIS-users mailing list one...@li... https://lists.sourceforge.net/lists/listinfo/onesis-users |
|
From: Josh E. <jj...@gm...> - 2018-11-19 17:36:24
|
This is just an NFS mount with normal caching behavior. It should never require a reboot to refresh the client. You can play tricks on the client-side such as calling opendir and closedir on the parent directory of a file to invalidates the NFS cache, but there are also many NFS tunables to play with. Here is a link that might help: https://www.avidandrew.com/understanding-nfs-caching.html -JE On Mon, Nov 19, 2018 at 5:59 AM Eric via oneSIS-users < one...@li...> wrote: > Does anyone know under RHEL 6 how to add a single file to a disk-less > NFSroot and refresh the client such that the file shows up without > rebooting? In our situation, we have several disk-less blades PXE booting > from DHCP on that server and also hosts read-only NFS "root" and read/write > "snapshot" file systems. The snapshot image space has a separate > sub-directory for each client (blade) in the cluster, and any *file or > directory* in the snapshot space get mounted read/write to the > corresponding root file system for that blade > > Again, we would like to add a single file to the snapshot r/w space on the > server for a given blade, and refresh the NFSroot mount on the client while > it's running, without having to reboot. > > E.g., the image directory on the server, /opt/.image/rhel6_4, might > contain entries like: > /opt/image/RHEL6_4/snapshot/blade1/etc/motd > /opt/image/RHEL6_4/snapshot/blade1/etc/sysconfig > /opt/image/RHEL6_4/snapshot/blade1/etc/passwd > /opt/image/RHEL6_4/snapshot/blade1/var/log/audit > /opt/image/RHEL6_4/snapshot/blade2/etc/motd > /opt/image/RHEL6_4/snapshot/blade2/etc/sysconfig > /opt/image/RHEL6_4/snapshot/blade2/etc/passwd > /opt/image/RHEL6_4/snapshot/blade2/var/log/audit > /opt/image/RHEL6_4/root/etc > /opt/image/RHEL6_4/root/sbin > /opt/image/RHEL6_4/root/dev > /opt/image/RHEL6_4/root/usr > /opt/image/RHEL6_4/root/var. > . > . > . > > Ex., we want to add a file to ./blade*N*/snapshot, say: > /opt/image/RHEL6_4/snapshot/blade*N*/usr/local/etc/visudo > > ...and mount that to blade*N* without rebooting. Is this possible? > _______________________________________________ > oneSIS-users mailing list > one...@li... > https://lists.sourceforge.net/lists/listinfo/onesis-users > |
|
From: Eric <thi...@ao...> - 2018-11-19 13:59:14
|
Does anyone know under RHEL 6 how to add a single file to a disk-less NFSroot and refresh the client such that the file shows up without rebooting? In our situation, we have several disk-less blades PXE booting from DHCP on that server and also hosts read-only NFS "root" and read/write "snapshot" file systems. The snapshot image spacehas a separate sub-directory for each client (blade) in the cluster, and any file or directory in the snapshot space get mounted read/write to the corresponding root file system for that blade Again, we would like to add a single file to the snapshot r/w space on the server for a given blade, and refresh the NFSroot mount on the client while it's running, without having to reboot. E.g., the image directory on the server, /opt/.image/rhel6_4, might contain entries like:/opt/image/RHEL6_4/snapshot/blade1/etc/motd /opt/image/RHEL6_4/snapshot/blade1/etc/sysconfig /opt/image/RHEL6_4/snapshot/blade1/etc/passwd /opt/image/RHEL6_4/snapshot/blade1/var/log/audit /opt/image/RHEL6_4/snapshot/blade2/etc/motd /opt/image/RHEL6_4/snapshot/blade2/etc/sysconfig /opt/image/RHEL6_4/snapshot/blade2/etc/passwd /opt/image/RHEL6_4/snapshot/blade2/var/log/audit /opt/image/RHEL6_4/root/etc/opt/image/RHEL6_4/root/sbin/opt/image/RHEL6_4/root/dev/opt/image/RHEL6_4/root/usr/opt/image/RHEL6_4/root/var.... Ex., we want to add a file to ./bladeN/snapshot, say:/opt/image/RHEL6_4/snapshot/bladeN/usr/local/etc/visudo ...and mount that to bladeN without rebooting. Is this possible? |
|
From: Josh E. <jj...@gm...> - 2017-10-18 16:08:47
|
Good fix. It does look like a newer version of busybox has support for xz compression. I'll add it to a TODO to roll this out. -JE On Wed, Oct 18, 2017 at 9:05 AM, Chris Petty <chr...@du...> wrote: > I uncompressed them all with unxz and regenerated the modules.dep with > depmod -a and my new kernel booted normally > > > On Oct 18, 2017, at 9:44 AM, Chris Petty <chr...@du...> wrote: > > > I did a yum update on my scientific linux 7.3 system which bumped my > kernel from 3.10.0-514.26.2.el7.x86_64 to 3.10.0-693.2.2.el7.x86_64 > > I noticed that all the kernel modules are now coming compressed “.ko.xz” > > When my initram boots up it cannot load any of the new compressed kernel > modules …. is there an update that can handle these compressed modules? > > [root@blade01 ~]# rpm -qf `which mk-initramfs-oneSIS` > oneSIS-2.0.5-1.noarch > > when i’m dropped into a shell, modprobe complains that all the modules are > an invalid format: > *modprobe bnx2* > *modprobe: can’t load module bnx2 ( > kernel/drivers/net/ethernet/broadcom/bnx2.ko.xz ) : invalid module format * > > I suppose i could try to untar all of the modules and regenerate the > modules.dep/modules.dep.bin files > > Thanks, > -Chris > > > ------------------------------------------------------------ > ------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! https://urldefense.proofpoint. > com/v2/url?u=http-3A__sdm.link_slashdot&d=DwICAg&c= > imBPVzF25OnBgGmVOlcsiEgHoG1i6YHLR0Sj_gZ4adc&r=l2_qKcRWmsMf_ > TvdNuSAXgE8pDC1pNZBZdBXT7-7WwE&m=zPkcL29Q9So5t652Ba604EBZazTQhM > 6npmp7XB5bqko&s=gYFfzq88VBQyQEW_F2TGp7guXjM7aE1kwWhQYg9n4uk&e= > > _______________________________________________ > oneSIS-users mailing list > one...@li... > https://urldefense.proofpoint.com/v2/url?u=https-3A__lists. > sourceforge.net_lists_listinfo_onesis-2Dusers&d=DwICAg&c= > imBPVzF25OnBgGmVOlcsiEgHoG1i6YHLR0Sj_gZ4adc&r=l2_qKcRWmsMf_ > TvdNuSAXgE8pDC1pNZBZdBXT7-7WwE&m=zPkcL29Q9So5t652Ba604EBZazTQhM > 6npmp7XB5bqko&s=Fn3jV0zC8rBS6T1PL_oFkjVn9hopM5m2oMJ7uKyGCZY&e= > > > ------------------------------------------------------------ > ------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > oneSIS-users mailing list > one...@li... > https://lists.sourceforge.net/lists/listinfo/onesis-users > > |
|
From: Chris P. <chr...@du...> - 2017-10-18 16:05:32
|
I uncompressed them all with unxz and regenerated the modules.dep with depmod -a and my new kernel booted normally On Oct 18, 2017, at 9:44 AM, Chris Petty <chr...@du...<mailto:chr...@du...>> wrote: I did a yum update on my scientific linux 7.3 system which bumped my kernel from 3.10.0-514.26.2.el7.x86_64 to 3.10.0-693.2.2.el7.x86_64 I noticed that all the kernel modules are now coming compressed “.ko.xz” When my initram boots up it cannot load any of the new compressed kernel modules …. is there an update that can handle these compressed modules? [root@blade01 ~]# rpm -qf `which mk-initramfs-oneSIS` oneSIS-2.0.5-1.noarch when i’m dropped into a shell, modprobe complains that all the modules are an invalid format: modprobe bnx2 modprobe: can’t load module bnx2 ( kernel/drivers/net/ethernet/broadcom/bnx2.ko.xz ) : invalid module format I suppose i could try to untar all of the modules and regenerate the modules.dep/modules.dep.bin files Thanks, -Chris ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org<http://Slashdot.org>! https://urldefense.proofpoint.com/v2/url?u=http-3A__sdm.link_slashdot&d=DwICAg&c=imBPVzF25OnBgGmVOlcsiEgHoG1i6YHLR0Sj_gZ4adc&r=l2_qKcRWmsMf_TvdNuSAXgE8pDC1pNZBZdBXT7-7WwE&m=zPkcL29Q9So5t652Ba604EBZazTQhM6npmp7XB5bqko&s=gYFfzq88VBQyQEW_F2TGp7guXjM7aE1kwWhQYg9n4uk&e= _______________________________________________ oneSIS-users mailing list one...@li...<mailto:one...@li...> https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.sourceforge.net_lists_listinfo_onesis-2Dusers&d=DwICAg&c=imBPVzF25OnBgGmVOlcsiEgHoG1i6YHLR0Sj_gZ4adc&r=l2_qKcRWmsMf_TvdNuSAXgE8pDC1pNZBZdBXT7-7WwE&m=zPkcL29Q9So5t652Ba604EBZazTQhM6npmp7XB5bqko&s=Fn3jV0zC8rBS6T1PL_oFkjVn9hopM5m2oMJ7uKyGCZY&e= |
|
From: Chris P. <chr...@du...> - 2017-10-18 13:44:43
|
I did a yum update on my scientific linux 7.3 system which bumped my kernel from 3.10.0-514.26.2.el7.x86_64 to 3.10.0-693.2.2.el7.x86_64 I noticed that all the kernel modules are now coming compressed “.ko.xz” When my initram boots up it cannot load any of the new compressed kernel modules …. is there an update that can handle these compressed modules? [root@blade01 ~]# rpm -qf `which mk-initramfs-oneSIS` oneSIS-2.0.5-1.noarch when i’m dropped into a shell, modprobe complains that all the modules are an invalid format: modprobe bnx2 modprobe: can’t load module bnx2 ( kernel/drivers/net/ethernet/broadcom/bnx2.ko.xz ) : invalid module format I suppose i could try to untar all of the modules and regenerate the modules.dep/modules.dep.bin files Thanks, -Chris |
|
From: Administrator H. <hp...@me...> - 2017-08-18 12:45:38
|
Hello, could someone please help me port oneSIS 2.0.5 to Centos7? -- Best regards, Artur Kańczugowski |
|
From: Josh E. <jj...@gm...> - 2017-06-07 16:04:41
|
I think you'll probably still have to use some custom logic in the
initramfs to set up the vlans the way you want to.
-JE
On Wed, Jun 7, 2017 at 8:24 AM, Chris Petty <chr...@du...> wrote:
>
> Since apparently i’m not going to be running receiving info via DHCP
> anymore within the oneSIS bootup, is there a straightforward mechanism to
> apply a VLAN ( vconfig ) once oneSIS brings up my network connections and
> bonds them?
>
> I had edited mk-initramfs and the init script in my own template to handle
> this during initial boot up, but that doesn’t seem as necessary anymore
> since i won’t need to VLAN tag to get a DHCP offer.
>
>
> I was having to add a tag on to my dhcp devices, then remove it … then add
> it on to my bond for a subset of machine.
>
> if [ -n "$vlan" ]; then
> tagging_loaded=`lsmod |grep 8021q`
> if [ -z "$tagging_loaded" ]; then
> log echo "oneSIS: loading 8021q module for tagging"
> log modprobe 8021q
> fi
> vlandev=`echo "${dhcp_interface}.${vlan}"`
> log echo "oneSIS: setting up VLAN with tag $vlan on
> $dhcp_interface for DHCP request"
> log vconfig add ${dhcp_interface} $vlan
> log ifconfig ${dhcp_interface} 0.0.0.0 up
> interfaces=$vlandev
> sleep 3
> fi
>
> ...
>
> if [ -n "$vlan" ]; then
> log echo "oneSIS: setting up VLAN with tag $vlan on bond0"
> log vconfig add bond0 $vlan
> log ifconfig "bond0.${vlan}" $IPADDR $NETMASK_ARG
> $BROADCAST_ARG
> log ifconfig bond0 0.0.0.0
> sleep 3
> log ifconfig bond0 up
> fi
>
>
>
>
>
>
> On Jun 7, 2017, at 10:09 AM, Josh England <jj...@gm...> wrote:
>
> That is interesting. Good job finding the root cause.
>
> -JE
>
> On Jun 7, 2017 6:57 AM, "Chris Petty" <chr...@du...> wrote:
>
>>
>> I found that after the recent kernel updates to 6.9, or while trying to
>> boot 7.3 i had to alter my pxe setup to pass along the nfs location within
>> pxe, rather than in my dhcp server:
>> "root=10.12.128.4:/cluster/sl7”
>>
>> Nothing i tried with dhcp ( version 4.2.5 ) sent along the "root-path”
>> option that i've always used, which lead to not booting properly and
>> dropping into a shell.
>>
>> After passing root via pxe, i am able to get my 7.3 image booted, with
>> ramdisk.
>>
>> -Chris
>>
>>
>> > On Jun 2, 2017, at 3:49 PM, Chris Petty <chr...@du...> wrote:
>> >
>> >
>> > After a recent update from scientific-linux from 6.8 -> 6.9 oneSIS
>> would no longer make the RAMDISK at boot.
>> >
>> > I could get my initramfs booted, however no /dev/ram* existed and
>> therefore nothing in my image really worked. After a day of debugging i
>> reverted back to version 6.8 ( using the redhat-el-6.2 patch ).
>> >
>> > I’m now in the process of trying to get a SL 7.3 image ( using the
>> redhat-sl-7 patch ) built and am running into the same issues. No RAMDISK
>> is built, therefore nothing is really working properly.
>> >
>> > Also, after the update ( and with 7.3 ), my hostname info from dhcp
>> doesn’t seem to be working. /proc/cmdline is the same as it was in 6.8
>> and my 6.8 image boots normally.
>> >
>> > Anyone successfully booting RH based 7 images?
>> >
>> > Thanks,
>> > Chris
>> > ------------------------------------------------------------
>> ------------------
>> > Check out the vibrant tech community on one of the world's most
>> > engaging tech sites, Slashdot.org! https://urldefense.proofpoint.
>> com/v2/url?u=http-3A__sdm.link_slashdot&d=DwIGaQ&c=imBPVzF25
>> OnBgGmVOlcsiEgHoG1i6YHLR0Sj_gZ4adc&r=l2_qKcRWmsMf_TvdNuSAX
>> gE8pDC1pNZBZdBXT7-7WwE&m=ZUOz-xW4QjovTMVq2eFn-6By-
>> xspLb0WGyvqEUiBaKI&s=1mRKjtykJFJ9N9SuWYFV3JQPiL9Fu2b-9yLqlE7afsQ&e=
>> > _______________________________________________
>> > oneSIS-users mailing list
>> > one...@li...
>> > https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.s
>> ourceforge.net_lists_listinfo_onesis-2Dusers&d=DwIGaQ&c=imBP
>> VzF25OnBgGmVOlcsiEgHoG1i6YHLR0Sj_gZ4adc&r=l2_qKcRWmsMf_TvdNu
>> SAXgE8pDC1pNZBZdBXT7-7WwE&m=ZUOz-xW4QjovTMVq2eFn-6By-
>> xspLb0WGyvqEUiBaKI&s=SiPH4ZbZJXX0m2hwKUTermYK1PCpA-WcDOT5ixPhEUg&e=
>>
>> ------------------------------------------------------------
>> ------------------
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>> <https://urldefense.proofpoint.com/v2/url?u=http-3A__sdm.link_slashdot&d=DwMFaQ&c=imBPVzF25OnBgGmVOlcsiEgHoG1i6YHLR0Sj_gZ4adc&r=l2_qKcRWmsMf_TvdNuSAXgE8pDC1pNZBZdBXT7-7WwE&m=jTDmReQGY8FnwHGGvmDuK347v8RxgLljliG-aLTEA1Y&s=S3Zol5oG9OUJebj2YOho2wrtX5V5-7xVnSgaY-mlT-A&e=>
>> _______________________________________________
>> oneSIS-users mailing list
>> one...@li...
>> https://lists.sourceforge.net/lists/listinfo/onesis-users
>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.sourceforge.net_lists_listinfo_onesis-2Dusers&d=DwMFaQ&c=imBPVzF25OnBgGmVOlcsiEgHoG1i6YHLR0Sj_gZ4adc&r=l2_qKcRWmsMf_TvdNuSAXgE8pDC1pNZBZdBXT7-7WwE&m=jTDmReQGY8FnwHGGvmDuK347v8RxgLljliG-aLTEA1Y&s=qx84olHUyESp73nmTybfDoA5UZg-oJ9wqTYmr0dQgAE&e=>
>>
>
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> oneSIS-users mailing list
> one...@li...
> https://lists.sourceforge.net/lists/listinfo/onesis-users
>
>
|
|
From: Chris P. <chr...@du...> - 2017-06-07 15:24:17
|
Since apparently i’m not going to be running receiving info via DHCP anymore within the oneSIS bootup, is there a straightforward mechanism to apply a VLAN ( vconfig ) once oneSIS brings up my network connections and bonds them?
I had edited mk-initramfs and the init script in my own template to handle this during initial boot up, but that doesn’t seem as necessary anymore since i won’t need to VLAN tag to get a DHCP offer.
I was having to add a tag on to my dhcp devices, then remove it … then add it on to my bond for a subset of machine.
if [ -n "$vlan" ]; then
tagging_loaded=`lsmod |grep 8021q`
if [ -z "$tagging_loaded" ]; then
log echo "oneSIS: loading 8021q module for tagging"
log modprobe 8021q
fi
vlandev=`echo "${dhcp_interface}.${vlan}"`
log echo "oneSIS: setting up VLAN with tag $vlan on $dhcp_interface for DHCP request"
log vconfig add ${dhcp_interface} $vlan
log ifconfig ${dhcp_interface} 0.0.0.0 up
interfaces=$vlandev
sleep 3
fi
...
if [ -n "$vlan" ]; then
log echo "oneSIS: setting up VLAN with tag $vlan on bond0"
log vconfig add bond0 $vlan
log ifconfig "bond0.${vlan}" $IPADDR $NETMASK_ARG $BROADCAST_ARG
log ifconfig bond0 0.0.0.0
sleep 3
log ifconfig bond0 up
fi
On Jun 7, 2017, at 10:09 AM, Josh England <jj...@gm...<mailto:jj...@gm...>> wrote:
That is interesting. Good job finding the root cause.
-JE
On Jun 7, 2017 6:57 AM, "Chris Petty" <chr...@du...<mailto:chr...@du...>> wrote:
I found that after the recent kernel updates to 6.9, or while trying to boot 7.3 i had to alter my pxe setup to pass along the nfs location within pxe, rather than in my dhcp server:
"root=10.12.128.4:/cluster/sl7”
Nothing i tried with dhcp ( version 4.2.5 ) sent along the "root-path” option that i've always used, which lead to not booting properly and dropping into a shell.
After passing root via pxe, i am able to get my 7.3 image booted, with ramdisk.
-Chris
> On Jun 2, 2017, at 3:49 PM, Chris Petty <chr...@du...<mailto:chr...@du...>> wrote:
>
>
> After a recent update from scientific-linux from 6.8 -> 6.9 oneSIS would no longer make the RAMDISK at boot.
>
> I could get my initramfs booted, however no /dev/ram* existed and therefore nothing in my image really worked. After a day of debugging i reverted back to version 6.8 ( using the redhat-el-6.2 patch ).
>
> I’m now in the process of trying to get a SL 7.3 image ( using the redhat-sl-7 patch ) built and am running into the same issues. No RAMDISK is built, therefore nothing is really working properly.
>
> Also, after the update ( and with 7.3 ), my hostname info from dhcp doesn’t seem to be working. /proc/cmdline is the same as it was in 6.8 and my 6.8 image boots normally.
>
> Anyone successfully booting RH based 7 images?
>
> Thanks,
> Chris
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org<http://Slashdot.org>! https://urldefense.proofpoint.com/v2/url?u=http-3A__sdm.link_slashdot&d=DwIGaQ&c=imBPVzF25OnBgGmVOlcsiEgHoG1i6YHLR0Sj_gZ4adc&r=l2_qKcRWmsMf_TvdNuSAXgE8pDC1pNZBZdBXT7-7WwE&m=ZUOz-xW4QjovTMVq2eFn-6By-xspLb0WGyvqEUiBaKI&s=1mRKjtykJFJ9N9SuWYFV3JQPiL9Fu2b-9yLqlE7afsQ&e=
> _______________________________________________
> oneSIS-users mailing list
> one...@li...<mailto:one...@li...>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.sourceforge.net_lists_listinfo_onesis-2Dusers&d=DwIGaQ&c=imBPVzF25OnBgGmVOlcsiEgHoG1i6YHLR0Sj_gZ4adc&r=l2_qKcRWmsMf_TvdNuSAXgE8pDC1pNZBZdBXT7-7WwE&m=ZUOz-xW4QjovTMVq2eFn-6By-xspLb0WGyvqEUiBaKI&s=SiPH4ZbZJXX0m2hwKUTermYK1PCpA-WcDOT5ixPhEUg&e=
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org<http://Slashdot.org>! http://sdm.link/slashdot<https://urldefense.proofpoint.com/v2/url?u=http-3A__sdm.link_slashdot&d=DwMFaQ&c=imBPVzF25OnBgGmVOlcsiEgHoG1i6YHLR0Sj_gZ4adc&r=l2_qKcRWmsMf_TvdNuSAXgE8pDC1pNZBZdBXT7-7WwE&m=jTDmReQGY8FnwHGGvmDuK347v8RxgLljliG-aLTEA1Y&s=S3Zol5oG9OUJebj2YOho2wrtX5V5-7xVnSgaY-mlT-A&e=>
_______________________________________________
oneSIS-users mailing list
one...@li...<mailto:one...@li...>
https://lists.sourceforge.net/lists/listinfo/onesis-users<https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.sourceforge.net_lists_listinfo_onesis-2Dusers&d=DwMFaQ&c=imBPVzF25OnBgGmVOlcsiEgHoG1i6YHLR0Sj_gZ4adc&r=l2_qKcRWmsMf_TvdNuSAXgE8pDC1pNZBZdBXT7-7WwE&m=jTDmReQGY8FnwHGGvmDuK347v8RxgLljliG-aLTEA1Y&s=qx84olHUyESp73nmTybfDoA5UZg-oJ9wqTYmr0dQgAE&e=>
|
|
From: Josh E. <jj...@gm...> - 2017-06-07 14:09:59
|
That is interesting. Good job finding the root cause. -JE On Jun 7, 2017 6:57 AM, "Chris Petty" <chr...@du...> wrote: > > I found that after the recent kernel updates to 6.9, or while trying to > boot 7.3 i had to alter my pxe setup to pass along the nfs location within > pxe, rather than in my dhcp server: > "root=10.12.128.4:/cluster/sl7” > > Nothing i tried with dhcp ( version 4.2.5 ) sent along the "root-path” > option that i've always used, which lead to not booting properly and > dropping into a shell. > > After passing root via pxe, i am able to get my 7.3 image booted, with > ramdisk. > > -Chris > > > > On Jun 2, 2017, at 3:49 PM, Chris Petty <chr...@du...> wrote: > > > > > > After a recent update from scientific-linux from 6.8 -> 6.9 oneSIS would > no longer make the RAMDISK at boot. > > > > I could get my initramfs booted, however no /dev/ram* existed and > therefore nothing in my image really worked. After a day of debugging i > reverted back to version 6.8 ( using the redhat-el-6.2 patch ). > > > > I’m now in the process of trying to get a SL 7.3 image ( using the > redhat-sl-7 patch ) built and am running into the same issues. No RAMDISK > is built, therefore nothing is really working properly. > > > > Also, after the update ( and with 7.3 ), my hostname info from dhcp > doesn’t seem to be working. /proc/cmdline is the same as it was in 6.8 > and my 6.8 image boots normally. > > > > Anyone successfully booting RH based 7 images? > > > > Thanks, > > Chris > > ------------------------------------------------------------ > ------------------ > > Check out the vibrant tech community on one of the world's most > > engaging tech sites, Slashdot.org! https://urldefense.proofpoint. > com/v2/url?u=http-3A__sdm.link_slashdot&d=DwIGaQ&c= > imBPVzF25OnBgGmVOlcsiEgHoG1i6YHLR0Sj_gZ4adc&r=l2_qKcRWmsMf_ > TvdNuSAXgE8pDC1pNZBZdBXT7-7WwE&m=ZUOz-xW4QjovTMVq2eFn- > 6By-xspLb0WGyvqEUiBaKI&s=1mRKjtykJFJ9N9SuWYFV3JQPiL9Fu2b-9yLqlE7afsQ&e= > > _______________________________________________ > > oneSIS-users mailing list > > one...@li... > > https://urldefense.proofpoint.com/v2/url?u=https-3A__lists. > sourceforge.net_lists_listinfo_onesis-2Dusers&d=DwIGaQ&c= > imBPVzF25OnBgGmVOlcsiEgHoG1i6YHLR0Sj_gZ4adc&r=l2_qKcRWmsMf_ > TvdNuSAXgE8pDC1pNZBZdBXT7-7WwE&m=ZUOz-xW4QjovTMVq2eFn- > 6By-xspLb0WGyvqEUiBaKI&s=SiPH4ZbZJXX0m2hwKUTermYK1PCpA-WcDOT5ixPhEUg&e= > > ------------------------------------------------------------ > ------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > oneSIS-users mailing list > one...@li... > https://lists.sourceforge.net/lists/listinfo/onesis-users > |
|
From: Chris P. <chr...@du...> - 2017-06-07 13:56:53
|
I found that after the recent kernel updates to 6.9, or while trying to boot 7.3 i had to alter my pxe setup to pass along the nfs location within pxe, rather than in my dhcp server: "root=10.12.128.4:/cluster/sl7” Nothing i tried with dhcp ( version 4.2.5 ) sent along the "root-path” option that i've always used, which lead to not booting properly and dropping into a shell. After passing root via pxe, i am able to get my 7.3 image booted, with ramdisk. -Chris > On Jun 2, 2017, at 3:49 PM, Chris Petty <chr...@du...> wrote: > > > After a recent update from scientific-linux from 6.8 -> 6.9 oneSIS would no longer make the RAMDISK at boot. > > I could get my initramfs booted, however no /dev/ram* existed and therefore nothing in my image really worked. After a day of debugging i reverted back to version 6.8 ( using the redhat-el-6.2 patch ). > > I’m now in the process of trying to get a SL 7.3 image ( using the redhat-sl-7 patch ) built and am running into the same issues. No RAMDISK is built, therefore nothing is really working properly. > > Also, after the update ( and with 7.3 ), my hostname info from dhcp doesn’t seem to be working. /proc/cmdline is the same as it was in 6.8 and my 6.8 image boots normally. > > Anyone successfully booting RH based 7 images? > > Thanks, > Chris > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! https://urldefense.proofpoint.com/v2/url?u=http-3A__sdm.link_slashdot&d=DwIGaQ&c=imBPVzF25OnBgGmVOlcsiEgHoG1i6YHLR0Sj_gZ4adc&r=l2_qKcRWmsMf_TvdNuSAXgE8pDC1pNZBZdBXT7-7WwE&m=ZUOz-xW4QjovTMVq2eFn-6By-xspLb0WGyvqEUiBaKI&s=1mRKjtykJFJ9N9SuWYFV3JQPiL9Fu2b-9yLqlE7afsQ&e= > _______________________________________________ > oneSIS-users mailing list > one...@li... > https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.sourceforge.net_lists_listinfo_onesis-2Dusers&d=DwIGaQ&c=imBPVzF25OnBgGmVOlcsiEgHoG1i6YHLR0Sj_gZ4adc&r=l2_qKcRWmsMf_TvdNuSAXgE8pDC1pNZBZdBXT7-7WwE&m=ZUOz-xW4QjovTMVq2eFn-6By-xspLb0WGyvqEUiBaKI&s=SiPH4ZbZJXX0m2hwKUTermYK1PCpA-WcDOT5ixPhEUg&e= |
|
From: Chris P. <chr...@du...> - 2017-06-02 19:50:02
|
After a recent update from scientific-linux from 6.8 -> 6.9 oneSIS would no longer make the RAMDISK at boot. I could get my initramfs booted, however no /dev/ram* existed and therefore nothing in my image really worked. After a day of debugging i reverted back to version 6.8 ( using the redhat-el-6.2 patch ). I’m now in the process of trying to get a SL 7.3 image ( using the redhat-sl-7 patch ) built and am running into the same issues. No RAMDISK is built, therefore nothing is really working properly. Also, after the update ( and with 7.3 ), my hostname info from dhcp doesn’t seem to be working. /proc/cmdline is the same as it was in 6.8 and my 6.8 image boots normally. Anyone successfully booting RH based 7 images? Thanks, Chris |
|
From: Josh E. <jj...@gm...> - 2017-05-22 15:55:50
|
Robin,
Thanks for the exceptional feedback! I hadn't run into your case with
overlayfs yet but I'm sure it would have come up eventually. Completely
disabling cache in the upper of overlayfs seems like a perfectly valid fix
for this case.
I haven't played around with copying up files into the upper layer in the
way you mention. I suppose the RAMDIR and RAMFILE options could
potentially be overloaded to do a copy up when overlay mode is enabled.
This would save having to create a lot of symlinks on the filesystem but it
would require mk-sysimage to have to make assumptions about whether all
clients would run in overlay mode or not. Another (less integrated)
solution could be to just do the copy up from a script run from rc.local or
similar.
-JE
On Mon, May 22, 2017 at 7:42 AM, Robin Humble <rjh...@ci...>
wrote:
> Hi Josh,
>
> On Wed, Mar 01, 2017 at 09:42:05AM -0800, Josh England wrote:
> >Try playing around with the new RAM overlay options (built into
> >mk-initramfs-oneSIS, but you could clone the logic for dracut). It
>
> I'm really liking overlayfs. it makes things easier and tidier.
> looks like the future to me. I also like how you arranged the upper
> and lower dirs so we can still see them whilst we use the merged root.
>
> however (of course there had to be a 'however' :-) I don't have the
> same success with the ovl_revalidate patch as you do. mostly it works,
> but an important exception is files that are deleted (or accessed
> before they exist) and then re-created in the lower dir - they never
> re-appear in the merged view. rsync uses this technique (unless you use
> --inplace), so it's not uncommon. eg.
>
> setup
> server # # export an empty /export dir to client
> client # mount -t nfs server:/export /mnt/nfs
> client # mount -t tmpfs -o seclabel,mode=0755 /dev/ram /mnt/ram
> client # mkdir /mnt/ram/{upperdir,workdir} /mnt/merged
> client # mount -t overlay overlay -olowerdir=/mnt/nfs,upperdir=/
> mnt/ram/upperdir,workdir=/mnt/ram/workdir /mnt/merged
>
> and then
> client # cat /mnt/merged/hello
> cat: /mnt/merged/hello: No such file or directory # the expected result
> server # echo hello > /export/hello
> client # cat /mnt/merged/hello
> cat: /mnt/merged/hello: No such file or directory # wrong
>
> or
> server # echo blah > /export/blah
> client # cat /mnt/merged/blah
> blah
> server # rsync -avPxH /export/hello /export/blah
> client # cat /mnt/merged/blah
> cat: /mnt/merged/blah: Stale file handle # wrong, although works with
> nfsv3 instead of v4
>
> much the same thing happens with lustre as a lowerdir or local fs's
> (forced to remote=true in super.c for the sake of testing). nfsv3,
> nfsv4, lustre and the local fs mockups behave a tad differently, but
> the basic problem seems common to all.
>
> after a bit of playing, I found that overlayfs works fine if I change
> fs/overlayfs/super.c to simply ->
>
> static int ovl_dentry_revalidate(struct dentry *dentry, unsigned int flags)
> {
> return 0;
> }
>
> AFAICT this effectively turns off all inode caching in overylayfs.
> the VFS just scraps the dentry and re-issues a lookup(). seems a bit
> violent, but I don't know enough to make it more subtle.
>
> the lower (gloabl) fs inodes are still fully cached on clients, just
> the overlayfs layer isn't. as our upper is on tmpfs, overlayfs
> performance will be pretty much the same as now. return=0 is too lame
> for a general fix, but for our use case, I haven't yet thought of a
> real down side.
>
> oneSIS with overlayfs now works well for me.
> it was fun to shrink /ram to 20kb as it's got no files in it now, only
> symlinks :)
>
> BTW have you experimented with copying 'hot' files to the upper layer?
> with centos6 I put /lib64 and /sbin and /bin into a ramdisk for
> performance reasons (it took ~1/2 the iops off the lustre metadata
> server), but with centos7 + overlayfs maybe this sort of tweaking can
> be more fine grained?
>
> cheers,
> robin
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> oneSIS-users mailing list
> one...@li...
> https://lists.sourceforge.net/lists/listinfo/onesis-users
>
|
|
From: Robin H. <rjh...@ci...> - 2017-05-22 15:02:08
|
Hi Josh,
On Wed, Mar 01, 2017 at 09:42:05AM -0800, Josh England wrote:
>Try playing around with the new RAM overlay options (built into
>mk-initramfs-oneSIS, but you could clone the logic for dracut). It
I'm really liking overlayfs. it makes things easier and tidier.
looks like the future to me. I also like how you arranged the upper
and lower dirs so we can still see them whilst we use the merged root.
however (of course there had to be a 'however' :-) I don't have the
same success with the ovl_revalidate patch as you do. mostly it works,
but an important exception is files that are deleted (or accessed
before they exist) and then re-created in the lower dir - they never
re-appear in the merged view. rsync uses this technique (unless you use
--inplace), so it's not uncommon. eg.
setup
server # # export an empty /export dir to client
client # mount -t nfs server:/export /mnt/nfs
client # mount -t tmpfs -o seclabel,mode=0755 /dev/ram /mnt/ram
client # mkdir /mnt/ram/{upperdir,workdir} /mnt/merged
client # mount -t overlay overlay -olowerdir=/mnt/nfs,upperdir=/mnt/ram/upperdir,workdir=/mnt/ram/workdir /mnt/merged
and then
client # cat /mnt/merged/hello
cat: /mnt/merged/hello: No such file or directory # the expected result
server # echo hello > /export/hello
client # cat /mnt/merged/hello
cat: /mnt/merged/hello: No such file or directory # wrong
or
server # echo blah > /export/blah
client # cat /mnt/merged/blah
blah
server # rsync -avPxH /export/hello /export/blah
client # cat /mnt/merged/blah
cat: /mnt/merged/blah: Stale file handle # wrong, although works with nfsv3 instead of v4
much the same thing happens with lustre as a lowerdir or local fs's
(forced to remote=true in super.c for the sake of testing). nfsv3,
nfsv4, lustre and the local fs mockups behave a tad differently, but
the basic problem seems common to all.
after a bit of playing, I found that overlayfs works fine if I change
fs/overlayfs/super.c to simply ->
static int ovl_dentry_revalidate(struct dentry *dentry, unsigned int flags)
{
return 0;
}
AFAICT this effectively turns off all inode caching in overylayfs.
the VFS just scraps the dentry and re-issues a lookup(). seems a bit
violent, but I don't know enough to make it more subtle.
the lower (gloabl) fs inodes are still fully cached on clients, just
the overlayfs layer isn't. as our upper is on tmpfs, overlayfs
performance will be pretty much the same as now. return=0 is too lame
for a general fix, but for our use case, I haven't yet thought of a
real down side.
oneSIS with overlayfs now works well for me.
it was fun to shrink /ram to 20kb as it's got no files in it now, only
symlinks :)
BTW have you experimented with copying 'hot' files to the upper layer?
with centos6 I put /lib64 and /sbin and /bin into a ramdisk for
performance reasons (it took ~1/2 the iops off the lustre metadata
server), but with centos7 + overlayfs maybe this sort of tweaking can
be more fine grained?
cheers,
robin
|
|
From: Josh E. <jj...@gm...> - 2017-05-02 23:05:18
|
A few more quick notes: LINKFILE does not really make sense for directories. Having multiple directives per directory does not do anything (the later one wins). Having a LINKDIR nested under another LINKDIR is probable not what you want. Copying the current contents of /tmp and /var/log to /ram is probably not needed, so you don't need the '-d' in those cases. You don't need '-c compute' for each directive since that is your only class anyway. Plus it might bite you when you want more versions of /etc/fstab but that directive only gets applied to compute nodes. NBD Here's a simplification of your config: DISTRO: redhat-el 7 NODECLASS_REGEXP: mcs64\d+ compute RAMSIZE: 4g LINKDIR: /tmp LINKDIR: /var/log LINKDIR: /var/run -d LINKDIR: /var/lock -d LINKBACK: /etc/fstab CLASS -JE On Tue, May 2, 2017 at 11:49 AM, ROSS, MARK D CTR USAF AFMC 412 RANS/ENR < mar...@us...> wrote: > HI > New oneSIS user hoping to ask a couple of dumb questions here.. > We have been using Scientific linux 6.7 on bootable DVD's for quite a > while now and are now moving to Scientific Linux 7.3 I am hoping to get > away from the DVD's. > I was hoping to use oneSIS to get off the DVD's. Our systems are quite > simple with 4 linux computers in a rack, each computer uses an identical > software setup with DHCP providing any unique information. > > On my diskless computer I am able to PXE boot and nfs mount its file > system but I am getting a lot of errors as the systems boots, Most likely > related to a read only file system. I have tried several different > /etc/sysimage.cfg configurations to make /var/ linked to /ram but each time > I boot the /ram dir is empty. Can anyone tell me what I might be doing > wrong ? Shouldn't /ram have the run, lock directories ? > > Here is my changes to the /etc/sysimage.cfg config contents > DISTRO: redhat-el 7 > NODECLASS_REGEXP: mcs64\d+ compute > RAMSIZE: 4g -c compute > RAMDIR: /var -d -c compute > LINKDIR: /var -d -c compute > LINKDIR: /var/run -d -c compute > LINKDIR: /var/lock -d -c compute > LINKDIR: /tmp -d -c compute > LINKFILE: /var/run -d -c compute > LINKFILE: /var/log -d -c compute > LINKFILE: /var/lock -d -c compute > LINKFILE: /tmp -d -c compute > LINKBACK: /etc/fstab CLASS -c compute > > Then on the computer that has the disk image > mk-sysimage -c /etc/sysimage.conf /var/lib/oneSIS/image > > thanks for any help. > > > > ------------------------------------------------------------ > ------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > oneSIS-users mailing list > one...@li... > https://lists.sourceforge.net/lists/listinfo/onesis-users > |
|
From: Josh E. <jj...@gm...> - 2017-05-02 21:34:11
|
Yes, I'm not sure why /ram isn't populated. Can you log into the system at
all?
If so, check the output of 'df' for a ramdisk mounted on /ram, then try
running 'update-node -r' and see what it does.
-JE
On Tue, May 2, 2017 at 2:23 PM, ROSS, MARK D CTR USAF AFMC 412 RANS/ENR <
mar...@us...> wrote:
> >>Try altering your etc/systemd/system.conf to enable console logging on
> bootup.
> >>Set DefaultStandardOutput=journal+console then reboot. You should
> get much more output which might help point out what's going on.
>
> >>-JE
>
> Ok, I see errors about /var file system. My /var is linked to /ram but
> there is still no files in /ram, I would expect to see all the
> /var/log/messages in there ???
>
>
> [ 6.518771] hidraw: raw HID events driver (C) Jiri Kosina
> [ 6.518946] usbcore: registered new interface driver usbhid
> [ 6.518947] usbhid: USB HID core driver
> [ 6.519052] drop_monitor: Initializing network drop monitor service
> [ 6.519265] TCP: cubic registered
> [ 6.519270] Initializing XFRM netlink socket
> [ 6.519512] NET: Registered protocol family 10
> [ 6.520087] NET: Registered protocol family 17
> [ 6.523692] microcode: CPU0 sig=0x206d7, pf=0x1, revision=0x710
> [ 6.523705] microcode: CPU1 sig=0x206d7, pf=0x1, revision=0x710
> [ 6.523714] microcode: CPU2 sig=0x206d7, pf=0x1, revision=0x710
> [ 6.523725] microcode: CPU3 sig=0x206d7, pf=0x1, revision=0x710
> [ 6.523742] microcode: CPU4 sig=0x206d7, pf=0x1, revision=0x710
> [ 6.523761] microcode: CPU5 sig=0x206d7, pf=0x1, revision=0x710
> [ 6.523768] microcode: CPU6 sig=0x206d7, pf=0x1, revision=0x710
> [ 6.523779] microcode: CPU7 sig=0x206d7, pf=0x1, revision=0x710
> [ 6.523790] microcode: CPU8 sig=0x206d7, pf=0x1, revision=0x710
> [ 6.523802] microcode: CPU9 sig=0x206d7, pf=0x1, revision=0x710
> [ 6.523814] microcode: CPU10 sig=0x206d7, pf=0x1, revision=0x710
> [ 6.523825] microcode: CPU11 sig=0x206d7, pf=0x1, revision=0x710
> [ 6.523922] microcode: Microcode Update Driver: v2.01 <
> ti...@ai...>, Peter Oruba
> [ 6.524212] Loading compiled-in X.509 certificates
> [ 6.526085] Loaded X.509 cert 'Fermi National Accelerator Laboratory:
> Scientific Linux 7 kpatch signing key: c8e46da25bf2b6ed33675277e795de
> 682b4666d6'
> [ 6.527851] Loaded X.509 cert 'Fermi National Accelerator Laboratory:
> Scientific Linux 7 driver update signing key: 98ec7b1456fb6a6b00e81292343a0f
> f7268df'
> [ 6.528907] Loaded X.509 cert 'Red Hat Enterprise Linux kernel signing
> key: 02c33df7a9cd1651f844f720041963da33995e99'
> [ 6.528922] registered taskstats version 1
> [ 6.530658] Key type trusted registered
> [ 6.531952] Key type encrypted registered
> [ 6.533245] IMA: No TPM chip found, activating TPM-bypass!
> [ 6.544010] rtc_cmos 00:01: setting system clock to 2017-05-02 21:11:59
> UTC (1493759519)
> [ 6.614736] usb 1-1: new high-speed USB device number 2 using ehci-pci
> [ 6.714734] usb 2-1: new high-speed USB device number 2 using ehci-pci
> [ 6.776435] Freeing unused kernel memory: 1684k freed
> [ 6.779012] usb 1-1: New USB device found, idVendor=8087, idProduct=0024
> [ 6.779013] usb 1-1: New USB device strings: Mfr=0, Product=0,
> SerialNumber=0
> [ 6.779294] hub 1-1:1.0: USB hub found
> [ 6.779389] hub 1-1:1.0: 6 ports detected
>
> AT S7=45 S0=0 LoneSIS: Running /init
> oneSIS: Loading pci modules
> [ 6.846139] usb 2-1: New USB device found, idVendor=8087, idProduct=0024
> [ 6.853627] usb 2-1: New USB device strings: Mfr=0, Product=0,
> SerialNumber=0
> [ 6.862619] hub 2-1:1.0: USB hub found
> [ 6.867011] hub 2-1:1.0: 8 ports detected
> [ 7.052746] usb 1-1.6: new high-speed USB device number 3 using ehci-pci
> [ 7.146511] usb 1-1.6: New USB device found, idVendor=0624,
> idProduct=0248
> [ 7.154202] usb 1-1.6: New USB device strings: Mfr=1, Product=2,
> SerialNumber=3
> [ 7.162369] usb 1-1.6: Product: Gadget USB HUB
> [ 7.167328] usb 1-1.6: Manufacturer: no manufacturer
> [ 7.172872] usb 1-1.6: SerialNumber: 0123456789
> [ 7.177936] usb 2-1.2: new low-speed USB device number 3 using ehci-pci
> [ 7.186442] hub 1-1.6:1.0: USB hub found
> [ 7.190968] hub 1-1.6:1.0: 6 ports detected
> [ 7.270115] usb 2-1.2: New USB device found, idVendor=0d3d,
> idProduct=0040
> [ 7.277801] usb 2-1.2: New USB device strings: Mfr=0, Product=2,
> SerialNumber=0
> [ 7.285950] usb 2-1.2: Product: USB CAT5
> [ 7.296368] input: USB CAT5 as /devices/pci0000:00/0000:00:
> 1d.0/usb2/2-1/2-1.2/2-1.2:1.0/input/input1
> [ 7.359104] hid-generic 0003:0D3D:0040.0001: input,hidraw0: USB HID
> v1.00 Keyboard [USB CAT5] on usb-0000:00:1d.0-1.2/input0
> [ 7.375909] input: USB CAT5 as /devices/pci0000:00/0000:00:
> 1d.0/usb2/2-1/2-1.2/2-1.2:1.1/input/input2
> [ 7.387680] hid-generic 0003:0D3D:0040.0002: input,hidraw1: USB HID
> v1.00 Mouse [USB CAT5] on usb-0000:00:1d.0-1.2/input1
> [ 7.488683] usb 1-1.6.1: new high-speed USB device number 4 using
> ehci-pci
> [ 7.582095] usb 1-1.6.1: New USB device found, idVendor=0624,
> idProduct=0249
> [ 7.589981] usb 1-1.6.1: New USB device strings: Mfr=4, Product=5,
> SerialNumber=6
> [ 7.598333] usb 1-1.6.1: Product: Keyboard/Mouse Function
> [ 7.604356] usb 1-1.6.1: Manufacturer: Avocent
> [ 7.609313] usb 1-1.6.1: SerialNumber: 20120917
> [ 7.621696] input: Avocent Keyboard/Mouse Function as
> /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6/1-1.6.1/1-
> 1.6.1:1.0/input/input3
> [ 7.687044] hid-generic 0003:0624:0249.0003: input,hidraw2: USB HID
> v1.00 Keyboard [Avocent Keyboard/Mouse Function] on
> usb-0000:00:1a.0-1.6.1/input0
> [ 7.704356] input: Avocent Keyboard/Mouse Function as
> /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6/1-1.6.1/1-
> 1.6.1:1.1/input/input4
> [ 7.719285] hid-generic 0003:0624:0249.0004: input,hidraw3: USB HID
> v1.00 Mouse [Avocent Keyboard/Mouse Function] on
> usb-0000:00:1a.0-1.6.1/input1
> [ 7.736019] input: Avocent Keyboard/Mouse Function as
> /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6/1-1.6.1/1-
> 1.6.1:1.2/input/input5
> [ 7.750823] hid-generic 0003:0624:0249.0005: input,hidraw4: USB HID
> v1.00 Mouse [Avocent Keyboard/Mouse Function] on
> usb-0000:00:1a.0-1.6.1/input2
> [ 24.020936] pps_core: LinuxPPS API ver. 1 registered
> [ 24.026490] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo
> Giometti <gio...@li...>
> [ 24.042173] PTP clock support registered
> [ 24.053548] tg3.c:v3.137 (May 11, 2014)
> [ 24.069783] tg3 0000:01:00.0 eth0: Tigon3 [partno(BCM95720) rev
> 5720000] (PCI Express) MAC address b8:ca:3a:f8:67:1e
> [ 24.081547] tg3 0000:01:00.0 eth0: attached PHY is 5720C
> (10/100/1000Base-T Ethernet) (WireSpeed[1], EEE[1])
> [ 24.092523] tg3 0000:01:00.0 eth0: RXcsums[1] LinkChgREG[0] MIirq[0]
> ASF[1] TSOcap[1]
> [ 24.101272] tg3 0000:01:00.0 eth0: dma_rwctrl[00000001] dma_mask[64-bit]
> [ 24.131117] tg3 0000:01:00.1 eth1: Tigon3 [partno(BCM95720) rev
> 5720000] (PCI Express) MAC address b8:ca:3a:f8:67:1f
> [ 24.142873] tg3 0000:01:00.1 eth1: attached PHY is 5720C
> (10/100/1000Base-T Ethernet) (WireSpeed[1], EEE[1])
> [ 24.153839] tg3 0000:01:00.1 eth1: RXcsums[1] LinkChgREG[0] MIirq[0]
> ASF[1] TSOcap[1]
> [ 24.162579] tg3 0000:01:00.1 eth1: dma_rwctrl[00000001] dma_mask[64-bit]
> [ 24.192642] tg3 0000:02:00.0 eth2: Tigon3 [partno(BCM95720) rev
> 5720000] (PCI Express) MAC address b8:ca:3a:f8:67:20
> [ 24.204397] tg3 0000:02:00.0 eth2: attached PHY is 5720C
> (10/100/1000Base-T Ethernet) (WireSpeed[1], EEE[1])
> [ 24.215369] tg3 0000:02:00.0 eth2: RXcsums[1] LinkChgREG[0] MIirq[0]
> ASF[1] TSOcap[1]
> [ 24.224107] tg3 0000:02:00.0 eth2: dma_rwctrl[00000001] dma_mask[64-bit]
> [ 24.253254] tg3 0000:02:00.1 eth3: Tigon3 [partno(BCM95720) rev
> 5720000] (PCI Express) MAC address b8:ca:3a:f8:67:21
> [ 24.265018] tg3 0000:02:00.1 eth3: attached PHY is 5720C
> (10/100/1000Base-T Ethernet) (WireSpeed[1], EEE[1])
> [ 24.275984] tg3 0000:02:00.1 eth3: RXcsums[1] LinkChgREG[0] MIirq[0]
> ASF[1] TSOcap[1]
> [ 24.284726] tg3 0000:02:00.1 eth3: dma_rwctrl[00000001] dma_mask[64-bit]
> [ 24.308912] RPC: Registered named UNIX socket transport module.
> [ 24.315545] RPC: Registered udp transport module.
> [ 24.320798] RPC: Registered tcp transport module.
> [ 24.326053] RPC: Registered tcp NFSv4.1 backchannel transport module.
> [ 24.344624] FS-Cache: Loaded
> [ 24.358154] FS-Cache: Netfs 'nfs' registered for caching
> Attempting DHCP on eth0 ...
> udhcpc (v1.18.5) started
> [ 24.503652] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
> Sending discover...
> Sending discover...
> [ 28.030502] tg3 0000:01:00.0 eth0: Link is up at 1000 Mbps, full duplex
> [ 28.037886] tg3 0000:01:00.0 eth0: Flow control is off for TX and off
> for RX
> [ 28.045758] tg3 0000:01:00.0 eth0: EEE is disabled
> [ 28.051121] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
> Sending discover...
> Sending select for 192.168.106.103...
> Lease of 192.168.106.103 obtained, lease time 604800
> oneSIS: Setting IP address on eth0: 192.168.106.103
> oneSIS: Setting default route: 192.168.106.1
> oneSIS: Setting hostname: mcs64
> oneSIS: Checking network connectivity to 192.168.106.1
> oneSIS: Mounting NFS root filesystem: /var/lib/oneSIS/image from
> xxx.198.80.51
> oneSIS: Leaving initramfs
> [ 31.839619] SELinux: Disabled at runtime.
> [ 31.883641] type=1404 audit(1493759544.849:2): selinux=0
> auid=4294967295 ses=4294967295
> [ 31.908663] ERST: NVRAM ERST Log Address Range is not implemented yet
> [ 31.921938] systemd[1]: systemd 219 running in system mode. (+PAM
> +AUDIT +SELINUX +IMA -APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP
> +GCRYPT +GNUTLS +A)
> [ 31.942494] systemd[1]: Detected architecture x86-64.
>
> Welcome to Scientific Linux 7.3 (Nitrogen)!
>
> [ 32.386978] systemd[1]: Started Forward assword Requests to Wall
> Directory Watch.
> [ 32.395479] systemd[1]: Starting Forward assword Requests to Wall
> Directory Watch.
> [ OK ] Reached target Swap.
> [ 32.408706] systemd[1]: Reached target Swap.
> [ 32.413503] systemd[1]: Starting Swap.
> [ OK ] Created slice Root Slice.
> [ 32.422685] systemd[1]: Created slice Root Slice.
> [ 32.427965] systemd[1]: Starting Root Slice.
> [ OK ] Listening on Delayed Shutdown Socket.
> [ 32.439693] systemd[1]: Listening on Delayed Shutdown Socket.
> [ 32.446136] systemd[1]: Starting Delayed Shutdown Socket.
> [ OK ] Listening on udev Control Socket.
> [ 32.459684] systemd[1]: Listening on udev Control Socket.
> [ 32.465746] systemd[1]: Starting udev Control Socket.
> [ OK ] Created slice User and Session Slice.
> [ 32.477680] systemd[1]: Created slice User and Session Slice.
> [ 32.484129] systemd[1]: Starting User and Session Slice.
> [ OK ] Created slice System Slice.
> [ 32.496709] systemd[1]: Created slice System Slice.
> [ 32.502207] systemd[1]: Starting System Slice.
> [ OK ] Created slice system-getty.slice.
> [ 32.513673] systemd[1]: Created slice system-getty.slice.
> [ 32.519725] systemd[1]: Starting system-getty.slice.
> [ OK ] Reached target User and Group Name Lookups.
> [ 32.531676] systemd[1]: Reached target User and Group Name Lookups.
> [ 32.538696] systemd[1]: Starting User and Group Name Lookups.
> [ OK ] Set up automount Arbitrary Executab...ats File System Automount
> Point.
> [ 32.554702] systemd[1]: Set up automount Arbitrary Executable File
> Formats File System Automount Point.
> [ 32.565218] systemd[1]: Starting Arbitrary Executable File Formats File
> System Automount Point.
> [ OK ] Listening on Device-mapper event daemon FIFOs.
> [ 32.582664] systemd[1]: Listening on Device-mapper event daemon FIFOs.
> [ 32.589976] systemd[1]: Starting Device-mapper event daemon FIFOs.
> [ 32.597358] systemd[1]: Starting Collect Read-Ahead Data...
> Starting Collect Read-Ahead Data...
> [ OK ] Listening on LVM2 metadata daemon socket.
> [ 32.615662] systemd[1]: Listening on LVM2 metadata daemon socket.
> [ 32.622496] systemd[1]: Starting LVM2 metadata daemon socket.
> [ OK ] Listening on udev Kernel Socket.
> [ 32.635662] systemd[1]: Listening on udev Kernel Socket.
> [ 32.641618] systemd[1]: Starting udev Kernel Socket.
> [ OK ] Listening on /dev/initctl Compatibility Named Pipe.
> [ 32.655668] systemd[1]: Listening on /dev/initctl Compatibility Named
> Pipe.
> [ 32.663462] systemd[1]: Starting /dev/initctl Compatibility Named Pipe.
> [ 32.671394] systemd[1]: Starting Replay Read-Ahead Data...
> Starting Replay Read-Ahead Data...
> [ OK ] Created slice system-selinux\x2dpol...grate\
> x2dlocal\x2dchanges.slice.
> [ 32.693763] systemd[1]: Created slice system-selinux\x2dpolicy\
> x2dmigrate\x2dlocal\x2dchanges.slice.
> [ 32.704122] systemd[1]: Starting system-selinux\x2dpolicy\
> x2dmigrate\x2dlocal\x2dchanges.slice.
> [ OK ] Listening on Journal Socket.
> [ 32.721654] systemd[1]: Listening on Journal Socket.
> [ 32.727299] systemd[1]: Starting Journal Socket.
> [ 32.733872] systemd[1]: Starting Monitoring of LVM2 mirrors, snapshots
> etc. using dmeventd or progress polling...
> Starting Monitoring of LVM2 mirrors... dmeventd or progress
> polling...
> [ 32.755461] systemd[1]: Starting Journal Service...
> Starting Journal Service...
> [ 32.766406] systemd[1]: Mounting NFSD configuration filesystem...
> Mounting NFSD configuration filesystem...
> [ 32.780118] systemd[1]: MESSAGE=Failed to check directory
> /var/lib/nfs/rpc_pipefs: No such file or directory
> [ 32.791762] systemd[1]: Mounting RPC Pipe File System...
> Mounting RPC Pipe File System...
> [ 32.803492] systemd[1]: Mounting Huge Pages File System...
> Mounting Huge Pages File System...
> [ OK ] Listening on LVM2 poll daemon socket.
> [ 32.820638] systemd[1]: Listening on LVM2 poll daemon socket.
> [ 32.827089] systemd[1]: Starting LVM2 poll daemon socket.
> [ OK ] Created slice system-serial\x2dgetty.slice.
> [ 32.839668] systemd[1]: Created slice system-serial\x2dgetty.slice.
> [ 32.846703] systemd[1]: Starting system-serial\x2dgetty.slice.
> [ 32.853860] systemd[1]: Mounting Debug File System...
> Mounting Debug File System...
> [ 32.865228] systemd[1]: Mounting POSIX Message Queue File System...
> Mounting POSIX Message Queue File System...
> [ OK ] Reached target Slices.
> [ 32.883629] systemd[1]: Reached target Slices.
> [ 32.888619] systemd[1]: Starting Slices.
> [ OK ] Started Collect Read-Ahead Data.
> [ 32.900644] systemd[1]: Started Collect Read-Ahead Data.
> [ OK ] Started Replay Read-Ahead Data.
> [ 32.913711] systemd[1]: Started Replay Read-Ahead Data.
> [ 32.926948] systemd[1]: Starting Create Static Device Nodes in /dev...
> Starting Create Static Device Nodes in /dev...
> [ 32.948394] systemd[1]: Starting Apply Kernel Variables...
> Starting Apply Kernel Variables...
> [ 32.960282] systemd[1]: Mounting Configuration File System...
> Mounting Configuration File System...
> [ 32.972250] systemd[1]: Starting oneSIS System Init...
> Starting oneSIS System Init...
> [ 32.983138] systemd[1]: Starting Load/Save Random Seed...
> Starting Load/Save Random Seed...
> [ 32.583186] mount[1146]: mount: unknown files[ 33.001384] systemd[1]:
> Starting udev Coldplug all Devices...
> ystem type 'nfsd'
> Starting udev Coldplug all Devices...
> [ 32.597503] m[ 33.017146] systemd[1]: Starting Setup Virtual
> Console...
> ount[1147]: mount: mount point /var/lib/nfs/rpc_pipefs does not exist
> Starting Setup Virtual Console...
> [ OK ] Mounted POSIX Message Queue File System.
> [ 33.044590] systemd[1]: Mounted POSIX Message Queue File System.
> [ OK ] Mounted Huge Pages File System.
> [ 33.057587] systemd[1]: Mounted Huge Pages File System.
> [ OK ] Mounted Debug File System.
> [ 33.068568] systemd[1]: Mounted Debug File System.
> [ OK ] Mounted Configuration File System.
> [ 33.090580] systemd[1]: Mounted Configuration File System.
> [ OK ] Started Journal Service.
> [ 33.101598] systemd[1]: Started Journal Service.
> [FAILED] Failed to mount NFSD configuration filesystem.
> See 'systemctl status proc-fs-nfsd.mount' for details.
> [DEPEND] Dependency failed for GSSAPI Proxy Daemon.
> [FAILED] Failed to mount RPC Pipe File System.
> See 'systemctl status var-lib-nfs-rpc_pipefs.mount' for details.
> [DEPEND] Dependency failed for RPC security service for NFS server.
> [DEPEND] Dependency failed for RPC security service for NFS client and
> server.
> [ OK ] Started Create Static Device Nodes in /dev.
> [ OK ] Started Apply Kernel Variables.
> [FAILED] Failed to start Load/Save Random Seed.
> See 'systemctl status systemd-random-seed.service' for details.
> [ 32.773506] rc.preinit[1168]: oneSIS: Initializing
> [ OK ] Started LVM2 metadata daemon.
> [ 32.788611] Starting LVM2 metadata daemon...rc.preinit
> [1168]: oneSIS: preinit complete
> Starting udev Kernel Device Manager...
> [ OK ] Reached target NFS client services.
> Starting Flush Journal to Persistent Storage...
> [ OK ] Started Monitoring of LVM2 mirrors,...ng dmeventd or progress
> polling.
> [ OK ] Started oneSIS System Init.
> [ OK ] Started Setup Virtual Console.
> [ OK ] Started udev Coldplug all Devices.
> Starting udev Wait for Complete Device Initialization...
> Starting Configure read-only root support...
> [ OK ] Reached target Local File Systems (Pre).
> [ 33.349183] systemd-journald[1144]: Received request to flush runtime
> journal from PID 1
> [ OK ] Started Configure read-only root support.
> [ OK ] Started Flush Journal to Persistent Storage.
> [ OK ] Started udev Kernel Device Manager.
> Starting Show Plymouth Boot Screen...
> [ OK ] Started Show Plymouth Boot Screen.
> [ OK ] Found device /dev/ttyS1.
> G[ OK ] Started udev Wait for Complete Device Initialization.
> Starting Activation of DM RAID sets...
> [ OK ] Started Activation of DM RAID sets.
> [ OK ] Reached target Encrypted Volumes.
> [ OK ] Reached target Local File Systems.
> Starting Preprocess NFS configuration...
> Starting Tell Plymouth To Write Out Runtime Data...
> Starting Create Volatile Files and Directories...
> Starting Update is Completed...
> [FAILED] Failed to start Update is Completed.
> See 'systemctl status systemd-update-done.service' for details.
> [ OK ] Started Preprocess NFS configuration.
> [ OK ] Started Tell Plymouth To Write Out Runtime Data.
> [FAILED] Failed to start Create Volatile Files and Directories.
> See 'systemctl status systemd-tmpfiles-setup.service' for details.
> Starting Security Auditing Service...
> [ 34.190695] augenrules[2348]: mktemp: failed to create file via
> template ��‘/tmp/aurules.XXXXXXXX��’: No such file or
> directory
> [ 34.193367] augenrules[2348]: /sbin/augenrules: line 76: ${TmpRules}:
> ambiguous redirect
> [ 34.194978] augenrules[2348]: /sbin/augenrules: line 99: ${TmpRules}:
> ambiguous redirect
> [ 34.225184] augenrules[2348]: cp: cannot create regular file
> ��‘/etc/audit/audit.rules.prev��’: Read-only file system
> [ 34.234550] augenrules[2348]: cp: missing destination file operand
> after ��‘/etc/audit/audit.rules��’
> [ 34.234932] augenrules[2348]: Try 'cp --help' for more information.
> [ 34.242053] augenrules[2348]: chmod: changing permissions of
> ��‘/etc/audit/audit.rules��’: Read-only file system
> [FAILED] Failed to start Security Auditing Service.
> See 'systemctl status auditd.service' for details.
> Starting Update UTMP about System Boot/Shutdown...
> [ OK ] Started Update UTMP about System Boot/Shutdown.
> [ OK ] Reached target System Initialization.
> [ OK ] Reached target Timers.
> [FAILED] Failed to listen on CUPS Printing Service Sockets.
> See 'systemctl status cups.socket' for details.
> [FAILED] Failed to listen on RPCbind Server Activation Socket.
> See 'systemctl status rpcbind.socket' for details.
> [FAILED] Failed to listen on Virtual machine log manager socket.
> See 'systemctl status virtlogd.socket' for details.
> [DEPEND] Dependency failed for Virtualization daemon.
> [FAILED] Failed to listen on Virtual machine lock manager socket.
> See 'systemctl status virtlockd.socket' for details.
> [FAILED] Failed to listen on Avahi mDNS/DNS-SD Stack Activation Socket.
> See 'systemctl status avahi-daemon.socket' for details.
> [DEPEND] Dependency failed for Avahi mDNS/DNS-SD Stack.
> [ OK ] Reached target Paths.
> [ OK ] Listening on Open-iSCSI iscsid Socket.
> [FAILED] Failed to listen on D-Bus System Message Bus Socket.
> See 'systemctl status dbus.socket' for details.
> [DEPEND] Dependency failed for D-Bus System Message Bus.
> [DEPEND] Dependency failed for Dynamic System Tuning Daemon.
> [ OK ] Listening on Open-iSCSI iscsiuio Socket.
> [ OK ] Reached target Sockets.
> [ OK ] Reached target Basic System.
> Starting Resets System Activity Logs...
> [ OK ] Started irqbalance daemon.
> Starting irqbalance daemon...
> Starting Network Manager...
> [ OK ] Started ABRT Automated Bug Reporting Tool.
> Starting ABRT Automated Bug Reporting Tool...
> [ OK ] Started libstoragemgmt plug-in server daemon.
> Starting libstoragemgmt plug-in server daemon...
> [ OK ] Started Hardware RNG Entropy Gatherer Daemon.
> Starting Hardware RNG Entropy Gatherer Daemon...
> Starting Load CPU microcode update...
> Starting Run automatic yum updates as a cron job...
> Starting Accounts Service...
> [ 34.291019] rngd[2373]: Unable to open file: /dev/tpm0
> [ 34.291328] rngd[2373]: can't open any entropy source
> [ 34.291581] rngd[2373]: Maybe RNG device modules are not loaded
> Starting Kernel Samepage Merging...
> Starting Login Service...
> Starting Console Mouse manager...
> [ OK ] Started Manage Sound Card State (restore and store).
> Starting Manage Sound Card State (restore and store)...
> [ 34.337535] lsmd[2372]: Unable to access socket directory
> /var/run/lsm/ipc, errno= 2
> [ 34.338430] Starting Install ABRT coredump hook...
> touch[2376]: /bin/touch: cannot touch ��‘/var/lock/subsys/yum-cron��’:
> No such file or directory
> Starting Authorization Manager...
> Starting Dump dmesg to /var/log/dmesg...
> [FAILED] Failed to start RealtimeKit Scheduling Policy Service.
> See 'systemctl status rtkit-daemon.service' for details.
> Starting RealtimeKit Scheduling Policy Service...
> [ OK ] Started Self Monitoring and Reporting Technology (SMART) Daemon.
> Starting Self Monitoring and Reporting Technology (SMART)
> Daemon...
> [ OK ] Started ABRT kernel log watcher.
> Starting ABRT kernel log watcher...
> [FAILED] Failed to start Run automatic yum updates as a cron job.
> See 'systemctl status yum-cron.service' for details.
> [ OK ] Started Kernel Samepage Merging.
> Starting Kernel Samepage Merging (KSM) Tuning Daemon...
> [FAILED] Failed to start Console Mouse manager.
> See 'systemctl status gpm.service' for details.
> [ OK ] Started Load CPU microcode update.
> [ 34.421302] rhel-dmesg[2388]: /usr/lib/systemd/rhel-dmesg: line 3:
> /var/log/dmesg: No such file or directory
> [FAILED] Failed to start Dump dmesg to /var/log/dmesg.
> See 'systemctl status rhel-dmesg.service' for details.
> [FAILED] Failed to start Login Service.
> See 'systemctl status systemd-logind.service' for details.
> [ OK ] Stopped Login Service.
> [FAILED] Failed to listen on D-Bus System Message Bus Socket.
> See 'systemctl status dbus.socket' for details.
> Starting Login Service...
> [ 34.480028] sa1[2368]: Cannot open /var/log/sa/sa02: No such file or
> directory
> [FAILED] Failed to start Resets System Activity Logs.
> See 'systemctl status sysstat.service' for details.
> [FAILED] Failed to start Login Service.
> See 'systemctl status systemd-logind.service' for details.
> [ OK ] Stopped Login Service.
> [FAILED] Failed to listen on D-Bus System Message Bus Socket.
> See 'systemctl status dbus.socket' for details.
> Starting Login Service...
> [ 34.496286] ksmtuned[2394]: touch: cannot touch
> ��‘/var/run/ksmtune.pid��’: No such file or directory
> [ OK ] Started Kernel Samepage Merging (KSM) Tuning Daemon.
> [ OK ] Started Accounts Service.
> [FAILED] Failed to start Login Service.
> See 'systemctl status systemd-logind.service' for details.
> [ OK ] Stopped Login Service.
> [FAILED] Failed to listen on D-Bus System Message Bus Socket.
> See 'systemctl status dbus.socket' for details.
> Starting Login Service...
> [FAILED] Failed to start Login Service.
> See 'systemctl status systemd-logind.service' for details.
> [ OK ] Stopped Login Service.
> [FAILED] Failed to listen on D-Bus System Message Bus Socket.
> See 'systemctl status dbus.socket' for details.
> Starting Login Service...
> [FAILED] Failed to start Login Service.
> See 'systemctl status systemd-logind.service' for details.
> [ OK ] Stopped Login Service.
> [FAILED] Failed to listen on D-Bus System Message Bus Socket.
> See 'systemctl status dbus.socket' for details.
> [FAILED] Failed to start Login Service.
> See 'systemctl status systemd-logind.service' for details.
> [ 34.590198] NetworkManager[2370]: Cannot create parents for
> '/var/lib/NetworkManager': No such file or directory
> [FAILED] Failed to start Network Manager.
> See 'systemctl status NetworkManager.service' for details.
> [DEPEND] Dependency failed for Network Manager Wait Online.
> Starting LSB: Bring up/down networking...
> [ 34.648250] abrt-install-ccpp-hook[2384]: mkdir: cannot create
> directory ��‘/var��’: File exists
> [ 34.649080] abrt-install-ccpp-hook[2384]: /usr/sbin/abrt-install-ccpp-hook:
> line 55: /var/run/abrt/saved_core_pattern: No such file or directory
> [ OK ] Started Install ABRT coredump hook.
> [ OK ] Started Authorization Manager.
> [ OK ] Stopped Network Manager.
> Starting Network Manager...
> [ 34.816374] NetworkManager[2451]: Cannot create parents for
> '/var/lib/NetworkManager': No such file or directory
> [FAILED] Failed to start Network Manager.
> See 'systemctl status NetworkManager.service' for details.
> [DEPEND] Dependency failed for Network Manager Wait Online.
> [ OK ] Stopped Network Manager.
> Starting Network Manager...
> [ 35.203398] NetworkManager[2487]: Cannot create parents for
> '/var/lib/NetworkManager': No such file or directory
> [FAILED] Failed to start Network Manager.
> See 'systemctl status NetworkManager.service' for details.
> [DEPEND] Dependency failed for Network Manager Wait Online.
> [ OK ] Stopped Network Manager.
> Starting Network Manager...
> [ 35.581257] network[2421]: Bringing up loopback interface:
> ./network-functions: line 262: cd: /var/run/netreport: No such file or
> directory
> [ 35.582507] network[2421]: [ OK ]
> [ 35.589441] NetworkManager[2543]: Cannot create parents for
> '/var/lib/NetworkManager': No such file or directory
> [FAILED] Failed to start Network Manager.
> See 'systemctl status NetworkManager.service' for details.
> [DEPEND] Dependency failed for Network Manager Wait Online.
> [ 35.860630] network[2421]: Bringing up interface enp11s0: ERROR :
> [/etc/sysconfig/network-scripts/ifup-eth] Device enp11s0 does not seem to
> be presen.
> [ 35.872926] network[2421]: [FAILED]
> [ OK ] Stopped Network Manager.
> Starting Network Manager...
> [ 35.970192] network[2421]: touch: cannot touch
> ��‘/var/lock/subsys/network��’: No such file or directory
> [FAILED] Failed to start LSB: Bring up/down networking.
> See 'systemctl status network.service' for details.
> [ 35.975743] NetworkManager[2610]: Cannot create parents for
> '/var/lib/NetworkManager': No such file or directory
> [FAILED] Failed to start Network Manager.
> See 'systemctl status NetworkManager.service' for details.
> [DEPEND] Dependency failed for Network Manager Wait Online.
> [ OK ] Reached target Network.
> Starting OpenSSH server daemon...
> Starting Notify NFS peers of a restart...
> Starting Logout off all iSCSI sessions on shutdown...
> Starting Postfix Mail Transport Agent...
> Starting System Logging Service...
> [FAILED] Failed to start CUPS Printing Service.
> See 'systemctl status cups.service' for details.
> Starting CUPS Printing Service...
> [ OK ] Reached target Network is Online.
> [ OK ] Started Logout off all iSCSI sessions on shutdown.
> [ OK ] Reached target Remote File Systems (Pre).
> [ OK ] Reached target Remote File Systems.
> Starting Crash recovery kernel arming...
> Starting Permit User Sessions...
> Starting Availability of block devices...
> [ OK ] Started Availability of block devices.
> [ OK ] Started Notify NFS peers of a restart.
> [ OK ] Started Permit User Sessions.
> [ OK ] Started Command Scheduler.
> Starting Command Scheduler...
> Starting Wait for Plymouth Boot Screen to Quit...
> Starting GNOME Display Manager...
> [ OK ] Started Job spooling tools.
> Starting Job spooling tools...
> [ 36.058063] kdumpctl[2625]: /usr/bin/kdumpctl: line 31:
> /var/lock/kdump: No such file or directory
> [FAILED] Failed to start Crash recovery kernel arming.
> See 'systemctl status kdump.service' for details.
> [ 36.068516] crond[2631]: crond: can't open or create
> /var/run/crond.pid: No such file or directory
> [ OK ] Stopped Network Manager.
> [FAILED] Failed to start Network Manager.
> See 'systemctl status NetworkManager.service' for details.
> [DEPEND] Dependency failed for Network Manager Wait Online.
> [FAILED] Failed to start System Logging Service.
> See 'systemctl status rsyslog.service' for details.
> [ 36.117548] sshd[2619]: Missing privilege separation directory:
> /var/empty/sshd
> [FAILED] Failed to start OpenSSH server daemon.
> See 'systemctl status sshd.service' for details.
> [ 36.151970] aliasesdb[2622]: newaliases: fatal: chdir
> /var/spool/postfix: No such file or directory
> [ 36.155433] aliasesdb[2622]: touch: cannot touch ��‘/var/lib/misc/
> postfix.aliasesdb-stamp��’: No such file or directory
> [ OK ] Stopped System Logging Service.
> Starting System Logging Service...
> [FAILED] Failed to start System Logging Service.
> See 'systemctl status rsyslog.service' for details.
> [ OK ] Stopped System Logging Service.
> Starting System Logging Service...
> [FAILED] Failed to start System Logging Service.
> See 'systemctl status rsyslog.service' for details.
> [FAILED] Failed to start Postfix Mail Transport Agent.
> See 'systemctl status postfix.service' for details.
> [ OK ] Stopped System Logging Service.
> Starting System Logging Service...
> [FAILED] Failed to start System Logging Service.
> See 'systemctl status rsyslog.service' for details.
> [ OK ] Stopped System Logging Service.
> Starting System Logging Service...
> [FAILED] Failed to start System Logging Service.
> See 'systemctl status rsyslog.service' for details.
> [ OK ] Stopped System Logging Service.
> [FAILED] Failed to start System Logging Service.
> See 'systemctl status rsyslog.service' for details.
> [ OK ] Stopped OpenSSH server daemon.
> Starting OpenSSH server daemon...
> [ 78.379658] sshd[2659]: Missing privilege separation directory:
> /var/empty/sshd
> [FAILED] Failed to start OpenSSH server daemon.
> See 'systemctl status sshd.service' for details.
> [ OK ] Stopped OpenSSH server daemon.
> Starting OpenSSH server daemon...
> [ 120.621684] sshd[2661]: Missing privilege separation directory:
> /var/empty/sshd
> [FAILED] Failed to start OpenSSH server daemon.
> See 'systemctl status sshd.service' for details.
> [FAILED] Failed to start GNOME Display Manager.
> See 'systemctl status gdm.service' for details.
> Starting Terminate Plymouth Boot Screen...
>
> Scientific Linux 7.3 (Nitrogen)
> Kernel 3.10.0-514.el7.x86_64 on an x86_64
>
> mcs64 login: [ 152.623495] systemd-readahead[1141]: Failed to open pack
> file: Read-only file system
>
> CTRL-A Z for help |115200 8N1 | NOR | Minicom 2.3 | VT102 | Online
> 00:02
>
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> oneSIS-users mailing list
> one...@li...
> https://lists.sourceforge.net/lists/listinfo/onesis-users
>
|
|
From: ROSS, M. D C. U. A. 4. RANS/E. <mar...@us...> - 2017-05-02 21:24:01
|
>>Try altering your etc/systemd/system.conf to enable console logging on bootup.
>>Set DefaultStandardOutput=journal+console then reboot. You should get much more output which might help point out what's going on.
>>-JE
Ok, I see errors about /var file system. My /var is linked to /ram but there is still no files in /ram, I would expect to see all the /var/log/messages in there ???
[ 6.518771] hidraw: raw HID events driver (C) Jiri Kosina
[ 6.518946] usbcore: registered new interface driver usbhid
[ 6.518947] usbhid: USB HID core driver
[ 6.519052] drop_monitor: Initializing network drop monitor service
[ 6.519265] TCP: cubic registered
[ 6.519270] Initializing XFRM netlink socket
[ 6.519512] NET: Registered protocol family 10
[ 6.520087] NET: Registered protocol family 17
[ 6.523692] microcode: CPU0 sig=0x206d7, pf=0x1, revision=0x710
[ 6.523705] microcode: CPU1 sig=0x206d7, pf=0x1, revision=0x710
[ 6.523714] microcode: CPU2 sig=0x206d7, pf=0x1, revision=0x710
[ 6.523725] microcode: CPU3 sig=0x206d7, pf=0x1, revision=0x710
[ 6.523742] microcode: CPU4 sig=0x206d7, pf=0x1, revision=0x710
[ 6.523761] microcode: CPU5 sig=0x206d7, pf=0x1, revision=0x710
[ 6.523768] microcode: CPU6 sig=0x206d7, pf=0x1, revision=0x710
[ 6.523779] microcode: CPU7 sig=0x206d7, pf=0x1, revision=0x710
[ 6.523790] microcode: CPU8 sig=0x206d7, pf=0x1, revision=0x710
[ 6.523802] microcode: CPU9 sig=0x206d7, pf=0x1, revision=0x710
[ 6.523814] microcode: CPU10 sig=0x206d7, pf=0x1, revision=0x710
[ 6.523825] microcode: CPU11 sig=0x206d7, pf=0x1, revision=0x710
[ 6.523922] microcode: Microcode Update Driver: v2.01 <ti...@ai...>, Peter Oruba
[ 6.524212] Loading compiled-in X.509 certificates
[ 6.526085] Loaded X.509 cert 'Fermi National Accelerator Laboratory: Scientific Linux 7 kpatch signing key: c8e46da25bf2b6ed33675277e795de682b4666d6'
[ 6.527851] Loaded X.509 cert 'Fermi National Accelerator Laboratory: Scientific Linux 7 driver update signing key: 98ec7b1456fb6a6b00e81292343a0ff7268df'
[ 6.528907] Loaded X.509 cert 'Red Hat Enterprise Linux kernel signing key: 02c33df7a9cd1651f844f720041963da33995e99'
[ 6.528922] registered taskstats version 1
[ 6.530658] Key type trusted registered
[ 6.531952] Key type encrypted registered
[ 6.533245] IMA: No TPM chip found, activating TPM-bypass!
[ 6.544010] rtc_cmos 00:01: setting system clock to 2017-05-02 21:11:59 UTC (1493759519)
[ 6.614736] usb 1-1: new high-speed USB device number 2 using ehci-pci
[ 6.714734] usb 2-1: new high-speed USB device number 2 using ehci-pci
[ 6.776435] Freeing unused kernel memory: 1684k freed
[ 6.779012] usb 1-1: New USB device found, idVendor=8087, idProduct=0024
[ 6.779013] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 6.779294] hub 1-1:1.0: USB hub found
[ 6.779389] hub 1-1:1.0: 6 ports detected
AT S7=45 S0=0 LoneSIS: Running /init
oneSIS: Loading pci modules
[ 6.846139] usb 2-1: New USB device found, idVendor=8087, idProduct=0024
[ 6.853627] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 6.862619] hub 2-1:1.0: USB hub found
[ 6.867011] hub 2-1:1.0: 8 ports detected
[ 7.052746] usb 1-1.6: new high-speed USB device number 3 using ehci-pci
[ 7.146511] usb 1-1.6: New USB device found, idVendor=0624, idProduct=0248
[ 7.154202] usb 1-1.6: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 7.162369] usb 1-1.6: Product: Gadget USB HUB
[ 7.167328] usb 1-1.6: Manufacturer: no manufacturer
[ 7.172872] usb 1-1.6: SerialNumber: 0123456789
[ 7.177936] usb 2-1.2: new low-speed USB device number 3 using ehci-pci
[ 7.186442] hub 1-1.6:1.0: USB hub found
[ 7.190968] hub 1-1.6:1.0: 6 ports detected
[ 7.270115] usb 2-1.2: New USB device found, idVendor=0d3d, idProduct=0040
[ 7.277801] usb 2-1.2: New USB device strings: Mfr=0, Product=2, SerialNumber=0
[ 7.285950] usb 2-1.2: Product: USB CAT5
[ 7.296368] input: USB CAT5 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2/2-1.2:1.0/input/input1
[ 7.359104] hid-generic 0003:0D3D:0040.0001: input,hidraw0: USB HID v1.00 Keyboard [USB CAT5] on usb-0000:00:1d.0-1.2/input0
[ 7.375909] input: USB CAT5 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2/2-1.2:1.1/input/input2
[ 7.387680] hid-generic 0003:0D3D:0040.0002: input,hidraw1: USB HID v1.00 Mouse [USB CAT5] on usb-0000:00:1d.0-1.2/input1
[ 7.488683] usb 1-1.6.1: new high-speed USB device number 4 using ehci-pci
[ 7.582095] usb 1-1.6.1: New USB device found, idVendor=0624, idProduct=0249
[ 7.589981] usb 1-1.6.1: New USB device strings: Mfr=4, Product=5, SerialNumber=6
[ 7.598333] usb 1-1.6.1: Product: Keyboard/Mouse Function
[ 7.604356] usb 1-1.6.1: Manufacturer: Avocent
[ 7.609313] usb 1-1.6.1: SerialNumber: 20120917
[ 7.621696] input: Avocent Keyboard/Mouse Function as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6/1-1.6.1/1-1.6.1:1.0/input/input3
[ 7.687044] hid-generic 0003:0624:0249.0003: input,hidraw2: USB HID v1.00 Keyboard [Avocent Keyboard/Mouse Function] on usb-0000:00:1a.0-1.6.1/input0
[ 7.704356] input: Avocent Keyboard/Mouse Function as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6/1-1.6.1/1-1.6.1:1.1/input/input4
[ 7.719285] hid-generic 0003:0624:0249.0004: input,hidraw3: USB HID v1.00 Mouse [Avocent Keyboard/Mouse Function] on usb-0000:00:1a.0-1.6.1/input1
[ 7.736019] input: Avocent Keyboard/Mouse Function as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6/1-1.6.1/1-1.6.1:1.2/input/input5
[ 7.750823] hid-generic 0003:0624:0249.0005: input,hidraw4: USB HID v1.00 Mouse [Avocent Keyboard/Mouse Function] on usb-0000:00:1a.0-1.6.1/input2
[ 24.020936] pps_core: LinuxPPS API ver. 1 registered
[ 24.026490] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <gio...@li...>
[ 24.042173] PTP clock support registered
[ 24.053548] tg3.c:v3.137 (May 11, 2014)
[ 24.069783] tg3 0000:01:00.0 eth0: Tigon3 [partno(BCM95720) rev 5720000] (PCI Express) MAC address b8:ca:3a:f8:67:1e
[ 24.081547] tg3 0000:01:00.0 eth0: attached PHY is 5720C (10/100/1000Base-T Ethernet) (WireSpeed[1], EEE[1])
[ 24.092523] tg3 0000:01:00.0 eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[1] TSOcap[1]
[ 24.101272] tg3 0000:01:00.0 eth0: dma_rwctrl[00000001] dma_mask[64-bit]
[ 24.131117] tg3 0000:01:00.1 eth1: Tigon3 [partno(BCM95720) rev 5720000] (PCI Express) MAC address b8:ca:3a:f8:67:1f
[ 24.142873] tg3 0000:01:00.1 eth1: attached PHY is 5720C (10/100/1000Base-T Ethernet) (WireSpeed[1], EEE[1])
[ 24.153839] tg3 0000:01:00.1 eth1: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[1] TSOcap[1]
[ 24.162579] tg3 0000:01:00.1 eth1: dma_rwctrl[00000001] dma_mask[64-bit]
[ 24.192642] tg3 0000:02:00.0 eth2: Tigon3 [partno(BCM95720) rev 5720000] (PCI Express) MAC address b8:ca:3a:f8:67:20
[ 24.204397] tg3 0000:02:00.0 eth2: attached PHY is 5720C (10/100/1000Base-T Ethernet) (WireSpeed[1], EEE[1])
[ 24.215369] tg3 0000:02:00.0 eth2: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[1] TSOcap[1]
[ 24.224107] tg3 0000:02:00.0 eth2: dma_rwctrl[00000001] dma_mask[64-bit]
[ 24.253254] tg3 0000:02:00.1 eth3: Tigon3 [partno(BCM95720) rev 5720000] (PCI Express) MAC address b8:ca:3a:f8:67:21
[ 24.265018] tg3 0000:02:00.1 eth3: attached PHY is 5720C (10/100/1000Base-T Ethernet) (WireSpeed[1], EEE[1])
[ 24.275984] tg3 0000:02:00.1 eth3: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[1] TSOcap[1]
[ 24.284726] tg3 0000:02:00.1 eth3: dma_rwctrl[00000001] dma_mask[64-bit]
[ 24.308912] RPC: Registered named UNIX socket transport module.
[ 24.315545] RPC: Registered udp transport module.
[ 24.320798] RPC: Registered tcp transport module.
[ 24.326053] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 24.344624] FS-Cache: Loaded
[ 24.358154] FS-Cache: Netfs 'nfs' registered for caching
Attempting DHCP on eth0 ...
udhcpc (v1.18.5) started
[ 24.503652] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Sending discover...
Sending discover...
[ 28.030502] tg3 0000:01:00.0 eth0: Link is up at 1000 Mbps, full duplex
[ 28.037886] tg3 0000:01:00.0 eth0: Flow control is off for TX and off for RX
[ 28.045758] tg3 0000:01:00.0 eth0: EEE is disabled
[ 28.051121] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Sending discover...
Sending select for 192.168.106.103...
Lease of 192.168.106.103 obtained, lease time 604800
oneSIS: Setting IP address on eth0: 192.168.106.103
oneSIS: Setting default route: 192.168.106.1
oneSIS: Setting hostname: mcs64
oneSIS: Checking network connectivity to 192.168.106.1
oneSIS: Mounting NFS root filesystem: /var/lib/oneSIS/image from xxx.198.80.51
oneSIS: Leaving initramfs
[ 31.839619] SELinux: Disabled at runtime.
[ 31.883641] type=1404 audit(1493759544.849:2): selinux=0 auid=4294967295 ses=4294967295
[ 31.908663] ERST: NVRAM ERST Log Address Range is not implemented yet
[ 31.921938] systemd[1]: systemd 219 running in system mode. (+PAM +AUDIT +SELINUX +IMA -APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +A)
[ 31.942494] systemd[1]: Detected architecture x86-64.
Welcome to Scientific Linux 7.3 (Nitrogen)!
[ 32.386978] systemd[1]: Started Forward assword Requests to Wall Directory Watch.
[ 32.395479] systemd[1]: Starting Forward assword Requests to Wall Directory Watch.
[ OK ] Reached target Swap.
[ 32.408706] systemd[1]: Reached target Swap.
[ 32.413503] systemd[1]: Starting Swap.
[ OK ] Created slice Root Slice.
[ 32.422685] systemd[1]: Created slice Root Slice.
[ 32.427965] systemd[1]: Starting Root Slice.
[ OK ] Listening on Delayed Shutdown Socket.
[ 32.439693] systemd[1]: Listening on Delayed Shutdown Socket.
[ 32.446136] systemd[1]: Starting Delayed Shutdown Socket.
[ OK ] Listening on udev Control Socket.
[ 32.459684] systemd[1]: Listening on udev Control Socket.
[ 32.465746] systemd[1]: Starting udev Control Socket.
[ OK ] Created slice User and Session Slice.
[ 32.477680] systemd[1]: Created slice User and Session Slice.
[ 32.484129] systemd[1]: Starting User and Session Slice.
[ OK ] Created slice System Slice.
[ 32.496709] systemd[1]: Created slice System Slice.
[ 32.502207] systemd[1]: Starting System Slice.
[ OK ] Created slice system-getty.slice.
[ 32.513673] systemd[1]: Created slice system-getty.slice.
[ 32.519725] systemd[1]: Starting system-getty.slice.
[ OK ] Reached target User and Group Name Lookups.
[ 32.531676] systemd[1]: Reached target User and Group Name Lookups.
[ 32.538696] systemd[1]: Starting User and Group Name Lookups.
[ OK ] Set up automount Arbitrary Executab...ats File System Automount Point.
[ 32.554702] systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point.
[ 32.565218] systemd[1]: Starting Arbitrary Executable File Formats File System Automount Point.
[ OK ] Listening on Device-mapper event daemon FIFOs.
[ 32.582664] systemd[1]: Listening on Device-mapper event daemon FIFOs.
[ 32.589976] systemd[1]: Starting Device-mapper event daemon FIFOs.
[ 32.597358] systemd[1]: Starting Collect Read-Ahead Data...
Starting Collect Read-Ahead Data...
[ OK ] Listening on LVM2 metadata daemon socket.
[ 32.615662] systemd[1]: Listening on LVM2 metadata daemon socket.
[ 32.622496] systemd[1]: Starting LVM2 metadata daemon socket.
[ OK ] Listening on udev Kernel Socket.
[ 32.635662] systemd[1]: Listening on udev Kernel Socket.
[ 32.641618] systemd[1]: Starting udev Kernel Socket.
[ OK ] Listening on /dev/initctl Compatibility Named Pipe.
[ 32.655668] systemd[1]: Listening on /dev/initctl Compatibility Named Pipe.
[ 32.663462] systemd[1]: Starting /dev/initctl Compatibility Named Pipe.
[ 32.671394] systemd[1]: Starting Replay Read-Ahead Data...
Starting Replay Read-Ahead Data...
[ OK ] Created slice system-selinux\x2dpol...grate\x2dlocal\x2dchanges.slice.
[ 32.693763] systemd[1]: Created slice system-selinux\x2dpolicy\x2dmigrate\x2dlocal\x2dchanges.slice.
[ 32.704122] systemd[1]: Starting system-selinux\x2dpolicy\x2dmigrate\x2dlocal\x2dchanges.slice.
[ OK ] Listening on Journal Socket.
[ 32.721654] systemd[1]: Listening on Journal Socket.
[ 32.727299] systemd[1]: Starting Journal Socket.
[ 32.733872] systemd[1]: Starting Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling...
Starting Monitoring of LVM2 mirrors... dmeventd or progress polling...
[ 32.755461] systemd[1]: Starting Journal Service...
Starting Journal Service...
[ 32.766406] systemd[1]: Mounting NFSD configuration filesystem...
Mounting NFSD configuration filesystem...
[ 32.780118] systemd[1]: MESSAGE=Failed to check directory /var/lib/nfs/rpc_pipefs: No such file or directory
[ 32.791762] systemd[1]: Mounting RPC Pipe File System...
Mounting RPC Pipe File System...
[ 32.803492] systemd[1]: Mounting Huge Pages File System...
Mounting Huge Pages File System...
[ OK ] Listening on LVM2 poll daemon socket.
[ 32.820638] systemd[1]: Listening on LVM2 poll daemon socket.
[ 32.827089] systemd[1]: Starting LVM2 poll daemon socket.
[ OK ] Created slice system-serial\x2dgetty.slice.
[ 32.839668] systemd[1]: Created slice system-serial\x2dgetty.slice.
[ 32.846703] systemd[1]: Starting system-serial\x2dgetty.slice.
[ 32.853860] systemd[1]: Mounting Debug File System...
Mounting Debug File System...
[ 32.865228] systemd[1]: Mounting POSIX Message Queue File System...
Mounting POSIX Message Queue File System...
[ OK ] Reached target Slices.
[ 32.883629] systemd[1]: Reached target Slices.
[ 32.888619] systemd[1]: Starting Slices.
[ OK ] Started Collect Read-Ahead Data.
[ 32.900644] systemd[1]: Started Collect Read-Ahead Data.
[ OK ] Started Replay Read-Ahead Data.
[ 32.913711] systemd[1]: Started Replay Read-Ahead Data.
[ 32.926948] systemd[1]: Starting Create Static Device Nodes in /dev...
Starting Create Static Device Nodes in /dev...
[ 32.948394] systemd[1]: Starting Apply Kernel Variables...
Starting Apply Kernel Variables...
[ 32.960282] systemd[1]: Mounting Configuration File System...
Mounting Configuration File System...
[ 32.972250] systemd[1]: Starting oneSIS System Init...
Starting oneSIS System Init...
[ 32.983138] systemd[1]: Starting Load/Save Random Seed...
Starting Load/Save Random Seed...
[ 32.583186] mount[1146]: mount: unknown files[ 33.001384] systemd[1]: Starting udev Coldplug all Devices...
ystem type 'nfsd'
Starting udev Coldplug all Devices...
[ 32.597503] m[ 33.017146] systemd[1]: Starting Setup Virtual Console...
ount[1147]: mount: mount point /var/lib/nfs/rpc_pipefs does not exist
Starting Setup Virtual Console...
[ OK ] Mounted POSIX Message Queue File System.
[ 33.044590] systemd[1]: Mounted POSIX Message Queue File System.
[ OK ] Mounted Huge Pages File System.
[ 33.057587] systemd[1]: Mounted Huge Pages File System.
[ OK ] Mounted Debug File System.
[ 33.068568] systemd[1]: Mounted Debug File System.
[ OK ] Mounted Configuration File System.
[ 33.090580] systemd[1]: Mounted Configuration File System.
[ OK ] Started Journal Service.
[ 33.101598] systemd[1]: Started Journal Service.
[FAILED] Failed to mount NFSD configuration filesystem.
See 'systemctl status proc-fs-nfsd.mount' for details.
[DEPEND] Dependency failed for GSSAPI Proxy Daemon.
[FAILED] Failed to mount RPC Pipe File System.
See 'systemctl status var-lib-nfs-rpc_pipefs.mount' for details.
[DEPEND] Dependency failed for RPC security service for NFS server.
[DEPEND] Dependency failed for RPC security service for NFS client and server.
[ OK ] Started Create Static Device Nodes in /dev.
[ OK ] Started Apply Kernel Variables.
[FAILED] Failed to start Load/Save Random Seed.
See 'systemctl status systemd-random-seed.service' for details.
[ 32.773506] rc.preinit[1168]: oneSIS: Initializing
[ OK ] Started LVM2 metadata daemon.
[ 32.788611] Starting LVM2 metadata daemon...rc.preinit
[1168]: oneSIS: preinit complete
Starting udev Kernel Device Manager...
[ OK ] Reached target NFS client services.
Starting Flush Journal to Persistent Storage...
[ OK ] Started Monitoring of LVM2 mirrors,...ng dmeventd or progress polling.
[ OK ] Started oneSIS System Init.
[ OK ] Started Setup Virtual Console.
[ OK ] Started udev Coldplug all Devices.
Starting udev Wait for Complete Device Initialization...
Starting Configure read-only root support...
[ OK ] Reached target Local File Systems (Pre).
[ 33.349183] systemd-journald[1144]: Received request to flush runtime journal from PID 1
[ OK ] Started Configure read-only root support.
[ OK ] Started Flush Journal to Persistent Storage.
[ OK ] Started udev Kernel Device Manager.
Starting Show Plymouth Boot Screen...
[ OK ] Started Show Plymouth Boot Screen.
[ OK ] Found device /dev/ttyS1.
G[ OK ] Started udev Wait for Complete Device Initialization.
Starting Activation of DM RAID sets...
[ OK ] Started Activation of DM RAID sets.
[ OK ] Reached target Encrypted Volumes.
[ OK ] Reached target Local File Systems.
Starting Preprocess NFS configuration...
Starting Tell Plymouth To Write Out Runtime Data...
Starting Create Volatile Files and Directories...
Starting Update is Completed...
[FAILED] Failed to start Update is Completed.
See 'systemctl status systemd-update-done.service' for details.
[ OK ] Started Preprocess NFS configuration.
[ OK ] Started Tell Plymouth To Write Out Runtime Data.
[FAILED] Failed to start Create Volatile Files and Directories.
See 'systemctl status systemd-tmpfiles-setup.service' for details.
Starting Security Auditing Service...
[ 34.190695] augenrules[2348]: mktemp: failed to create file via template ��‘/tmp/aurules.XXXXXXXX��’: No such file or directory
[ 34.193367] augenrules[2348]: /sbin/augenrules: line 76: ${TmpRules}: ambiguous redirect
[ 34.194978] augenrules[2348]: /sbin/augenrules: line 99: ${TmpRules}: ambiguous redirect
[ 34.225184] augenrules[2348]: cp: cannot create regular file ��‘/etc/audit/audit.rules.prev��’: Read-only file system
[ 34.234550] augenrules[2348]: cp: missing destination file operand after ��‘/etc/audit/audit.rules��’
[ 34.234932] augenrules[2348]: Try 'cp --help' for more information.
[ 34.242053] augenrules[2348]: chmod: changing permissions of ��‘/etc/audit/audit.rules��’: Read-only file system
[FAILED] Failed to start Security Auditing Service.
See 'systemctl status auditd.service' for details.
Starting Update UTMP about System Boot/Shutdown...
[ OK ] Started Update UTMP about System Boot/Shutdown.
[ OK ] Reached target System Initialization.
[ OK ] Reached target Timers.
[FAILED] Failed to listen on CUPS Printing Service Sockets.
See 'systemctl status cups.socket' for details.
[FAILED] Failed to listen on RPCbind Server Activation Socket.
See 'systemctl status rpcbind.socket' for details.
[FAILED] Failed to listen on Virtual machine log manager socket.
See 'systemctl status virtlogd.socket' for details.
[DEPEND] Dependency failed for Virtualization daemon.
[FAILED] Failed to listen on Virtual machine lock manager socket.
See 'systemctl status virtlockd.socket' for details.
[FAILED] Failed to listen on Avahi mDNS/DNS-SD Stack Activation Socket.
See 'systemctl status avahi-daemon.socket' for details.
[DEPEND] Dependency failed for Avahi mDNS/DNS-SD Stack.
[ OK ] Reached target Paths.
[ OK ] Listening on Open-iSCSI iscsid Socket.
[FAILED] Failed to listen on D-Bus System Message Bus Socket.
See 'systemctl status dbus.socket' for details.
[DEPEND] Dependency failed for D-Bus System Message Bus.
[DEPEND] Dependency failed for Dynamic System Tuning Daemon.
[ OK ] Listening on Open-iSCSI iscsiuio Socket.
[ OK ] Reached target Sockets.
[ OK ] Reached target Basic System.
Starting Resets System Activity Logs...
[ OK ] Started irqbalance daemon.
Starting irqbalance daemon...
Starting Network Manager...
[ OK ] Started ABRT Automated Bug Reporting Tool.
Starting ABRT Automated Bug Reporting Tool...
[ OK ] Started libstoragemgmt plug-in server daemon.
Starting libstoragemgmt plug-in server daemon...
[ OK ] Started Hardware RNG Entropy Gatherer Daemon.
Starting Hardware RNG Entropy Gatherer Daemon...
Starting Load CPU microcode update...
Starting Run automatic yum updates as a cron job...
Starting Accounts Service...
[ 34.291019] rngd[2373]: Unable to open file: /dev/tpm0
[ 34.291328] rngd[2373]: can't open any entropy source
[ 34.291581] rngd[2373]: Maybe RNG device modules are not loaded
Starting Kernel Samepage Merging...
Starting Login Service...
Starting Console Mouse manager...
[ OK ] Started Manage Sound Card State (restore and store).
Starting Manage Sound Card State (restore and store)...
[ 34.337535] lsmd[2372]: Unable to access socket directory /var/run/lsm/ipc, errno= 2
[ 34.338430] Starting Install ABRT coredump hook...
touch[2376]: /bin/touch: cannot touch ��‘/var/lock/subsys/yum-cron��’: No such file or directory
Starting Authorization Manager...
Starting Dump dmesg to /var/log/dmesg...
[FAILED] Failed to start RealtimeKit Scheduling Policy Service.
See 'systemctl status rtkit-daemon.service' for details.
Starting RealtimeKit Scheduling Policy Service...
[ OK ] Started Self Monitoring and Reporting Technology (SMART) Daemon.
Starting Self Monitoring and Reporting Technology (SMART) Daemon...
[ OK ] Started ABRT kernel log watcher.
Starting ABRT kernel log watcher...
[FAILED] Failed to start Run automatic yum updates as a cron job.
See 'systemctl status yum-cron.service' for details.
[ OK ] Started Kernel Samepage Merging.
Starting Kernel Samepage Merging (KSM) Tuning Daemon...
[FAILED] Failed to start Console Mouse manager.
See 'systemctl status gpm.service' for details.
[ OK ] Started Load CPU microcode update.
[ 34.421302] rhel-dmesg[2388]: /usr/lib/systemd/rhel-dmesg: line 3: /var/log/dmesg: No such file or directory
[FAILED] Failed to start Dump dmesg to /var/log/dmesg.
See 'systemctl status rhel-dmesg.service' for details.
[FAILED] Failed to start Login Service.
See 'systemctl status systemd-logind.service' for details.
[ OK ] Stopped Login Service.
[FAILED] Failed to listen on D-Bus System Message Bus Socket.
See 'systemctl status dbus.socket' for details.
Starting Login Service...
[ 34.480028] sa1[2368]: Cannot open /var/log/sa/sa02: No such file or directory
[FAILED] Failed to start Resets System Activity Logs.
See 'systemctl status sysstat.service' for details.
[FAILED] Failed to start Login Service.
See 'systemctl status systemd-logind.service' for details.
[ OK ] Stopped Login Service.
[FAILED] Failed to listen on D-Bus System Message Bus Socket.
See 'systemctl status dbus.socket' for details.
Starting Login Service...
[ 34.496286] ksmtuned[2394]: touch: cannot touch ��‘/var/run/ksmtune.pid��’: No such file or directory
[ OK ] Started Kernel Samepage Merging (KSM) Tuning Daemon.
[ OK ] Started Accounts Service.
[FAILED] Failed to start Login Service.
See 'systemctl status systemd-logind.service' for details.
[ OK ] Stopped Login Service.
[FAILED] Failed to listen on D-Bus System Message Bus Socket.
See 'systemctl status dbus.socket' for details.
Starting Login Service...
[FAILED] Failed to start Login Service.
See 'systemctl status systemd-logind.service' for details.
[ OK ] Stopped Login Service.
[FAILED] Failed to listen on D-Bus System Message Bus Socket.
See 'systemctl status dbus.socket' for details.
Starting Login Service...
[FAILED] Failed to start Login Service.
See 'systemctl status systemd-logind.service' for details.
[ OK ] Stopped Login Service.
[FAILED] Failed to listen on D-Bus System Message Bus Socket.
See 'systemctl status dbus.socket' for details.
[FAILED] Failed to start Login Service.
See 'systemctl status systemd-logind.service' for details.
[ 34.590198] NetworkManager[2370]: Cannot create parents for '/var/lib/NetworkManager': No such file or directory
[FAILED] Failed to start Network Manager.
See 'systemctl status NetworkManager.service' for details.
[DEPEND] Dependency failed for Network Manager Wait Online.
Starting LSB: Bring up/down networking...
[ 34.648250] abrt-install-ccpp-hook[2384]: mkdir: cannot create directory ��‘/var��’: File exists
[ 34.649080] abrt-install-ccpp-hook[2384]: /usr/sbin/abrt-install-ccpp-hook: line 55: /var/run/abrt/saved_core_pattern: No such file or directory
[ OK ] Started Install ABRT coredump hook.
[ OK ] Started Authorization Manager.
[ OK ] Stopped Network Manager.
Starting Network Manager...
[ 34.816374] NetworkManager[2451]: Cannot create parents for '/var/lib/NetworkManager': No such file or directory
[FAILED] Failed to start Network Manager.
See 'systemctl status NetworkManager.service' for details.
[DEPEND] Dependency failed for Network Manager Wait Online.
[ OK ] Stopped Network Manager.
Starting Network Manager...
[ 35.203398] NetworkManager[2487]: Cannot create parents for '/var/lib/NetworkManager': No such file or directory
[FAILED] Failed to start Network Manager.
See 'systemctl status NetworkManager.service' for details.
[DEPEND] Dependency failed for Network Manager Wait Online.
[ OK ] Stopped Network Manager.
Starting Network Manager...
[ 35.581257] network[2421]: Bringing up loopback interface: ./network-functions: line 262: cd: /var/run/netreport: No such file or directory
[ 35.582507] network[2421]: [ OK ]
[ 35.589441] NetworkManager[2543]: Cannot create parents for '/var/lib/NetworkManager': No such file or directory
[FAILED] Failed to start Network Manager.
See 'systemctl status NetworkManager.service' for details.
[DEPEND] Dependency failed for Network Manager Wait Online.
[ 35.860630] network[2421]: Bringing up interface enp11s0: ERROR : [/etc/sysconfig/network-scripts/ifup-eth] Device enp11s0 does not seem to be presen.
[ 35.872926] network[2421]: [FAILED]
[ OK ] Stopped Network Manager.
Starting Network Manager...
[ 35.970192] network[2421]: touch: cannot touch ��‘/var/lock/subsys/network��’: No such file or directory
[FAILED] Failed to start LSB: Bring up/down networking.
See 'systemctl status network.service' for details.
[ 35.975743] NetworkManager[2610]: Cannot create parents for '/var/lib/NetworkManager': No such file or directory
[FAILED] Failed to start Network Manager.
See 'systemctl status NetworkManager.service' for details.
[DEPEND] Dependency failed for Network Manager Wait Online.
[ OK ] Reached target Network.
Starting OpenSSH server daemon...
Starting Notify NFS peers of a restart...
Starting Logout off all iSCSI sessions on shutdown...
Starting Postfix Mail Transport Agent...
Starting System Logging Service...
[FAILED] Failed to start CUPS Printing Service.
See 'systemctl status cups.service' for details.
Starting CUPS Printing Service...
[ OK ] Reached target Network is Online.
[ OK ] Started Logout off all iSCSI sessions on shutdown.
[ OK ] Reached target Remote File Systems (Pre).
[ OK ] Reached target Remote File Systems.
Starting Crash recovery kernel arming...
Starting Permit User Sessions...
Starting Availability of block devices...
[ OK ] Started Availability of block devices.
[ OK ] Started Notify NFS peers of a restart.
[ OK ] Started Permit User Sessions.
[ OK ] Started Command Scheduler.
Starting Command Scheduler...
Starting Wait for Plymouth Boot Screen to Quit...
Starting GNOME Display Manager...
[ OK ] Started Job spooling tools.
Starting Job spooling tools...
[ 36.058063] kdumpctl[2625]: /usr/bin/kdumpctl: line 31: /var/lock/kdump: No such file or directory
[FAILED] Failed to start Crash recovery kernel arming.
See 'systemctl status kdump.service' for details.
[ 36.068516] crond[2631]: crond: can't open or create /var/run/crond.pid: No such file or directory
[ OK ] Stopped Network Manager.
[FAILED] Failed to start Network Manager.
See 'systemctl status NetworkManager.service' for details.
[DEPEND] Dependency failed for Network Manager Wait Online.
[FAILED] Failed to start System Logging Service.
See 'systemctl status rsyslog.service' for details.
[ 36.117548] sshd[2619]: Missing privilege separation directory: /var/empty/sshd
[FAILED] Failed to start OpenSSH server daemon.
See 'systemctl status sshd.service' for details.
[ 36.151970] aliasesdb[2622]: newaliases: fatal: chdir /var/spool/postfix: No such file or directory
[ 36.155433] aliasesdb[2622]: touch: cannot touch ��‘/var/lib/misc/postfix.aliasesdb-stamp��’: No such file or directory
[ OK ] Stopped System Logging Service.
Starting System Logging Service...
[FAILED] Failed to start System Logging Service.
See 'systemctl status rsyslog.service' for details.
[ OK ] Stopped System Logging Service.
Starting System Logging Service...
[FAILED] Failed to start System Logging Service.
See 'systemctl status rsyslog.service' for details.
[FAILED] Failed to start Postfix Mail Transport Agent.
See 'systemctl status postfix.service' for details.
[ OK ] Stopped System Logging Service.
Starting System Logging Service...
[FAILED] Failed to start System Logging Service.
See 'systemctl status rsyslog.service' for details.
[ OK ] Stopped System Logging Service.
Starting System Logging Service...
[FAILED] Failed to start System Logging Service.
See 'systemctl status rsyslog.service' for details.
[ OK ] Stopped System Logging Service.
[FAILED] Failed to start System Logging Service.
See 'systemctl status rsyslog.service' for details.
[ OK ] Stopped OpenSSH server daemon.
Starting OpenSSH server daemon...
[ 78.379658] sshd[2659]: Missing privilege separation directory: /var/empty/sshd
[FAILED] Failed to start OpenSSH server daemon.
See 'systemctl status sshd.service' for details.
[ OK ] Stopped OpenSSH server daemon.
Starting OpenSSH server daemon...
[ 120.621684] sshd[2661]: Missing privilege separation directory: /var/empty/sshd
[FAILED] Failed to start OpenSSH server daemon.
See 'systemctl status sshd.service' for details.
[FAILED] Failed to start GNOME Display Manager.
See 'systemctl status gdm.service' for details.
Starting Terminate Plymouth Boot Screen...
Scientific Linux 7.3 (Nitrogen)
Kernel 3.10.0-514.el7.x86_64 on an x86_64
mcs64 login: [ 152.623495] systemd-readahead[1141]: Failed to open pack file: Read-only file system
CTRL-A Z for help |115200 8N1 | NOR | Minicom 2.3 | VT102 | Online 00:02
|
|
From: Josh E. <jj...@gm...> - 2017-05-02 20:59:42
|
Try altering your etc/systemd/system.conf to enable console logging on bootup. Set DefaultStandardOutput=journal+console then reboot. You should get much more output which might help point out what's going on. -JE On Tue, May 2, 2017 at 1:46 PM, ROSS, MARK D CTR USAF AFMC 412 RANS/ENR < mar...@us...> wrote: > Thanks Josh here is the output. > > [ 6.494020] i8042: No controller found > [ 6.498239] tsc: Refined TSC clocksource calibration: 2299.999 MHz > [ 6.498268] mousedev: PS/2 mouse device common for all mice > [ 6.498388] rtc_cmos 00:01: RTC can wake from S4 > [ 6.498545] rtc_cmos 00:01: rtc core: registered rtc_cmos as rtc0 > [ 6.498582] rtc_cmos 00:01: alarms up to one day, y3k, 242 bytes nvram, > hpet irqs > [ 6.498626] Intel P-state driver initializing. > [ 6.505782] cpuidle: using governor menu > [ 6.506408] hidraw: raw HID events driver (C) Jiri Kosina > [ 6.506599] usbcore: registered new interface driver usbhid > [ 6.506599] usbhid: USB HID core driver > [ 6.506692] drop_monitor: Initializing network drop monitor service > [ 6.506925] TCP: cubic registered > [ 6.506930] Initializing XFRM netlink socket > [ 6.507167] NET: Registered protocol family 10 > [ 6.507770] NET: Registered protocol family 17 > [ 6.511357] microcode: CPU0 sig=0x206d7, pf=0x1, revision=0x710 > [ 6.511370] microcode: CPU1 sig=0x206d7, pf=0x1, revision=0x710 > [ 6.511378] microcode: CPU2 sig=0x206d7, pf=0x1, revision=0x710 > [ 6.511429] microcode: CPU3 sig=0x206d7, pf=0x1, revision=0x710 > [ 6.511442] microcode: CPU4 sig=0x206d7, pf=0x1, revision=0x710 > [ 6.511455] microcode: CPU5 sig=0x206d7, pf=0x1, revision=0x710 > [ 6.511464] microcode: CPU6 sig=0x206d7, pf=0x1, revision=0x710 > [ 6.511476] microcode: CPU7 sig=0x206d7, pf=0x1, revision=0x710 > [ 6.511484] microcode: CPU8 sig=0x206d7, pf=0x1, revision=0x710 > [ 6.511497] microcode: CPU9 sig=0x206d7, pf=0x1, revision=0x710 > [ 6.511505] microcode: CPU10 sig=0x206d7, pf=0x1, revision=0x710 > [ 6.511518] microcode: CPU11 sig=0x206d7, pf=0x1, revision=0x710 > [ 6.511594] microcode: Microcode Update Driver: v2.01 < > ti...@ai...>, Peter Oruba > [ 6.511717] Loading compiled-in X.509 certificates > [ 6.512597] Loaded X.509 cert 'Fermi National Accelerator Laboratory: > Scientific Linux 7 kpatch signing key: c8e46da25bf2b6ed33675277e795de > 682b4666d6' > [ 6.513448] Loaded X.509 cert 'Fermi National Accelerator Laboratory: > Scientific Linux 7 driver update signing key: 98ec7b1456fb6a6b00e81292343a0f > f7268df8 > 21' > [ 6.513979] Loaded X.509 cert 'Red Hat Enterprise Linux kernel signing > key: 02c33df7a9cd1651f844f720041963da33995e99' > [ 6.513996] registered taskstats version 1 > [ 6.516697] Key type trusted registered > [ 6.518792] Key type encrypted registered > [ 6.520721] IMA: No TPM chip found, activating TPM-bypass! > [ 6.531699] rtc_cmos 00:01: setting system clock to 2017-05-02 20:07:19 > UTC (1493755639) > [ 6.749018] Switched to clocksource tsc > [ 6.754142] Freeing unused kernel memory: 1684k freed > oneSIS: Running /init > oneSIS: Loading pci modules > [ 6.854922] usb 2-1: new high-speed USB device number 2 using ehci-pci > [ 6.862238] usb 1-1: new high-speed USB device number 2 using ehci-pci > [ 6.983295] usb 2-1: New USB device found, idVendor=8087, idProduct=0024 > [ 6.990790] usb 2-1: New USB device strings: Mfr=0, Product=0, > SerialNumber=0 > [ 6.998756] usb 1-1: New USB device found, idVendor=8087, idProduct=0024 > [ 7.006244] usb 1-1: New USB device strings: Mfr=0, Product=0, > SerialNumber=0 > [ 7.015082] hub 2-1:1.0: USB hub found > [ 7.019280] hub 1-1:1.0: USB hub found > [ 7.023717] hub 1-1:1.0: 6 ports detected > [ 7.028201] hub 2-1:1.0: 8 ports detected > [ 7.305885] usb 1-1.6: new high-speed USB device number 3 using ehci-pci > [ 7.313378] usb 2-1.2: new low-speed USB device number 3 using ehci-pci > [ 7.407193] usb 1-1.6: New USB device found, idVendor=0624, > idProduct=0248 > [ 7.414894] usb 1-1.6: New USB device strings: Mfr=1, Product=2, > SerialNumber=3 > [ 7.423083] usb 1-1.6: Product: Gadget USB HUB > [ 7.428052] usb 1-1.6: Manufacturer: no manufacturer > [ 7.433599] usb 1-1.6: SerialNumber: 0123456789 > [ 7.439419] hub 1-1.6:1.0: USB hub found > [ 7.443942] hub 1-1.6:1.0: 6 ports detected > [ 7.449521] usb 2-1.2: New USB device found, idVendor=0d3d, > idProduct=0040 > [ 7.457211] usb 2-1.2: New USB device strings: Mfr=0, Product=2, > SerialNumber=0 > [ 7.465374] usb 2-1.2: Product: USB CAT5 > [ 7.474793] input: USB CAT5 as /devices/pci0000:00/0000:00: > 1d.0/usb2/2-1/2-1.2/2-1.2:1.0/input/input1 > [ 7.536746] hid-generic 0003:0D3D:0040.0001: input,hidraw0: USB HID > v1.00 Keyboard [USB CAT5] on usb-0000:00:1d.0-1.2/input0 > [ 7.563652] input: USB CAT5 as /devices/pci0000:00/0000:00: > 1d.0/usb2/2-1/2-1.2/2-1.2:1.1/input/input2 > [ 7.574900] hid-generic 0003:0D3D:0040.0002: input,hidraw1: USB HID > v1.00 Mouse [USB CAT5] on usb-0000:00:1d.0-1.2/input1 > [ 7.758907] usb 1-1.6.1: new high-speed USB device number 4 using > ehci-pci > [ 7.852331] usb 1-1.6.1: New USB device found, idVendor=0624, > idProduct=0249 > [ 7.860210] usb 1-1.6.1: New USB device strings: Mfr=4, Product=5, > SerialNumber=6 > [ 7.868575] usb 1-1.6.1: Product: Keyboard/Mouse Function > [ 7.874605] usb 1-1.6.1: Manufacturer: Avocent > [ 7.879569] usb 1-1.6.1: SerialNumber: 20120917 > [ 7.891350] input: Avocent Keyboard/Mouse Function as > /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6/1-1.6.1/1- > 1.6.1:1.0/input/input3 > [ 7.956769] hid-generic 0003:0624:0249.0003: input,hidraw2: USB HID > v1.00 Keyboard [Avocent Keyboard/Mouse Function] on > usb-0000:00:1a.0-1.6.1/input0 > [ 7.973514] input: Avocent Keyboard/Mouse Function as > /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6/1-1.6.1/1- > 1.6.1:1.1/input/input4 > [ 7.988101] hid-generic 0003:0624:0249.0004: input,hidraw3: USB HID > v1.00 Mouse [Avocent Keyboard/Mouse Function] on > usb-0000:00:1a.0-1.6.1/input1 > [ 8.004336] input: Avocent Keyboard/Mouse Function as > /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6/1-1.6.1/1- > 1.6.1:1.2/input/input5 > [ 8.018503] hid-generic 0003:0624:0249.0005: input,hidraw4: USB HID > v1.00 Mouse [Avocent Keyboard/Mouse Function] on > usb-0000:00:1a.0-1.6.1/input2 > [ 23.868972] pps_core: LinuxPPS API ver. 1 registered > [ 23.874526] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo > Giometti <gio...@li...> > [ 23.889402] PTP clock support registered > [ 23.900677] tg3.c:v3.137 (May 11, 2014) > [ 23.917098] tg3 0000:01:00.0 eth0: Tigon3 [partno(BCM95720) rev > 5720000] (PCI Express) MAC address b8:ca:3a:f8:67:1e > [ 23.928866] tg3 0000:01:00.0 eth0: attached PHY is 5720C > (10/100/1000Base-T Ethernet) (WireSpeed[1], EEE[1]) > [ 23.939842] tg3 0000:01:00.0 eth0: RXcsums[1] LinkChgREG[0] MIirq[0] > ASF[1] TSOcap[1] > [ 23.948586] tg3 0000:01:00.0 eth0: dma_rwctrl[00000001] dma_mask[64-bit] > [ 23.977974] tg3 0000:01:00.1 eth1: Tigon3 [partno(BCM95720) rev > 5720000] (PCI Express) MAC address b8:ca:3a:f8:67:1f > [ 23.989737] tg3 0000:01:00.1 eth1: attached PHY is 5720C > (10/100/1000Base-T Ethernet) (WireSpeed[1], EEE[1]) > [ 24.000715] tg3 0000:01:00.1 eth1: RXcsums[1] LinkChgREG[0] MIirq[0] > ASF[1] TSOcap[1] > [ 24.009456] tg3 0000:01:00.1 eth1: dma_rwctrl[00000001] dma_mask[64-bit] > [ 24.038852] tg3 0000:02:00.0 eth2: Tigon3 [partno(BCM95720) rev > 5720000] (PCI Express) MAC address b8:ca:3a:f8:67:20 > [ 24.050611] tg3 0000:02:00.0 eth2: attached PHY is 5720C > (10/100/1000Base-T Ethernet) (WireSpeed[1], EEE[1]) > [ 24.061587] tg3 0000:02:00.0 eth2: RXcsums[1] LinkChgREG[0] MIirq[0] > ASF[1] TSOcap[1] > [ 24.070328] tg3 0000:02:00.0 eth2: dma_rwctrl[00000001] dma_mask[64-bit] > [ 24.099836] tg3 0000:02:00.1 eth3: Tigon3 [partno(BCM95720) rev > 5720000] (PCI Express) MAC address b8:ca:3a:f8:67:21 > [ 24.111594] tg3 0000:02:00.1 eth3: attached PHY is 5720C > (10/100/1000Base-T Ethernet) (WireSpeed[1], EEE[1]) > [ 24.122561] tg3 0000:02:00.1 eth3: RXcsums[1] LinkChgREG[0] MIirq[0] > ASF[1] TSOcap[1] > [ 24.131303] tg3 0000:02:00.1 eth3: dma_rwctrl[00000001] dma_mask[64-bit] > [ 24.151679] RPC: Registered named UNIX socket transport module. > [ 24.158299] RPC: Registered udp transport module. > [ 24.163552] RPC: Registered tcp transport module. > [ 24.168800] RPC: Registered tcp NFSv4.1 backchannel transport module. > [ 24.184744] FS-Cache: Loaded > [ 24.198031] FS-Cache: Netfs 'nfs' registered for caching > Attempting DHCP on eth0 ... > udhcpc (v1.18.5) started > [ 24.344714] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready > Sending discover... > Sending discover... > [ 27.832421] tg3 0000:01:00.0 eth0: Link is up at 1000 Mbps, full duplex > [ 27.839807] tg3 0000:01:00.0 eth0: Flow control is off for TX and off > for RX > [ 27.847673] tg3 0000:01:00.0 eth0: EEE is disabled > [ 27.853034] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready > Sending discover... > Sending select for 192.168.106.103... > Lease of 192.168.106.103 obtained, lease time 604800 > oneSIS: Setting IP address on eth0: 192.168.106.103 > oneSIS: Setting default route: 192.168.106.1 > oneSIS: Setting hostname: mcs64 > oneSIS: Checking network connectivity to 192.168.106.1 > oneSIS: Mounting NFS root filesystem: /var/lib/oneSIS/image from > xxx.198.80.51 > oneSIS: Leaving initramfs > [ 31.682161] SELinux: Disabled at runtime. > [ 31.721182] type=1404 audit(1493755664.696:2): selinux=0 > auid=4294967295 ses=4294967295 > [ 31.747925] ERST: NVRAM ERST Log Address Range is not implemented yet > [ 31.761540] systemd[1]: systemd 219 running in system mode. (+PAM > +AUDIT +SELINUX +IMA -APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP > +GCRYPT +GNUTLS +AC > L +XZ -LZ4 -SECCOMP +BLKID +ELFUTILS +KMOD +IDN) > [ 31.782092] systemd[1]: Detected architecture x86-64. > > Welcome to Scientific Linux 7.3 (Nitrogen)! > > [ OK ] Reached target User and Group Name Lookups. > [ 32.223306] systemd[1]: Reached target User and Group Name Lookups. > [ 32.230355] systemd[1]: Starting User and Group Name Lookups. > [ OK ] Reached target Swap. > [ 32.241280] systemd[1]: Reached target Swap. > [ 32.246079] systemd[1]: Starting Swap. > [ OK ] Set up automount Arbitrary Executab...ats File System Automount > Point. > [ 32.260294] systemd[1]: Set up automount Arbitrary Executable File > Formats File System Automount Point. > [ 32.270824] systemd[1]: Starting Arbitrary Executable File Formats File > System Automount Point. > [ 32.280664] systemd[1]: Started Forward Requests to Wall Directory > Watch. > [ 32.289127] systemd[1]: Starting Forward Requests to Wall Directory > Watch. > [ OK ] Created slice Root Slice. > [ 32.304300] systemd[1]: Created slice Root Slice. > [ 32.309603] systemd[1]: Starting Root Slice. > [ OK ] Created slice User and Session Slice. > [ 32.321317] systemd[1]: Created slice User and Session Slice. > [ 32.327761] systemd[1]: Starting User and Session Slice. > [ OK ] Listening on Delayed Shutdown Socket. > [ 32.340283] systemd[1]: Listening on Delayed Shutdown Socket. > [ 32.346716] systemd[1]: Starting Delayed Shutdown Socket. > [ OK ] Listening on udev Control Socket. > [ 32.359296] systemd[1]: Listening on udev Control Socket. > [ 32.365398] systemd[1]: Starting udev Control Socket. > [ OK ] Listening on udev Kernel Socket. > [ 32.377321] systemd[1]: Listening on udev Kernel Socket. > [ 32.383276] systemd[1]: Starting udev Kernel Socket. > [ OK ] Listening on LVM2 metadata daemon socket. > [ 32.396289] systemd[1]: Listening on LVM2 metadata daemon socket. > [ 32.403128] systemd[1]: Starting LVM2 metadata daemon socket. > [ OK ] Listening on Device-mapper event daemon FIFOs. > [ 32.417292] systemd[1]: Listening on Device-mapper event daemon FIFOs. > [ 32.424631] systemd[1]: Starting Device-mapper event daemon FIFOs. > [ OK ] Listening on /dev/initctl Compatibility Named Pipe. > [ 32.440291] systemd[1]: Listening on /dev/initctl Compatibility Named > Pipe. > [ 32.448102] systemd[1]: Starting /dev/initctl Compatibility Named Pipe. > [ OK ] Listening on Journal Socket. > [ 32.461293] systemd[1]: Listening on Journal Socket. > [ 32.466880] systemd[1]: Starting Journal Socket. > [ OK ] Created slice System Slice. > [ 32.477299] systemd[1]: Created slice System Slice. > [ 32.482782] systemd[1]: Starting System Slice. > [ 32.488529] systemd[1]: Starting Journal Service... > Starting Journal Service... > [ 32.500040] systemd[1]: Starting Collect Read-Ahead Data... > Starting Collect Read-Ahead Data... > [ OK ] Created slice system-getty.slice. > [ 32.519227] systemd[1]: Created slice system-getty.slice. > [ 32.525318] systemd[1]: Starting system-getty.slice. > [ 32.531655] systemd[1]: Starting Monitoring of LVM2 mirrors, snapshots > etc. using dmeventd or progress polling... > Starting Monitoring of LVM2 mirrors... dmeventd or progress > polling... > [ OK ] Created slice system-serial\x2dgetty.slice. > [ 32.559257] systemd[1]: Created slice system-serial\x2dgetty.slice. > [ 32.566295] systemd[1]: Starting system-serial\x2dgetty.slice. > [ OK ] Created slice system-selinux\x2dpol...grate\ > x2dlocal\x2dchanges.slice. > [ 32.582243] systemd[1]: Created slice system-selinux\x2dpolicy\ > x2dmigrate\x2dlocal\x2dchanges.slice. > [ 32.592753] systemd[1]: Starting system-selinux\x2dpolicy\ > x2dmigrate\x2dlocal\x2dchanges.slice. > [ 32.603279] systemd[1]: Starting Replay Read-Ahead Data... > Starting Replay Read-Ahead Data... > [ 32.617063] systemd[1]: Mounting POSIX Message Queue File System... > Mounting POSIX Message Queue File System... > [ 32.631054] systemd[1]: Mounting Debug File System... > Mounting Debug File System... > [ 32.754464] systemd[1]: MESSAGE=Failed to check directory > /var/lib/nfs/rpc_pipefs: No such file or directory > [ 32.766584] systemd[1]: Mounting RPC Pipe File System... > Mounting RPC Pipe File System... > [ 32.778782] systemd[1]: Mounting Huge Pages File System... > Mounting Huge Pages File System... > [ OK ] Reached target Slices. > [ 32.796241] systemd[1]: Reached target Slices. > [ 32.801317] systemd[1]: Starting Slices. > [ 32.806507] systemd[1]: Mounting NFSD configuration filesystem... > Mounting NFSD configuration filesystem... > [ OK ] Listening on LVM2 poll daemon socket. > [ 32.826262] systemd[1]: Listening on LVM2 poll daemon socket. > [ 32.832708] systemd[1]: Starting LVM2 poll daemon socket. > [ OK ] Mounted POSIX Message Queue File System. > [ 32.846259] systemd[1]: Mounted POSIX Message Queue File System. > [ OK ] Mounted Huge Pages File System. > [ 32.859281] systemd[1]: Mounted Huge Pages File System. > [ OK ] Mounted Debug File System. > [ 32.870283] systemd[1]: Mounted Debug File System. > [ OK ] Started Collect Read-Ahead Data. > [ 32.882285] systemd[1]: Started Collect Read-Ahead Data. > [ OK ] Started Journal Service. > [ 32.893250] systemd[1]: Started Journal Service. > [ OK ] Started Replay Read-Ahead Data. > [FAILED] Failed to mount RPC Pipe File System. > See 'systemctl status var-lib-nfs-rpc_pipefs.mount' for details. > [DEPEND] Dependency failed for RPC security service for NFS server. > [DEPEND] Dependency failed for RPC security service for NFS client and > server. > [FAILED] Failed to mount NFSD configuration filesystem. > See 'systemctl status proc-fs-nfsd.mount' for details. > [DEPEND] Dependency failed for GSSAPI Proxy Daemon. > [ OK ] Started LVM2 metadata daemon. > Starting LVM2 metadata daemon... > [ OK ] Reached target NFS client services. > Mounting Configuration File System... > Starting Setup Virtual Console... > Starting oneSIS System Init... > Starting Flush Journal to Persistent Storage... > Starting Apply Kernel Variables... > Starting Load/Save Random Seed... > Starting udev Coldplug all Devices... > Starting Create Static Device Nodes in /dev... > [ OK ] Mounted Configuration File System. > [ OK ] Started Monitoring of LVM2 mirrors,...ng dmeventd or progress > polling. > [ OK ] Started Apply Kernel Variables. > [FAILED] Failed to start Load/Save Random Seed. > See 'systemctl status systemd-random-seed.service' for details. > [ OK ] Started Create Static Device Nodes in /dev. > Starting udev Kernel Device Manager... > [ OK ] Reached target Local File Systems (Pre). > [ 33.133713] systemd-journald[1142]: Received request to flush runtime > journal from PID 1 > [ OK ] Started Flush Journal to Persistent Storage. > [ OK ] Started Setup Virtual Console. > [ OK ] Started udev Coldplug all Devices. > Starting udev Wait for Complete Device Initialization... > [ OK ] Started oneSIS System Init. > Starting Configure read-only root support... > [ OK ] Started Configure read-only root support. > [ OK ] Started udev Kernel Device Manager. > Starting Show Plymouth Boot Screen... > [ OK ] Started Show Plymouth Boot Screen. > G[ OK ] Found device /dev/ttyS1. > [ OK ] Started udev Wait for Complete Device Initialization. > Starting Activation of DM RAID sets... > [ OK ] Started Activation of DM RAID sets. > [ OK ] Reached target Local File Systems. > Starting Update is Completed... > Starting Tell Plymouth To Write Out Runtime Data... > Starting Preprocess NFS configuration... > Starting Create Volatile Files and Directories... > [ OK ] Reached target Encrypted Volumes. > [FAILED] Failed to start Update is Completed. > See 'systemctl status systemd-update-done.service' for details. > [ OK ] Started Tell Plymouth To Write Out Runtime Data. > [ OK ] Started Preprocess NFS configuration. > [FAILED] Failed to start Create Volatile Files and Directories. > See 'systemctl status systemd-tmpfiles-setup.service' for details. > Starting Security Auditing Service... > [FAILED] Failed to start Security Auditing Service. > See 'systemctl status auditd.service' for details. > Starting Update UTMP about System Boot/Shutdown... > [ OK ] Started Update UTMP about System Boot/Shutdown. > [ OK ] Reached target System Initialization. > [ OK ] Listening on Open-iSCSI iscsiuio Socket. > [FAILED] Failed to listen on D-Bus System Message Bus Socket. > See 'systemctl status dbus.socket' for details. > [DEPEND] Dependency failed for D-Bus System Message Bus. > [DEPEND] Dependency failed for Dynamic System Tuning Daemon. > [ OK ] Reached target Timers. > [FAILED] Failed to listen on Avahi mDNS/DNS-SD Stack Activation Socket. > See 'systemctl status avahi-daemon.socket' for details. > [DEPEND] Dependency failed for Avahi mDNS/DNS-SD Stack. > [FAILED] Failed to listen on Virtual machine lock manager socket. > See 'systemctl status virtlockd.socket' for details. > [FAILED] Failed to listen on CUPS Printing Service Sockets. > See 'systemctl status cups.socket' for details. > [ OK ] Reached target Paths. > [ OK ] Listening on Open-iSCSI iscsid Socket. > [FAILED] Failed to listen on Virtual machine log manager socket. > See 'systemctl status virtlogd.socket' for details. > [DEPEND] Dependency failed for Virtualization daemon. > [FAILED] Failed to listen on RPCbind Server Activation Socket. > See 'systemctl status rpcbind.socket' for details. > [ OK ] Reached target Sockets. > [ OK ] Reached target Basic System. > Starting Resets System Activity Logs... > [ OK ] Started irqbalance daemon. > Starting irqbalance daemon... > Starting Accounts Service... > [ OK ] Started Self Monitoring and Reporting Technology (SMART) Daemon. > Starting Self Monitoring and Reporting Technology (SMART) > Daemon... > Starting Login Service... > Starting Console Mouse manager... > Starting Load CPU microcode update... > [ OK ] Started Manage Sound Card State (restore and store). > Starting Manage Sound Card State (restore and store)... > Starting Run automatic yum updates as a cron job... > [ OK ] Started ABRT Automated Bug Reporting Tool. > Starting ABRT Automated Bug Reporting Tool... > [ OK ] Started ABRT kernel log watcher. > Starting ABRT kernel log watcher... > Starting Authorization Manager... > [ OK ] Started Hardware RNG Entropy Gatherer Daemon. > Starting Hardware RNG Entropy Gatherer Daemon... > Starting Install ABRT coredump hook... > Starting Dump dmesg to /var/log/dmesg... > Starting Kernel Samepage Merging... > Starting Network Manager... > [FAILED] Failed to start RealtimeKit Scheduling Policy Service. > See 'systemctl status rtkit-daemon.service' for details. > Starting RealtimeKit Scheduling Policy Service... > [ OK ] Started libstoragemgmt plug-in server daemon. > Starting libstoragemgmt plug-in server daemon... > [FAILED] Failed to start Console Mouse manager. > See 'systemctl status gpm.service' for details. > [FAILED] Failed to start Run automatic yum updates as a cron job. > See 'systemctl status yum-cron.service' for details. > [ OK ] Started Kernel Samepage Merging. > Starting Kernel Samepage Merging (KSM) Tuning Daemon... > [FAILED] Failed to start Login Service. > See 'systemctl status symd-logind.service' for details. > [ OK ] Stopped Login Service. > [FAILED] Failed to listen on D-Bus System Message Bus Socket. > See 'systemctl status dbus.socket' for details. > Starting Login Service... > [FAILED] Failed to start Dump dmesg to /var/log/dmesg. > See 'systemctl status rhel-dmesg.service' for details. > [ OK ] Started Load CPU microcode update. > [FAILED] Failed to start Login Service. > See 'systemctl status systemd-logind.service' for details. > [FAILED] Failed to start Resets System Activity Logs. > See 'systemctl status sysstat.service' for details. > [ OK ] Stopped Login Service. > [FAILED] Failed to listen on D-Bus System Message Bus Socket. > See 'systemctl status dbus.socket' for details. > Starting Login Service... > [ OK ] Started Kernel Samepage Merging (KSM) Tuning Daemon. > [FAILED] Failed to start Login Service. > See 'systemctl status systemd-logind.service' for details. > [ OK ] Started Accounts Service. > [ OK ] Stopped Login Service. > [FAILED] Failed to listen on D-Bus System Message Bus Socket. > See 'systemctl status dbus.socket' for details. > Starting Login Service... > [FAILED] Failed to start Login Service. > See 'systemctl status systemd-logind.service' for details. > [ OK ] Stopped Login Service. > [FAILED] Failed to listen on D-Bus System Message Bus Socket. > See 'systemctl status dbus.socket' for details. > Starting Login Service... > [FAILED] Failed to start Login Service. > See 'systemctl status systemd-logind.service' for details. > [ OK ] Stopped Login Service. > [FAILED] Failed to listen on D-Bus System Message Bus Socket. > See 'systemctl status dbus.socket' for details. > [FAILED] Failed to start Login Service. > See 'systemctl status systemd-logind.service' for details. > [FAILED] Failed to start Network Manager. > See 'systemctl status NetworkManager.service' for details. > [DEPEND] Dependency failed for Network Manager Wait Online. > Starting LSB: Bring up/down networking... > [ OK ] Started Install ABRT coredump hook. > [ OK ] Started Authorization Manager. > [ OK ] Stopped Network Manager. > Starting Network Manager... > [FAILED] Failed to start Network Manager. > See 'systemctl status NetworkManager.service' for details. > [DEPEND] Dependency failed for Network Manager Wait Online. > [ OK ] Stopped Network Manager. > Starting Network Manager... > [FAILED] Failed to start Network Manager. > See 'systemctl status NetworkManager.service' for details. > [DEPEND] Dependency failed for Network Manager Wait Online. > [ OK ] Stopped Network Manager. > Starting Network Manager... > [FAILED] Failed to start Network Manager. > See 'systemctl status NetworkManager.service' for details. > [DEPEND] Dependency failed for Network Manager Wait Online. > [ OK ] Stopped Network Manager. > Starting Network Manager... > [FAILED] Failed to start Network Manager. > See 'systemctl status NetworkManager.service' for details. > [DEPEND] Dependency failed for Network Manager Wait Online. > [ OK ] Stopped Network Manager. > [FAILED] Failed to start Network Manager. > See 'systemctl status NetworkManager.service' for details. > [DEPEND] Dependency failed for Network Manager Wait Online. > [FAILED] Failed to start LSB: Bring up/down networking. > See 'systemctl status network.service' for details. > [ OK ] Reached target Network. > Starting Postfix Mail Transport Agent... > [FAILED] Failed to start CUPS Printing Service. > See 'systemctl status cups.service' for details. > Starting CUPS Printing Service... > Starting Logout off all iSCSI sessions on shutdown... > Starting System Logging Service... > Starting Notify NFS peers of a restart... > Starting OpenSSH server daemon... > [ OK ] Reached target Network is Online. > [ OK ] Started Logout off all iSCSI sessions on shutdown. > [ OK ] Reached target Remote File Systems (Pre). > [ OK ] Reached target Remote File Systems. > Starting Crash recovery kernel arming... > Starting Permit User Sessions... > Starting Availability of block devices... > [ OK ] Started Availability of block devices. > [ OK ] Started Permit User Sessions. > Starting GNOME Display Manager... > [ OK ] Started Job spooling tools. > Starting Job spooling tools... > [ OK ] Started Command Scheduler. > Starting Command Scheduler... > Starting Wait for Plymouth Boot Screen to Quit... > [ OK ] Started Notify NFS peers of a restart. > [FAILED] Failed to start Crash recovery kernel arming. > See 'systemctl status kdump.service' for details. > [FAILED] Failed to start System Logging Service. > See 'systemctl status rsyslog.service' for details. > [FAILED] Failed to start OpenSSH server daemon. > See 'systemctl status sshd.service' for details. > [ OK ] Stopped System Logging Service. > Starting System Logging Service... > [FAILED] Failed to start System Logging Service. > See 'systemctl status rsyslog.service' for details. > [ OK ] Stopped System Logging Service. > Starting System Logging Service... > [FAILED] Failed to start System Logging Service. > See 'systemctl status rsyslog.service' for details. > [ OK ] Stopped System Logging Service. > Starting System Logging Service... > [FAILED] Failed to start System Logging Service. > See 'systemctl status rsyslog.service' for details. > [ OK ] Stopped System Logging Service. > Starting System Logging Service... > [FAILED] Failed to start System Logging Service. > See 'systemctl status rsyslog.service' for details. > [FAILED] Failed to start Postfix Mail Transport Agent. > See 'systemctl status postfix.service' for details. > [ OK ] Stopped System Logging Service. > [FAILED] Failed to start System Logging Service. > See 'systemctl status rsyslog.service' for details. > [ OK ] Stopped OpenSSH server daemon. > Starting OpenSSH server daemon... > [FAILED] Failed to start OpenSSH server daemon. > See 'systemctl status sshd.service' for details. > [ OK ] Stopped OpenSSH server daemon. > Starting OpenSSH server daemon... > [FAILED] Failed to start OpenSSH server daemon. > See 'systemctl status sshd.service' for details. > [FAILED] Failed to start GNOME Display Manager. > See 'systemctl status gdm.service' for details. > Starting Terminate Plymouth Boot Screen... > > Scientific Linux 7.3 (Nitrogen) > Kernel 3.10.0-514.el7.x86_64 on an x86_64 > > mcs64 login: [ 152.541483] systemd-readahead[1143]: Failed to open pack > file: Read-only file system > > Scientific Linux 7.3 (Nitrogen) > Kernel 3.10.0-514.el7.x86_64 on an x86_64 > > mcs64 login: > [root@mcs64 ~]# ls -l / > total 60 > -rw-r--r-- 1 root root 0 Apr 28 12:11 1 > lrwxrwxrwx 1 root root 7 Apr 28 14:14 bin -> usr/bin > dr-xr-xr-x 4 root root 4096 Apr 28 14:16 boot > drwxr-xr-x 11 root root 2600 May 2 13:07 dev > drwxr-xr-x 147 root root 12288 May 2 11:12 etc > drwxr-xr-x 2 root root 4096 Nov 3 10:01 home > drwxr-xr-x 2 root root 4096 Apr 28 14:20 initrd > lrwxrwxrwx 1 root root 7 Apr 28 14:14 lib -> usr/lib > lrwxrwxrwx 1 root root 9 Apr 28 14:14 lib64 -> usr/lib64 > drwx------ 2 root root 4096 Apr 28 12:02 lost+found > drwxr-xr-x 2 root root 4096 Nov 3 10:01 media > drwxr-xr-x 5 root root 4096 Apr 28 14:20 mnt > drwxr-xr-x 3 root root 4096 Apr 28 14:14 opt > dr-xr-xr-x 154 root root 0 May 2 13:07 proc > drwxr-xr-x 2 root root 40 May 2 13:07 ram > dr-xr-x--- 4 root root 4096 May 1 15:20 root > drwxr-xr-x 18 root root 440 May 2 13:07 run > lrwxrwxrwx 1 root root 8 Apr 28 14:14 sbin -> usr/sbin > drwxr-xr-x 2 root root 4096 Nov 3 10:01 srv > dr-xr-xr-x 13 root root 0 May 2 13:07 sys > lrwxrwxrwx 1 root root 8 May 2 11:10 tmp -> /ram/tmp > drwxrwxrwt 11 root root 4096 May 1 16:36 tmp.default > drwxr-xr-x 13 root root 4096 Apr 28 14:14 usr > lrwxrwxrwx 1 root root 8 May 2 11:10 var -> /ram/var > drwxr-xr-x 22 root root 4096 May 2 11:10 var.default > [root@mcs64 ~]# ls -l /ram > total 0 > > > > -----Original Message----- > From: Josh England [mailto:jj...@gm...] > Sent: Tuesday, May 02, 2017 1:24 PM > To: ROSS, MARK D CTR USAF AFMC 412 RANS/ENR > Cc: one...@li... > Subject: [Non-DoD Source] Re: [oneSIS-users] new oneSIS user > > It is very difficult to tell without seeing output from your boot > sequence. Can you capture that and post it? > > -JE > > > On Tue, May 2, 2017 at 11:49 AM, ROSS, MARK D CTR USAF AFMC 412 RANS/ENR < > mar...@us...> wrote: > > > HI > New oneSIS user hoping to ask a couple of dumb questions here.. > We have been using Scientific linux 6.7 on bootable DVD's for > quite a while now and are now moving to Scientific Linux 7.3 I am hoping to > get away from the DVD's. > I was hoping to use oneSIS to get off the DVD's. Our systems are > quite simple with 4 linux computers in a rack, each computer uses an > identical software setup with DHCP providing any unique information. > > On my diskless computer I am able to PXE boot and nfs mount its > file system but I am getting a lot of errors as the systems boots, Most > likely related to a read only file system. I have tried several different > /etc/sysimage.cfg configurations to make /var/ linked to /ram but each time > I boot the /ram dir is empty. Can anyone tell me what I might be doing > wrong ? Shouldn't /ram have the run, lock directories ? > > Here is my changes to the /etc/sysimage.cfg config contents > DISTRO: redhat-el 7 > NODECLASS_REGEXP: mcs64\d+ compute > RAMSIZE: 4g -c compute > RAMDIR: /var -d -c compute > LINKDIR: /var -d -c compute > LINKDIR: /var/run -d -c compute > LINKDIR: /var/lock -d -c compute > LINKDIR: /tmp -d -c compute > LINKFILE: /var/run -d -c compute > LINKFILE: /var/log -d -c compute > LINKFILE: /var/lock -d -c compute > LINKFILE: /tmp -d -c compute > LINKBACK: /etc/fstab CLASS -c compute > > Then on the computer that has the disk image > mk-sysimage -c /etc/sysimage.conf /var/lib/oneSIS/image > > thanks for any help. > > > > ------------------------------------------------------------ > ------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > oneSIS-users mailing list > one...@li... <mailto:oneSIS-users@lists. > sourceforge.net> > https://lists.sourceforge.net/lists/listinfo/onesis-users < > https://lists.sourceforge.net/lists/listinfo/onesis-users> > > > > ------------------------------------------------------------ > ------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > oneSIS-users mailing list > one...@li... > https://lists.sourceforge.net/lists/listinfo/onesis-users > |
|
From: ROSS, M. D C. U. A. 4. RANS/E. <mar...@us...> - 2017-05-02 20:47:06
|
Thanks Josh here is the output.
[ 6.494020] i8042: No controller found
[ 6.498239] tsc: Refined TSC clocksource calibration: 2299.999 MHz
[ 6.498268] mousedev: PS/2 mouse device common for all mice
[ 6.498388] rtc_cmos 00:01: RTC can wake from S4
[ 6.498545] rtc_cmos 00:01: rtc core: registered rtc_cmos as rtc0
[ 6.498582] rtc_cmos 00:01: alarms up to one day, y3k, 242 bytes nvram, hpet irqs
[ 6.498626] Intel P-state driver initializing.
[ 6.505782] cpuidle: using governor menu
[ 6.506408] hidraw: raw HID events driver (C) Jiri Kosina
[ 6.506599] usbcore: registered new interface driver usbhid
[ 6.506599] usbhid: USB HID core driver
[ 6.506692] drop_monitor: Initializing network drop monitor service
[ 6.506925] TCP: cubic registered
[ 6.506930] Initializing XFRM netlink socket
[ 6.507167] NET: Registered protocol family 10
[ 6.507770] NET: Registered protocol family 17
[ 6.511357] microcode: CPU0 sig=0x206d7, pf=0x1, revision=0x710
[ 6.511370] microcode: CPU1 sig=0x206d7, pf=0x1, revision=0x710
[ 6.511378] microcode: CPU2 sig=0x206d7, pf=0x1, revision=0x710
[ 6.511429] microcode: CPU3 sig=0x206d7, pf=0x1, revision=0x710
[ 6.511442] microcode: CPU4 sig=0x206d7, pf=0x1, revision=0x710
[ 6.511455] microcode: CPU5 sig=0x206d7, pf=0x1, revision=0x710
[ 6.511464] microcode: CPU6 sig=0x206d7, pf=0x1, revision=0x710
[ 6.511476] microcode: CPU7 sig=0x206d7, pf=0x1, revision=0x710
[ 6.511484] microcode: CPU8 sig=0x206d7, pf=0x1, revision=0x710
[ 6.511497] microcode: CPU9 sig=0x206d7, pf=0x1, revision=0x710
[ 6.511505] microcode: CPU10 sig=0x206d7, pf=0x1, revision=0x710
[ 6.511518] microcode: CPU11 sig=0x206d7, pf=0x1, revision=0x710
[ 6.511594] microcode: Microcode Update Driver: v2.01 <ti...@ai...>, Peter Oruba
[ 6.511717] Loading compiled-in X.509 certificates
[ 6.512597] Loaded X.509 cert 'Fermi National Accelerator Laboratory: Scientific Linux 7 kpatch signing key: c8e46da25bf2b6ed33675277e795de682b4666d6'
[ 6.513448] Loaded X.509 cert 'Fermi National Accelerator Laboratory: Scientific Linux 7 driver update signing key: 98ec7b1456fb6a6b00e81292343a0ff7268df8
21'
[ 6.513979] Loaded X.509 cert 'Red Hat Enterprise Linux kernel signing key: 02c33df7a9cd1651f844f720041963da33995e99'
[ 6.513996] registered taskstats version 1
[ 6.516697] Key type trusted registered
[ 6.518792] Key type encrypted registered
[ 6.520721] IMA: No TPM chip found, activating TPM-bypass!
[ 6.531699] rtc_cmos 00:01: setting system clock to 2017-05-02 20:07:19 UTC (1493755639)
[ 6.749018] Switched to clocksource tsc
[ 6.754142] Freeing unused kernel memory: 1684k freed
oneSIS: Running /init
oneSIS: Loading pci modules
[ 6.854922] usb 2-1: new high-speed USB device number 2 using ehci-pci
[ 6.862238] usb 1-1: new high-speed USB device number 2 using ehci-pci
[ 6.983295] usb 2-1: New USB device found, idVendor=8087, idProduct=0024
[ 6.990790] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 6.998756] usb 1-1: New USB device found, idVendor=8087, idProduct=0024
[ 7.006244] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 7.015082] hub 2-1:1.0: USB hub found
[ 7.019280] hub 1-1:1.0: USB hub found
[ 7.023717] hub 1-1:1.0: 6 ports detected
[ 7.028201] hub 2-1:1.0: 8 ports detected
[ 7.305885] usb 1-1.6: new high-speed USB device number 3 using ehci-pci
[ 7.313378] usb 2-1.2: new low-speed USB device number 3 using ehci-pci
[ 7.407193] usb 1-1.6: New USB device found, idVendor=0624, idProduct=0248
[ 7.414894] usb 1-1.6: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 7.423083] usb 1-1.6: Product: Gadget USB HUB
[ 7.428052] usb 1-1.6: Manufacturer: no manufacturer
[ 7.433599] usb 1-1.6: SerialNumber: 0123456789
[ 7.439419] hub 1-1.6:1.0: USB hub found
[ 7.443942] hub 1-1.6:1.0: 6 ports detected
[ 7.449521] usb 2-1.2: New USB device found, idVendor=0d3d, idProduct=0040
[ 7.457211] usb 2-1.2: New USB device strings: Mfr=0, Product=2, SerialNumber=0
[ 7.465374] usb 2-1.2: Product: USB CAT5
[ 7.474793] input: USB CAT5 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2/2-1.2:1.0/input/input1
[ 7.536746] hid-generic 0003:0D3D:0040.0001: input,hidraw0: USB HID v1.00 Keyboard [USB CAT5] on usb-0000:00:1d.0-1.2/input0
[ 7.563652] input: USB CAT5 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2/2-1.2:1.1/input/input2
[ 7.574900] hid-generic 0003:0D3D:0040.0002: input,hidraw1: USB HID v1.00 Mouse [USB CAT5] on usb-0000:00:1d.0-1.2/input1
[ 7.758907] usb 1-1.6.1: new high-speed USB device number 4 using ehci-pci
[ 7.852331] usb 1-1.6.1: New USB device found, idVendor=0624, idProduct=0249
[ 7.860210] usb 1-1.6.1: New USB device strings: Mfr=4, Product=5, SerialNumber=6
[ 7.868575] usb 1-1.6.1: Product: Keyboard/Mouse Function
[ 7.874605] usb 1-1.6.1: Manufacturer: Avocent
[ 7.879569] usb 1-1.6.1: SerialNumber: 20120917
[ 7.891350] input: Avocent Keyboard/Mouse Function as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6/1-1.6.1/1-1.6.1:1.0/input/input3
[ 7.956769] hid-generic 0003:0624:0249.0003: input,hidraw2: USB HID v1.00 Keyboard [Avocent Keyboard/Mouse Function] on usb-0000:00:1a.0-1.6.1/input0
[ 7.973514] input: Avocent Keyboard/Mouse Function as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6/1-1.6.1/1-1.6.1:1.1/input/input4
[ 7.988101] hid-generic 0003:0624:0249.0004: input,hidraw3: USB HID v1.00 Mouse [Avocent Keyboard/Mouse Function] on usb-0000:00:1a.0-1.6.1/input1
[ 8.004336] input: Avocent Keyboard/Mouse Function as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6/1-1.6.1/1-1.6.1:1.2/input/input5
[ 8.018503] hid-generic 0003:0624:0249.0005: input,hidraw4: USB HID v1.00 Mouse [Avocent Keyboard/Mouse Function] on usb-0000:00:1a.0-1.6.1/input2
[ 23.868972] pps_core: LinuxPPS API ver. 1 registered
[ 23.874526] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <gio...@li...>
[ 23.889402] PTP clock support registered
[ 23.900677] tg3.c:v3.137 (May 11, 2014)
[ 23.917098] tg3 0000:01:00.0 eth0: Tigon3 [partno(BCM95720) rev 5720000] (PCI Express) MAC address b8:ca:3a:f8:67:1e
[ 23.928866] tg3 0000:01:00.0 eth0: attached PHY is 5720C (10/100/1000Base-T Ethernet) (WireSpeed[1], EEE[1])
[ 23.939842] tg3 0000:01:00.0 eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[1] TSOcap[1]
[ 23.948586] tg3 0000:01:00.0 eth0: dma_rwctrl[00000001] dma_mask[64-bit]
[ 23.977974] tg3 0000:01:00.1 eth1: Tigon3 [partno(BCM95720) rev 5720000] (PCI Express) MAC address b8:ca:3a:f8:67:1f
[ 23.989737] tg3 0000:01:00.1 eth1: attached PHY is 5720C (10/100/1000Base-T Ethernet) (WireSpeed[1], EEE[1])
[ 24.000715] tg3 0000:01:00.1 eth1: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[1] TSOcap[1]
[ 24.009456] tg3 0000:01:00.1 eth1: dma_rwctrl[00000001] dma_mask[64-bit]
[ 24.038852] tg3 0000:02:00.0 eth2: Tigon3 [partno(BCM95720) rev 5720000] (PCI Express) MAC address b8:ca:3a:f8:67:20
[ 24.050611] tg3 0000:02:00.0 eth2: attached PHY is 5720C (10/100/1000Base-T Ethernet) (WireSpeed[1], EEE[1])
[ 24.061587] tg3 0000:02:00.0 eth2: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[1] TSOcap[1]
[ 24.070328] tg3 0000:02:00.0 eth2: dma_rwctrl[00000001] dma_mask[64-bit]
[ 24.099836] tg3 0000:02:00.1 eth3: Tigon3 [partno(BCM95720) rev 5720000] (PCI Express) MAC address b8:ca:3a:f8:67:21
[ 24.111594] tg3 0000:02:00.1 eth3: attached PHY is 5720C (10/100/1000Base-T Ethernet) (WireSpeed[1], EEE[1])
[ 24.122561] tg3 0000:02:00.1 eth3: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[1] TSOcap[1]
[ 24.131303] tg3 0000:02:00.1 eth3: dma_rwctrl[00000001] dma_mask[64-bit]
[ 24.151679] RPC: Registered named UNIX socket transport module.
[ 24.158299] RPC: Registered udp transport module.
[ 24.163552] RPC: Registered tcp transport module.
[ 24.168800] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 24.184744] FS-Cache: Loaded
[ 24.198031] FS-Cache: Netfs 'nfs' registered for caching
Attempting DHCP on eth0 ...
udhcpc (v1.18.5) started
[ 24.344714] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Sending discover...
Sending discover...
[ 27.832421] tg3 0000:01:00.0 eth0: Link is up at 1000 Mbps, full duplex
[ 27.839807] tg3 0000:01:00.0 eth0: Flow control is off for TX and off for RX
[ 27.847673] tg3 0000:01:00.0 eth0: EEE is disabled
[ 27.853034] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Sending discover...
Sending select for 192.168.106.103...
Lease of 192.168.106.103 obtained, lease time 604800
oneSIS: Setting IP address on eth0: 192.168.106.103
oneSIS: Setting default route: 192.168.106.1
oneSIS: Setting hostname: mcs64
oneSIS: Checking network connectivity to 192.168.106.1
oneSIS: Mounting NFS root filesystem: /var/lib/oneSIS/image from xxx.198.80.51
oneSIS: Leaving initramfs
[ 31.682161] SELinux: Disabled at runtime.
[ 31.721182] type=1404 audit(1493755664.696:2): selinux=0 auid=4294967295 ses=4294967295
[ 31.747925] ERST: NVRAM ERST Log Address Range is not implemented yet
[ 31.761540] systemd[1]: systemd 219 running in system mode. (+PAM +AUDIT +SELINUX +IMA -APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +AC
L +XZ -LZ4 -SECCOMP +BLKID +ELFUTILS +KMOD +IDN)
[ 31.782092] systemd[1]: Detected architecture x86-64.
Welcome to Scientific Linux 7.3 (Nitrogen)!
[ OK ] Reached target User and Group Name Lookups.
[ 32.223306] systemd[1]: Reached target User and Group Name Lookups.
[ 32.230355] systemd[1]: Starting User and Group Name Lookups.
[ OK ] Reached target Swap.
[ 32.241280] systemd[1]: Reached target Swap.
[ 32.246079] systemd[1]: Starting Swap.
[ OK ] Set up automount Arbitrary Executab...ats File System Automount Point.
[ 32.260294] systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point.
[ 32.270824] systemd[1]: Starting Arbitrary Executable File Formats File System Automount Point.
[ 32.280664] systemd[1]: Started Forward Requests to Wall Directory Watch.
[ 32.289127] systemd[1]: Starting Forward Requests to Wall Directory Watch.
[ OK ] Created slice Root Slice.
[ 32.304300] systemd[1]: Created slice Root Slice.
[ 32.309603] systemd[1]: Starting Root Slice.
[ OK ] Created slice User and Session Slice.
[ 32.321317] systemd[1]: Created slice User and Session Slice.
[ 32.327761] systemd[1]: Starting User and Session Slice.
[ OK ] Listening on Delayed Shutdown Socket.
[ 32.340283] systemd[1]: Listening on Delayed Shutdown Socket.
[ 32.346716] systemd[1]: Starting Delayed Shutdown Socket.
[ OK ] Listening on udev Control Socket.
[ 32.359296] systemd[1]: Listening on udev Control Socket.
[ 32.365398] systemd[1]: Starting udev Control Socket.
[ OK ] Listening on udev Kernel Socket.
[ 32.377321] systemd[1]: Listening on udev Kernel Socket.
[ 32.383276] systemd[1]: Starting udev Kernel Socket.
[ OK ] Listening on LVM2 metadata daemon socket.
[ 32.396289] systemd[1]: Listening on LVM2 metadata daemon socket.
[ 32.403128] systemd[1]: Starting LVM2 metadata daemon socket.
[ OK ] Listening on Device-mapper event daemon FIFOs.
[ 32.417292] systemd[1]: Listening on Device-mapper event daemon FIFOs.
[ 32.424631] systemd[1]: Starting Device-mapper event daemon FIFOs.
[ OK ] Listening on /dev/initctl Compatibility Named Pipe.
[ 32.440291] systemd[1]: Listening on /dev/initctl Compatibility Named Pipe.
[ 32.448102] systemd[1]: Starting /dev/initctl Compatibility Named Pipe.
[ OK ] Listening on Journal Socket.
[ 32.461293] systemd[1]: Listening on Journal Socket.
[ 32.466880] systemd[1]: Starting Journal Socket.
[ OK ] Created slice System Slice.
[ 32.477299] systemd[1]: Created slice System Slice.
[ 32.482782] systemd[1]: Starting System Slice.
[ 32.488529] systemd[1]: Starting Journal Service...
Starting Journal Service...
[ 32.500040] systemd[1]: Starting Collect Read-Ahead Data...
Starting Collect Read-Ahead Data...
[ OK ] Created slice system-getty.slice.
[ 32.519227] systemd[1]: Created slice system-getty.slice.
[ 32.525318] systemd[1]: Starting system-getty.slice.
[ 32.531655] systemd[1]: Starting Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling...
Starting Monitoring of LVM2 mirrors... dmeventd or progress polling...
[ OK ] Created slice system-serial\x2dgetty.slice.
[ 32.559257] systemd[1]: Created slice system-serial\x2dgetty.slice.
[ 32.566295] systemd[1]: Starting system-serial\x2dgetty.slice.
[ OK ] Created slice system-selinux\x2dpol...grate\x2dlocal\x2dchanges.slice.
[ 32.582243] systemd[1]: Created slice system-selinux\x2dpolicy\x2dmigrate\x2dlocal\x2dchanges.slice.
[ 32.592753] systemd[1]: Starting system-selinux\x2dpolicy\x2dmigrate\x2dlocal\x2dchanges.slice.
[ 32.603279] systemd[1]: Starting Replay Read-Ahead Data...
Starting Replay Read-Ahead Data...
[ 32.617063] systemd[1]: Mounting POSIX Message Queue File System...
Mounting POSIX Message Queue File System...
[ 32.631054] systemd[1]: Mounting Debug File System...
Mounting Debug File System...
[ 32.754464] systemd[1]: MESSAGE=Failed to check directory /var/lib/nfs/rpc_pipefs: No such file or directory
[ 32.766584] systemd[1]: Mounting RPC Pipe File System...
Mounting RPC Pipe File System...
[ 32.778782] systemd[1]: Mounting Huge Pages File System...
Mounting Huge Pages File System...
[ OK ] Reached target Slices.
[ 32.796241] systemd[1]: Reached target Slices.
[ 32.801317] systemd[1]: Starting Slices.
[ 32.806507] systemd[1]: Mounting NFSD configuration filesystem...
Mounting NFSD configuration filesystem...
[ OK ] Listening on LVM2 poll daemon socket.
[ 32.826262] systemd[1]: Listening on LVM2 poll daemon socket.
[ 32.832708] systemd[1]: Starting LVM2 poll daemon socket.
[ OK ] Mounted POSIX Message Queue File System.
[ 32.846259] systemd[1]: Mounted POSIX Message Queue File System.
[ OK ] Mounted Huge Pages File System.
[ 32.859281] systemd[1]: Mounted Huge Pages File System.
[ OK ] Mounted Debug File System.
[ 32.870283] systemd[1]: Mounted Debug File System.
[ OK ] Started Collect Read-Ahead Data.
[ 32.882285] systemd[1]: Started Collect Read-Ahead Data.
[ OK ] Started Journal Service.
[ 32.893250] systemd[1]: Started Journal Service.
[ OK ] Started Replay Read-Ahead Data.
[FAILED] Failed to mount RPC Pipe File System.
See 'systemctl status var-lib-nfs-rpc_pipefs.mount' for details.
[DEPEND] Dependency failed for RPC security service for NFS server.
[DEPEND] Dependency failed for RPC security service for NFS client and server.
[FAILED] Failed to mount NFSD configuration filesystem.
See 'systemctl status proc-fs-nfsd.mount' for details.
[DEPEND] Dependency failed for GSSAPI Proxy Daemon.
[ OK ] Started LVM2 metadata daemon.
Starting LVM2 metadata daemon...
[ OK ] Reached target NFS client services.
Mounting Configuration File System...
Starting Setup Virtual Console...
Starting oneSIS System Init...
Starting Flush Journal to Persistent Storage...
Starting Apply Kernel Variables...
Starting Load/Save Random Seed...
Starting udev Coldplug all Devices...
Starting Create Static Device Nodes in /dev...
[ OK ] Mounted Configuration File System.
[ OK ] Started Monitoring of LVM2 mirrors,...ng dmeventd or progress polling.
[ OK ] Started Apply Kernel Variables.
[FAILED] Failed to start Load/Save Random Seed.
See 'systemctl status systemd-random-seed.service' for details.
[ OK ] Started Create Static Device Nodes in /dev.
Starting udev Kernel Device Manager...
[ OK ] Reached target Local File Systems (Pre).
[ 33.133713] systemd-journald[1142]: Received request to flush runtime journal from PID 1
[ OK ] Started Flush Journal to Persistent Storage.
[ OK ] Started Setup Virtual Console.
[ OK ] Started udev Coldplug all Devices.
Starting udev Wait for Complete Device Initialization...
[ OK ] Started oneSIS System Init.
Starting Configure read-only root support...
[ OK ] Started Configure read-only root support.
[ OK ] Started udev Kernel Device Manager.
Starting Show Plymouth Boot Screen...
[ OK ] Started Show Plymouth Boot Screen.
G[ OK ] Found device /dev/ttyS1.
[ OK ] Started udev Wait for Complete Device Initialization.
Starting Activation of DM RAID sets...
[ OK ] Started Activation of DM RAID sets.
[ OK ] Reached target Local File Systems.
Starting Update is Completed...
Starting Tell Plymouth To Write Out Runtime Data...
Starting Preprocess NFS configuration...
Starting Create Volatile Files and Directories...
[ OK ] Reached target Encrypted Volumes.
[FAILED] Failed to start Update is Completed.
See 'systemctl status systemd-update-done.service' for details.
[ OK ] Started Tell Plymouth To Write Out Runtime Data.
[ OK ] Started Preprocess NFS configuration.
[FAILED] Failed to start Create Volatile Files and Directories.
See 'systemctl status systemd-tmpfiles-setup.service' for details.
Starting Security Auditing Service...
[FAILED] Failed to start Security Auditing Service.
See 'systemctl status auditd.service' for details.
Starting Update UTMP about System Boot/Shutdown...
[ OK ] Started Update UTMP about System Boot/Shutdown.
[ OK ] Reached target System Initialization.
[ OK ] Listening on Open-iSCSI iscsiuio Socket.
[FAILED] Failed to listen on D-Bus System Message Bus Socket.
See 'systemctl status dbus.socket' for details.
[DEPEND] Dependency failed for D-Bus System Message Bus.
[DEPEND] Dependency failed for Dynamic System Tuning Daemon.
[ OK ] Reached target Timers.
[FAILED] Failed to listen on Avahi mDNS/DNS-SD Stack Activation Socket.
See 'systemctl status avahi-daemon.socket' for details.
[DEPEND] Dependency failed for Avahi mDNS/DNS-SD Stack.
[FAILED] Failed to listen on Virtual machine lock manager socket.
See 'systemctl status virtlockd.socket' for details.
[FAILED] Failed to listen on CUPS Printing Service Sockets.
See 'systemctl status cups.socket' for details.
[ OK ] Reached target Paths.
[ OK ] Listening on Open-iSCSI iscsid Socket.
[FAILED] Failed to listen on Virtual machine log manager socket.
See 'systemctl status virtlogd.socket' for details.
[DEPEND] Dependency failed for Virtualization daemon.
[FAILED] Failed to listen on RPCbind Server Activation Socket.
See 'systemctl status rpcbind.socket' for details.
[ OK ] Reached target Sockets.
[ OK ] Reached target Basic System.
Starting Resets System Activity Logs...
[ OK ] Started irqbalance daemon.
Starting irqbalance daemon...
Starting Accounts Service...
[ OK ] Started Self Monitoring and Reporting Technology (SMART) Daemon.
Starting Self Monitoring and Reporting Technology (SMART) Daemon...
Starting Login Service...
Starting Console Mouse manager...
Starting Load CPU microcode update...
[ OK ] Started Manage Sound Card State (restore and store).
Starting Manage Sound Card State (restore and store)...
Starting Run automatic yum updates as a cron job...
[ OK ] Started ABRT Automated Bug Reporting Tool.
Starting ABRT Automated Bug Reporting Tool...
[ OK ] Started ABRT kernel log watcher.
Starting ABRT kernel log watcher...
Starting Authorization Manager...
[ OK ] Started Hardware RNG Entropy Gatherer Daemon.
Starting Hardware RNG Entropy Gatherer Daemon...
Starting Install ABRT coredump hook...
Starting Dump dmesg to /var/log/dmesg...
Starting Kernel Samepage Merging...
Starting Network Manager...
[FAILED] Failed to start RealtimeKit Scheduling Policy Service.
See 'systemctl status rtkit-daemon.service' for details.
Starting RealtimeKit Scheduling Policy Service...
[ OK ] Started libstoragemgmt plug-in server daemon.
Starting libstoragemgmt plug-in server daemon...
[FAILED] Failed to start Console Mouse manager.
See 'systemctl status gpm.service' for details.
[FAILED] Failed to start Run automatic yum updates as a cron job.
See 'systemctl status yum-cron.service' for details.
[ OK ] Started Kernel Samepage Merging.
Starting Kernel Samepage Merging (KSM) Tuning Daemon...
[FAILED] Failed to start Login Service.
See 'systemctl status symd-logind.service' for details.
[ OK ] Stopped Login Service.
[FAILED] Failed to listen on D-Bus System Message Bus Socket.
See 'systemctl status dbus.socket' for details.
Starting Login Service...
[FAILED] Failed to start Dump dmesg to /var/log/dmesg.
See 'systemctl status rhel-dmesg.service' for details.
[ OK ] Started Load CPU microcode update.
[FAILED] Failed to start Login Service.
See 'systemctl status systemd-logind.service' for details.
[FAILED] Failed to start Resets System Activity Logs.
See 'systemctl status sysstat.service' for details.
[ OK ] Stopped Login Service.
[FAILED] Failed to listen on D-Bus System Message Bus Socket.
See 'systemctl status dbus.socket' for details.
Starting Login Service...
[ OK ] Started Kernel Samepage Merging (KSM) Tuning Daemon.
[FAILED] Failed to start Login Service.
See 'systemctl status systemd-logind.service' for details.
[ OK ] Started Accounts Service.
[ OK ] Stopped Login Service.
[FAILED] Failed to listen on D-Bus System Message Bus Socket.
See 'systemctl status dbus.socket' for details.
Starting Login Service...
[FAILED] Failed to start Login Service.
See 'systemctl status systemd-logind.service' for details.
[ OK ] Stopped Login Service.
[FAILED] Failed to listen on D-Bus System Message Bus Socket.
See 'systemctl status dbus.socket' for details.
Starting Login Service...
[FAILED] Failed to start Login Service.
See 'systemctl status systemd-logind.service' for details.
[ OK ] Stopped Login Service.
[FAILED] Failed to listen on D-Bus System Message Bus Socket.
See 'systemctl status dbus.socket' for details.
[FAILED] Failed to start Login Service.
See 'systemctl status systemd-logind.service' for details.
[FAILED] Failed to start Network Manager.
See 'systemctl status NetworkManager.service' for details.
[DEPEND] Dependency failed for Network Manager Wait Online.
Starting LSB: Bring up/down networking...
[ OK ] Started Install ABRT coredump hook.
[ OK ] Started Authorization Manager.
[ OK ] Stopped Network Manager.
Starting Network Manager...
[FAILED] Failed to start Network Manager.
See 'systemctl status NetworkManager.service' for details.
[DEPEND] Dependency failed for Network Manager Wait Online.
[ OK ] Stopped Network Manager.
Starting Network Manager...
[FAILED] Failed to start Network Manager.
See 'systemctl status NetworkManager.service' for details.
[DEPEND] Dependency failed for Network Manager Wait Online.
[ OK ] Stopped Network Manager.
Starting Network Manager...
[FAILED] Failed to start Network Manager.
See 'systemctl status NetworkManager.service' for details.
[DEPEND] Dependency failed for Network Manager Wait Online.
[ OK ] Stopped Network Manager.
Starting Network Manager...
[FAILED] Failed to start Network Manager.
See 'systemctl status NetworkManager.service' for details.
[DEPEND] Dependency failed for Network Manager Wait Online.
[ OK ] Stopped Network Manager.
[FAILED] Failed to start Network Manager.
See 'systemctl status NetworkManager.service' for details.
[DEPEND] Dependency failed for Network Manager Wait Online.
[FAILED] Failed to start LSB: Bring up/down networking.
See 'systemctl status network.service' for details.
[ OK ] Reached target Network.
Starting Postfix Mail Transport Agent...
[FAILED] Failed to start CUPS Printing Service.
See 'systemctl status cups.service' for details.
Starting CUPS Printing Service...
Starting Logout off all iSCSI sessions on shutdown...
Starting System Logging Service...
Starting Notify NFS peers of a restart...
Starting OpenSSH server daemon...
[ OK ] Reached target Network is Online.
[ OK ] Started Logout off all iSCSI sessions on shutdown.
[ OK ] Reached target Remote File Systems (Pre).
[ OK ] Reached target Remote File Systems.
Starting Crash recovery kernel arming...
Starting Permit User Sessions...
Starting Availability of block devices...
[ OK ] Started Availability of block devices.
[ OK ] Started Permit User Sessions.
Starting GNOME Display Manager...
[ OK ] Started Job spooling tools.
Starting Job spooling tools...
[ OK ] Started Command Scheduler.
Starting Command Scheduler...
Starting Wait for Plymouth Boot Screen to Quit...
[ OK ] Started Notify NFS peers of a restart.
[FAILED] Failed to start Crash recovery kernel arming.
See 'systemctl status kdump.service' for details.
[FAILED] Failed to start System Logging Service.
See 'systemctl status rsyslog.service' for details.
[FAILED] Failed to start OpenSSH server daemon.
See 'systemctl status sshd.service' for details.
[ OK ] Stopped System Logging Service.
Starting System Logging Service...
[FAILED] Failed to start System Logging Service.
See 'systemctl status rsyslog.service' for details.
[ OK ] Stopped System Logging Service.
Starting System Logging Service...
[FAILED] Failed to start System Logging Service.
See 'systemctl status rsyslog.service' for details.
[ OK ] Stopped System Logging Service.
Starting System Logging Service...
[FAILED] Failed to start System Logging Service.
See 'systemctl status rsyslog.service' for details.
[ OK ] Stopped System Logging Service.
Starting System Logging Service...
[FAILED] Failed to start System Logging Service.
See 'systemctl status rsyslog.service' for details.
[FAILED] Failed to start Postfix Mail Transport Agent.
See 'systemctl status postfix.service' for details.
[ OK ] Stopped System Logging Service.
[FAILED] Failed to start System Logging Service.
See 'systemctl status rsyslog.service' for details.
[ OK ] Stopped OpenSSH server daemon.
Starting OpenSSH server daemon...
[FAILED] Failed to start OpenSSH server daemon.
See 'systemctl status sshd.service' for details.
[ OK ] Stopped OpenSSH server daemon.
Starting OpenSSH server daemon...
[FAILED] Failed to start OpenSSH server daemon.
See 'systemctl status sshd.service' for details.
[FAILED] Failed to start GNOME Display Manager.
See 'systemctl status gdm.service' for details.
Starting Terminate Plymouth Boot Screen...
Scientific Linux 7.3 (Nitrogen)
Kernel 3.10.0-514.el7.x86_64 on an x86_64
mcs64 login: [ 152.541483] systemd-readahead[1143]: Failed to open pack file: Read-only file system
Scientific Linux 7.3 (Nitrogen)
Kernel 3.10.0-514.el7.x86_64 on an x86_64
mcs64 login:
[root@mcs64 ~]# ls -l /
total 60
-rw-r--r-- 1 root root 0 Apr 28 12:11 1
lrwxrwxrwx 1 root root 7 Apr 28 14:14 bin -> usr/bin
dr-xr-xr-x 4 root root 4096 Apr 28 14:16 boot
drwxr-xr-x 11 root root 2600 May 2 13:07 dev
drwxr-xr-x 147 root root 12288 May 2 11:12 etc
drwxr-xr-x 2 root root 4096 Nov 3 10:01 home
drwxr-xr-x 2 root root 4096 Apr 28 14:20 initrd
lrwxrwxrwx 1 root root 7 Apr 28 14:14 lib -> usr/lib
lrwxrwxrwx 1 root root 9 Apr 28 14:14 lib64 -> usr/lib64
drwx------ 2 root root 4096 Apr 28 12:02 lost+found
drwxr-xr-x 2 root root 4096 Nov 3 10:01 media
drwxr-xr-x 5 root root 4096 Apr 28 14:20 mnt
drwxr-xr-x 3 root root 4096 Apr 28 14:14 opt
dr-xr-xr-x 154 root root 0 May 2 13:07 proc
drwxr-xr-x 2 root root 40 May 2 13:07 ram
dr-xr-x--- 4 root root 4096 May 1 15:20 root
drwxr-xr-x 18 root root 440 May 2 13:07 run
lrwxrwxrwx 1 root root 8 Apr 28 14:14 sbin -> usr/sbin
drwxr-xr-x 2 root root 4096 Nov 3 10:01 srv
dr-xr-xr-x 13 root root 0 May 2 13:07 sys
lrwxrwxrwx 1 root root 8 May 2 11:10 tmp -> /ram/tmp
drwxrwxrwt 11 root root 4096 May 1 16:36 tmp.default
drwxr-xr-x 13 root root 4096 Apr 28 14:14 usr
lrwxrwxrwx 1 root root 8 May 2 11:10 var -> /ram/var
drwxr-xr-x 22 root root 4096 May 2 11:10 var.default
[root@mcs64 ~]# ls -l /ram
total 0
-----Original Message-----
From: Josh England [mailto:jj...@gm...]
Sent: Tuesday, May 02, 2017 1:24 PM
To: ROSS, MARK D CTR USAF AFMC 412 RANS/ENR
Cc: one...@li...
Subject: [Non-DoD Source] Re: [oneSIS-users] new oneSIS user
It is very difficult to tell without seeing output from your boot sequence. Can you capture that and post it?
-JE
On Tue, May 2, 2017 at 11:49 AM, ROSS, MARK D CTR USAF AFMC 412 RANS/ENR <mar...@us...> wrote:
HI
New oneSIS user hoping to ask a couple of dumb questions here..
We have been using Scientific linux 6.7 on bootable DVD's for quite a while now and are now moving to Scientific Linux 7.3 I am hoping to get away from the DVD's.
I was hoping to use oneSIS to get off the DVD's. Our systems are quite simple with 4 linux computers in a rack, each computer uses an identical software setup with DHCP providing any unique information.
On my diskless computer I am able to PXE boot and nfs mount its file system but I am getting a lot of errors as the systems boots, Most likely related to a read only file system. I have tried several different /etc/sysimage.cfg configurations to make /var/ linked to /ram but each time I boot the /ram dir is empty. Can anyone tell me what I might be doing wrong ? Shouldn't /ram have the run, lock directories ?
Here is my changes to the /etc/sysimage.cfg config contents
DISTRO: redhat-el 7
NODECLASS_REGEXP: mcs64\d+ compute
RAMSIZE: 4g -c compute
RAMDIR: /var -d -c compute
LINKDIR: /var -d -c compute
LINKDIR: /var/run -d -c compute
LINKDIR: /var/lock -d -c compute
LINKDIR: /tmp -d -c compute
LINKFILE: /var/run -d -c compute
LINKFILE: /var/log -d -c compute
LINKFILE: /var/lock -d -c compute
LINKFILE: /tmp -d -c compute
LINKBACK: /etc/fstab CLASS -c compute
Then on the computer that has the disk image
mk-sysimage -c /etc/sysimage.conf /var/lib/oneSIS/image
thanks for any help.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
oneSIS-users mailing list
one...@li... <mailto:one...@li...>
https://lists.sourceforge.net/lists/listinfo/onesis-users <https://lists.sourceforge.net/lists/listinfo/onesis-users>
|
|
From: Josh E. <jj...@gm...> - 2017-05-02 20:24:18
|
It is very difficult to tell without seeing output from your boot sequence. Can you capture that and post it? -JE On Tue, May 2, 2017 at 11:49 AM, ROSS, MARK D CTR USAF AFMC 412 RANS/ENR < mar...@us...> wrote: > HI > New oneSIS user hoping to ask a couple of dumb questions here.. > We have been using Scientific linux 6.7 on bootable DVD's for quite a > while now and are now moving to Scientific Linux 7.3 I am hoping to get > away from the DVD's. > I was hoping to use oneSIS to get off the DVD's. Our systems are quite > simple with 4 linux computers in a rack, each computer uses an identical > software setup with DHCP providing any unique information. > > On my diskless computer I am able to PXE boot and nfs mount its file > system but I am getting a lot of errors as the systems boots, Most likely > related to a read only file system. I have tried several different > /etc/sysimage.cfg configurations to make /var/ linked to /ram but each time > I boot the /ram dir is empty. Can anyone tell me what I might be doing > wrong ? Shouldn't /ram have the run, lock directories ? > > Here is my changes to the /etc/sysimage.cfg config contents > DISTRO: redhat-el 7 > NODECLASS_REGEXP: mcs64\d+ compute > RAMSIZE: 4g -c compute > RAMDIR: /var -d -c compute > LINKDIR: /var -d -c compute > LINKDIR: /var/run -d -c compute > LINKDIR: /var/lock -d -c compute > LINKDIR: /tmp -d -c compute > LINKFILE: /var/run -d -c compute > LINKFILE: /var/log -d -c compute > LINKFILE: /var/lock -d -c compute > LINKFILE: /tmp -d -c compute > LINKBACK: /etc/fstab CLASS -c compute > > Then on the computer that has the disk image > mk-sysimage -c /etc/sysimage.conf /var/lib/oneSIS/image > > thanks for any help. > > > > ------------------------------------------------------------ > ------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > oneSIS-users mailing list > one...@li... > https://lists.sourceforge.net/lists/listinfo/onesis-users > |
28 messages has been excluded from this view by a project administrator.