XPost: aus.computers
From: not@telling.you.invalid
In aus.computers Axel wrote:
> Axel wrote:
>> Computer Nerd Kev wrote:
>>> In aus.computers Axel wrote:
>>>> Computer Nerd Kev wrote:
>>>>> In aus.computers Axel wrote:
>>>>>> So the sad tale thus far. But first, some detail. This PC (specs
>>>>>> below)
>>>>>> has LM 22.2 installed on a 1Tb NVME. It also has two mobile racks for
>>>>>> easy insertion and removal of HD's. The lower rack I use for the
>>>>>> Timeshift disk, and the upper one for the files disk, a WD 1Tb
>>>>>> mechanical disk formatted in Ext4. It also has two external USB cases
>>>>>> for additional hard drives. Following a process of trial and
>>>>>> error, I've
>>>>>> discovered that the problem of file errors only occurs when I
>>>>>> write to
>>>>>> the files disk in the mobile rack. I can read/write both ways NVME to
>>>>>> USB without errors, and read/write both ways USB to USB without
>>>>>> errors.
>>>>> Does any of that mean you tried the most obvious thing of
>>>>> connecting the "files disk" without using the rack, in case the
>>>>> drive is faulty?
>>>> not specifically, but the drive is new, and the problem was present
>>>> with
>>>> any drive in that bay
>>> C'mon you just said: "today I tried an old 320 Gb NTFS HD in the
>>> rack, and I could write to it without limitation". Which of you do
>>> I believe?
>>>
>>>>>> I can also read from the files disk to write to either USB without
>>>>>> errors. So my trouble shooting has been focused on the mobile
>>>>>> rack. I
>>>>>> replaced it, and also the cable, and swapped the cable to another
>>>>>> motherboard (MB) SATA port. Since USB transfers work, and the USB
>>>>>> boxes
>>>>>> have their own power supply, I thought maybe it was a power issue
>>>>>> within
>>>>>> the PC. According to the newegg calculator
>>>>>> [https://promotions.newegg.com/tools/power-supply-calculator/v2/ ] I
>>>>>> need 600 -700 watts for this PC. The PS was only 550 watts so I
>>>>>> swapped
>>>>>> it out with a 750 watt PS. Having said all this, I can write to the
>>>>>> Files disk if I transfer folders/files in small lots of up to about
>>>>>> 10Gb, and today I tried an old 320 Gb NTFS HD in the rack, and I
>>>>>> could
>>>>>> write to it without limitation. ???
>>>>> Sounds like you've just narrowed the issue down to the "files disk"
>>>>> itself.
>>>>>
>>>> no, unfortunately
>>> Unfortunately your story changes all the time...
>>>
>>
>> no it doesn't. read the whole thread if you want the full story
>>
>
> or in a nutshell.. the question now is why did it write to that drive
> and not others? is the size of the drive or it's software/technology
> relevant?
Maybe that drive (or the NTFS driver) is just too slow for whatever
signal issue you have with the rack to be triggered.
I'm not sure if they still do it on new HDDs, but maybe there's a
jumper setting on the other drives to limit the speed?
https://en.wikipedia.org/wiki/SATA#SATA_1.5_Gbit/s_and_SATA_3_Gbit/s
--
__ __
#_ < |\| |< _#
--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)
|
