Can you tell me, this bin firmware file with what exe program to update the hard disk in win10 OSA little too big for forum attachments, uploaded here permanently.
Can you tell me, this bin firmware file with what exe program to update the hard disk in win10 OSA little too big for forum attachments, uploaded here permanently.
Thank you,Whaaat.
root@schizo:~# sg_write_buffer -vv -m 5 --in=MPGNA3A0.bin /dev/sg3
open /dev/sg3 with flags=0x802
tried to read 8388608 bytes from MPGNA3A0.bin, got 1179648 bytes
will write 1179648 bytes
sending single write buffer, mode=0x5, mpsec=0, id=0, offset=0, len=1179648
Write buffer cdb: 3b 05 00 00 00 00 12 00 00 00
Write buffer parameter list (first 256 bytes):
12 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 ff ff ff ff
48 47 53 54 2c 20 61 20 57 65 73 74 65 72 6e 20
44 69 67 69 74 61 6c 20 43 6f 6d 70 61 6e 79 20
49 43 33 35 4c 78 78 78 55 78 44 33 32 31 30 2d
30 20 4d 69 63 72 6f 63 6f 64 65 20 28 43 29 20
43 6f 70 79 72 69 67 68 74 20 57 65 73 74 65 72
6e 20 44 69 67 69 74 61 6c 20 43 6f 72 70 2e 20
32 30 31 32 2c 20 32 30 31 32 2d 32 30 31 33 2e
20 41 6c 6c 20 72 69 67 68 74 73 20 72 65 73 65
72 76 65 64 2e 20 20 55 53 20 47 6f 76 65 72 6e
6d 65 6e 74 20 55 73 65 72 73 20 52 65 73 74 72
69 63 74 65 64 20 52 69 67 68 74 73 20 2d 20 55
73 65 20 64 75 70 6c 69 63 61 74 69 6f 6e 20 66
6f 72 20 64 69 73 63 6c 6f 73 75 72 65 20 72 65
73 74 72 69 63 74 65 64 20 62 79 20 47 43 41 20
ioctl(SG_IO v3) failed: Invalid argument (errno=22)
Write buffer: pass-through os error: Invalid argument
Write buffer failed: OS error: Invalid argument
root@schizo:~# lsscsi -sig
[0:0:32:0] enclosu DP BACKPLANE 1.07 - - /dev/sg0 -
[0:2:0:0] disk DELL PERC 6/i 1.22 /dev/sda 36842b2b053f1d100244390220b2c638b /dev/sg1 119GB
[0:2:1:0] disk DELL PERC 6/i 1.22 /dev/sdb 36842b2b053f1d1002443903f0ceb8a75 /dev/sg2 1.99TB
[1:0:0:0] disk HGST HUS724040ALS640 A280 /dev/sdd 35000cca0734fd568 /dev/sg3 4.00TB
This is because you should send the firmware file in smaller chunks:The IR mode was not allowing direct passthrough.
sg_write_buffer -b 4k
What clicking problem?Didn't fix my clicking problem
Sorry, my post is now visible, see here.What clicking problem?
A7JXAny firmware for huh728080al4200 ?
I believe it's normal, but if you prefer complete silence disable background media scan and enable idle power saving - this will prevent drive from unnecessary head movementsSince you have these drives, do you know if it's a normal behavior?
Ok thank you! But how can I do that? Is it a setting on the drive controller or somehow on the HDD itself? Because the drive is simply connected to the controller and not event mounted or does this even if its disconnected from the SAS and only powered.I Ielieve it's normal, but if you prefer complete silence disable background media scan and enable idle power saving - this will prevent drive from unnecessary head movements
That number sounds like an OEM firmware version (maybe that's what was asked for, I didn't review the entire thread). White-box versions of the HUH728080AL4200 drive normally come with 5xx series firmware versions. Also, I thing there are multiple underlying part numbers for the HUH728080AL4200 drive. The one I'm familiar with is 0F23651. I don't know if un-bundled firmware is universal across part numbers.
Well, actually first letter "A" of microcode revision is omitted on the drive label but will be shown by the software info tools like smartctl. A5xx is a very old fimware (2014), you will rather find a drive with A7J0 (2015-2016) or A907 (2017-2018). I don't have anything fresher than A7JX for this particular model.White-box versions of the HUH728080AL4200 drive normally come with 5xx series firmware versions
You're correct - I was mistaken. I have a bunch of drives at different revision levels, including A907. Is there any way to extract the firmware from the drive - I'd be glad to post A907 if it is retrievable. There's no documented SAS command to do it, but if it can be done via the serial management port or JTAG, I'm game.Well, actually first letter "A" of microcode revision is omitted on the drive label but will be shown by the software info tools like smartctl. A5xx is a very old fimware (2014), you will rather find a drive with A7J0 (2015-2016) or A907 (2017-2018). I don't have anything fresher than A7JX for this particular model.
<HGST HUH728080AL4200 A7JD> at scbus7 target 16 lun 0 (pass3,da0)
<HGST HUH728080AL4200 A7JD> at scbus7 target 17 lun 0 (pass4,da1)
<HGST HUH728080AL4200 A7JD> at scbus7 target 18 lun 0 (pass5,da2)
<HGST HUH728080AL4200 A7JD> at scbus7 target 19 lun 0 (pass6,da3)
<HGST HUH728080AL4200 A515> at scbus7 target 20 lun 0 (pass7,da4)
<HGST HUH728080AL4200 A7JD> at scbus7 target 21 lun 0 (pass8,da5)
<HGST HUH728080AL4200 A515> at scbus7 target 22 lun 0 (pass9,da6)
<HGST HUH728080AL4200 A515> at scbus7 target 23 lun 0 (pass10,da7)
<HGST HUH728080AL4200 A515> at scbus7 target 24 lun 0 (pass11,da8)
<HGST HUH728080AL4200 A515> at scbus7 target 25 lun 0 (pass12,da9)
<HGST HUH728080AL4200 A907> at scbus7 target 26 lun 0 (pass13,da10)
<HGST HUH728080AL4200 A907> at scbus7 target 27 lun 0 (pass14,da11)
<HGST HUH728080AL4200 A907> at scbus7 target 28 lun 0 (pass15,da12)
<HGST HUH728080AL4200 A907> at scbus7 target 29 lun 0 (pass16,da13)
<HGST HUH728080AL4200 A907> at scbus7 target 30 lun 0 (pass17,da14)
<HGST HUH728080AL4200 A907> at scbus7 target 31 lun 0 (pass18,da15)
Vendor: NETAPP
Product: X316_HAKPE06TA07
Revision: NA00