ServerBuddies Support Blog

Badblocks - search a device for bad blocks

Important note: If the output of badblocks is going to be fed to the e2fsck or mke2fs programs, it is important that the block size is properly specified, since the block numbers which are generated are very dependent on the block size in use by the filesystem. For this reason, it is strongly recommended that users not run badblocks directly, but rather use the -c option of the e2fsck and mke2fs programs.

This would check the drive “sdb” in non-destructive read-write mode and display progress by writing out the block numbers as they are checked.

This would check the sixth partition of the drive “sdb”, in destructive read-write mode and display progress by writing out the block numbers as they are checked. All data will be overwritten at the block level. If used on an entire disk as in the previous example, it destroys MBRs, partitions and data alike.

HTTP Error 502 Bad Gateway, 503 Service Unavailable

This error is usually due to improperly configured proxy servers. However, the problem may also arise when there is poor IP communication amongst back-end computers, when the client’s ISP is overloaded, or when a firewall is functioning improperly.

The first step in resolving the issue is to clear the client’s cache. This action should result in the a different proxy being used to resolve the web server’s content.

503 Service Unavailable

This error occurs when the server is unable to handle requests due to a temporary overload or due to the server being temporarily closed for maintenance. The error signifies that the server will only temporarily be down. It is possible to receive other errors in place of 503.