LBA

Similar Questions

• Portege M300 - how many bits are supported by LBA

  Hello

  Anyone know how many bits are supported by LBA? It has 48-bit?

  I need to know if I can get a 120 GB hard drive against a 160 GB for a major upgrade.
  I can't find this information on the toshiba site: is there a changelog BIOS place?

  Thank you

  Yes, as far as I know the LBA (Logical block addressing) use 48-bit.

  Check this box:
  http://www.48bitlba.com/

• Setting the mode BIOS LBA - Satellite A100 - 011 PSAARE

  I have the tool 'EASEUS Partition manager', and when I start this tool, I have an error message "Manager Easeus partition detected an error on the disk 1" "start LBA value partition xxxxxxxxxxxxxxxxx is invalid". "." Using the tool says:
  --------
  Change the BIOS LBA mode setting

  CAUTION: Never change the LBA mode in the BIOS of your system once the data are present on any hard disk. Changing this setting can cause loss and alteration of the data.
  More modern designs of BIOS system supports LBA or Logical Block Addressing. The LBA mode no definition, no matter enabled on your system, or not, determines how your computer translates logical addresses cylinder-head-sector (CHS). If you change this setting, shift resulting in the CHS values may corrupt the files and partitions on your hard disks.

  If you must change the setting of the LBA mode in the BIOS of your system, first back up the data on your hard drives. Contact the BIOS and/or support services of the drive manufacturer to make sure that understand how to proceed safely.
  -----
  Can someone help me?

  Thank you very much

  Hello

  The LBA can be enabled in the registry of the Windows XP operating system!
  Microsoft has released the paper support and the guide line;
  http://support.Microsoft.com/kb/303013

  The LBA allows a computer treat a disk HARD more than 528 megabytes.
  Logical block addressing is one of the defining features of the IDE improved HARD drive interface.

  If you wish, you can read some details here:
  Logical Block Addressing (LBA) defined
  http://support.Microsoft.com/kb/q122052/

