Could it just be the LPX network protocol? I have reinstalled the software and still not able to bring the drives back up. Then the system crash. Also, I think the request queue is indicated by the output dpcd1 near the very end of the line. It contains hybrid storage and has an ultra low voltage processor for increased battery life. Did the startech ethernet cable adapter solve the problem? In the function you can see that the slot can be determined by the queue.
|Date Added:||19 July 2011|
|File Size:||26.76 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
On a side note, however, we might have chosen a 6 Gbps SSD rather than the XM13 3Gbps drive and we also would have switched data connections. I’m connected to the same switch as the NDAS. I want to discover why this driver is loading the same queue on two different block storages, and determine if that is causing the duplicate blkid during the initial registration process.
We were so impressed, in fact, that we posted our initial impression on Twitter. You can follow the question or vote as helpful, but you cannot reply to this thread.
Suspicious Activity Detected
Sterne12 Replied on August 23, I hope this is enough background information. I updated then the 4th machine having all the usualproblems but this time I didn’t succeeded in solving.
I share the solution to the bug that led me to post this question. Reinstalled the latest software and still get periodic window crash reports stating that the system suffered an unknown error with lpx.
They were running well on XP. Frequent readers of TSSDR understand my opinion of both, an opinion that was initially hard to contain with their teaming up in what appears to be an attractive ultra design. As far as I know, this is the standard operation.
ShieldSquare reCAPTCHA Page
Now, as Windows 10 updated, computer crash at boot again and the only way to solve the situation is to do a restauration point before installation of the NDAS driver, as I’m not an expert of debugging Windows to deactivate the driver at boot. But when I go ahead and mount hdb1 it also comes up with the same blkid and in fact, the driver is reading it from hda, not hdb.
Hi, has anybody a solution for this problem? The result is, if I have 1 partition on hda and 1 partitions on hdb, as soon as I connect hda there is a partition that can be mounted. It is also 0.
Thanks for looking at this situation for me. Tell us about your experience with tendisk site. So you will see slot 2 in this log because the first device has already been connected and mounted. The driver is now about to begin scanning the hard drive for existing partitions.
In reply to Sterne12’s post on August 23, An un-educated guess might be:. Then came Windows 7 and I got problems with crashing at boot during many months with the 3. Ndass recommend this discussion You can help protect yourself from scammers by verifying that the contact is a Microsoft Agent or Microsoft Employee and that the phone number is an official Microsoft global customer service number.
An un-educated guess might be: The first network drive that was already mounted. Could it be done?
In reply to Sterne12’s post on August 25, In reply to ABarnettceo’s post on September 22, Here is a log output. In the log output that follows, the second device, hdb has just dnas connected, right after hda was connected and hda1 was mounted to the system.
ABarnettceo Replied on September 22, PeterThys Replied on September 5,