Yes I already tried that, see earlier post with the diagram of the motherboard
Try Installing into an external powered USB 3.0 container perhaps? Requires a purchase of powered caddy.
1 Like
Already tried a USB enclosure to check that the drive was working (see original post).
I did fit this firewire card a year agoā¦
https://www.startech.com/en-gb/cards-adapters/pex1394b3
It might have been shortly after that when I started having issues with the 4TB drive which eventually failed 6 months ago.
I dont need the firewire card anymore so removed it and so far the 6TB drive is behaving.
It could just be a coincidence, because I expect the firewire card would draw very little power so I would be suprised if this was the cause.
I have contacted the supplier who has agreed to exchange the 6TB drive, but as its currenlty working Im not sure what to do.
As for trying another PSU, I dont have access to any other PSU so would have to buy one.
But it seems that Dell dont use a standard size PSU so there is very little choice.
If someone could recommend a suitable PSU then I would consider upgrading it from the existing 290W PSU.
It depends on the case, you could mount a ānormalā psu if there is enough room in the case and there is an adapter from 8-pin power to 24-pin power cable. https://www.ebay.com/itm/127029613844 I dont know where you can find it in France.
1 Like
That being the case, then you have identified an incompatibility regarding ābus presenceā or āsignal recognition conflictā ā¦
or ā¦
however small it might be, the power draw by the firewire pushed the voltage levels below the minimum threshold at which the deviceās internal logic triggered shut down, out of self-preservation to protect the circuitry.
It is possible that the device was less tolerant than the other drives (variations within manufacturing tolerances), which is why only that drive was impacted.
Switching out the drive could give you a drive that was either more, or less, tolerant than the one you currently have, so itās all a matter of living with āthe devil that you knowā type of situation.
Just glad to hear that you seem to be past the hump.
Form Factor: Mini Tower (MT)
That would imply a standard āprofileā for PSU.
So ā¦ if you can identify the Make & Model of the existing PSU which is in your chassis, you can do a lookup for an āupscaledā replacement.
Looking at online info, you have the following reference:
Apparently, there is a Dell 360W PSU that would supposedly be a direct swap-out, but maybe check with those 3rd-party suppliers or with Dell directly.
Just be sure that they confirm at least the same number of connectors for the various PSU output cables.
2 Likes
Apparently the Dell T30 uses a AC290EM-01 290W PSU
Dell ONFX6T proprietary 290W PSU (175 mm x 36 mm x 454 mm) with an 4-pin and 8-pin ATX power connectors.
Youāre getting NCQ errors. Do the following to solve the problemā¦
Native Command Queuing (NCQ) is an extension of the Serial ATA protocol allowing hard disk drives to internally optimize the order in which received read and write commands are executed.
Edit `sudo -H gedit /etc/default/grub` and change the following line to include this extra parameter. Then do `sudo update-grub` to write the changes to disk. Reboot. Monitor hangs/etc., and watch `grep -i FPDMA /var/log/syslog*` or `dmesg` for continued error messages.
GRUB_CMDLINE_LINUX_DEFAULT=āquiet splash libata.force=noncqā
Note: https://bugzilla.kernel.org/show_bug.cgi?id=201693
Alternate: libata.force=noncqtrim
Al, I donāt know enough about it, but could something like a Kernel āquirkā parameter in GRUB address the issue youāve identified? I use a quirk myself to deal with proper USB interraction between my USB3 external backup drive and my computerās USB2 ports.
[EDIT: stripping the below down to only the quirk-related components to avoid confusion]
Below is the example of my using a quirk for my own instance, but it is NOT meant to solve the OPās issue,
GRUB_CMDLINE_LINUX_DEFAULT="scsi_mod.use_blk_mq=1 usb-storage.quirks=1058:25ee:u usbcore.autosuspend=-1"
Yes. The NCQ error can be squashed via GRUB.
Your GRUB parameters look wrong to me. resume_offset=0 probably shouldnāt be 0. modeset=0 disables your video. The usb-storage.quirks should only be used if you have trouble seeing/mounting a diskā¦ and you can do that in a file in /etc/modprobe.d like soā¦
drop this into /etc/modprobe.d/disable_uas.conf
should look like this:
-rw-rār-- 1 root root 505 Apr 30 11:36 disable-uas.conf
sources:
https://unix.stackexchange.com/questions/525290/usb-hdd-not-found
https://unix.stackexchange.com/questions/239782/connection-problem-with-usb3-e
xternal-storage-on-linux-uas-driver-problem
examples for single/multiple disks:
options usb-storage quirks=059f:105e:u
options usb-storage quirks=059f:105f:u,059f:105e:u,174c:1351:u
commands to complete this install:
sudo update-initramfs -u
reboot
Toshiba America Inc External USB 3.0
#options usb-storage quirks=0480:a00c:u
Crucial external USB 3.0 2TB SSD
#options usb-storage quirks=0634:5602:u
1 Like
Thank you, Al. I was only giving an example of the use of a quirk. I will go back and make a comment that the example was NOT meant to solve the OPās issue, only to raise another avenue of investigation for a solution.
Remember to fix your GRUB line errors.
1 Like
This topic was automatically closed after 30 days. New replies are no longer allowed.