SOLVED: ix2-dl soho software won't mount disks












0















TL;DR the web gui and event viewer as well as soho.log don't actually print when mounting disks. It mounted itself eventually after a few days of uptime. No log message, no warnings or errors. No idea why a powerloss caused it so much grief.





Mounting the logical volume in a temp folder showed that all of the data appears intact... so I'm not freaking out. Yet.



This product is EOL so I'm not expecting useful support from whomever owns this iomega stuff now. Don't really know who to ask... Lenovo? EMC?



One of the hard drives is making noise, but the web GUI is less than helpful - it doesn't show the usual bad disk or whatever.



hdparm -tT /dev/sda (and sdb) read the disk with no issues
smartctl -a claims the disk doesn't support SMART SCSI commands, even though hdparm tells me it does. might be a botched smartctl build in their firmware.



mdraid seems happy:



cat /proc/mdstat
Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4]
md1 : active raid1 sdb2[2] sda2[3]
2909129536 blocks super 1.1 [2/2] [UU]

md0 : active raid1 sda1[3] sdb1[2]
20971448 blocks super 1.0 [2/2] [UU]


however, /var/log/soho.log is in a checking disks loop which repeats every 30 seconds on the dot. this is actually normal, it's doing some sort of periodic consistency check. still no idea when it actually mounted.



2019/01/31 20:02:46.587956: svcd[2166.2900]: TRACE: dm_empty_trash_thread(1221): Checking volume: /dev/md0_vg/vol1
2019/01/31 20:02:46.588508: svcd[2166.2900]: TRACE: dm_empty_trash_thread(1227): Volume root: /mnt/system
2019/01/31 20:02:46.589046: svcd[2166.2900]: TRACE: dm_empty_trash_thread(1221): Checking volume: /dev/md0_vg/BFDlv
2019/01/31 20:02:46.589575: svcd[2166.2900]: TRACE: dm_empty_trash_thread(1221): Checking volume: /dev/4b0110bf_vg/lv20d5ec23









share|improve this question









New contributor




lev.s is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.





















  • and yes, i've tried rebooting the device. it goes back into its' checking disks loop after a reboot. I have not updated the firmware and won't do that until the mounts are up again. ix2-dl FW Version: 4.1.304.34286

    – lev.s
    2 days ago


















0















TL;DR the web gui and event viewer as well as soho.log don't actually print when mounting disks. It mounted itself eventually after a few days of uptime. No log message, no warnings or errors. No idea why a powerloss caused it so much grief.





Mounting the logical volume in a temp folder showed that all of the data appears intact... so I'm not freaking out. Yet.



This product is EOL so I'm not expecting useful support from whomever owns this iomega stuff now. Don't really know who to ask... Lenovo? EMC?



One of the hard drives is making noise, but the web GUI is less than helpful - it doesn't show the usual bad disk or whatever.



hdparm -tT /dev/sda (and sdb) read the disk with no issues
smartctl -a claims the disk doesn't support SMART SCSI commands, even though hdparm tells me it does. might be a botched smartctl build in their firmware.



mdraid seems happy:



cat /proc/mdstat
Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4]
md1 : active raid1 sdb2[2] sda2[3]
2909129536 blocks super 1.1 [2/2] [UU]

md0 : active raid1 sda1[3] sdb1[2]
20971448 blocks super 1.0 [2/2] [UU]


however, /var/log/soho.log is in a checking disks loop which repeats every 30 seconds on the dot. this is actually normal, it's doing some sort of periodic consistency check. still no idea when it actually mounted.



2019/01/31 20:02:46.587956: svcd[2166.2900]: TRACE: dm_empty_trash_thread(1221): Checking volume: /dev/md0_vg/vol1
2019/01/31 20:02:46.588508: svcd[2166.2900]: TRACE: dm_empty_trash_thread(1227): Volume root: /mnt/system
2019/01/31 20:02:46.589046: svcd[2166.2900]: TRACE: dm_empty_trash_thread(1221): Checking volume: /dev/md0_vg/BFDlv
2019/01/31 20:02:46.589575: svcd[2166.2900]: TRACE: dm_empty_trash_thread(1221): Checking volume: /dev/4b0110bf_vg/lv20d5ec23









share|improve this question









New contributor




lev.s is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.





















  • and yes, i've tried rebooting the device. it goes back into its' checking disks loop after a reboot. I have not updated the firmware and won't do that until the mounts are up again. ix2-dl FW Version: 4.1.304.34286

    – lev.s
    2 days ago
















0












0








0








TL;DR the web gui and event viewer as well as soho.log don't actually print when mounting disks. It mounted itself eventually after a few days of uptime. No log message, no warnings or errors. No idea why a powerloss caused it so much grief.





Mounting the logical volume in a temp folder showed that all of the data appears intact... so I'm not freaking out. Yet.



This product is EOL so I'm not expecting useful support from whomever owns this iomega stuff now. Don't really know who to ask... Lenovo? EMC?



One of the hard drives is making noise, but the web GUI is less than helpful - it doesn't show the usual bad disk or whatever.



hdparm -tT /dev/sda (and sdb) read the disk with no issues
smartctl -a claims the disk doesn't support SMART SCSI commands, even though hdparm tells me it does. might be a botched smartctl build in their firmware.



mdraid seems happy:



cat /proc/mdstat
Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4]
md1 : active raid1 sdb2[2] sda2[3]
2909129536 blocks super 1.1 [2/2] [UU]

md0 : active raid1 sda1[3] sdb1[2]
20971448 blocks super 1.0 [2/2] [UU]


however, /var/log/soho.log is in a checking disks loop which repeats every 30 seconds on the dot. this is actually normal, it's doing some sort of periodic consistency check. still no idea when it actually mounted.



2019/01/31 20:02:46.587956: svcd[2166.2900]: TRACE: dm_empty_trash_thread(1221): Checking volume: /dev/md0_vg/vol1
2019/01/31 20:02:46.588508: svcd[2166.2900]: TRACE: dm_empty_trash_thread(1227): Volume root: /mnt/system
2019/01/31 20:02:46.589046: svcd[2166.2900]: TRACE: dm_empty_trash_thread(1221): Checking volume: /dev/md0_vg/BFDlv
2019/01/31 20:02:46.589575: svcd[2166.2900]: TRACE: dm_empty_trash_thread(1221): Checking volume: /dev/4b0110bf_vg/lv20d5ec23









share|improve this question









New contributor




lev.s is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.












TL;DR the web gui and event viewer as well as soho.log don't actually print when mounting disks. It mounted itself eventually after a few days of uptime. No log message, no warnings or errors. No idea why a powerloss caused it so much grief.





Mounting the logical volume in a temp folder showed that all of the data appears intact... so I'm not freaking out. Yet.



This product is EOL so I'm not expecting useful support from whomever owns this iomega stuff now. Don't really know who to ask... Lenovo? EMC?



One of the hard drives is making noise, but the web GUI is less than helpful - it doesn't show the usual bad disk or whatever.



hdparm -tT /dev/sda (and sdb) read the disk with no issues
smartctl -a claims the disk doesn't support SMART SCSI commands, even though hdparm tells me it does. might be a botched smartctl build in their firmware.



mdraid seems happy:



cat /proc/mdstat
Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4]
md1 : active raid1 sdb2[2] sda2[3]
2909129536 blocks super 1.1 [2/2] [UU]

md0 : active raid1 sda1[3] sdb1[2]
20971448 blocks super 1.0 [2/2] [UU]


however, /var/log/soho.log is in a checking disks loop which repeats every 30 seconds on the dot. this is actually normal, it's doing some sort of periodic consistency check. still no idea when it actually mounted.



2019/01/31 20:02:46.587956: svcd[2166.2900]: TRACE: dm_empty_trash_thread(1221): Checking volume: /dev/md0_vg/vol1
2019/01/31 20:02:46.588508: svcd[2166.2900]: TRACE: dm_empty_trash_thread(1227): Volume root: /mnt/system
2019/01/31 20:02:46.589046: svcd[2166.2900]: TRACE: dm_empty_trash_thread(1221): Checking volume: /dev/md0_vg/BFDlv
2019/01/31 20:02:46.589575: svcd[2166.2900]: TRACE: dm_empty_trash_thread(1221): Checking volume: /dev/4b0110bf_vg/lv20d5ec23






debian lvm hard-disk mdadm software-raid






share|improve this question









New contributor




lev.s is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.











share|improve this question









New contributor




lev.s is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









share|improve this question




share|improve this question








edited 3 mins ago







lev.s













New contributor




lev.s is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









asked 2 days ago









lev.slev.s

11




11




New contributor




lev.s is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.





New contributor





lev.s is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.






lev.s is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.













  • and yes, i've tried rebooting the device. it goes back into its' checking disks loop after a reboot. I have not updated the firmware and won't do that until the mounts are up again. ix2-dl FW Version: 4.1.304.34286

    – lev.s
    2 days ago





















  • and yes, i've tried rebooting the device. it goes back into its' checking disks loop after a reboot. I have not updated the firmware and won't do that until the mounts are up again. ix2-dl FW Version: 4.1.304.34286

    – lev.s
    2 days ago



















and yes, i've tried rebooting the device. it goes back into its' checking disks loop after a reboot. I have not updated the firmware and won't do that until the mounts are up again. ix2-dl FW Version: 4.1.304.34286

– lev.s
2 days ago







and yes, i've tried rebooting the device. it goes back into its' checking disks loop after a reboot. I have not updated the firmware and won't do that until the mounts are up again. ix2-dl FW Version: 4.1.304.34286

– lev.s
2 days ago












0






active

oldest

votes











Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});






lev.s is a new contributor. Be nice, and check out our Code of Conduct.










draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f498046%2fsolved-ix2-dl-soho-software-wont-mount-disks%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























0






active

oldest

votes








0






active

oldest

votes









active

oldest

votes






active

oldest

votes








lev.s is a new contributor. Be nice, and check out our Code of Conduct.










draft saved

draft discarded


















lev.s is a new contributor. Be nice, and check out our Code of Conduct.













lev.s is a new contributor. Be nice, and check out our Code of Conduct.












lev.s is a new contributor. Be nice, and check out our Code of Conduct.
















Thanks for contributing an answer to Unix & Linux Stack Exchange!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f498046%2fsolved-ix2-dl-soho-software-wont-mount-disks%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

Loup dans la culture

How to solve the problem of ntp “Unable to contact time server” from KDE?

ASUS Zenbook UX433/UX333 — Configure Touchpad-embedded numpad on Linux