• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Recent content by ido2

  1. I

    3TB drive stopped working - linux recognizes as 2tb now

    F**K what a SAGA. The solution was to add 'libata.ignore_hpa=1' to the linux cmdline - which actually worked and linux saw the full size of the drive. I could then mount the drive properly. probably I had an older kernel on the NAS and it was rebooted only now, so I didn't know it until...
  2. I

    3TB drive stopped working - linux recognizes as 2tb now

    omniscence: yes for hdparm. I did get the cmdline to work just now. linux shows the correct sector sizes, but gdisk still isn't happy with the size. fsck is working right now (heck only a few sectors missing at the end of the drive, i rather have the rest of the data working..
  3. I

    3TB drive stopped working - linux recognizes as 2tb now

    the drive physically seems fine. (checked with smartctl). its 3TB and NOT backed up. I'm pretty sure its a software issue, and the partition was made on an older system, so it ignored HPA, which is what fucked up everything. Also, it might also have to do with a bad GPT now that I've played...
  4. I

    3TB drive stopped working - linux recognizes as 2tb now

    the hdparm man page says these commands just might not work well with some controllers/drives. I might be able to override this by recompiling the kernel (to ignore HPA and disabling hpa for all drives), but I doubt that would help for getting the drive to mount ? (or would it)
  5. I

    3TB drive stopped working - linux recognizes as 2tb now

    cmdline - dunno why - probably I am not entering it correctly. as for hdparm - It says it works, when i check again with N only, it says the right number, but after a reboot the hpa values seem to stick :( oh boy its a full 3TB drive :(
  6. I

    3TB drive stopped working - linux recognizes as 2tb now

    Yeah, I found out how to disable with hdparm already, but both CMDLINE and hdparm methods don't work for me..
  7. I

    3TB drive stopped working - linux recognizes as 2tb now

    UPDATE2: I found out whats the problem with the geometry size - seems the drive has something thats called HPA (host protected area) on the disk, thats why linux didn't see the whole size. - you can get linux to ignore it by passing ide_core.nohpa=0.0 in the commandline I'm currently...
  8. I

    3TB drive stopped working - linux recognizes as 2tb now

    UPDATE: I booted a different linux distrubution, and this could see the whole 3TB (weird, because I don't remember changing kernels on the old one!). In any case, there's another problem. the drive won't mount because it sees a DIFFERENT drive geometry. the old says: First usable sector is...
  9. I

    3TB drive stopped working - linux recognizes as 2tb now

    SEE UPDATE ON SECOND POST... Hi, I have a seagate 3TB drive formatted with GPT working on my NAS for a long time now (it is NOT bootable). All the sudden, yesterday it stopped working. When I look at the boot log files I see: [ 45.620232] ata3: exception Emask 0x10 SAct 0x0 SErr...
See more
Back
Top