![]() ![]() Smartctl version 5.38 Copyright (C) 2002-8 Bruce Allenĭevice is: In smartctl database Mdadm: cannot open device /dev/sda: Device or resource busy ~]cat /proc/mdstat Mdadm: cannot open device /dev/sdb1: Device or resource busy Mdadm: cannot open device /dev/sdd1: Device or resource busy Mdadm: cannot open device /dev/sde1: Device or resource busy Mdadm: no recogniseable superblock on /dev/block/9:0 Mdadm: no recogniseable superblock on /dev/sdc2 Mdadm: cannot open device /dev/sdb: Device or resource busy Mdadm: cannot open device /dev/sdd: Device or resource busy Mdadm: cannot open device /dev/sde: Device or resource busy Mdadm: looking for devices for further assembly Mdadm: /dev/md/0 has been started with 3 drives (out of 4). Mdadm: no uptodate device for slot 0 of /dev/md/0 Mdadm: /dev/sdb1 is identified as a member of /dev/md/0, slot 1. Mdadm: /dev/sdd1 is identified as a member of /dev/md/0, slot 2. ![]() Mdadm: /dev/sde1 is identified as a member of /dev/md/0, slot 3. Mdadm: cannot open device /dev/sda: Device or resource busy Mdadm: cannot open device /dev/sda1: Device or resource busy ![]() Mdadm: cannot open device /dev/sdc: Device or resource busy Mdadm: cannot open device /dev/sdc1: Device or resource busy Mdadm: cannot open device /dev/sdc5: Device or resource busy Mdadm: cannot open device /dev/root: Device or resource busy Mdadm: cannot open device /dev/block/251:1: Device or resource busy It's no surprise that drives that get too hot or are otherwise stressed beyond normal limits tend to fail early.Code: mdadm: looking for devices for further assembly Smartctl also reports on things like drive temperature, how long the drive has been powered on, how many times it has been started and shut down etc. They point out that maybe a quarter of their drives fail when all these statistics are 0, so a healthy SMART report does not necessarily mean a healthy drive, but almost none of their drives survive having errors on all five counts. SMART 197 | Current Pending Sector Timeout |ī (who run huge raid arrays) have a lot of interesting information on their site. SMART 187 | Reported Uncorrectable Errors | stats that can be looked at which will provide clues: When you read the "When things go wrogn" section, you will see that smartctl is a very important diagnostic tool, but it also provides a lot of proactive information to help you anticipate a drive failure. This tool tells you all sorts of information about your drives. It's not unknown for the daemon to fail.ĭon't rely on this! Check regularly on a manual basis! Sequence as you should - that you will be notified about important events. It won't tell you if anything goes wrong with the monitoring! You cannot assume - even if you put this in your boot-up To the specified address if it detects any problems related to a disk failure. It will daemonize and run in the background, sending an email Mdadm mdadm -monitor -scan -mail will fire up mdadm to keep an eye on your arrays. The author leaves xosview running permanently on his desktop to provide an overview of system performance. It is currently (2016) being updated to read the status directly from /sys, and should hopefully soon be able to display raid status correctly. It is capable of displaying the state of raid arrays, but unfortunately currently the code is broken - it reads mdstat, and doesn't understand the current output. Xosview is a venerable utility, and one of the author's favourites. This will tell you the state of your arrays, and very importantly it will tell you whether any drives have failed, and whether any arrays are degraded. You should get to know /proc/mdstat, looking at it often. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |