HDD problems causing Kernel panics in Linux/Debian?
in [Storage]
|
Prev: [fw] Oracle Drops Hitachi Data Storage Arrays
Next: Any way to revive a dropped 1.5TB Seagate drive? MUST GET IT TO SPIN UP
From: Arno on 7 Mar 2010 12:24 In comp.sys.ibm.pc.hardware.storage Pascal Hambourg <boite-a-spam(a)plouf.fr.eu.org> wrote: > Rod Speed a ?crit : >> Pascal Hambourg wrote >> >>> Aren't pending sectors sectors waiting to be remapped because of read errors ? >> >> Thats not the same thing as unreadable sectors. > Aren't pending sectors unreadable, because of read errors ? A pending sector is one that the disk tried to read but failed. Additional reads may recover it, but the disk has already done the maximum it will do and will not try by itself again. A pending sector will also become a realocated sector on write, unless that time the disk can read it without any problem after writing it. Such "vanishing pending sectors" are possible when the reason for the unreadability of the sector is external, for example vribrarion or mechanical shock during the initial write or a PSU that has unclean output voltages. Arno -- Arno Wagner, Dr. sc. techn., Dipl. Inform., CISSP -- Email: arno(a)wagner.name GnuPG: ID: 1E25338F FP: 0C30 5782 9D93 F785 E79C 0296 797F 6B50 1E25 338F ---- Cuddly UI's are the manifestation of wishful thinking. -- Dylan Evans
From: Ant on 7 Mar 2010 13:00 On 3/7/2010 9:20 AM PT, Arno typed: > You don't need to, no disk access is possible after a kernel > panic, hence no loging. The only thing you can do, is to > look at the screen or to enable the serial console output and > log that on another machine. > > The reason no disk access is possible is simple: A kernel > panic only hapens when the kernel internal state is regarded > as seriously corrupted. A disk access could then cause serious > filesystem corruption (at least writing) and is therefore > not done. So Windows' blue screens with memory dumps are different? -- "When many work together for a goal, great things may be accomplished. It is said a lion cub was killed by a single colony of ants." --Saskya Pandita /\___/\ / /\ /\ \ Phil./Ant @ http://antfarm.ma.cx (Personal Web Site) | |o o| | Ant's Quality Foraged Links: http://aqfl.net \ _ / Nuke ANT from e-mail address: philpi(a)earthlink.netANT ( ) or ANTant(a)zimage.com Ant is/was listening to a song on his home computer: Phyortek - Synthetic Deviance (ID: 316343)
From: Pascal Hambourg on 7 Mar 2010 14:07 Arno a �crit : > Pascal Hambourg <boite-a-spam(a)plouf.fr.eu.org> wrote: >> Rod Speed a �crit : >>> Pascal Hambourg wrote >>> >>>> Aren't pending sectors sectors waiting to be remapped because of read errors ? >>> >>> Thats not the same thing as unreadable sectors. > >> Aren't pending sectors unreadable, because of read errors ? > > A pending sector is one that the disk tried to read but > failed. "Tried to read but failed", that looks very much like the definition of "unreadable" to me. [skip the rest of the explaination I already knew about]
From: Yousuf Khan on 7 Mar 2010 14:19 Pascal Hambourg wrote: > Rod Speed a �crit : >> Pascal Hambourg wrote >> >>> Aren't pending sectors sectors waiting to be remapped because of read errors ? >> Thats not the same thing as unreadable sectors. > > Aren't pending sectors unreadable, because of read errors ? Pending sectors are still readable, but they are weak when it comes time to write to them. So they are pending remapping during the next write to them. Yousuf Khan
From: Rod Speed on 7 Mar 2010 15:41
Pascal Hambourg wrote > Rod Speed wrote >> Pascal Hambourg wrote >>> Aren't pending sectors sectors waiting to be remapped because of read errors ? >> Thats not the same thing as unreadable sectors. > Aren't pending sectors unreadable, because of read errors ? Not necessarily. |