Topic: [Solved] Crash server after "Enabling local filesystem quotas:"

[guitsou]

Hi everyone,

Yesterday my server was frozen. No more access. So I launch an hard reboot.

During the restart my server stop after "Enabling local filesystem quotas:". I let it try to start during the whole night but it failed.

So this morning I decided to plug my harddrive on another smeserver plugged with an USB adapter. My goal is to try to fix the drive or to save some files and rebuild a new server.

"fdisk -l" show me :

Disk /dev/sda: 122.9 GB, 122942324736 bytes
255 heads, 63 sectors/track, 14946 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *           1          13      104391   fd  Linux raid autodetect
/dev/sda2              14       14946   119949322+  fd  Linux raid autodetect

"# mount /dev/sda1 /media/usbdrive/" work fine. It's seems to be my /boot.

"# mount /dev/sda2 /media/usbdrive/" give "mount: you must specify the filesystem type"

# dmesg | tailEXT3 FS on sda1, internal journalEXT3-fs: recovery complete.EXT3-fs: mounted filesystem with ordered data mode.FAT: bogus number of reserved sectorsVFS: Can't find a valid FAT filesystem on dev sda2.kjournald starting.  Commit interval 5 secondsEXT3 FS on sda1, internal journalEXT3-fs: mounted filesystem with ordered data mode.FAT: bogus number of reserved sectorsVFS: Can't find a valid FAT filesystem on dev sda2.


I tried also:
# fsck /dev/sda2fsck 1.35 (28-Feb-2004)e2fsck 1.35 (28-Feb-2004)Couldn't find ext2 superblock, trying backup blocks...fsck.ext2: Bad magic number in super-block while trying to open /dev/sda2The superblock could not be read or does not describe a correct ext2filesystem.  If the device is valid and it really contains an ext2filesystem (and not swap or ufs or something else), then the superblockis corrupt, and you might try running e2fsck with an alternate superblock:    e2fsck -b 8193 <device>

I don't want to lose my drive. I need help !
Any ideas please?

(sorry for my english skills)

[mmccarn]

The install CD includes a 'rescue' mode that may help: http://wiki.contribs.org/Booting#Installer_Boot_Options

I also found this page on the wiki: http://wiki.contribs.org/Recovering_SME_Server_with_lvm_drives

[guitsou]

Thanks ! The rescue mode seems to be usefull.
The second links is about raid management but my installation is on a single drive.

The actual issue is that with the harddrive plugged in USB on another smeserver station I'm unable to fix/access my drive.
I'm gonna backup my drive using dd. I've try to find the good superblock but unsuccessfully.

Should I better plug my harddrive on an Ubuntu workstation to fix it ? Do we have more tools on another distrib to fix drives ?

[mmccarn]

Even though you only have one hdd installed, SME accesses it as a RAID  array, hence the notes about raid management.

[CharlieBrady]

I've try to find the good superblock but unsuccessfully.

Perhaps because you were looking in the wrong place. By default, you will need RAID1 and LVM layers active before you can look for a file system.

[guitsou]

You're right ! I have to see that point... 

Thank you !

[CharlieBrady]

I don't want to lose my drive. I need help !

It doesn't help you just now, but we do very strongly recommend that you have two hard drives, and SME server will use RAID1 mirroring automatically.

[guitsou]

Solved! I succeded to access my datas on the drive.

I had to boot with Rescue CD, and active LVM and RAID to access as said by mmccarn (the second link helps me to finish the job!). So thank you mmccarn!

CharlieBrady: issue was surely from the quotas during startup. In my case two disks don't save me! But you're right: both better than one in most cases.

That was my first post on this forum. Thank you guys you're very efficiants!

Best regards
Guitsou

[Stefano]

CharlieBrady: issue was surely from the quotas during startup.

there's no evidence of it.. it could be an hw problem..