vBulletin Search Engine Optimization
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| In article <vfo9vffip8oc87@corp.supernews.com>, pablo wrote: > Dear Newsgroupers, > > On our school we have a mandrake 8.2 server running. Since yesterday we have > serious troubles. > We can only get into the system via failsafe. > > It seems the filesystem is corrupted and in dmesg we find the advise to do > e2fsck. > When we try that we get the message > "Bad magic number in super-block while trying to open. Could not find valid > filesystem superblock." > > How can you retrieve the superblock information. this is just general comment, from past experience. fsck s/b able to find an alternate superblock w/o user intervention but it may be configured differently w/Mandrake. but if it cannot, you are toast, unless you have some 3rd party data recovery package. find a system that gets you a man page for fsck/e2fsck, even just a wintel box to use google, and figure out how to manually give fsck an alternate superblock. of course this assumes you know or can find out the offsets (there are several alt.sb's). i cannot help you w/that. good luck, --LOren > > And could a raid-controller faillure (Adaptec raid-controllers) be the cause > of that? > If so, how can you find the configuration of the raid devices? > > TIA, > > pablo k > > > |
| Thread Tools | |
| Display Modes | |
|
|