Sponsored Content
Operating Systems Linux Slackware Help with kernel panic - not syncing slackware 13.0 Post 302823185 by ElvijsL on Wednesday 19th of June 2013 03:02:14 AM
Old 06-19-2013
Linux Help with kernel panic - not syncing slackware 13.0

Hi,

first of all I'm 110% newbie, sorry for any mistake if I made it.

In my country there are no normal or active linux forums, so i found this forum.

Ok, that's for begining, but not for may real problem.
---------------------------------------------------
I am system administrator usually administer windows based servers or some times play with ubuntu, but now i got from another administrator (he leaved country) server which is running slackware 13.0, i just needed to get data out of this server and this is what i did:

1. found config files for IP adress and changed it to my local IP adress
2. restarted server

and then got this error:

Image

so... I'm stuck for about allready 3 days Smilie

What i know about server, that it is running raid 1 and raid 5 with mdadm (i don't have any previous expierence with mdadm) and there are 4 drives with 2TB capacity

what i have done this far:

1. burned slackware 13.1. (or do i need 13?)
2. booted default kernel into installation
3. mounted md0 to /mnt
4. tried sfck, one time with success, the i got md0 running, but gave me another kernel sync error

So, i swear i would buy box of bear from my salary who will help me to solve this.

Just give me please some kind of plan what to do, or i can post any questions, if You need any information from config files.

by the way, it's boot with lilo, when i press TAB i can see one list: Linux

Thanks for any help. Smilie
Help with kernel panic - not syncing slackware 13.0-20130614_175253jpg

Last edited by ElvijsL; 06-19-2013 at 04:04 AM.. Reason: picture not working
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

kernel panic

hello :-) I have one problem with my LiLO... I installed PLD Linux on my computer but when it boots, the last thing I can see is: request_module Root fs not mounted VFS: Cannot open root device 03:01 Kernel panic: VFS: unable to mount root fs on 03:01 and the system stops :-( what... (1 Reply)
Discussion started by: pgas
1 Replies

2. Linux

kernel panic

I have compiled kernel version 2.6.12 in my linux box mandrake 10.1. I have followed www.digitalhermit.com/linux/Kernel-Build-HOWTO.html instructions. I have copied .config file from /usr/src/linux and lightly modified it (only the processor type) by xconfig. I have compiled the source and modules.... (3 Replies)
Discussion started by: Davide71
3 Replies

3. UNIX for Dummies Questions & Answers

Kernel panic - not syncing == While RHEL AS install

I am trying to Install RHEL AS 4 on x86 pc, through VNC and got the below error, Am not pretty sure as how to resolve this. Can some one guide me through the process, or what might be missing.... Have Installed RHEL, many a times but cudnt find this out... Wud appreciate an early reply ......... (0 Replies)
Discussion started by: Crazy_murli
0 Replies

4. Linux

Kernel panic - not syncing: cannot execute a PAE-enabled kernel on PAE-less CPU

ok so I just installed fedora core 6 on my dell inspiron 700m and I go to boot into linux and I get this error. Has anyone seen this before? I also had XP Pro and Vista installed on this pc prior to putting fedora core 6 on the machine. I'm trying to setup a triple boot system. Please Help... (2 Replies)
Discussion started by: dave043
2 Replies

5. UNIX Desktop Questions & Answers

kernel panic-not syncing:fatal exception while booting

Hi ALL, I am getting error.. kernal panic-not syncing:fatal exception while booting. Please help me.. Thanks Jack (7 Replies)
Discussion started by: jack00423
7 Replies

6. UNIX for Advanced & Expert Users

what does the kernel panic mean?

Hi, all: How should I obtain the reason of kernel panic? How should I debug the program which result in a kernel panic? What can I get from the panic information? li, kunlun (3 Replies)
Discussion started by: liklstar
3 Replies

7. Ubuntu

kenel panic not syncing

I installed a new kernel 3.0.22 on ubuntu server 11.04 32 bit. when I select the kenel from boot loader it stops when Code: loading initial ramdisk... I added all_generic_ide at the end of linux line and also added dev/sda1 to linux line: root=UUID=dev/sda1 now it says that ... (12 Replies)
Discussion started by: dr_mabuse
12 Replies

8. Red Hat

Error: kernal panic not syncing

HI All, server stopped here, we are suspecting server crash, need install new OS. Any suggestions on this. kindly help to us. Thanks Rajesh (0 Replies)
Discussion started by: Rajesh_Apple
0 Replies

9. SCO

Kernel Panic

Hello when i booting my SCO Server I become this Message PLS can anyone help me? Cheers Christoph (1 Reply)
Discussion started by: cga
1 Replies

10. Red Hat

Kernel panic-not syncing

dear experts linux i am using RHEL 5.5 run on a physical server. i am front of a big trouble, the Rhel can't run correctly , it show me this error message in black screen: reading all physical volumes. this my take a while .. found volume group "VolGroup00" using metadata type lvm2 9... (1 Reply)
Discussion started by: wassimpb
1 Replies
mdadm_selinux(8)					       SELinux Policy mdadm						  mdadm_selinux(8)

NAME
mdadm_selinux - Security Enhanced Linux Policy for the mdadm processes DESCRIPTION
Security-Enhanced Linux secures the mdadm processes via flexible mandatory access control. The mdadm processes execute with the mdadm_t SELinux type. You can check if you have these processes running by executing the ps command with the -Z qualifier. For example: ps -eZ | grep mdadm_t ENTRYPOINTS
The mdadm_t SELinux type can be entered via the mdadm_exec_t file type. The default entrypoint paths for the mdadm_t domain are the following: /sbin/mdadm, /sbin/mdmon, /sbin/mdmpd, /sbin/iprdump, /sbin/iprinit, /sbin/iprupdate, /usr/sbin/mdadm, /usr/sbin/mdmpd, /usr/sbin/mdmon, /sbin/raid-check, /usr/sbin/iprdump, /usr/sbin/iprinit, /usr/sbin/iprupdate, /usr/sbin/raid-check PROCESS TYPES
SELinux defines process types (domains) for each process running on the system You can see the context of a process using the -Z option to ps Policy governs the access confined processes have to files. SELinux mdadm policy is very flexible allowing users to setup their mdadm pro- cesses in as secure a method as possible. The following process types are defined for mdadm: mdadm_t Note: semanage permissive -a mdadm_t can be used to make the process type mdadm_t permissive. SELinux does not deny access to permissive process types, but the AVC (SELinux denials) messages are still generated. BOOLEANS
SELinux policy is customizable based on least access required. mdadm policy is extremely flexible and has several booleans that allow you to manipulate the policy and run mdadm with the tightest access possible. If you want to allow users to resolve user passwd entries directly from ldap rather then using a sssd server, you must turn on the authlo- gin_nsswitch_use_ldap boolean. Disabled by default. setsebool -P authlogin_nsswitch_use_ldap 1 If you want to allow all daemons to write corefiles to /, you must turn on the daemons_dump_core boolean. Disabled by default. setsebool -P daemons_dump_core 1 If you want to enable cluster mode for daemons, you must turn on the daemons_enable_cluster_mode boolean. Enabled by default. setsebool -P daemons_enable_cluster_mode 1 If you want to allow all daemons to use tcp wrappers, you must turn on the daemons_use_tcp_wrapper boolean. Disabled by default. setsebool -P daemons_use_tcp_wrapper 1 If you want to allow all daemons the ability to read/write terminals, you must turn on the daemons_use_tty boolean. Disabled by default. setsebool -P daemons_use_tty 1 If you want to deny any process from ptracing or debugging any other processes, you must turn on the deny_ptrace boolean. Enabled by default. setsebool -P deny_ptrace 1 If you want to allow all domains to use other domains file descriptors, you must turn on the domain_fd_use boolean. Enabled by default. setsebool -P domain_fd_use 1 If you want to allow all domains to have the kernel load modules, you must turn on the domain_kernel_load_modules boolean. Disabled by default. setsebool -P domain_kernel_load_modules 1 If you want to allow all domains to execute in fips_mode, you must turn on the fips_mode boolean. Enabled by default. setsebool -P fips_mode 1 If you want to enable reading of urandom for all domains, you must turn on the global_ssp boolean. Disabled by default. setsebool -P global_ssp 1 If you want to allow confined applications to run with kerberos, you must turn on the kerberos_enabled boolean. Enabled by default. setsebool -P kerberos_enabled 1 If you want to allow system to run with NIS, you must turn on the nis_enabled boolean. Disabled by default. setsebool -P nis_enabled 1 If you want to allow confined applications to use nscd shared memory, you must turn on the nscd_use_shm boolean. Enabled by default. setsebool -P nscd_use_shm 1 NSSWITCH DOMAIN
If you want to allow users to resolve user passwd entries directly from ldap rather then using a sssd server for the mdadm_t, you must turn on the authlogin_nsswitch_use_ldap boolean. setsebool -P authlogin_nsswitch_use_ldap 1 If you want to allow confined applications to run with kerberos for the mdadm_t, you must turn on the kerberos_enabled boolean. setsebool -P kerberos_enabled 1 MANAGED FILES
The SELinux process type mdadm_t can manage files labeled with the following file types. The paths listed are the default paths for these file types. Note the processes UID still need to have DAC permissions. cgroup_t /cgroup(/.*)? /sys/fs/cgroup(/.*)? cluster_conf_t /etc/cluster(/.*)? cluster_var_lib_t /var/lib/pcsd(/.*)? /var/lib/cluster(/.*)? /var/lib/openais(/.*)? /var/lib/pengine(/.*)? /var/lib/corosync(/.*)? /usr/lib/heartbeat(/.*)? /var/lib/heartbeat(/.*)? /var/lib/pacemaker(/.*)? cluster_var_run_t /var/run/crm(/.*)? /var/run/cman_.* /var/run/rsctmp(/.*)? /var/run/aisexec.* /var/run/heartbeat(/.*)? /var/run/cpglockd.pid /var/run/corosync.pid /var/run/rgmanager.pid /var/run/cluster/rgmanager.sk kdump_lock_t /var/lock/kdump(/.*)? kdumpctl_tmp_t mdadm_conf_t /etc/mdadm.conf mdadm_tmp_t mdadm_tmpfs_t mdadm_var_run_t /dev/md/.* /var/run/mdadm(/.*)? /dev/.mdadm.map root_t / /initrd sysfs_t /sys(/.*)? systemd_passwd_var_run_t /var/run/systemd/ask-password(/.*)? /var/run/systemd/ask-password-block(/.*)? FILE CONTEXTS
SELinux requires files to have an extended attribute to define the file type. You can see the context of a file using the -Z option to ls Policy governs the access confined processes have to these files. SELinux mdadm policy is very flexible allowing users to setup their mdadm processes in as secure a method as possible. STANDARD FILE CONTEXT SELinux defines the file context types for the mdadm, if you wanted to store files with these types in a diffent paths, you need to execute the semanage command to sepecify alternate labeling and then use restorecon to put the labels on disk. semanage fcontext -a -t mdadm_conf_t '/srv/mdadm/content(/.*)?' restorecon -R -v /srv/mymdadm_content Note: SELinux often uses regular expressions to specify labels that match multiple files. The following file types are defined for mdadm: mdadm_conf_t - Set files with the mdadm_conf_t type, if you want to treat the files as mdadm configuration data, usually stored under the /etc direc- tory. mdadm_exec_t - Set files with the mdadm_exec_t type, if you want to transition an executable to the mdadm_t domain. Paths: /sbin/mdadm, /sbin/mdmon, /sbin/mdmpd, /sbin/iprdump, /sbin/iprinit, /sbin/iprupdate, /usr/sbin/mdadm, /usr/sbin/mdmpd, /usr/sbin/mdmon, /sbin/raid-check, /usr/sbin/iprdump, /usr/sbin/iprinit, /usr/sbin/iprupdate, /usr/sbin/raid-check mdadm_initrc_exec_t - Set files with the mdadm_initrc_exec_t type, if you want to transition an executable to the mdadm_initrc_t domain. mdadm_tmp_t - Set files with the mdadm_tmp_t type, if you want to store mdadm temporary files in the /tmp directories. mdadm_tmpfs_t - Set files with the mdadm_tmpfs_t type, if you want to store mdadm files on a tmpfs file system. mdadm_unit_file_t - Set files with the mdadm_unit_file_t type, if you want to treat the files as mdadm unit content. Paths: /usr/lib/systemd/system/mdmon@.*, /usr/lib/systemd/system/mdmonitor.* mdadm_var_run_t - Set files with the mdadm_var_run_t type, if you want to store the mdadm files under the /run or /var/run directory. Paths: /dev/md/.*, /var/run/mdadm(/.*)?, /dev/.mdadm.map Note: File context can be temporarily modified with the chcon command. If you want to permanently change the file context you need to use the semanage fcontext command. This will modify the SELinux labeling database. You will need to use restorecon to apply the labels. COMMANDS
semanage fcontext can also be used to manipulate default file context mappings. semanage permissive can also be used to manipulate whether or not a process type is permissive. semanage module can also be used to enable/disable/install/remove policy modules. semanage boolean can also be used to manipulate the booleans system-config-selinux is a GUI tool available to customize SELinux policy settings. AUTHOR
This manual page was auto-generated using sepolicy manpage . SEE ALSO
selinux(8), mdadm(8), semanage(8), restorecon(8), chcon(1), sepolicy(8) , setsebool(8) mdadm 14-06-10 mdadm_selinux(8)
All times are GMT -4. The time now is 09:31 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy