larrymoencurly
[H]ard|Gawd
- Joined
- Jul 18, 2002
- Messages
- 1,635
It leaves the data intact, as did the firmware upgrades for my Hitachi 7K1000.C and Seagate 7200.12.Does the firmware upgrade wipe the clean, or does it leave data in tact?
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
It leaves the data intact, as did the firmware upgrades for my Hitachi 7K1000.C and Seagate 7200.12.Does the firmware upgrade wipe the clean, or does it leave data in tact?
It leaves the data intact, as did the firmware upgrades for my Hitachi 7K1000.C and Seagate 7200.12.
I am really sorry for the thousands of people owning this disk and not knowing about this serious fault. What makes me more sad is that finding this and that a fix is available makes the drive even more attractive to me now
(I've been scratching my head about this issue for weeks - blaming OS, controllers, PSUs, ram and whatnot)... Usually when 10 disks all fail it's something else that is to blame - but not in this case...
I thought it was a bug in badblocks or the linux kernel or some damage to my motherboard. Although I was confused because I have never seen this behavior in the 2 years the machine has been running and none of my other drives were corrupting.
My last post wasn't clear. I have a software RAID using mdadm and I'm not using a RAID controller so all drives are connected directly to the motherboard controller. I was just hoping the firmware would update all drives at the same time and I wouldn't have to power the computer on and off lots of times and swap ports.
!
I wonder if that is different from the one that was originally released. I mean 181550HD204UI.EXE
Hey, would you mind confirming if the flash utility upgraded all your drives at the same time?
Yes the flash utility did upgrade all 4 of my drives at the same time.
I was just hoping the firmware would update all drives at the same time and I wouldn't have to power the computer on and off lots of times and swap ports.
utar already mentioned they are identical (I can confirm). Probably just renamed it so that people have to deal with the 8.3 dos file name weirdness.
Meh. FreeDOS wouldn't complete the boot sequence until I plugged in a CD/DVD drive.
I didn't try doing more than one drive at a time, but I did 5 drives one-at-a-time via an external eSATA dock and can confirm that you can swap drives without power cycling the computer. I would just swap the drive and then rerun the update utility from the DOS prompt. The utility rescans the SATA ports and reports the serial number of the drive, so I was able to confirm that it matched the drive I just inserted in the dock.
In case it matters, my motherboard uses one of the Intel ICH10 ports for eSATA, and I had AHCI enabled in the BIOS.
For anyone having trouble creating a bootable FreeDOS USB flash drive, you might try UNetbootin:
http://unetbootin.sourceforge.net/
It can create bootable USB flash drives for a lot of different things, and one of the choices is FreeDOS.
After you create the FreeDOS flash drive, just copy the Samsung exectuable to the root directory of the flash drive. When you boot from FreeDOS, you will need to type C: to get to the Samsung executable that you copied.
jmd0 ~ # smartctl --all /dev/sdd
smartctl 5.40 2010-10-16 r3189 [x86_64-pc-linux-gnu] (local build)
Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net
=== START OF INFORMATION SECTION ===
Model Family: SAMSUNG SpinPoint F4 EG series
Device Model: SAMSUNG HD204UI
Serial Number: S2HGJDWZ806049
Firmware Version: 1AQ10001
User Capacity: 2,000,398,934,016 bytes
Device is: In smartctl database [for details use: -P show]
ATA Version is: 8
ATA Standard is: ATA-8-ACS revision 6
Local Time is: Sun Dec 19 12:39:14 2010 EST
It makes me wonder if Samsung even has a clue.
It may be that they changed the firmware again. There seem to be several versions of this update..
That defintely sounds more plausible.
john@jmd0 ~/Downloads/temp $ md5sum -b F4EG.EXE ../181550HD204UI.EXE
ad1930d9fe53a6c8e20c3f57936452d1 *F4EG.EXE
ad1930d9fe53a6c8e20c3f57936452d1 *../181550HD204UI.EXE
john@jmd0 ~/Downloads/temp $ shasum -b F4EG.EXE ../181550HD204UI.EXE
1c9b6ca1e83c916ae27ec9bf326e6d94c11059d4 *F4EG.EXE
1c9b6ca1e83c916ae27ec9bf326e6d94c11059d4 *../181550HD204UI.EXE
$ strings F4EG.EXE | grep -i -C 10 fwver
`mMD
\`FE
x1 K
DHx`p(D
y(D%qMy(Deq
>p x
p3x;p#F
F.p%x[
:|7T`[
ActiveFW :
FWVer :
FLASHDAT
1AQ3c0p_
.163
00001
GEO_00
>DDpI
^P_@`
b)cCd
ebfegfh
t5u@v
It may be that they changed the firmware again. There seem to be several versions of this update..
Here's what I get when I do an MD5 on the files I used:
G:\install\Samsung HDD stuff\089312HD240UI_JP>md5 HD240UI_JP.EXE
EEE0492525D836392551021BB744CDCB HD240UI_JP.EXE
G:\install\Samsung HDD stuff\621878F4EG>md5 F4EG.EXE
AD1930D9FE53A6C8E20C3F57936452D1 F4EG.EXE
Here's what I get when I do an MD5 on the files I used:
G:\install\Samsung HDD stuff\089312HD240UI_JP>md5 HD240UI_JP.EXE
EEE0492525D836392551021BB744CDCB HD240UI_JP.EXE
G:\install\Samsung HDD stuff\621878F4EG>md5 F4EG.EXE
AD1930D9FE53A6C8E20C3F57936452D1 F4EG.EXE