LinuxQuestions.org - [SOLVED] Cooperative Linux/Arch disk check

- Linux - Newbie (https://www.linuxquestions.org/questions/linux-newbie-8/)

- - Cooperative Linux/Arch disk check (https://www.linuxquestions.org/questions/linux-newbie-8/cooperative-linux-arch-disk-check-774816/)

Cooperative Linux/Arch disk check

I just installed Cooperative Linux (WIN32 port of the linux kernel) with an arch linux image.
Heres the anoyance :
I get

Code:

:: Checking Filesystems                              [BUSY]

/dev/hda1:

The superblock could not be read or does not describe a corr

ect ext2

filesystem.  If the device is valid and it really contains a

n ext2

filesystem (and not swap or ufs or something else), then the

 superblock

is corrupt, and you might try running e2fsck with an alterna

te superblock:

    e2fsck -b 8193 <device>



                                                    [FAIL]



*****************  FILESYSTEM CHECK FAILED  ****************

*                                                          *

*  Please repair manually and reboot. Note that the root  *

*  file system is currently mounted read-only. To remount  *

*  it read-write type: mount -n -o remount,rw /            *

*  When you exit the maintenance shell the system will    *

*  reboot automatically.                                  *

*                                                          *

************************************************************

every bootup and i want it to stop[/code]

Just a few suggestions:

(1) Try running the debian image to see if the problem is isolated to the arch linux image.
(2) Download the arch image and uncompress it again (you did uncompress it, right?) to rule out file corruption.

Hope that helps

Quote:

Originally Posted by mostlyharmless (Post 3788088)

Just a few suggestions:

(1) Try running the debian image to see if the problem is isolated to the arch linux image.

Time to play clear out some disk space LOL.

Quote:

(2) Download the arch image and uncompress it again (you did uncompress it, right?) to rule out file corruption.

Hope that helps

I already did it the first time because the file was corrupted.

Fixed it! I just hat colinux configured wrong.