What is the process of discovering and solving bad disk tracks in Linux server
Linux server disk bad discovery and resolution process is how, many novices are not very clear about this, in order to help you solve this problem, the following editor will explain in detail for you, people with this need can come to learn, I hope you can gain something.
The disk of the server is not monitored, in fact, I do not know how to monitor the status of the disk, suddenly can not see the new data, went up to take a look at the disk, found that the disk is read-only, unable to write data.
I. processing process
1. Check the bad track of disk
After the problem, first stop the business, and then uninstall the disk to repair, this problem may be that the track of the disk has a bad area, I first checked the bad track of the disk.
Badblocks-sv / dev/sdb
After almost checking for some time, it was found that there was no bad way.
2. Repair the disk file system
When repairing the file system, it is found that it cannot be repaired, prompting Superblock invalid.
[root@ad4] # fsck-t ext4 / dev/sdb
Fsck from util-linux-ng 2.17.2
E2fsck 1.41.12 (17-May-2010)
Fsck.ext4: Superblock invalid, trying backup blocks...
Fsck.ext4: Bad magic number in super-block while trying to open / dev/sdb
The superblock could not be read or does not describe a correct ext2
Filesystem. If the device is valid and it really contains an ext2
Filesystem (and not swap or ufs or something else), then the superblock
Is corrupt, and you might try running e2fsck with an alternate superblock:
E2fsck-b 8193
3. View file system backup Superblock
[root@ad4] # mke2fs-n / dev/sdb
Mke2fs 1.41.12 (17-May-2010)
/ dev/sdb is entire device, not just one partition!
Proceed anyway? (YBM n) y
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=1 blocks, Stripe width=0 blocks
122093568 inodes, 488364854 blocks
24418242 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=4294967296
14904 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208
4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968
102400000, 214990848
4. Repair the file system
E2fsck-b 214990848-y / dev/sdb
There was a lot of repair, and it took a while to fix it.
After the repair is completed, install it into the directory and view it as follows
Is it helpful for you to read the above content? If you want to know more about the relevant knowledge or read more related articles, please follow the industry information channel, thank you for your support.
