I saw these errors after a fresh install of CentOS 5.2 during the process of preparing the server for ISPConfig. If you try to enable quotas after getting this error then quotaon will simply explain it cannot find the files like the below.
quotacheck Error: Probably Truncated
- [root@server /]# quotacheck -m /
- quotacheck: WARNING - Quotafile //aquota.user was probably truncated. Can't save quota settings...
- quotacheck: Something weird happened while scanning. Error 2133571361
quotacheck Error: Cannot Find Quota File On…
- [root@server /]# quotaon -avug
- quotaon: Cannot find quota file on / [/dev/hda3] to turn quotas on/off.
- quotaon: Cannot find quota file on / [/dev/hda3] to turn quotas on/off.
What has happened is even though the aquota.group and aquota.user files do exist the quotacheck command was not able to build the necessary table of disk usage into them because of your disk issues.
When you get these quotacheck errors when trying to enable quotas then check in /var/log/messages. Chances are you will see disk errors similar the below.
Messages Log File Snipit:
- Oct 4 06:56:37 server smartd[2057]: Device: /dev/hda, 1 Currently unreadable (pending) sectors
- Oct 4 06:56:37 server smartd[2057]: Device: /dev/hda, 1 Offline uncorrectable sectors
- Oct 4 07:05:14 server kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
- Oct 4 07:05:14 server kernel: hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=152926625, high=9, low=1931681, sector=152926491
- Oct 4 07:05:14 server kernel: ide: failed opcode was: unknown
- Oct 4 07:05:14 server kernel: end_request: I/O error, dev hda, sector 152926491
- Oct 4 07:05:14 server kernel: Buffer I/O error on device hda3, logical block 18579642
- Oct 4 07:05:18 server kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
- Oct 4 07:05:18 server kernel: hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=152926625, high=9, low=1931681, sector=152926499
- Oct 4 07:05:18 server kernel: ide: failed opcode was: unknown
In this case the disk was going bad and had to be replaced. So if this happens to you make sure to immediately back everything up and then investigate the errors further by running a bad blocks test on the server.
Update NOTE: Check comments below as some users have suggested other resolutions to this issue.
I solved it
Delete the file aquota.user & aquota.group
run quotacheck -c /home/
then will be ok
Hello Hilmy,
Good deal. Thanks for leaving this suggestion. In the case of the article the disk really was going bad and once replaced it worked without issue though from the details in your post it looks like there could be various different issues when running into this specific error.
Thanks again!
Thanks.
alex
get hold of the most current voucher codes from the protein works
protein works coupon codes