• Bad LBAs appearing on newspaper

  Hi all

  I have a Dell PowerEdge 2900 which log shows bad LBA for physical disk 01. These bad LBAs have appeared in journal 02/11/16 at 02/16/16.

  In Dell OpenManage, everything has a green check marks.

  Here's a copy paste log controller showing the bad LBA:

  11/02/16 0:42:43: EVT #59094-02 / 11 / 16 0:42:43: 113 = feel unexpected: PD 01 (e0x20/s1) path 5000c5003997d5b5, CDB: 28 00 01 22 97 3 a 00 00 08 00, meaning: 11/03/00
  11/02/16 0:42:43 : sens Raw pour PD 1 : f0 00 03 01 22 97 3 b 0 a 00 00 00 00 11 00 81 80 00 97
  11/02/16 0:42:43: DEV_REC:Medium Error DevId [1] retired Tgt 1 RDM = a08c5200 = 0
  11/02/16 0:42:43: MedErr is for: cmdId = ee, ld = 0, src = 1, cmd = 11, lba = 122973 a., cnt = 8, rmwOp = 0
  11/02/16 0:42:43: ErrLBAOffset (1) LBA(122973a) BadLba = 122973 b
  11/02/16 0:42:45: EVT #59095-02 / 11 / 16 0:42:45: 113 = feel unexpected: PD 01 (e0x20/s1) path 5000c5003997d5b5, CDB: 28 00 01 22 97 3 a 00 00 08 00, meaning: 11/03/00
  11/02/16 0:42:45 : sens Raw pour PD 1 : f0 00 03 01 22 97 3 b 0 a 00 00 00 00 11 00 81 80 00 97
  11/02/16 0:42:45: DEV_REC:Medium Error DevId [1] retired Tgt 1 RDM = a0710600 = 0
  11/02/16 0:42:45: MedErr is for: cmdId = ee, ld = 0, src = 1, cmd = 1, lba = 122973 a., cnt = 8, rmwOp = 0
  11/02/16 0:42:45: ErrLBAOffset (1) LBA(122973a) BadLba = 122973 b
  11/02/16 0:42:45: EBB_RecoverReadErrors: question WV for pd = 01, lba = 122973b
  11/02/16 0:42:45: show writing check pd = 01, physArm = 1, span = 0, blk = 122973b
  11/02/16 0:42:45: EVT #59096-02 / 11 / 16 0:42:45: 110 = average error corrected during PD 01 (e0x20/s1) recovery to 122973 b
  11/02/16 16:37:14: EVT #59097-02 / 11 / 16 16:37:14: 113 = feel unexpected: PD 01 (e0x20/s1) path 5000c5003997d5b5, PEH: 2 a 00 00 f6 50 3 a 00 00 38 00, meaning: 3/0 c/00
  11/02/16 16:37:14: feel Raw for PD 1: f0 00 03 00 f6 50 60 0 a 00 00 00 00 00 01 80 00 89 0c
  11/02/16 16:37:14: DEV_REC:Medium Error DevId [1] retired Tgt 1 RDM = a0835600 = 0
  11/02/16 16:37:14: MedErr is for: cmdId = 41F, ld = 0, src = 7, cmd = 2, lba = f65000, cnt = 80, rmwOp = 0
  11/02/16 16:37:14 :-> DelWrite: dirtyArms = 7, badPhys = ff - ff
  11/02/16 16:37:14: ErrLBAOffset (26) LBA (f6503a) BadLba = f65060
  11/02/16 16:37:14: writing MED ERR! ErrLBA (26) LBA (f6503a)
  11/02/16 18:13:24: EVT #59098-02 / 11 / 16 18:13:24: 113 = feel unexpected: PD 01 (e0x20/s1) path 5000c5003997d5b5, CDB: 28 00 01 21 c7 00 00 36 00 ca, meaning: 11/03/00
  11/02/16 18:13:24 : sens Raw pour PD 1 : f0 00 03 01 21 c7 db 0 a 00 00 00 00 11 00 81 80 00 97
  11/02/16 18:13:24: DEV_REC:Medium Error DevId [1] retired Tgt 1 RDM = a068ca00 = 0
  11/02/16 18:13:24: MedErr is for: cmdId = 3df, ld = 0, src = 1, cmd = 11, lba is 121c7ca, cnt = 80, rmwOp = 0
  11/02/16 18:13:24: ErrLBAOffset (11) LBA (121c7ca) BadLba = 121c7db
  11/02/16 18:13:26: EVT #59099-02 / 11 / 16 18:13:26: 113 = feel unexpected: PD 01 (e0x20/s1) path 5000c5003997d5b5, CDB: 28 00 01 21 c7 00 00 36 00 ca, meaning: 11/03/00
  11/02/16 18:13:26 : sens Raw pour PD 1 : f0 00 03 01 21 c7 db 0 a 00 00 00 00 11 00 81 80 00 97
  11/02/16 18:13:26: DEV_REC:Medium Error DevId [1] retired Tgt 1 RDM = a05cba00 = 0
  11/02/16 18:13:26: MedErr is for: cmdId = 3df, ld = 0, src = 1, cmd = 1, lba is 121c7ca, cnt = 80, rmwOp = 0
  11/02/16 18:13:26: ErrLBAOffset (11) LBA (121c7ca) BadLba = 121c7db
  11/02/16 18:13:26: EBB_RecoverReadErrors: question WV for pd = 01, lba = 121c7db
  11/02/16 18:13:26: show writing check pd = 01, physArm = 1, span = 0, blk = 121c7db
  11/02/16 18:13:26: EVT #59100-02 / 11 / 16 18:13:26: 110 = average error corrected during PD 01 (e0x20/s1) recovery at 121c7db
  11/02/16 18:13:28: EVT #59101-02 / 11 / 16 18:13:28: 113 = feel unexpected: PD 01 (e0x20/s1) path 5000c5003997d5b5, CDB: 28 00 01 21 c9 00 00 00 4 a 00, feel: 11/03/00
  11/02/16 18:13:28 : sens Raw pour PD 1 : f0 00 03 01 21 c9 0 a 04 00 00 00 00 11 00 81 80 00 97
  11/02/16 18:13:28: DEV_REC:Medium Error DevId [1] retired Tgt 1 RDM = a06cd000 = 0
  11/02/16 18:13:28: MedErr is for: cmdId = 173, ld = 0, src = 1, cmd = 11, lba is 121c8ca, cnt = 80, rmwOp = 0
  11/02/16 18:13:28: LBA (121c900) ErrLBAOffset BadLba (4) = 121 c 904
  11/02/16 18:13:29: EVT #59102-02 / 11 / 16 18:13:29: 113 = feel unexpected: PD 01 (e0x20/s1) path 5000c5003997d5b5, CDB: 28 00 01 21 c9 00 00 00 4 a 00, feel: 11/03/00
  11/02/16 18:13:29 : sens Raw pour PD 1 : f0 00 03 01 21 c9 0 a 04 00 00 00 00 11 00 81 80 00 97
  11/02/16 18:13:29: DEV_REC:Medium Error DevId [1] retired Tgt 1 RDM = a076bc00 = 0
  11/02/16 18:13:29: MedErr is for: cmdId = 173, ld = 0, src = 1, cmd = 1, lba is 121c8ca, cnt = 80, rmwOp = 0
  11/02/16 18:13:29: LBA (121c900) ErrLBAOffset BadLba (4) = 121 c 904
  11/02/16 18:13:29: EBB_RecoverReadErrors: question WV for pd = 01, lba = 121 c 904
  11/02/16 18:13:29: show writing check pd = 01, physArm = 1, span = 0, blk = 121 c 904
  11/02/16 18:13:30: EVT #59103-02 / 11 / 16 18:13:30: 110 = average error corrected during PD 01 (e0x20/s1) recovery to 121C 904
  11/02/16 18:40:20: EVT #59104-02 / 11 / 16 18:40:20: 113 = feel unexpected: PD 01 (e0x20/s1) path 5000c5003997d5b5, CDB: 28 00 00 80 00 00 32 00 4th f6, feel: 11/03/00
  11/02/16 18:40:20 : sens Raw pour PD 1 : f0 00 03 00 f6 4e 9 b 0 a 00 00 00 00 11 00 81 80 00 97
  11/02/16 18:40:20: DEV_REC:Medium Error DevId [1] retired Tgt 1 RDM = a08f2400 = 0
  11/02/16 18:40:20: MedErr is for: cmdId = 80, ld = 0, src = 1, cmd = 11, lba is f64e32, cnt = 80, rmwOp = 0
  11/02/16 18:40:20: ErrLBAOffset (1B) LBA (f64e80) BadLba = f64e9b
  11/02/16 19:36:35: EVT #59105-02 / 11 / 16 19:36:35: 113 = feel unexpected: PD 01 (e0x20/s1) path 5000c5003997d5b5, CDB: 2A 00 01 06 29 ca 00 00 36 00, meaning: 3/0 c/00
  11/02/16 19:36:35: feel Raw for PD 1: f0 00 03 01 06 29 d5 0 a 00 00 00 00 00 01 80 00 2nd 0c
  11/02/16 19:36:35: DEV_REC:Medium Error DevId [1] retired Tgt 1 RDM = a070fa00 = 0
  11/02/16 19:36:35: MedErr is for: cmdId = 426, ld = 0 src = 7, cmd = 2, lba = 1062980, cnt = 80, rmwOp = 0
  11/02/16 19:36:35 :-> DelWrite: dirtyArms = 7, badPhys = ff - ff
  11/02/16 19:36:35: ErrLBAOffset (b) LBA(10629ca) BadLba = 10629 d 5
  11/02/16 19:36:35: writing MED ERR! ErrLBA (b) LBA(10629ca)
  12/02/16 02:33:11: EVT #59106-02 / 12 / 16 2:33:11: 113 = feel unexpected: PD 01 (e0x20/s1) path 5000c5003997d5b5, CDB: 28 00 00 db 92 00 00 6F 00 d1, feel: 11/03/00
  12/02/16 02:33:11 : sens Raw pour PD 1 : f0 00 03 00 db d1 a8 0 a 00 00 00 00 11 00 81 80 00 97
  12/02/16 02:33:11: DEV_REC:Medium Error DevId [1] retired Tgt 1 RDM = a06e7000 = 0
  12/02/16 02:33:11: MedErr is for: cmdId = 4 d, ld = 0, src = 1, cmd = 11, lba is dbd192, cnt = 80, rmwOp = 0
  12/02/16 02:33:11: ErrLBAOffset (16) LBA (dbd192) BadLba = dbd1a8
  12/02/16 02:33:13: EVT #59107-02 / 12 / 16 2:33:13: 113 = feel unexpected: PD 01 (e0x20/s1) path 5000c5003997d5b5, CDB: 28 00 00 db 92 00 00 6F 00 d1, feel: 11/03/00
  12/02/16 02:33:13 : sens Raw pour PD 1 : f0 00 03 00 db d1 a7 0 a 00 00 00 00 11 00 81 80 00 97
  12/02/16 02:33:13: DEV_REC:Medium Error DevId [1] retired Tgt 1 RDM = a0526000 = 0
  12/02/16 02:33:13: MedErr is for: cmdId = 4 d, ld = 0, src = 1, cmd = 1, lba is dbd192, cnt = 80, rmwOp = 0
  12/02/16 02:33:13: ErrLBAOffset (15) LBA (dbd192) BadLba = dbd1a7
  12/02/16 02:33:13: EBB_RecoverReadErrors: question WV for pd = 01, lba = dbd1a7
  12/02/16 02:33:13: show writing check pd = 01, physArm = 1, span = 0, blk = dbd1a7
  12/02/16 02:33:13: EVT #59108-02 / 12 / 16 2:33:13: 110 = average error corrected during PD 01 (e0x20/s1) recovery at dbd1a7
  13/02/16 0:41:02: EVT #59109-02 / 13 / 16 0:41:02: 113 = feel unexpected: PD 01 (e0x20/s1) path 5000c5003997d5b5, PEH: 2 a 00 00 and 23 22 00 00 08 00 f5, meaning: 3/0 c/00
  13/02/16 0:41:02: feel Raw for PD 1: 00 03 00 23 f5 28 f0 0 a 00 00 00 00 00 01 80 00 89 0c
  13/02/16 0:41:02: DEV_REC:Medium Error DevId [1] retired Tgt 1 RDM = a06d7200 = 0
  13/02/16 0:41:02: MedErr is for: cmdId = 490, ld = 0 src = 7, cmd = 2, lba is 23f500, cnt = 80, rmwOp = 0
  13/02/16 0:41:02 :-> DelWrite: dirtyArms = 7, badPhys = ff - ff
  13/02/16 0:41:02: ErrLBAOffset (6) LBA (23f522) BadLba = 23f528
  13/02/16 0:41:02: writing MED ERR! ErrLBA (6) LBA (23f522)
  13/02/16 01:59:33: EVT #59110-02 / 13 / 16 1:59:33: 113 = feel unexpected: PD 01 (e0x20/s1) path 5000c5003997d5b5, CDB: 28 00 01 21 c7 00 00 a2 feel 5th 00: 11/03/00
  13/02/16 01:59:33 : sens Raw pour PD 1 : f0 00 03 01 21 c7 cc 0 a 00 00 00 00 11 00 81 80 00 97
  13/02/16 01:59:33: DEV_REC:Medium Error DevId [1] retired Tgt 1 RDM = a0800e00 = 0
  13/02/16 01:59:33: MedErr is for: cmdId = 26th, ld = 0, src = 1, cmd = 11, lba is 121c7a2, cnt = 80, rmwOp = 0
  13/02/16 01:59:33: BadLba LBA (121c7a2) ErrLBAOffset (2A) = 121c7cc
  13/02/16 01:59:35: EVT #59111-02 / 13 / 16 1:59:35: 113 = feel unexpected: PD 01 (e0x20/s1) path 5000c5003997d5b5, CDB: 28 00 01 21 c7 00 00 a2 feel 5th 00: 11/03/00
  13/02/16 01:59:35 : sens Raw pour PD 1 : f0 00 03 01 21 c7 cc 0 a 00 00 00 00 11 00 81 80 00 97
  13/02/16 01:59:35: DEV_REC:Medium Error DevId [1] retired Tgt 1 RDM = a0734e00 = 0
  13/02/16 01:59:35: MedErr is for: cmdId = 26th, ld = 0, src = 1, cmd = 1, lba is 121c7a2, cnt = 80, rmwOp = 0
  13/02/16 01:59:35: ErrLBAOffset (2A) LBA (121c7a2) BadLba = 121c7cc
  13/02/16 01:59:35: EBB_RecoverReadErrors: question WV for pd = 01, lba = 121c7cc
  13/02/16 01:59:35: show writing check pd = 01, physArm = 1, span = 0, blk = 121c7cc
  13/02/16 01:59:35: EVT #59112-02 / 13 / 16 1:59:35: 110 = average error corrected during PD 01 (e0x20/s1) recovery at 121c7cc
  16/02/16 18:01:53: #59113-02 EVT / 16 / 16 18:01:53: 113 = feel unexpected: PD 01 (e0x20/s1) path 5000c5003997d5b5, CDB: 28 00 01 05 d7 b2 00 00 00 4F, feel: 11/03/00
  16/02/16 18:01:53 : sens Raw pour PD 1 : f0 00 03 01 05 d7 e3 0 a 00 00 00 00 11 00 81 80 00 97
  16/02/16 18:01:53: DEV_REC:Medium Error DevId [1] retired Tgt 1 RDM = a07e8400 = 0
  16/02/16 18:01:53: MedErr is for: cmdId = 22 b, ld = 0, src = 1, cmd = 11, lba is 105d7b2, cnt = 50, rmwOp = 0
  16/02/16 18:01:53: ErrLBAOffset (31) LBA (105d7b2) BadLba = 105d7e3

  I intend keeping an eye on the controller log and running an analysis of consistency check soon.

  Don't you think that the disc is a failure?

  Thanks for the help!

  Hello.

  Looks like the average of errors on the existing LBA on the PD 01 have been corrected. Ensure that the controller and the drives hard firmware is up to date. Go head check consistency, a race of diagnoses and a review for more information.

