LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (http://www.linuxquestions.org/questions/slackware-14/)
-   -   A wild file error appeared! (http://www.linuxquestions.org/questions/slackware-14/a-wild-file-error-appeared-4175444555/)

NintendoFanboy 01-07-2013 04:05 PM

A wild file error appeared!
 
When I was shutting down once a text box came up saying "Failed error". After that it proceeded to log me off and shut down (me believing it had ironed out any issues). Once I tried to turn back on my computer, the black background text loading thingy came up and... BAM, it was loading my Slackware 14. But, towards the end, (right after loading my LCD screen), it said, "[insert my partition here] has a file error". It then says that I can press Ctrl-D to resume normal boot. Once I press Ctrl-D it reboots and the precess starts over again. The same thing happens.

marbangens 01-07-2013 04:26 PM

is it a mac? what boot loader is installed?

NintendoFanboy 01-07-2013 04:29 PM

HP Pavilion Dv6. Not sure what boot loader.

Iberwil 01-07-2013 06:35 PM

If it does get to towards the end it's probably not the bootloader which we assume is lilo as he doesn't know so it should be the default one.

But you don't go as far as login right?

There are plenty of live cd system recovery distributions that have some hard drive diagnostic tools. Perhaps you could try running one of them if you've some experience?

It might very well be a system file error. What does it attempt to load that fails and returns the error?

marbangens 01-08-2013 07:21 AM

I can be the kernel fallback mode or a stop in the initrd from booting root partition.
how is your boot set up? is it the generic kernel with initrd?

Martinus2u 01-08-2013 02:09 PM

Quote:

Originally Posted by Iberwil (Post 4864999)
There are plenty of live cd system recovery distributions that have some hard drive diagnostic tools. Perhaps you could try running one of them if you've some experience?

OP, you can use the Slackware installation disk for that. boot from it and issue
Code:

fsck -N -V your_partition
The -N flag prevents any changes being written to disk. If you feel lucky you can then execute fsck without the -N flag. You might end up with cryptic filenames in lost+found. In that case, if you can't restore them to their original path and filename, you might be hosed.

edit: roar of time would be the appropriate attack - going back to a suitable save point :p


All times are GMT -5. The time now is 02:58 PM.