{"id":548,"date":"2018-09-06T21:30:40","date_gmt":"2018-09-06T19:30:40","guid":{"rendered":"https:\/\/blog.nav.ro\/?p=548"},"modified":"2025-07-17T15:02:50","modified_gmt":"2025-07-17T12:02:50","slug":"depanarea-kernel-panic-in-linux","status":"publish","type":"post","link":"https:\/\/www.nav.ro\/blog\/depanarea-kernel-panic-in-linux\/","title":{"rendered":"Depanarea kernel panic \u00een Linux"},"content":{"rendered":"

Introducere<\/strong><\/p>\n

Termenul „kernel panic” nu este deloc \u00eensp\u0103im\u00e2nt\u0103tor pentru niciun administrator de sistem. O panic\u0103 a kernel-ului este o m\u0103sur\u0103 de siguran\u021b\u0103, \u00een ultim\u0103 faz\u0103, exercitat\u0103 de kernelul sistemului de operare \u00een momentul detect\u0103rii unei erori fatale interne pe care nu o poate recupera \u00een siguran\u021b\u0103 sau acesta nu poate continua s\u0103 func\u021bioneze f\u0103r\u0103 a avea un risc mult mai mare de pierdere a datelor importante. Rutinele de kernel care se ocup\u0103 de panic\u0103, cunoscute sub numele de panic () \u00een codul surs\u0103 derivat de la AT & T \u0219i BSD Unix, sunt \u00een general concepute pentru a transmite un mesaj de eroare consolei, \u0219i de a arunca o imagine a memoriei kernel-ului pe disc pentru depanare post-mortem, \u00een acest caz fie a\u0219tepta\u021bi ca sistemul s\u0103 fie repornit manual, fie ini\u021bia\u021bi o repornire automat\u0103. Informa\u021biile furnizate sunt de natur\u0103 extrem de tehnic\u0103 \u0219i au scopul de a asista un administrator de sistem sau mai precis un inginer de kernel \u00een diagnosticarea problemei. De\u0219i nu este foarte comun, panica kernel-ului poate fi de asemenea cauzat\u0103 de erori care provin din afara spa\u021biului acestuia.<\/p>\n

O panic\u0103 a kernelului ar putea fi cauzat\u0103 din numeroase motive diferite. \u00cen acest articol, vom demonstra pa\u0219ii pe care i-am efectuat pentru depanarea unui scenariu de kernel panic care a ap\u0103rut dup\u0103 ce am repornit un sistem \u00eentr-o activitate de patch-uri \/ actualiz\u0103ri de sistem.<\/p>\n

Scenariu<\/strong><\/p>\n

Sistemul pe care a ap\u0103rut panica kernel-ului rula RHEL 6.9, iar panica a fost provocat\u0103 dup\u0103 ce am restartat sistemul, astfel \u00eenc\u00e2t acesta s\u0103 porneasc\u0103 pe noul kernel instalat pe sistem printr-o activitate de actualizare „yum update”.<\/p>\n

Mai jos este o captur\u0103 de ecran a mesajului de kernel panic afi\u0219at pe consol\u0103<\/p>\n

Pa\u0219i de diagnosticare \u0219i depanare<\/strong><\/p>\n

Mesajul de panic\u0103 \u00een kernel \u00een sine nu era foarte descriptiv, a\u0219a cum probabil a\u021bi \u00een\u021beles din screenshot-ul afi\u0219at mai sus. Dar, dup\u0103 c\u00e2teva investiga\u021bii, am reu\u0219it s\u0103 identific\u0103m cauza singur\u0103 \u0219i s\u0103 o rezolv\u0103m. Vom descrie acum secven\u021ba de pa\u0219i pe care i-am urmat.
\n
\nDe la ce etap\u0103 a procesului de bootare sistemul intr\u0103 \u00een panic\u0103?<\/strong><\/p>\n

Am restartat sistemul cu noul kernel de c\u00e2teva ori pentru a realiza c\u0103 sistemul a fost panicat de \u00eendat\u0103 ce sistemul a \u00eencercat \u00eenc\u0103rcarea kernel-ului dup\u0103 afi\u0219area sec\u021biunii grub.<\/p>\n

S-a \u00eencercat boot-area cu vechiul kernel<\/strong><\/p>\n

Am reu\u0219it s\u0103 pornesc cu succes sistemul pentru a rula nivelul 3, f\u0103r\u0103 a \u00eent\u00e2mpina nepl\u0103ceri atunci c\u00e2nd am \u00eencercat s\u0103 bootez cu vechiul kernel.<\/p>\n

Trebuiesc diferen\u021biate liniile pentru kernel-ul vechi \u0219i cel nou<\/strong><\/p>\n

Am verificat fi\u0219ierul \/boot\/grub\/grub.conf \u0219i am examinat liniile de kernel la promptul grub pentru a constata c\u0103 fi\u0219ierul initramfs lipsea pentru noul kernel. Am restartat sistemul prin kernelul vechi din nou \u0219i am observat c\u0103 nu a fost creat niciun fi\u0219ier initramfs pentru noul kernel \u00een directorul \/ boot.<\/p>\n

[ssuri@linuxnix:\/boot] $ ls -ltr | grep -i initramfs
\n-rw––- 1 root root 26654700 Dec 11 2016 initramfs-2.6.32-642.6.2.el6.x86_64.img
\n-rw––- 1 root root 26088799 Jan 8 2017 initramfs-2.6.32-573.1.1.el6.x86_64.tmp
\n-rw––- 1 root root 26781018 Jun 11 2017 initramfs-2.6.32-642.13.1.el6.x86_64.img
\n-rw––- 1 root root 26088606 Dec 17 03:11 initramfs-2.6.32-573.18.1.el6.x86_64.tmp
\n-rw––- 1 root root 26785659 Dec 17 03:12 initramfs-2.6.32-642.6.2.el6.x86_64.tmp<\/em><\/p>\n

Dup\u0103 cum pute\u021bi observa din output-ul de mai sus, avem c\u00e2teva fi\u0219iere initramfs pentru kernel-urile mai vechi, dar lipse\u0219te fi\u0219ierul pentru cel mai nou kernel 2.6.32-696.6.3.el6.x86_64.<\/p>\n

S-a \u00eencercat crearea manual\u0103 a fi\u0219ierului initramfs<\/strong><\/p>\n

C\u00e2nd am \u00eencercat s\u0103 creez manual fi\u0219ierul initramfs pentru noul kernel, comanda „dracut” a e\u0219uat.<\/p>\n

[ssuri@linuxnix:\/boot] $ sudo dracut -f \/boot\/initramfs-2.6.32-696.6.3.el6.x86_64.img 2.6.32-696.6.3.el6.x86_64<\/em><\/p>\n

mktemp: failed to create directory via template `\/tmp\/initramfs.XXXXXX’: No space left on device
\nchmod: cannot access `’: No such file or directory
\nusage: plymouth [ –verbose | -v ] { –targetdir | -t } <\/em><\/p>\n

cp: `\/etc\/ld.so.conf’ and `\/etc\/ld.so.conf’ are the same file
\ncp: `\/etc\/ld.so.conf.d’ and `\/etc\/ld.so.conf.d’ are the same file
\nfind: cannot search `’: No such file or directory
\ncpio: File .\/initramfs-2.6.32-696.6.3.el6.x86_64.img grew, 19316736 new bytes not copied<\/em><\/p>\n

S-a c\u0103utat cauza lipsei fi\u0219ierului initramfs<\/strong><\/p>\n

Eroarea \u00een comanda „dracut” men\u021bionat\u0103 anterior m-a determinat s\u0103 verific starea sistemului de fi\u0219iere \/ tmp. De\u0219i sistemul de fi\u0219iere a avut o mul\u021bime de spa\u021biu de stocare disponibil, a ie\u0219it din inode-uri ceea ce a cauzat imposibilitatea creerii de noi fi\u0219iere temporare care ar fi putut fi necesare c\u0103tre comanda „dracut”.<\/p>\n

[ssuri@linuxnix:\/boot] $ df -h .
\nFilesystem Size Used Avail Use% Mounted on
\n\/dev\/mapper\/os_pvp1 493M 159M 309M 34% \/boot
\n[ssuri@linuxnix:\/boot] $
\n[ssuri@linuxnix:~] $ df -hi \/tmp
\nFilesystem Inodes IUsed IFree IUse% Mounted on
\n\/dev\/mapper\/os_vg-tmp_lv
\n128K 128K 0 100% \/tmp<\/em><\/p>\n

Elibera\u021bi inodes \u00een \/ tmp \u0219i crea\u021bi fi\u0219ierul initramfs<\/strong><\/p>\n

Imediat dup\u0103 vizualizarea st\u0103rii inode pentru sistemul de fi\u0219iere \/ tmp, am continuat s\u0103 \u00eel cur\u0103\u021b.<\/p>\n

[ssuri@linuxnix:~] $ df -hi \/tmp
\nFilesystem Inodes IUsed IFree IUse% Mounted on
\n\/dev\/mapper\/os_vg-tmp_lv
\n128K 232 128K 1% \/tmp
\n[ssuri@linuxnix:~] $<\/em><\/p>\n

Odat\u0103 ce s-au eliberat inode-urile, am creat fi\u0219ierul initramfs a\u0219a cum se arat\u0103 \u00een comanda de mai jos.<\/p>\n

[ssuri@linuxnix:\/boot] $ sudo dracut -f \/boot\/initramfs-2.6.32-696.6.3.el6.x86_64.img 2.6.32-696.6.3.el6.x86_64
\n[ssuri@linuxnix:\/boot] $ ls -ltr | grep -i initramfs
\n-rw––- 1 root root 26654700 Dec 11 2016 initramfs-2.6.32-642.6.2.el6.x86_64.img
\n-rw––- 1 root root 26088799 Jan 8 2017 initramfs-2.6.32-573.1.1.el6.x86_64.tmp
\n-rw––- 1 root root 26781018 Jun 11 2017 initramfs-2.6.32-642.13.1.el6.x86_64.img
\n-rw––- 1 root root 26088606 Dec 17 03:11 initramfs-2.6.32-573.18.1.el6.x86_64.tmp
\n-rw––- 1 root root 26785659 Dec 17 03:12 initramfs-2.6.32-642.6.2.el6.x86_64.tmp
\n-rw––- 1 root root 25606929 Jan 14 06:51 initramfs-2.6.32-696.6.3.el6.x86_64.img<\/em><\/p>\n

Comanda dracut a ad\u0103ugat automat intrarea pentru fi\u0219ierul initramfs pentru noul kernel din fi\u0219ierul \/boot\/grub\/grub.conf care mai lipsea mai devreme.<\/p>\n

[ssuri@linuxnix:~] $ sudo cat \/etc\/grub.conf<\/em><\/p>\n

# grub.conf generated by anaconda
\n#
\n# Note that you do not have to rerun grub after making changes to this file
\n# NOTICE: You have a \/boot partition. This means that
\n# all kernel and initrd paths are relative to \/boot\/, eg.
\n# root (hd3,0)
\n# kernel \/vmlinuz-version ro root=\/dev\/mapper\/os_vg-root_lv
\n# initrd \/initrd-[generic-]version.img
\n#boot=\/dev\/sda
\ndefault=0
\ntimeout=50
\n#splashimage=(hd0,0)\/grub\/splash.xpm.gz
\n#hiddenmenu<\/em><\/p>\n

title Red Hat Enterprise Linux Server (2.6.32-696.6.3.el6.x86_64)
\nroot (hd0,0)
\nkernel \/vmlinuz-2.6.32-696.6.3.el6.x86_64 ro root=\/dev\/mapper\/os_vg-root_lv rd_NO_LUKS LANG=en_US.UTF-8 rd_LVM_LV=os_vg\/swap_01_lv rd_NO_MD SYSFONT=latarcyrheb-sun16 crashkernel=512M rd_LVM_LV=os_vg\/root_lv KEYBOARDTYPE=pc KEYTABLE=us rd_NO_DM elevator=deadline transparent_hugepage=never debug KEYTABLE=us rd_NO_DM elevator=deadline transparent_hugepage=never debug<\/p>\n

initrd \/initramfs-2.6.32-696.6.3.el6.x86_64.img<\/p>\n

title Red Hat Enterprise Linux Server (2.6.32-642.13.1.el6.x86_64)
\nroot (hd0,0)
\nkernel \/vmlinuz-2.6.32-642.13.1.el6.x86_64 ro root=\/dev\/mapper\/os_vg-root_lv rd_NO_LUKS LANG=en_US.UTF-8 rd_LVM_LV=os_vg\/swap_01_lv rd_NO_MD SYSFONT=latarcyrheb-sun16 crashkernel=512M rd_LVM_LV=os_vg\/root_lv KEYBOARDTYPE=pc KEYTABLE=us rd_NO_DM elevator=deadline transparent_hugepage=never debug KEYTABLE=us rd_NO_DM elevator=deadline transparent_hugepage=never debug<\/p>\n

initrd \/initramfs-2.6.32-642.13.1.el6.x86_64.img<\/p>\n

title Red Hat Enterprise Linux Server (2.6.32-642.6.2.el6.x86_64)
\nroot (hd0,0)
\nkernel \/vmlinuz-2.6.32-642.6.2.el6.x86_64 ro root=\/dev\/mapper\/os_vg-root_lv rd_NO_LUKS LANG=en_US.UTF-8 rd_LVM_LV=os_vg\/swap_01_lv rd_NO_MD SYSFONT=latarcyrheb-sun16 crashkernel=512M rd_LVM_LV=os_vg\/root_lv KEYBOARDTYPE=pc KEYTABLE=us rd_NO_DM elevator=noop transparent_hugepage=never debug<\/p>\n

initrd \/initramfs-2.6.32-642.6.2.el6.x86_64.img<\/p>\n

title Red Hat Enterprise Linux Server (2.6.32-573.1.1.el6.x86_64)
\nroot (hd0,0)
\nkernel \/vmlinuz-2.6.32-573.1.1.el6.x86_64 ro root=\/dev\/mapper\/os_vg-root_lv rd_NO_LUKS LANG=en_US.UTF-8 rd_LVM_LV=os_vg\/swap_01_lv rd_NO_MD SYSFONT=latarcyrheb-sun16 crashkernel=512M rd_LVM_LV=os_vg\/root_lv KEYBOARDTYPE=pc KEYTABLE=us rd_NO_DM elevator=noop transparent_hugepage=never debug<\/p>\n

initrd \/initramfs-2.6.32-573.1.1.el6.x86_64.img
\n[ssuri@linuxnix:~] $<\/em><\/p>\n

Am pornit sistemul cu noul kernel<\/strong><\/p>\n

Am restartat sistemul din nou \u0219i de aceast\u0103 dat\u0103 serverul a reu\u0219it s\u0103 ruleze cu succes pe noul kernel.<\/p>\n

Concluzie<\/strong><\/p>\n

Scenariul pe care l-am discutat \u00een acest articol poate p\u0103rea neobi\u0219nuit, dar cu siguran\u021b\u0103 nu este improbabil. S-ar putea s\u0103 existe o serie de scenarii care ar putea necesita reconstruirea fi\u0219ierului initramfs \u0219i am demonstrat un astfel de scenariu \u00een acest articol. Sper\u0103m c\u0103 a\u021bi g\u0103sit explica\u021bia \u0219i demonstra\u021bia utile \u0219i a\u0219tept\u0103m cu ner\u0103bdare feedback-ul dvs.<\/p>\n","protected":false},"excerpt":{"rendered":"

Introducere Termenul „kernel panic” nu este deloc \u00eensp\u0103im\u00e2nt\u0103tor pentru niciun administrator de sistem. O panic\u0103 a kernel-ului este o m\u0103sur\u0103 de siguran\u021b\u0103, \u00een ultim\u0103 faz\u0103, exercitat\u0103 de kernelul sistemului de operare \u00een momentul detect\u0103rii unei erori fatale interne pe care nu o poate recupera \u00een siguran\u021b\u0103 sau acesta nu poate continua s\u0103 func\u021bioneze f\u0103r\u0103 a<\/p>\n","protected":false},"author":1,"featured_media":1020,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[152],"tags":[],"class_list":["post-548","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-data-room"],"yoast_head":"\nDepanarea kernel panic \u00een Linux - NAV.RO Blog<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.nav.ro\/blog\/depanarea-kernel-panic-in-linux\/\" \/>\n<meta property=\"og:locale\" content=\"ro_RO\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Depanarea kernel panic \u00een Linux - NAV.RO Blog\" \/>\n<meta property=\"og:description\" content=\"Introducere Termenul „kernel panic” nu este deloc \u00eensp\u0103im\u00e2nt\u0103tor pentru niciun administrator de sistem. O panic\u0103 a kernel-ului este o m\u0103sur\u0103 de siguran\u021b\u0103, \u00een ultim\u0103 faz\u0103, exercitat\u0103 de kernelul sistemului de operare \u00een momentul detect\u0103rii unei erori fatale interne pe care nu o poate recupera \u00een siguran\u021b\u0103 sau acesta nu poate continua s\u0103 func\u021bioneze f\u0103r\u0103 a\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.nav.ro\/blog\/depanarea-kernel-panic-in-linux\/\" \/>\n<meta property=\"og:site_name\" content=\"NAV.RO Blog\" \/>\n<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/nav6718\" \/>\n<meta property=\"article:published_time\" content=\"2018-09-06T19:30:40+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2025-07-17T12:02:50+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.nav.ro\/blog\/wp-content\/uploads\/2019\/01\/linux_kernel_panic.png\" \/>\n\t<meta property=\"og:image:width\" content=\"870\" \/>\n\t<meta property=\"og:image:height\" content=\"609\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"NAV.RO\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@nav6718\" \/>\n<meta name=\"twitter:site\" content=\"@nav6718\" \/>\n<meta name=\"twitter:label1\" content=\"Scris de\" \/>\n\t<meta name=\"twitter:data1\" content=\"NAV.RO\" \/>\n\t<meta name=\"twitter:label2\" content=\"Timp estimat pentru citire\" \/>\n\t<meta name=\"twitter:data2\" content=\"7 minute\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/www.nav.ro\/blog\/depanarea-kernel-panic-in-linux\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.nav.ro\/blog\/depanarea-kernel-panic-in-linux\/\"},\"author\":{\"name\":\"NAV.RO\",\"@id\":\"https:\/\/www.nav.ro\/blog\/#\/schema\/person\/c0271febcae717bbdbc3b2c6dbdec20e\"},\"headline\":\"Depanarea kernel panic \u00een Linux\",\"datePublished\":\"2018-09-06T19:30:40+00:00\",\"dateModified\":\"2025-07-17T12:02:50+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.nav.ro\/blog\/depanarea-kernel-panic-in-linux\/\"},\"wordCount\":1471,\"publisher\":{\"@id\":\"https:\/\/www.nav.ro\/blog\/#organization\"},\"image\":{\"@id\":\"https:\/\/www.nav.ro\/blog\/depanarea-kernel-panic-in-linux\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/www.nav.ro\/blog\/wp-content\/uploads\/2019\/01\/linux_kernel_panic.png\",\"articleSection\":[\"DATA ROOM\"],\"inLanguage\":\"ro-RO\"},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.nav.ro\/blog\/depanarea-kernel-panic-in-linux\/\",\"url\":\"https:\/\/www.nav.ro\/blog\/depanarea-kernel-panic-in-linux\/\",\"name\":\"Depanarea kernel panic \u00een Linux - NAV.RO Blog\",\"isPartOf\":{\"@id\":\"https:\/\/www.nav.ro\/blog\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/www.nav.ro\/blog\/depanarea-kernel-panic-in-linux\/#primaryimage\"},\"image\":{\"@id\":\"https:\/\/www.nav.ro\/blog\/depanarea-kernel-panic-in-linux\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/www.nav.ro\/blog\/wp-content\/uploads\/2019\/01\/linux_kernel_panic.png\",\"datePublished\":\"2018-09-06T19:30:40+00:00\",\"dateModified\":\"2025-07-17T12:02:50+00:00\",\"breadcrumb\":{\"@id\":\"https:\/\/www.nav.ro\/blog\/depanarea-kernel-panic-in-linux\/#breadcrumb\"},\"inLanguage\":\"ro-RO\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.nav.ro\/blog\/depanarea-kernel-panic-in-linux\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"ro-RO\",\"@id\":\"https:\/\/www.nav.ro\/blog\/depanarea-kernel-panic-in-linux\/#primaryimage\",\"url\":\"https:\/\/www.nav.ro\/blog\/wp-content\/uploads\/2019\/01\/linux_kernel_panic.png\",\"contentUrl\":\"https:\/\/www.nav.ro\/blog\/wp-content\/uploads\/2019\/01\/linux_kernel_panic.png\",\"width\":870,\"height\":609},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.nav.ro\/blog\/depanarea-kernel-panic-in-linux\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Prima pagin\u0103\",\"item\":\"https:\/\/www.nav.ro\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Depanarea kernel panic \u00een Linux\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/www.nav.ro\/blog\/#website\",\"url\":\"https:\/\/www.nav.ro\/blog\/\",\"name\":\"NAV.RO Blog\",\"description\":\"Stiri IT\u2705 de actualitate si noutati din domeniul Hosting \u279c Gazduire Web \u279c Servere Dedicate \/ VPS \u279c DATA CENTER \u279c Domenii \u2b50 Actualizare zilnica de la expertii NAV.RO\",\"publisher\":{\"@id\":\"https:\/\/www.nav.ro\/blog\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/www.nav.ro\/blog\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"ro-RO\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/www.nav.ro\/blog\/#organization\",\"name\":\"NAV Communications\",\"url\":\"https:\/\/www.nav.ro\/blog\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"ro-RO\",\"@id\":\"https:\/\/www.nav.ro\/blog\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/www.nav.ro\/blog\/wp-content\/uploads\/2022\/09\/nav_logo.png\",\"contentUrl\":\"https:\/\/www.nav.ro\/blog\/wp-content\/uploads\/2022\/09\/nav_logo.png\",\"width\":1120,\"height\":800,\"caption\":\"NAV Communications\"},\"image\":{\"@id\":\"https:\/\/www.nav.ro\/blog\/#\/schema\/logo\/image\/\"},\"sameAs\":[\"https:\/\/www.facebook.com\/nav6718\",\"https:\/\/x.com\/nav6718\"]},{\"@type\":\"Person\",\"@id\":\"https:\/\/www.nav.ro\/blog\/#\/schema\/person\/c0271febcae717bbdbc3b2c6dbdec20e\",\"name\":\"NAV.RO\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"ro-RO\",\"@id\":\"https:\/\/www.nav.ro\/blog\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/93c42d768fb29d2b7c2c9b94595b1770ec8dbbda107bfb5e6759247e857c9cda?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/93c42d768fb29d2b7c2c9b94595b1770ec8dbbda107bfb5e6759247e857c9cda?s=96&d=mm&r=g\",\"caption\":\"NAV.RO\"},\"sameAs\":[\"https:\/\/www.nav.ro\"],\"url\":\"https:\/\/www.nav.ro\/blog\/author\/useradmin\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Depanarea kernel panic \u00een Linux - NAV.RO Blog","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.nav.ro\/blog\/depanarea-kernel-panic-in-linux\/","og_locale":"ro_RO","og_type":"article","og_title":"Depanarea kernel panic \u00een Linux - NAV.RO Blog","og_description":"Introducere Termenul „kernel panic” nu este deloc \u00eensp\u0103im\u00e2nt\u0103tor pentru niciun administrator de sistem. O panic\u0103 a kernel-ului este o m\u0103sur\u0103 de siguran\u021b\u0103, \u00een ultim\u0103 faz\u0103, exercitat\u0103 de kernelul sistemului de operare \u00een momentul detect\u0103rii unei erori fatale interne pe care nu o poate recupera \u00een siguran\u021b\u0103 sau acesta nu poate continua s\u0103 func\u021bioneze f\u0103r\u0103 a","og_url":"https:\/\/www.nav.ro\/blog\/depanarea-kernel-panic-in-linux\/","og_site_name":"NAV.RO Blog","article_publisher":"https:\/\/www.facebook.com\/nav6718","article_published_time":"2018-09-06T19:30:40+00:00","article_modified_time":"2025-07-17T12:02:50+00:00","og_image":[{"width":870,"height":609,"url":"https:\/\/www.nav.ro\/blog\/wp-content\/uploads\/2019\/01\/linux_kernel_panic.png","type":"image\/png"}],"author":"NAV.RO","twitter_card":"summary_large_image","twitter_creator":"@nav6718","twitter_site":"@nav6718","twitter_misc":{"Scris de":"NAV.RO","Timp estimat pentru citire":"7 minute"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.nav.ro\/blog\/depanarea-kernel-panic-in-linux\/#article","isPartOf":{"@id":"https:\/\/www.nav.ro\/blog\/depanarea-kernel-panic-in-linux\/"},"author":{"name":"NAV.RO","@id":"https:\/\/www.nav.ro\/blog\/#\/schema\/person\/c0271febcae717bbdbc3b2c6dbdec20e"},"headline":"Depanarea kernel panic \u00een Linux","datePublished":"2018-09-06T19:30:40+00:00","dateModified":"2025-07-17T12:02:50+00:00","mainEntityOfPage":{"@id":"https:\/\/www.nav.ro\/blog\/depanarea-kernel-panic-in-linux\/"},"wordCount":1471,"publisher":{"@id":"https:\/\/www.nav.ro\/blog\/#organization"},"image":{"@id":"https:\/\/www.nav.ro\/blog\/depanarea-kernel-panic-in-linux\/#primaryimage"},"thumbnailUrl":"https:\/\/www.nav.ro\/blog\/wp-content\/uploads\/2019\/01\/linux_kernel_panic.png","articleSection":["DATA ROOM"],"inLanguage":"ro-RO"},{"@type":"WebPage","@id":"https:\/\/www.nav.ro\/blog\/depanarea-kernel-panic-in-linux\/","url":"https:\/\/www.nav.ro\/blog\/depanarea-kernel-panic-in-linux\/","name":"Depanarea kernel panic \u00een Linux - NAV.RO Blog","isPartOf":{"@id":"https:\/\/www.nav.ro\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.nav.ro\/blog\/depanarea-kernel-panic-in-linux\/#primaryimage"},"image":{"@id":"https:\/\/www.nav.ro\/blog\/depanarea-kernel-panic-in-linux\/#primaryimage"},"thumbnailUrl":"https:\/\/www.nav.ro\/blog\/wp-content\/uploads\/2019\/01\/linux_kernel_panic.png","datePublished":"2018-09-06T19:30:40+00:00","dateModified":"2025-07-17T12:02:50+00:00","breadcrumb":{"@id":"https:\/\/www.nav.ro\/blog\/depanarea-kernel-panic-in-linux\/#breadcrumb"},"inLanguage":"ro-RO","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.nav.ro\/blog\/depanarea-kernel-panic-in-linux\/"]}]},{"@type":"ImageObject","inLanguage":"ro-RO","@id":"https:\/\/www.nav.ro\/blog\/depanarea-kernel-panic-in-linux\/#primaryimage","url":"https:\/\/www.nav.ro\/blog\/wp-content\/uploads\/2019\/01\/linux_kernel_panic.png","contentUrl":"https:\/\/www.nav.ro\/blog\/wp-content\/uploads\/2019\/01\/linux_kernel_panic.png","width":870,"height":609},{"@type":"BreadcrumbList","@id":"https:\/\/www.nav.ro\/blog\/depanarea-kernel-panic-in-linux\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Prima pagin\u0103","item":"https:\/\/www.nav.ro\/blog\/"},{"@type":"ListItem","position":2,"name":"Depanarea kernel panic \u00een Linux"}]},{"@type":"WebSite","@id":"https:\/\/www.nav.ro\/blog\/#website","url":"https:\/\/www.nav.ro\/blog\/","name":"NAV.RO Blog","description":"Stiri IT\u2705 de actualitate si noutati din domeniul Hosting \u279c Gazduire Web \u279c Servere Dedicate \/ VPS \u279c DATA CENTER \u279c Domenii \u2b50 Actualizare zilnica de la expertii NAV.RO","publisher":{"@id":"https:\/\/www.nav.ro\/blog\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.nav.ro\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"ro-RO"},{"@type":"Organization","@id":"https:\/\/www.nav.ro\/blog\/#organization","name":"NAV Communications","url":"https:\/\/www.nav.ro\/blog\/","logo":{"@type":"ImageObject","inLanguage":"ro-RO","@id":"https:\/\/www.nav.ro\/blog\/#\/schema\/logo\/image\/","url":"https:\/\/www.nav.ro\/blog\/wp-content\/uploads\/2022\/09\/nav_logo.png","contentUrl":"https:\/\/www.nav.ro\/blog\/wp-content\/uploads\/2022\/09\/nav_logo.png","width":1120,"height":800,"caption":"NAV Communications"},"image":{"@id":"https:\/\/www.nav.ro\/blog\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/www.facebook.com\/nav6718","https:\/\/x.com\/nav6718"]},{"@type":"Person","@id":"https:\/\/www.nav.ro\/blog\/#\/schema\/person\/c0271febcae717bbdbc3b2c6dbdec20e","name":"NAV.RO","image":{"@type":"ImageObject","inLanguage":"ro-RO","@id":"https:\/\/www.nav.ro\/blog\/#\/schema\/person\/image\/","url":"https:\/\/secure.gravatar.com\/avatar\/93c42d768fb29d2b7c2c9b94595b1770ec8dbbda107bfb5e6759247e857c9cda?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/93c42d768fb29d2b7c2c9b94595b1770ec8dbbda107bfb5e6759247e857c9cda?s=96&d=mm&r=g","caption":"NAV.RO"},"sameAs":["https:\/\/www.nav.ro"],"url":"https:\/\/www.nav.ro\/blog\/author\/useradmin\/"}]}},"_links":{"self":[{"href":"https:\/\/www.nav.ro\/blog\/wp-json\/wp\/v2\/posts\/548","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.nav.ro\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.nav.ro\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.nav.ro\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.nav.ro\/blog\/wp-json\/wp\/v2\/comments?post=548"}],"version-history":[{"count":2,"href":"https:\/\/www.nav.ro\/blog\/wp-json\/wp\/v2\/posts\/548\/revisions"}],"predecessor-version":[{"id":3985,"href":"https:\/\/www.nav.ro\/blog\/wp-json\/wp\/v2\/posts\/548\/revisions\/3985"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.nav.ro\/blog\/wp-json\/wp\/v2\/media\/1020"}],"wp:attachment":[{"href":"https:\/\/www.nav.ro\/blog\/wp-json\/wp\/v2\/media?parent=548"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.nav.ro\/blog\/wp-json\/wp\/v2\/categories?post=548"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.nav.ro\/blog\/wp-json\/wp\/v2\/tags?post=548"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}