• Disk 0 x 80 (LBA): C/H/S = 1024/255/63, County/Size = 1953521664/512 Options If your HARD drive is su-ERS at 1 to.

  Windows 7 complete installation after Reboot then this Massege showing "Drive 0x80 (LBA): C/H/S = 1024/255/63, County/Size = 1953521664/512 Options If your HARD drive is larger than 1 TB; Move your startup file for a saller at the beginning of the HARD drive partition. Format the HARD drive allow Windows 7 to create a 100 MB Partiton boot. Shrink and move your partition with Gparted.

  Hello, MD. Nasir,

  Thanks for posting your question on the Microsoft community.

  We need more information about the issue so that we can help you better.

  1. What is the brand and model of your computer?
  2 did you the hardware changes to your computer like hard drive replacement?

  Thank you for details on the issue.

  This problem may occur because of damaged or missing Windows startup files.

  I suggest you run the Startup Repair tool and check if that helps.
  Refer to this article:
  What are the system recovery options in Windows?
  http://Windows.Microsoft.com/en-us/Windows/what-are-system-recovery-options#what-are-system-recovery-options=Windows-7

  It fixes some problems, such as missing system files or damaged, that might prevent Windows from starting correctly.

  Additional information:
  Startup Repair: frequently asked questions
  http://Windows.Microsoft.com/en-us/Windows/Startup-Repair-FAQ#1TC=Windows-7

  I hope this information helps.

  Please let us know if you need more help.

  Thank you

