Looking for drive testing tools for Proxmox storage drives.
- Thread starter Drax
- Start date
Got three system emails this morning. what do they mean? Please advise.
1.)
/etc/cron.daily/logrotate:
error: error creating output file /var/log/syslog.1.gz: File exists
run-parts: /etc/cron.daily/logrotate exited with return code 1
2.)
A DegradedArray event had been detected on md device /dev/md/0.
Faithfully yours, etc.
P.S. The /proc/mdstat file currently contains the following:
Personalities : [raid10]
md0 : active raid10 sda1[0] sdd1[3] sdg1[4](F) sdb1[1]
3906763776 blocks super 1.2 512K chunks 2 near-copies [4/3] [UU_U]
unused devices: <none>
3.)
A SparesMissing event had been detected on md device /dev/md/0.
Faithfully yours, etc.
P.S. The /proc/mdstat file currently contains the following:
Personalities : [raid10]
md0 : active raid10 sda1[0] sdd1[3] sdg1[4](F) sdb1[1]
3906763776 blocks super 1.2 512K chunks 2 near-copies [4/3] [UU_U]
unused devices: <none>
1.)
/etc/cron.daily/logrotate:
error: error creating output file /var/log/syslog.1.gz: File exists
run-parts: /etc/cron.daily/logrotate exited with return code 1
2.)
A DegradedArray event had been detected on md device /dev/md/0.
Faithfully yours, etc.
P.S. The /proc/mdstat file currently contains the following:
Personalities : [raid10]
md0 : active raid10 sda1[0] sdd1[3] sdg1[4](F) sdb1[1]
3906763776 blocks super 1.2 512K chunks 2 near-copies [4/3] [UU_U]
unused devices: <none>
3.)
A SparesMissing event had been detected on md device /dev/md/0.
Faithfully yours, etc.
P.S. The /proc/mdstat file currently contains the following:
Personalities : [raid10]
md0 : active raid10 sda1[0] sdd1[3] sdg1[4](F) sdb1[1]
3906763776 blocks super 1.2 512K chunks 2 near-copies [4/3] [UU_U]
unused devices: <none>
2 & 3: you have lost a disk. As you are using RAID10, replace it ASAP, now if sdb1 should fails, your whole array is gone
well you don't unless you keep the records of disk ID when you install them.
this 2 lines show you the disk
the first one list the disks and their numbers (sda1[0] sdd1[3] sdg1[4](F) sdb1[1])
the second show you the missing disk at the end ([UU_U]) see the underscore, that is your missing disk as in third disk in the list in the first line that is sdg (FYI it refers to actual count not the disk id or disk number shown, but the actual count location in the list.)
now you can run "blkid" or " ls -la /dev/disk/by-id " or "lsblk -f" or all of the above, to get a list of information.
copy and print the outputs for references.
shutdown the node and read the disks.
this would also be a good time to note the ids and location, somewhere and maybe even add a label listing id to the disk on the visible part of it so you can just pop the case and read the id when needed.
this 2 lines show you the disk
the first one list the disks and their numbers (sda1[0] sdd1[3] sdg1[4](F) sdb1[1])
the second show you the missing disk at the end ([UU_U]) see the underscore, that is your missing disk as in third disk in the list in the first line that is sdg (FYI it refers to actual count not the disk id or disk number shown, but the actual count location in the list.)
now you can run "blkid" or " ls -la /dev/disk/by-id " or "lsblk -f" or all of the above, to get a list of information.
copy and print the outputs for references.
shutdown the node and read the disks.
this would also be a good time to note the ids and location, somewhere and maybe even add a label listing id to the disk on the visible part of it so you can just pop the case and read the id when needed.