<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: RM FILE.TXT -&amp;gt; segmentation fault -&amp;gt; Major Crash in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/rm-file-txt-gt-segmentation-fault-gt-major-crash/m-p/2999805#M5196</link>
    <description>1. check the hardware. especially memory, coolers and hard disk (including hard disk temperature)&lt;BR /&gt;2. verify your hard disk. I mean, smartctl and all related stuff&lt;BR /&gt;3. verify that the machine has not been tampered (like in rootkit)&lt;BR /&gt;4. verify that the kernel image + modules (and other packages) you are using are all OK and updated to latest errata.&lt;BR /&gt;5. skip RH 8 if you can. either stick to 7.3 or switch to 9.</description>
    <pubDate>Wed, 18 Jun 2003 07:16:01 GMT</pubDate>
    <dc:creator>Manuel Wolfshant</dc:creator>
    <dc:date>2003-06-18T07:16:01Z</dc:date>
    <item>
      <title>RM FILE.TXT -&gt; segmentation fault -&gt; Major Crash</title>
      <link>https://community.hpe.com/t5/operating-system-linux/rm-file-txt-gt-segmentation-fault-gt-major-crash/m-p/2999804#M5195</link>
      <description>Hi all, here is some reading about an interesting error which leads to major crash.  So if you are up to it, please read on....&lt;BR /&gt;&lt;BR /&gt;Status/Symptoms before crash:&lt;BR /&gt;&lt;BR /&gt;SYMPTOM 1.  When I try to delete some files with ???rm file.txt??? it results to a segmentation fault.  I chmod the file to writable, try to delete again and succeed.&lt;BR /&gt;&lt;BR /&gt;SYMPTOM 2.  I have made this little program ???LittleProg.c??? which allocates, deallocates and displays a shared memory segment.  After I delete the executable ???LittleProg???, the object file ???LittleProg.o??? and compile the program it works fine.  Then I run ???ls ???l??? and after that, the little program gives me ???Illegal instruction??? message.  ???LittleProg??? will not work again until I repeat the deleting of the two files and re-compilation of the program.&lt;BR /&gt;&lt;BR /&gt;In hope that reboot will help, I reeboot but then the following problems occur in the same order as they appear here.&lt;BR /&gt;&lt;BR /&gt;1. Mounting Proc filesystems failed&lt;BR /&gt;2. Cannot open font file latarcyrheb-sun16&lt;BR /&gt;3. Mount USB filesystem failed&lt;BR /&gt;4. Could???nt open /proc/partitions: no such file or directory.  Is /Proc mounted?&lt;BR /&gt;5. Press &lt;CTRL d=""&gt; to start normally:  -&amp;gt;  ( I press &lt;CTRL-D&gt; ) -&amp;gt;&lt;BR /&gt;Unmounting filesystems&lt;BR /&gt;/etc/rc.d/rc.sysinit: line 269:  135 segmentation fault      mount ???n ???o remount, ro /&lt;BR /&gt; -&amp;gt; ( the computer reboots itself with the same error messages. )&lt;BR /&gt;&lt;BR /&gt;Before  I rebooted I checked if  ???/proc??? and its whole contents existed and it did.  I checked because this has happened 2 times before.&lt;BR /&gt;&lt;BR /&gt;At this point, I must install another hard disk drive in the computer, install a fresh OS(Red Hat 8.0) on it, mount the crashed disk to it and copy the data to the new one.  &lt;BR /&gt;&lt;BR /&gt;This process is very tireing.  So if anyone has a theory or a suggestion for me it would be highly appreciated.&lt;BR /&gt;&lt;BR /&gt;Keywords for what is being developed on the computer are: static library, dynamic library, JNI, RMI, shared memory and semaphores.&lt;BR /&gt;&lt;BR /&gt;With best regards, Siggi.&lt;/CTRL-D&gt;&lt;/CTRL&gt;</description>
      <pubDate>Tue, 17 Jun 2003 16:16:48 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/rm-file-txt-gt-segmentation-fault-gt-major-crash/m-p/2999804#M5195</guid>
      <dc:creator>sigurður Einarsson</dc:creator>
      <dc:date>2003-06-17T16:16:48Z</dc:date>
    </item>
    <item>
      <title>Re: RM FILE.TXT -&gt; segmentation fault -&gt; Major Crash</title>
      <link>https://community.hpe.com/t5/operating-system-linux/rm-file-txt-gt-segmentation-fault-gt-major-crash/m-p/2999805#M5196</link>
      <description>1. check the hardware. especially memory, coolers and hard disk (including hard disk temperature)&lt;BR /&gt;2. verify your hard disk. I mean, smartctl and all related stuff&lt;BR /&gt;3. verify that the machine has not been tampered (like in rootkit)&lt;BR /&gt;4. verify that the kernel image + modules (and other packages) you are using are all OK and updated to latest errata.&lt;BR /&gt;5. skip RH 8 if you can. either stick to 7.3 or switch to 9.</description>
      <pubDate>Wed, 18 Jun 2003 07:16:01 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/rm-file-txt-gt-segmentation-fault-gt-major-crash/m-p/2999805#M5196</guid>
      <dc:creator>Manuel Wolfshant</dc:creator>
      <dc:date>2003-06-18T07:16:01Z</dc:date>
    </item>
    <item>
      <title>Re: RM FILE.TXT -&gt; segmentation fault -&gt; Major Crash</title>
      <link>https://community.hpe.com/t5/operating-system-linux/rm-file-txt-gt-segmentation-fault-gt-major-crash/m-p/2999806#M5197</link>
      <description>That you can install another O/S and reboot at this point, confirms an O/S problem and not HW.&lt;BR /&gt;&lt;BR /&gt;Somewhere you are writting to the O/S disk and corrupting it.  But disk and physical memory are not physcially linked and segmentation fault is an indication of an illegal access to a segment of memory not mapped for your access, probably system memory.&lt;BR /&gt;&lt;BR /&gt;So the two should be unrelated.&lt;BR /&gt;&lt;BR /&gt;If you're not able to reboot because /proc is unmountable then ramdisk or /dev or the kernel have become corrupt.  &lt;BR /&gt;If you're able to reload the old kernel then this would confirm corruption of the kernel.&lt;BR /&gt;&lt;BR /&gt;It confuses me that you have to use a new disk.  You can't fdisk and reformat?</description>
      <pubDate>Wed, 18 Jun 2003 13:00:31 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/rm-file-txt-gt-segmentation-fault-gt-major-crash/m-p/2999806#M5197</guid>
      <dc:creator>Michael Steele_2</dc:creator>
      <dc:date>2003-06-18T13:00:31Z</dc:date>
    </item>
    <item>
      <title>Re: RM FILE.TXT -&gt; segmentation fault -&gt; Major Crash</title>
      <link>https://community.hpe.com/t5/operating-system-linux/rm-file-txt-gt-segmentation-fault-gt-major-crash/m-p/2999807#M5198</link>
      <description>Check for BIOS with the motherboard manufacturer.  Its the bios that maps out the disk geometry, but I can't see a relation to your problem unless an upgrade is needed.  Your motherboard has been stable all along, right?</description>
      <pubDate>Wed, 18 Jun 2003 13:02:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/rm-file-txt-gt-segmentation-fault-gt-major-crash/m-p/2999807#M5198</guid>
      <dc:creator>Michael Steele_2</dc:creator>
      <dc:date>2003-06-18T13:02:19Z</dc:date>
    </item>
    <item>
      <title>Re: RM FILE.TXT -&gt; segmentation fault -&gt; Major Crash</title>
      <link>https://community.hpe.com/t5/operating-system-linux/rm-file-txt-gt-segmentation-fault-gt-major-crash/m-p/2999808#M5199</link>
      <description>The crashed HD is not crashed in the sense that nothing can be retrieved from it.  I can mount it to another HD and copy my data, and that is what I do.  &lt;BR /&gt;Afterwards I can reformat the crashed disk and do whatever.&lt;BR /&gt;&lt;BR /&gt;Brg, Siggi</description>
      <pubDate>Wed, 18 Jun 2003 19:10:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/rm-file-txt-gt-segmentation-fault-gt-major-crash/m-p/2999808#M5199</guid>
      <dc:creator>sigurður Einarsson</dc:creator>
      <dc:date>2003-06-18T19:10:39Z</dc:date>
    </item>
    <item>
      <title>Re: RM FILE.TXT -&gt; segmentation fault -&gt; Major Crash</title>
      <link>https://community.hpe.com/t5/operating-system-linux/rm-file-txt-gt-segmentation-fault-gt-major-crash/m-p/2999809#M5200</link>
      <description>The crashed HD is not crashed in the sense that nothing can be retrieved from it.  I can mount it to another HD and copy my data, and that is what I do.  &lt;BR /&gt;Afterwards I can reformat the crashed disk and do whatever.&lt;BR /&gt;&lt;BR /&gt;Brg, Siggi</description>
      <pubDate>Wed, 18 Jun 2003 19:10:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/rm-file-txt-gt-segmentation-fault-gt-major-crash/m-p/2999809#M5200</guid>
      <dc:creator>sigurður Einarsson</dc:creator>
      <dc:date>2003-06-18T19:10:52Z</dc:date>
    </item>
  </channel>
</rss>