• I couldn't create a pool of LBaaS.

  Hi, I put the challenge to use the LBaaS function.

  But the treatment of the creation of a pool of LBaaS would fail.

  I have it set up as below.

  - http://pubs.vmware.com/integrated-openstack-2/index.jsp#com.vmware.openstack.install.doc/GUID-AF21F3D5-B208-4BB7-971F-217EB0C8C6C2.html

  Here is the result of the configuration.

  - https://gist.github.com/userlocalhost2000/c1c00dc5d793625335ee

  Then I run the "neutron lb-pool-create" command to create a Pool of LBaaS, but it fails.

  - https://gist.github.com/userlocalhost2000/de0287015b1968ca8e37

  The driver of the NSX of "edge_loadbalancer_driver" throws an exception.

  - https://gist.github.com/userlocalhost2000/c0df30cbb436b1ed1e16

  Is this a BUG?

  Here's my VIO/NSX-V environment.

  ---

  * version of VIO = 2.0.0 build 3037963

  * version of NSX - V = 6.2.0 build 2986609

  As mentioned in the documentation, you must create an exclusive router.

  You can try to recreate the router with:

  Neutron - create - router_type = exclusive lock

• 24 - bit LBA 48 bit vs

  I have a laptop Sager 5 years, with 2 hard drives showing the first signs of failure. (Yes, I'm fully and completely backed up!) Current readers are 2 x 100 GB, 7200 RPM Travelstars PATA Hitachi.  The OEM drives were 2 x 60 GB Travelstars.

  The mobo has a built-in Promise Ultra 100 controller.  I am running Windows XP SP3.

  My problems:

  1. I need more interior space.  Readers soon-to-be failed are a good excuse.  I'm willing to trade the speed of the drive for disk space.
     
  2. My new WD Scorpio PATA 250 GB disks are only considered as 128 GB each by the controller. (Gate of the 137 GB with 24-bit LBA)
     
  3. Newest BIOS of promise for their PCI Ultra 100 controller does not Flash my built-in controller.  I tried.
     
  4. Technical support from my vendor to see if the Sager has a updated BIOS updated to the integrated controller. (Wide ' net research indicates that this is unlikely)
  5. WD said a DDO will not work because the regulator is the problem, not the BIOS of the motherboard.  I have not tried a DDO.
  6. PATA hard drives for laptop (of any size) and related material are becoming harder and harder to find.

  My mobo/controller combo was built * after * LBA 48 bit became available, so my seller think something besides THE controller BIOS can prevent the system from see all 250 GB on each disc.  He suggested a new cable.  Is this reasonable?  I don't know how if a laptop PATA 'new' cable would be better/different then my laptop PATA cable existing.  What I am looking for?

  Are there other things I should try that I forgot?  I know this is really old technology and that if I just bought a new computer, this problem should go away.  But the cost to upgrade all my cell capacity current is prohibitively expensive at the time.  In addition, my boat anchor Sager has been a good friend for a long time, and I'm not willing to give it up just because of a few nearly dead drives.

  -Jeff

  The only possible solution for more storage at high speed I can think of that help would be to add a third but external - can - be a disk SATA 2.5 inch via a plugin card (I suspect that your year 5 Sager can be a CardBus - my old notebook interface of ~ 5 years has) this device drive controllers manages the address translation.  You can check with those people to see if this card would adapt and integrate software-wise your Sager, he announces "Add 1, 500Mbps high speed of the Serial ATA 2 Ports on your laptop to access storage devices and Support HDD like 137 GB very high performance!" I did not use this provider, I did an Addonics ADCB2SA-E that works perfectly on my laptop HP 5 year.

  If you stay with a 2.5-inch drive, it can be powered by the laptop that requires two power USB connections.  An external box eSATA as one I use (NexStar3) comes with the necessary cables. It also has an external drive eSATA/cord support if your office has not already.

  Good luck in your efforts to 'recycling '.

• "Missing operating system" is displayed when you try to start Windows 10

  I have been using bootcamp to access the 10 Windows for quite awhile. It was working perfectly until a member of the family installed a Windows Update, but the battery is dead during the update. Following this window would charge any. A black screen with a blinking cursor. After that, I went back on fairing and wrong used the partition synchronization tool. Now, Windows is in a worse state and the "Missing operating system" message when you try to get back in. In addition, the Mac startup disk no longer allows me to reboot the laptop using the bootcamp partition, as if the partition is not more detected. Disk utility simply shows a greyed out "Disk0s4."

  I spent a lot of time looking for a solution, but without success. Here are some of the things I've tried so far:

  I don't know if its of any importance but sudo fdisk e/dev/disk0 the following message is displayed:

  #: cyl hd s - cyl hd s id [Start - size]

  ------------------------------------------------------------------------

  1: EA 1023 254 63 - 1023 254 63 [1-409639] < unknown ID >

  2: AF 1023 254 63 - 1023 254 63 [409640-174722176] HFS +.

  3: AB 1023 254 63 - 1023 254 63 Boot Darwin [175131816-1269536]

  * 4: 0 b 1023 254 63-1023 254 63 [244256768-244140032] Win95 FAT-32

  The partition Inspector displays this:

  Report for internal hard drive *.

  Current GPT partition table:

  # Start end LBA LBA Type

  1 40 409639 system EFI (FAT)

  2 409640 175131815 mac OS X HFS +.

  3 175131816 176401351 Mac OS X startup

  4 244256768 488396799 database

  Current MBR partition table:

  # A Type starting ending LBA LBA

  1 1 409639 ee EFI protection

  2 409640 175131815 af Mac OS X HFS +.

  3 175131816 176401351 ab Mac OS X startup

  4 * 244256768 488396799 0 b FAT32 (CHS)

  MBR content:

  Bootcode: unknown, but bootable

  LBA 40 partition:

  Startup code: no (Non-system disk message)

  File system: FAT32

  Filed under GPT partition 1, type system EFI (FAT)

  LBA 409640 partition:

  Startup code: no

  File system: HFS extended (HFS +)

  Filed under GPT partition 2, type Mac OS X HFS +.

  Classified in the MBR partition 2, type af Mac OS X HFS +.

  LBA 175131816 partition:

  Startup code: no

  File system: HFS extended (HFS +)

  Filed under GPT partition 3, type Mac OS X startup

  Classified in the MBR partition 3, type ab Mac OS X startup

  LBA 244256768 partition:

  Startup code: no

  File system: unknown

  Filed under GPT partition 4, type database

  Classified in the MBR partition 4, type 0 b FAT32 (CHS), active

  I also tried to use Windows, but without success startup repair.

  If there is no solution to this problem, all least, hope to be able to back up everything that was on the Windows partition.

  Thank you very much

  What is the year/model of your Mac? Please after the release of

  sudo dd if = / dev/rdisk0s4 account = 1 2 >/dev/null | hexdump - C

  This will show the first block of the Disk0s4.

• "Reading DMA Ext" SMART error reported for a 27 "Mac (model end 2013)

  Hello

  I have experienced a strange behavior in last week, where my iMac starts upward normally, but directly obtained subsequently very slow and lazy. Each program showed the wait mouse cursor und switch between programs by using the Task Manager did not work. If available, I could click through the mouse on a different program of an application window, but only to bring in the und before then the wait cursor shown here as well.

  I had to reboot several times, until all behaved as usual.

  I checked the State of the disk hard und SMART monitor indicated failures during the power on unit (UNC at LBA). And it seemed that this error has occurred several times (once at the start of the iMac, I retried several times).

  I installed the tool console smartctl to get more detailed information and it reported an error count of 534 where were the last 4 errors of this type (history does not seem to store more errors). The last error reported was of type READ FPDMA queued (global error at LBA UNC).

  I ran a SMART long test, which passed without error.

  And if the system boots properly, there is no indication that the hard disk has a problem.

  Someone knows something similar and has a suggestion, what to do? Is there something wrong with the hard drive, controller, plugging in the cable?

  I really appreciate your thought and suggestions about this strange behavior.

  Thank you for your support in advance!

  Best regards

  René

  Here some information copied from the smartctl journal:

  ----------------------------------------------------------

  = START OF SECTION INFORMATION =.

  Phone model: APPLE disk HARD ST1000DM003

  Serial number: S1DCF1AX

  LU WWN device ID: 5 000c 50 061b9b612

  Firmware version: AP18

  [User capability: 1,000,204,886,016 1.00 TB bytes]

  Sector size: 512 byte logical, physical 4 096 bytes

  Rotation speed: 7200 RPM

  Form factor: 3.5 inches

  Device is: not in smartctl database [for details: showall - P]

  ATA Version is: DCC-2, 3-ACS T13 / 2161 - D revision 3B

  SATA version: SATA 3.1, 6.0 GB/s (current: 3.0 Gb/s)

  Local time is: Sun Jul 10 12:04:36 CEST 2016

  SMART support is: available - device has SMART capability.

  SMART support is: enabled

  = START OF SECTION ERROR =.

  Error 534 to disk works to life: 6143 hours (255 days + 23)

  When the command that caused the error occurred, the aircraft was active or inactive.

  After the completion of the order has occurred, the registers were:

  ST ST SC SN CL CH DH

  -- -- -- -- -- -- --

  40 51 00 70 b4 76 01 error: UNC at LBA = 0x0176b470 = 24556656

  Orders, leading to the command that caused the error were:

  CR EN SC SN CL CH DH DC Powered_Up_Time command/Feature_Name

  -- -- -- -- -- -- -- --  ----------------  --------------------

  25 00 20 70 76 41 00 00:27:49.218 LU DMA EXT b4

  25 00 20 70 76 41 00 00:27:45.476 LU DMA EXT b4

  25 00 20 70 76 41 00 00:27:41.811 LU DMA EXT b4

  25 00 20 70 76 41 00 00:27:38.207 LU DMA EXT b4

  25 00 10 88 08 40 00 00:27:38.204 LU DMA EXT c6

  ...

  Error 530 to disk works to life: 6143 hours (255 days + 23)

  When the command that caused the error occurred, the aircraft was active or inactive.

  After the completion of the order has occurred, the registers were:

  ST ST SC SN CL CH DH

  -- -- -- -- -- -- --

  40 51 00 70 b4 76 01 error: UNC at LBA = 0x0176b470 = 24556656

  Orders, leading to the command that caused the error were:

  CR EN SC SN CL CH DH DC Powered_Up_Time command/Feature_Name

  -- -- -- -- -- -- -- --  ----------------  --------------------

  60 00 20 70 76 41 00 00:27:34.254 LU FPDMA queued b4

  60 00 10 88 08 40 00 00:27:34.254 LU FPDMA queued c6

  60 00 10 18 22 20 40 00 00:27:34.254 READ FPDMA QUEUED

  60 00 10 a8 c7 1 d 40 00 00:27:34.254 READ FPDMA queued

  60 00 08 ff ff ff 4f 00 00:27:34.150 READ FPDMA queued

  It's a lot of information that virtually no one knows what to do with... but my guess is that everything points to a failing hard drive.

• Portege M100 BIOS supports more than 128 GB of HARD drive?

  subj

  Portege m100 BIOS does support HDD > 128 (137) Go?

  What IDE controller has been integrated?
  You could install a tool of diagnosis of equipment as Everest home edition and could check your hardware specifications.

  But I guess the protégé M100 supports South Bridge Intel ICH4 - M and the IDE controller must support the Ultra ATA 100/66/33

  However, you must still install these diagnostic tools to ensure a what IDE controller has been installed.

  The fact is that since ATA - 6 (also known as Ultra DMA/100, Ultra DMA 5 or Ultra-ATA100 mode) the 48-bit LBA is supported which allows to use more large 128 GB drives

  Good bye

• Extension of storage on Portege 3490CT

  Hello

  I would like to extend the main storage of my 3490CT with an Intel Pentium III.
  However, it has 256 MB. The chips seem strange. Where I get fitting parts?
  Thank you
  dagoross

  Akuma is right. Portege 3490 cannot be upgraded because you already have 256 MB of RAM.

  You want to upgrade the HARD drive? What HARD drive you have right now?
  I think you can take t each HARD drive because your laptop is quite old and I know, that it limited the 28-bit LBA ([www.48bitlba.com])

• Portege S100 - upgrade after cloning BSOD & HARD disk

  Hi all

  I wonder if anyone can help me please. I have a laptop Portege S100 with a standard 80 GB drive. I want to upgrade to a 200 GB drive.
  Here's what I did.

  I ran Acronis to save an image of the 80 GB HARD drive. All backed by an external USB disk and checked. I inverted the readers and restored the image on the 200 GB drive. All restored and verified.

  I restart the PC with the new hard drive in place. "Windows XP" logo comes up, then aarrgh blue screen. Stop x7B.
  Swapped the old disk, system boots fine.
  Check in the BIOS, with the old hard drive in place that the RAID configuration is enabled by default

  New swap disk, JBOD configuration is enabled in the BIOS. Could this be why it is not booting? If I want to activate the RAID configuration, it is ok, but I'm told that it will wipe the hard drive!

  I have no qualms about wiping the new hard drive, but it will work? If I change the RAID configuration, then restore the image? The only reason why I have not done it so far is because it took some time to create the image, and then writing it back on the new disk and at that time there the owner of the laptop is needed it back. !

  Help appreciated!
  Thank you very much
  Alex

  Hello!

  Can you post the BSOD detailed please?

  I'm a little confused on RAID m parameters are you wrote. As I know the Portege S100 can handle only a single HARD disk.
  In addition, you must use the same settings as with the old HDD RAID.

  Maybe the SATA controller has a limitation of LBA 28 bit and can't handle a 200 GB HARD drive. In this case, the larger HARD drive should have 120 GB. Here you can learn more about the limitation:
  http://www.48bitlba.com

  Last but not least, you can see the new HARD drive for errors. Maybe it s faulty. For this, you can use the Drive Fitness Test:
  http://www.HitachiGST.com/HDD/support/download.htm#DFT

  Sorry, but for the moment I put t have more ideas.

  Good bye

• Tecra A2 - Upgrade 40 GB HARD drive to something bigger

  Here's my laptop specs.

  Tecra A2-104: Intel® Celeron®...
  Part number: PTA20E-07701QEN
  Main features
  Processor Intel® Celeron® M 330 (1.40 GHz)
  Windows XP Professional
  1 GB OF RAM DDR
  40 GB hard drive. Speed - 4200 RPM. Certification - S.M.A.R.T

  Could someone advise me as to what type of HDD would be better that the current one is not just big enough. I don't want to go buy one and realize that it does not work.

  Thank you

  Hi duff321,

  Upgrade the HARD drive is usually no problem because it s not delicate procedure and if you buy a HARD drive with more RPM (revolutions per minute) and something more grand (120 GB for example) your computer should work a little faster had more high density of data.

  Anyway, motherboards with IDE controller have limitation of LBA 28 bits, which means that you can use hard disks up to 128 GB or with other words 120 GB would be the maximum capacity of the HARD drive and it should be ok because he three times as much as on the old HARD drive.
  I can recommend for example of hard drives from Western Digital, but all other brands should work correctly.

  Just take a look at a few online shops or ask your authorized service provider.

• Tecra A2 used power up after upgrading the hard drive

  I have a Toshiba Tecra A2. Hard drive 60 GB factory begins to run out, so I installed a new 160 GB drive.

  But the system will not power on with the 160GB inside.
  When I press the power button the AC light goes from green to orange and blinks short short short Long Long Long in this sequence

  If I put the original drive, it does not supply power to the top.

  Any ideas what I can do about it? I got tired of updating bios on Toshiba website, but he has not made a difference.

  Thank you

  Hi DenSys,

  > Any ideas what I can do about it?
  In my opinion, the case is clear: either this new HARD drive is defective or it s is not compatible to your laptop. But if everything works with the old HDD, you contact the new 160 GB back

  Your laptop has an IDE interface for HARD drive? If so don t forget that it will be able to manage the hard disks up to 128 GB only due limitation LBA 28 bits. In order to check another model.

• Tecra M2 - I need a new HARD drive compatible

  Hi, I just bought a 2nd hand Tecra M2, but the hard drive will be replaced soon because it is endangered. I found a hard drive on ebay that says it's compatible, it says in the title for the hard drive

  "Toshiba Laptop Tecra TE S2 S1 M3 M2 M1 hard disk 120 GB.
  (Here's a direct link http://cgi.ebay.co.uk/Toshiba-120GB-Laptop-Hard-Drive-Tecra-TE-S2-S1-M3-M2-M1_W0QQitemZ230361558318QQcmdZViewItemQQptZPCC_Dri ves_Storage_Internal? hash = item35a29e6d2e & _trksid = p 3286.m63.l1177)

  but there seems to be so many models of m2 that I don't know if this drive will be compatible with each other. I'm a novice, if you have not already guessed! So, I would be very grateful for the advice. Model No. my particular M2. is PTM20E-01KK3-FR

  Thank you very much!

  Hello

  For the Tecra M2 you need a HARD drive with IDE interface, and this means that the HDD from eBay should also work on your laptop properly.

  As far as I know the Tecra M2 may due the only handful of 28-bit LBA limit s HDD up to 128 GB 120 GB HARD drive should work. :)

  Welcome them