V1.4.0 on W95

I tried to install Java SDK V1.4.0 (with Forte) on a 486/W95 machine by offline execution of the self extracting installation file. All appeared to work, there were no error messages and it informed me that the installation was successful. The installed program was registered, it created the destination folder BUT THE FOLDER WAS EMPTY! I could look at the temporary file into which all the stuff was extracted and it looked like it was all there; but it was never moved to the actual destination and the contents of the temporary file were deleted in the end. I would have thought that if my machine was inadequate for the installation I would have gotten a message informing me of that fact or some sort of error message. ???
I would much appreciate an explanation of what is happening here.
Craig

That is a good question? I'd like to be sure about it.
The installation notes for 1.4.0 say W95 is included. Starting with 1.4.1 W95 was removed.
Starting with 1.4.0_01 "586" is appended to the download name which may indicate that a 486 machine would not work (?) but there is no such indication on 1.4.0.
The installation notes for 1.4.0 do say that "A Pentium 166MHz or faster processor ..." but this sounds to me like a recomendation for speed for desirable operation of "graphical based applications" not an opertional requirment.
In any case, I seem to have the 1.4.0 JRE installed and working (unless it will fail in some special cases I have not encountered yet). I don't know about the SDK. Does anyone?
Craig

Similar Messages

  • "System Exec" command in NT / W95 How to use?

    Hi LVers,
    I can start the shell with the System Exec command with LV, but how can I put
    additional (batch) commandos into it?
    I already tried:
    - piping "cmd < dir"
    - batch files "mybatch.bat"
    Where are the differencies btw. NT and W95
    thanks
    tom

    I am not sure that I understand what you are trying to do.
    Anyway, in LVWUtil32.zip you can find some VIs that improve the use of System Exec[http://digital.ni.com/public.nsf/3efedde4322f​ef19862567740067f3cc/824b3db43031317686256aaf00713​218/$FILE/LVWUtil32.zip]. As far as I remember you have some good documentation inside.
    Also, you can use a KeyGenerator [http://hamiltondesign-consulting.com/ftpfiles/Sen​dKey.zip] to send commands to a shell window (via keystrokes).
    Hope this helps

  • W95/CTX Mcaffee quarantines files on the VMS server

    Just a heads up I had numerous files quarantined back on 03/11/06 and basically the VMS box stopped sending email alerts and I have know idea what else stopped functioning but here is a link if you see quarantine files on sig W95/CTX
    http://vil.nai.com/vil/stinger/ctxundo.asp

    What is the version of firmware running on the VMS box? I think the VMS firmware files have got corrupt. You may need to reinstall the VMS.

  • Hello, I am a newbe, and I need help. I have used WD for a very long time, since w95 I think.

    I had a PC I coud not fix-all companies say-forget it!  But WD sent me a Disk. And gave me instructions on how to fix. It was some deep PC stuff. Low level format or someother stuff like that. It took great work for me, but when I finished and it worked!!!  I felt like I completed one of those calculas problems that took 5 pages just to get to the anwser!!
    You can't imagine how itt feels unkess you have felt it!!
    I am WD's biggest sales man in a store! And out-I have nothing but good to say about WD.
    Enough of me--I have a WD external Dr. 750GB.
    S/N [Deleted]
    WD P/N WD7500H1U-00
    There is much space that I can not controll!!  This is very frustating as I do not have money to spend unnessaryly.  I seem to remember haveing a disk to use with my new WD External Hard Drive.  I have what I call 2 partitions.  "H" and "G"  They are both big. My "H" volume has 195GB, and my "G" has 292GB. That comes out to 487 GB. Where is the other  263 GB?  I am sking for help here. It can't be that hard!
      So any help is very much appreciated, I am at the end of my PC journey, and thats ok.
    I don;t live in the getto. Its not Bill Gates turf But I will leave the PC's I have to the kids in the neighbor, Not a Lot, But it would be nice. I do not know what knid of ppl you are but I ask that the things I have said here will remain here .
    No I did not proof read this, It just didnt feel
     

    Hello,
    It is possible the remaining space is unallocated.
    Verify this in disk management.
    If that's the case then you can create a new partition with that space.
     

  • Oracle JDBC Thin driver & W95+IE

    I have problem with applet in IE4(5) and Windows 95:
    DriverManager.registerDriver( new OracleDriver() );
    -- Ok!
    Connection con = DriverManager.getConnection...
    -- this except with message "NullPointerException" or
    "Connection refused".
    It worked without any problems in Windows 98 and Windows NT 4.0.
    What's it?
    null

    German V. Selenskih (guest) wrote:
    : I have problem with applet in IE4(5) and Windows 95:
    : DriverManager.registerDriver( new OracleDriver() );
    : -- Ok!
    : Connection con = DriverManager.getConnection...
    : -- this except with message "NullPointerException" or
    : "Connection refused"
    : It worked without any problems in Windows 98 and Windows NT
    4.0.
    : What's it?
    i remember reading something about a different in the "winsock"
    software between 95 and (98 or nt)
    it may not be the issue but you might want to check it out on
    the msft web site.
    i hope this helps ...
    null

  • Forms Runtime crashes when installing on clients (W95)

    I'm trying to test my application which has been created with Developer 2000. Forms only, no reports or anything else yet.
    It is my understanding that all I have to do is install the FORMS RUNTIME item from the developer CD. If this is wrong, please correct me. My problem is when it gets a small portion of the way through the install, it crashes - why and how do I fix this? My error is a GPF, 'Orainst caused an invalid page fault in module kernel32.dll'. This happens on every machine so far, all Windows 95B.
    Any advice is appreciated.

    I finally callled Oracle Tech Support and figured out my problem. Thought I'd post it in case anyone else has this trouble. I had the Ora8i client installed because my app was originally VB & used ODBC drivers etc.
    I uninstalled every Oracle component on my machine.
    Physically deleted the Oracle folders from C: and from C:\Program Files
    In Regedit I physically deleted the two Oracle keys under HKEY_LOCAL_MACHINE/SOFTWARE and HKEY_LOCAL_USER/SOFTWARE.
    Reinstalled the forms runtime files using the default Oracle Home (which it requires). Then installed Net80 components to enable communication with my database.
    So far so good.
    null

  • How I tried fix my partitions and restore a Dell Diagnostic Partition.

    UPDATED: 2 September 2012
    UPDATE: Now that I reflect back on the incidence, I realize that the Dell Utility partition had lost its ability to boot long before I had messed up my partition table. But I realized it only when I was testing all my partitions after fixing the partition table. But as I have already written this long post, lets just keep it here for future reference of anyone else stumbling across a similar problem. Read on to know about my experience.
    RECOMMENDATION: I do not recommend trying out all the steps below as they did not completely solve the problem for me. If you need the Diagnostic Utility, download the update package from Dell's support website for your model. This package can be used to create a boot-able USB drive and/or CD/DVD. These work fine and are pretty fast also.
    Something strange happened to me and I am now reporting my experience in trying to solve it (somewhat unsuccessfully!!)
    First of all, my setup is: Dell Studio 1555 laptop. I dual boot Windows 7 and Archlinux. So here's how it went:
    After using the partitioning tool Gparted under Archlinux to resize a partition, I found a problem had occurred. The Partition was NTFS formatted and all of my data files were stored on it. The partition worked fine under Archlinux as I was able to access my files fine under it. But in Windows, although the partition was listed under Windows explorer, it wanted to format it!! When I tried to access the partition it gave an error that it was not formatted (
    The drive is not formatted, do you want to format it now?
    ). Of course, that was not right and Gparted had messed something up. I fixed that using Testdisk under Archlinux (See the Details). So now the partition problem under windows was fixed. But now another problem cropped up under Archlinux. When I booted into Archlinux and started Gparted to confirm everything was fine I saw something strange in Gparted. The whole space on my hard disk was marked as "unallocated" under Gparted. Windows and Archlinux could "see" the partitions. By this I mean that I was able to boot fine under both my OSes. And I could access all my files under all my partitions. But somehow Gparted was not able to "see" them. Gparted was reporting my whole disk to be marked as unallocated. After that I researched a lot and lots of stuff happened experimenting to fix the problem. I used a lot of utilities. But actually only one fixed the problem-fixparts from the gptfdisk package. But it seemed like a lot of work trying to get the problem fixed (See the Details).
    Now we get to the point in discussion. I was able to get my partitions back under Gparted. But I lost the Dell Diagnostics Utility partition's ability to boot up. [Actually, now that I reflect back on the incidence, I realize that the Dell Utility partition had lost its ability to boot long before I had messed up my partition table. But I realized it only when I was testing all my partition after fixing the partition table. But more on this later.] It gave an error that the partition was not found.
    So, in short: After all this restoring partitions' visibility under Gparted, I realized that the Dell Utility partition on my Studio 1555 was not booting up. To explain this, it means that when I press F-12 when starting the laptop and select Diagnostics from the menu to run the Diagnostic Utility and after running the Pre-boot System Assesment tests when I consented to boot the Diagnostic Utility partition, it gave me the error that the partition was not found. When I tried to run the "Dell 32 Bit Diagnostics (Graphical User Interface version)" update package under Windows, it resulted in a similar error: Partition not found.
    For some background on what makes the Dell Utility partition so special, please read this thread and the third post on this thread.
    WARNING: You and only you are responsible for your data. Please make a backup before performing any of the partitioning steps below.
    NOTE: Please read the entire post before actually performing the steps.
    So, to try and fix this I did the following:
    Boot into Windows 7.
    Open Disk Management under the Computer Management console (To open the Computer Management console, right click on Computer in the Start menu and select Manage).
    Reformat the Dell Diagnostic Utility partition as FAT(not FAT32). This is the first partition on the drive (marked as Healthy (OEM Partition) under the Status column). [This step may not be required, however I had done it. See Notes below.]
    UPDATE: After reading around a bit I found that these steps to format the partition might not actually be necessary. Simply changing the type of the partition (as detailed below) might also work. However as I had done that, lets just keep these steps over here.
    Reboot into a Linux distribution Live CD (I had Ubuntu 10.10). Or, If you dual boot with a Linux distribution that does not complain about the now inconsistent fstab entry, you can also boot into that distribution directly. I had to boot into Live CD to fix my /etc/fstab.
    UPDATE: After considering all the aspects from start to end I have come to a conclusion regarding the efficacy of this method on dual boot machines with Windows and Linux installed. I doubt anyone with a dual boot Windows/Linux setup would be able to boot into the Dell Diagnostic Utility even with the Utility Partition restored. This is detailed below.
    (As noted above my Archlinux install did not boot up after I had reformatted  my Dell Diagnostic Utility partition. This is because I was mounting the Dell Utility partition at boot using fstab inside Archlinux. And I was using the UUID to mount the partition. After reformatting the partition its UUID changed. So, it wouldn't mount. And because of how my fstab was setup Archlinux won't boot. So, I had to boot into a live environment to fix this. This step applied only to me. YRMV.) Fix the fstab entry.
    (This step also applied to me.) Boot into the repaired Linux Distribution.
    And open a Terminal.
    In the open terminal run fdisk on your drive, e.g.,
    fdisk /dev/sda
    This is how it looks:
    [abhishek@Nitaichand ~]$ sudo fdisk /dev/sda
    Password:
    Command (m for help):
    To change the partition type give the appropriate command, i.e.,
    Command (m for help): t
    Specify the partition, i.e.,
    Partition number (1-10): 1
    Type L to see available codes:
    Hex code (type L to list codes):L
    0 Empty 24 NEC DOS 81 Minix / old Lin bf Solaris
    1 FAT12 27 Hidden NTFS Win 82 Linux swap / So c1 DRDOS/sec (FAT-
    2 XENIX root 39 Plan 9 83 Linux c4 DRDOS/sec (FAT-
    3 XENIX usr 3c PartitionMagic 84 OS/2 hidden C: c6 DRDOS/sec (FAT-
    4 FAT16 <32M 40 Venix 80286 85 Linux extended c7 Syrinx
    5 Extended 41 PPC PReP Boot 86 NTFS volume set da Non-FS data
    6 FAT16 42 SFS 87 NTFS volume set db CP/M / CTOS / .
    7 HPFS/NTFS/exFAT 4d QNX4.x 88 Linux plaintext de Dell Utility
    8 AIX 4e QNX4.x 2nd part 8e Linux LVM df BootIt
    9 AIX bootable 4f QNX4.x 3rd part 93 Amoeba e1 DOS access
    a OS/2 Boot Manag 50 OnTrack DM 94 Amoeba BBT e3 DOS R/O
    b W95 FAT32 51 OnTrack DM6 Aux 9f BSD/OS e4 SpeedStor
    c W95 FAT32 (LBA) 52 CP/M a0 IBM Thinkpad hi eb BeOS fs
    e W95 FAT16 (LBA) 53 OnTrack DM6 Aux a5 FreeBSD ee GPT
    f W95 Ext'd (LBA) 54 OnTrackDM6 a6 OpenBSD ef EFI (FAT-12/16/
    10 OPUS 55 EZ-Drive a7 NeXTSTEP f0 Linux/PA-RISC b
    11 Hidden FAT12 56 Golden Bow a8 Darwin UFS f1 SpeedStor
    12 Compaq diagnost 5c Priam Edisk a9 NetBSD f4 SpeedStor
    14 Hidden FAT16 <3 61 SpeedStor ab Darwin boot f2 DOS secondary
    16 Hidden FAT16 63 GNU HURD or Sys af HFS / HFS+ fb VMware VMFS
    17 Hidden HPFS/NTF 64 Novell Netware b7 BSDI fs fc VMware VMKCORE
    18 AST SmartSleep 65 Novell Netware b8 BSDI swap fd Linux raid auto
    1b Hidden W95 FAT3 70 DiskSecure Mult bb Boot Wizard hid fe LANstep
    1c Hidden W95 FAT3 75 PC/IX be Solaris boot ff BBT
    1e Hidden W95 FAT1 80 Old Minix
    Type the desired code, i.e.,
    Hex code (type L to list codes): de
    Write the partition table with:
    Command (m for help): w
    The partition table has been altered!
    Calling ioctl() to re-read partition table.
    WARNING: Re-reading the partition table failed with error 16: Device or resource busy.
    The kernel still uses the old table. The new table will be used at
    the next reboot or after you run partprobe(8) or kpartx(8)
    Syncing disks.
    [abhishek@Nitaichand ~]$
    Download the required Diagnostics Update Package from the Drivers Download page for your model. Got mine from here.
    Run the downloaded package under the OS you it downloaded for. That is, run the .exe on Windows. Or, if you downloaded the .bin file for Linux then first make it executable:
    chmod u+x CL1367A0.bin
    And now run it under a Linux distribution with an older version of python installed (I think <2.7). I say this because the .bin package didn't run on an updated Archlinux for me, probably because it has the latest python. I ran it from the Ubuntu 10.10 Live CD and it ran fine under that.
    On Windows, If you are not automatically prompted with an option to update your Utility Partition then you need to browse to the location where the package was extracted (for me it was C:\dell\drivers\R239866).
    Now you need to manually run the extracted file (for me it was DDDP.exe). Most probably you'll need to right-click it and run it as an Administrator. And if all went well, it will extract/update the diagnostic utilities to/on the Dell Utility Partition.
    I believe the above steps should be sufficient for someone who's lucky and who's update package is smart enough. However these steps were not sufficient for me. My "Partition not found" error was gone because I had changed the partition type. And so the update package was able to recognize the partition and extract the necessary files to it. But I was still not able to boot the utility partition. After the Pre-boot System Assessment although I no longer got the "Partition not found" error, but I was just dropped onto the GRUB boot menu prompt.
    [UPDATE: As stated above, I realize that the recovery partition had lost its ability to boot long before I had messed up my partition table. But I realized it only when I was testing all my partition after fixing the partition table. Please refer to this forum thread for further Details. I  do not think that it is possible longer to boot from the Dell Utility Parttion on my setup which has GRUB installed to the MBR. But the rest of the post documents my attempts to slove the problem without the knowledge from the forum post.]
    Anyways, it was a pain to again and again set up/update the partition and test it after waiting half an hour or so for the Pre-boot System Assessment to complete. But I was determined to solve the problem at-least partially, until next time. So I created a GRUB entry to boot the Utility partition. Assuming the partition is the first partition on the drive (which is the case here), the grub entry is simply:
    title Dell Utility
    rootnoverify (hd0,0)
    chainloader +1
    I tried downloading an older update package. I updated my Partition with it. And tested. Still, I was unsuccessful. I researched a little bit and found this link. Out of frustration,I decided to use brute force this time . So, the below are the steps which let me have at-least a glimpse of The Dell Diagnostic Utility booting up from the partition:
    Backup your partition table using the sfdisk command (not fdisk).
    Follow the instructions in the link I gave above (i.e., http://community.spiceworks.com/how_to/show/1123) and build your Utility Partition from scratch.
    Now after that when you try to boot into the OS you'll be presented with an blue bar on top. This is because the mkup batch file from the Dell Diagnostic/Drivers CD/DVD wiped your partition table and rewrote it with only one partition on it- the Dell utility partition.
    Boot into a Live environment and restore your partition table from the backup created earlier using sfdisk.
    Now boot with a Windows disc to repair your Windows boot problem. This applied to me but may not apply to you.
    Again boot into a live environment and restore GRUB to MBR.
    After a reboot press F-12 to get to the BIOS boot menu and select Diagnostics.
    Let the Pre-boot Assessment run and after its complete it will ask you to press any key to boot the Dell Utility partition. Do that.
    You'll notice your still dropped into GRUB instead of getting the Diagnostics GUI.
    Now when on GRUB prompt don't boot any other OS.
    Press any key (other than <Enter>, that is ) to stop the timer if you have one set.
    Now look carefully at the boot menu.
    Remember I told you that I had created a GRUB menu entry to boot the Dell Utility partition. Select that. And if you are lucky you might just be able boot the partition. This worked for me (finally!).
    After this initial run I was unable to run the Diagnostics GUI from the GRUB menu entry again. I haven't tried to re-run the Pre-boot Assessment and wait to see, if I'm able to boot it from there. But now, I'm satisfied that at-least the file there are in a running condition.
    Also, the update package can be used to create boot-able USB drives or boot-able CD/DVDs which can run the Diagnostics just fine. They are almost as fast as the partition (especially the USB which seems even faster). They are recommend, instead of going into this trouble to recreate the partition. That is unless you are a purist/perfectionist .
    Notes:
    At first, I panicked and tried a lot of steps that are not exactly documented above for the sake of convenience to others who might refer.
    I have thus rewritten the post in a manner to make it very general in nature as it did not become very fruitful for myself.  If you attempt to use this guide, use common sense where necessary .
    Of course, if you are trying to build a Utility partition on a bare hard drive or you're feeling adventurous, you can always follow this link .
    Last edited by bhadotia (2012-10-08 19:03:18)

    bhadotia wrote:Anyway's the file downloaded from dell to update the partition for Studio 1555 is corrupted (checksums don't match). My partition still doesn't boot. I'm working to fix this and will update my post when I'm done.
    The file seems to create the CD/DVD/Image and USB just fine. So I used this only to create a CD image which I then wrote on a blank CD which seems to work fine. Also, I played around a bit and had some partial success in booting the partition. I've updated my original opening post with the new findings.
    Whew!! what a waste of time! Never want to do all of this again .
    Last edited by bhadotia (2012-03-03 00:05:22)

  • USB disk access of every type is hosed - HELP!?

    Newbie with the very latest "Don't Panic" running on a laptop.  I'm coming off a year with various bloateddistros, looking for something fast and stable.
    I've got my internal drive up, networking, x, gnome and openoffice all working great.  Next step is to plug in my external 160gig drive with all my data on it.  This is a very standard USB2-to-EIDE drive, I've had no problems with it in any distro.  It's split between a 32gig FAT32 partition and a 119gig Ext3.
    I followed the wiki on autofs.  Nothing.  Then played with HAL and the like.  Made my user a member of group "storage".  Still nothing.
    I've seen mount problems before of course, so I tried adding gparted via pacman and running that from a root command line just to see what's physically out there.  Not good: gparted never finishes getting past the "Scanning all devices....." process with the blue bar bouncing back and forth.  When gparted first starts I can hear the external disk spin up and chug for a few seconds, but then nothing.
    I tried a 1gig USB flash critter (probably Fat32), nothing there either.  I think something is fundamentally hosed in my USB disk support.  I do have a USB external trackball working though...so my ports are up.
    My daemons at present:
    DAEMONS=(syslog-ng network netfs crond ntpd hal cups gdm alunnd)
    Heeeelp!  Neeeed my daaaata!
    Wait, something else weird: if I turn on the external disk I see some CPU activity on my gnome panel monitor.  Nothing major, a few light spikes.  I've got a Celeron 1.6 but with the new 533 memory bus and 2gigs RAM.  Once I run gparted it goes bananas and then once I close gparted CPU activity is pegged hard at 100% - yet there's no listed process eating that.  Then when I turn off the external drive, CPU activity falls back to normal.
    WTF, over?
    Jim

    Well before reading Veek's post I got further along.  Almost there I think.
    I went and loaded XFCE4 plus extras, and logged in with a XFCE session.  I like having a backup desktop environment anyways in case Gnome gets squirrelly.
    In XFCE Thunar shows the disks, but when I try and access 'em I get:
    Failed to mount "128G Volume".
    (exo-mount:4613): Gtk-WARNING **: Locale not supported by C library.
        Using the fallback 'C' locale.
    You are not privileged to mount the volume "128G Volume".
    What I can't figure out is, what permissions?  I'm added to groups "storage" and "disks"...any more needed?
    The output from fdisk -l:
    bash-3.2$ fdisk -l
    Disk /dev/sda: 80.0 GB, 80026361856 bytes
    255 heads, 63 sectors/track, 9729 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
       Device Boot      Start         End      Blocks   Id  System
    /dev/sda1   *           1        9729    78148161   83  Linux
    Disk /dev/sdb: 160.0 GB, 160041885696 bytes
    255 heads, 63 sectors/track, 19457 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
       Device Boot      Start         End      Blocks   Id  System
    /dev/sdb1               1       19457   156288321    5  Extended
    /dev/sdb5               1        3824    30716217    b  W95 FAT32
    /dev/sdb6            3825       19457   125572041   83  Linux
    bash-3.2$
    I'm going to jump back to Gnome and try Veek's concepts...

  • System Recovery Kit for dv7-3165dx fails to restore factory image to replacement hd

    I'm posting this wall of text here in case someone else has any suggestions before I contact HP Support to see what options they have.
    My attempt to recover the factory image to a replacement hard drive in an HP Pavilion dv7-3165dx notebook is failing. An error occurs when SM.exe is trying to merge the WIM files. The SSRD.Log shows an error:
    SM, 13, Set reference file fail
    after that, SM.exe displays this message when run from a command line:
    SM, Failure, Can not load imagex 1 from src WIM file
    The following are the symptoms that the Recovery Manager displays on the screen.
    The Recovery Manager reads the two DVDs and after a few seconds, it pops up an error message:
    Reducer
    C:\RM\Image\TempBASE.WIM was not found.
    The message has on "OK" button that when clicked on, closes the message window.
    After that, nothing happens. No disk or DVD activity for over an hour. The mouse moves, but no key presses have any effect, including CTRL-ALT-DEL. You can use the mouse to move the Recovery Manager window around, and there is nothing hidden behind it. Clicking on the Recovery Manager Back, Next, or Cancel buttons produce no response at all.
    The only option at this point is to hold down the power switch until it powers down.
    When the power is turned back on, the hard drive boots and Recovery Manager displays a message that incorrectly claims "Recovery is complete" and has a "Click Finish to restart" button. After clicking on "Finish", it reboots but since the System Recovery did not actually complete, all it does is display:
    BOOTMGR is missing
    Press CTRL+ALT+DEL to restart
    Before attempting the recovery, the notebook passed all diagnostic tests.
    The 2x2GB memory cards, which still have HP stickers on them, were tested with Memtest86+ V5.01 and completed over six passes in over seven hours with zero errors.
    The replacement 500GB HGST Travelstar Z5K500 drive was tested with gsmartcontrol. The SMART status showed no errors in the past with over 400 hours of power-on time. Both of the SMART short self-test and extended self-test tests were run, which it passed without any errors.
    The HP System Diagnostics from the Startup Menu were run on the memory and hard drive and they passed those tests without any errors.
    While waiting for the HP "System Recovery Kit for Consumer Notebook (3 Disks)" Software Part Number 599357-001 to arrive, both Fedora 21 64bit and Windows Vista 64bit were successfully installed on the harddrive.
    Both System Recovery DVDs were read on different machines without any errors. This System Recovery Kit supports the notebook's System Id which is 3638, so they appear to be the correct discs.
    Now a list of workaround attempts that were suggested.
    After the Recovery Manager failed a few times with the same error message, some googling came up with other users mentioning the "TempBASE.WIM was not found" error message. I tried these suggestions that I read about.
    Run KillDisk to fill the HD with zeros.
    Running Recovery Manager after that failed with the same error message.
    Run the CyberLink Recovery Discs Utility (sp44645.exe).
    Running Recovery Manager after that failed with the same error message.
    Installed Windows VISTA 64bit again and upgraded the BIOS from F10 to F13.
    Running Recovery Manager after that failed with the same error message.
    Try only using a single 2GB memory card to see if it was a 64bit problem.
    Running Recovery Manager after that failed with the same error message.
    The BIOS does not have an option to change from AHCI mode to IDE mode.
    I don't have a Windows 7 OEM install disc and am trying to avoid spending $100 to buy one.
    That is when I decided that it is not a PC hardware problem, but a problem with the HP System Recovery Kit. Here are the details of what I think the Kit is doing.
    After running Recovery Manager and getting the error message, instead of just re-booting and letting the "Recovery is complete" message appear, I re-booted with a Linux USB drive and inspected what was on the hard drive.
    fdisk -l shows this:
    Disk /dev/sda: 465.8 GiB, 500107862016 bytes, 976773168 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 4096 bytes
    I/O size (minimum/optimal): 4096 bytes / 4096 bytes
    Disklabel type: dos
    Disk identifier: 0xa5dddc41
    Device Boot Start End Sectors Size Id Type
    /dev/sda1 409600 143013887 142604288 68G 7 HPFS/NTFS/exFAT
    /dev/sda2 * 143013888 143833087 819200 400M c W95 FAT32 (LBA)
    fsarchiver probe shows this:
    [======DISK=] [=============NAME====] [====SIZE==] [MAJ] [MIN]
    [sda                     ] [HGST HTS545050A7                ]  [  465.76 GB] [     8] [     0]
    [=====DEVICE] [==FILESYS==] [=====LABEL=] [====SIZE==] [MAJ] [MIN]
    [sda1                 ] [ntfs                  ] [<unknown>      ] [     68.00 GB] [    8] [     1]
    [sda2                 ] [vfat                  ] [SDV                     ] [  400.00 MB] [   8] [     2]
    Running gparted shows about 200 MB of unallocated space before the sda1 NTFS partition. The rest of the disk is unallocated after the bootable sda2.
    The sda1 NTFS partition has a \SSRD.Log file and an empty \RM\Image directory.
    The sda2 FAT32 partition has the Recovery Manager application files in it:
    /mnt/sda2:
    total 400
    -rwxr-xr-x 1 root root 15 Apr 9 23:36 SDV.FLG
    drwxr-xr-x 4 root root 4096 Apr 9 23:36 SYSTEM.SAV
    drwxr-xr-x 3 root root 4096 Nov 1 2009 BOOT
    drwxr-xr-x 3 root root 4096 Nov 1 2009 EFI
    drwxr-xr-x 2 root root 4096 Nov 1 2009 SOURCES
    drwxr-xr-x 3 root root 4096 Jul 27 2009 TOOL
    -rwxr-xr-x 1 root root 383562 Jul 13 2009 bootmgr
    The SOURCES directory has boot.wim, and the TOOL directory has all the programs, like Reducer.exe and SM.exe, in it.
    After shutting down the Linux system and rebooting, the Recovery Manager then boots from sda2 and displays the "Recovery is complete" message and "Click Finish to restart" button. During this process, it removes the sda2 partition and marks the sda1 NTFS partition as the active bootable partition. When the PC restarts, all that is left is the sda1 NTFS partition with the empty C:\RM\Image directory and the SSRD.Log file, so there is no BOOTMGR to boot with.
    The SSRD.Log file logs the tasks that the Recovery Manager performs.
    The Recovery Manager runs some initialization tasks and then reads the two System Recovery DVDs. It then calls MergeWimFile which runs SM.exe and starts to merge BASE.WIM with the other BASE*.WIM files. SM.exe merges 20 WIM files with log entries like these:
    SM, Success, refName= C:\RM\IMAGE\BASE22.WIM
    SM, Success, refName= C:\RM\IMAGE\BASE23.WIM
    SM, Success, refName= C:\RM\IMAGE\BASE3.WIM
    SM, Success, refName= C:\RM\IMAGE\BASE4.WIM
    SM, Success, refName= C:\RM\IMAGE\BASE5.WIM
    SM, Success, refName= C:\RM\IMAGE\BASE6.WIM
    SM, Success, refName= C:\RM\IMAGE\BASE7.WIM
    Then, with only two WIM files left, BASE8.WIM and BASE9.WIM, the log shows:
    SM, 13, Set reference file fail
    This must be when Recovery Manager pops up the "Reducer C:\RM\Image\TempBASE.WIM was not found" error message.
    That narrowed down the problem.
    I copied all of the WIM files and the TOOLS directory to a Windows 8.1 system. The two DVDs did not have any errors while being read. Running SM.exe from an admin Command Prompt with the same parameters that were logged in the SSRD.Log produced the same error message. There was an additional error message that appeared in the Command Prompt window:
    SM, 13, Set reference file fail
    SM, Failure, Can not load imagex 1 from src WIM file
    and the TempBASE.WIM was not created.
    SM.exe /? did not provide a help message. I could not find any documentation on the SM.exe command.
    If I removed three of the WIM files, (BASE7.WIM BASE8.WIM BASE9.WIM) then SM.exe could create the TempBASE.WIM file, but it would fail while merging index 2 of 3 with this message:
    SM, 11%, Merge index 2 of 3 Processing
    SM, Failed, Export image failed
    The TempBASE.WIM is 3,421,518 KB in size after that.
    This is where I came to a dead end and cannot think of anything else that I can do. Maybe I'm missing something obvious, but it appears to me that there was some kind of error building this System Recovery Kit and it is not able to perform a factory install on this notebook.
    ps
    If I can figure out how to add an attachment, I will add the SSRD.Log file.  If not, then ask and I will post it as a followup.

    Downloaded Windows Assessment and Deployment Kit which contains the latest imagex program.
    Running imagex.exe on the BASE7.WIM file on the second System Recovery DVD:
    imagex.exe /info K:\PRELOAD\BASE7.WIM
    ImageX Tool for Windows
    Version: 6.2.9200.16384
    Error opening file [K:\PRELOAD\BASE7.WIM].
    The data is invalid.
    The same error message is shown for BASE7.WIM, BASE8.WIM, and BASE9.WIM.
    The other WIM files in the PRELOAD directory, BASE5.WIM, BASE6.WIM, BASE10.WIM, BASE13.WIM, BASE15.WIM, BASE17.WIM and BASE23.WIM, could be read by imagex without any errors.

  • Asus EEE 701 4G stuck when booting

    So, here's the deal. I got a eee 701, i upgraded ram(2g), and now i wanna put archlinux on it, but it wont boot, actually it starts booting, but it stops at: 'waiting for udev uevents to be processed', but it doesnt freeze, i can type, go to newline, etc, but it wont go further.
    My sd card is in the eee, might this be causing the problem?

    the output of fdisk -l should look somthing like this
    fdisk -l
    Platte /dev/sda: 4001 MByte, 4001292288 Byte
    255 Köpfe, 63 Sektoren/Spur, 486 Zylinder
    Einheiten = Zylinder von 16065 × 512 = 8225280 Bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    Disk identifier: 0xaebcaebc
       Gerät  boot.     Anfang        Ende     Blöcke   Id  System
    /dev/sda1               1         300     2409718+  83  Linux
    /dev/sda2             301         484     1477980   83  Linux
    /dev/sda3             485         485        8032+   c  W95 FAT32 (LBA)
    /dev/sda4             486         486        8032+  ef  EFI (FAT-12/16/32)
    Platte /dev/sdb: 8239 MByte, 8239710208 Byte
    193 Köpfe, 23 Sektoren/Spur, 3625 Zylinder
    Einheiten = Zylinder von 4439 × 512 = 2272768 Bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    Disk identifier: 0x000843a4
       Gerät  boot.     Anfang        Ende     Blöcke   Id  System
    /dev/sdb1               1        3625     8045676   83  Linux
    you can also whatch dmesg before and after putting in the card

  • Special device does not exist, FSTAB Issue

    I set up this arch64 install last night, and till now I've managed all right except for one niggling issue.  For some odd reason, when I installed everything I forgot to add my "sandbox" partition in Fstab.  I thought I could just generate a UUID then add a line to Fstab later, and I did just that.  However, as its not part of my LVM, I'm wondering if thats why I cannot mount my sandbox partition from Fstab.  Ideas appreciated. 
    My fdisk -l output:
    [root@acer ~]# fdisk -l
    Disk /dev/sda: 120.0 GB, 120034123776 bytes
    255 heads, 63 sectors/track, 14593 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Disk identifier: 0x379c7acb
    Device Boot Start End Blocks Id System
    /dev/sda1 * 1 13 104391 83 Linux
    /dev/sda2 14 6428 51528487+ 5 Extended
    /dev/sda3 6429 14593 65585362+ 8e Linux LVM
    /dev/sda5 14 6428 51528456 83 Linux
    Disk /dev/mmcblk0: 7969 MB, 7969177600 bytes
    221 heads, 20 sectors/track, 3521 cylinders
    Units = cylinders of 4420 * 512 = 2263040 bytes
    Disk identifier: 0x00000000
    Device Boot Start End Blocks Id System
    /dev/mmcblk0p1 2 3522 7778304 b W95 FAT32
    Fstab as it stands now -
    /etc/fstab: static file system information
    (cut out irrelevant lines about tmpfs & commented out optical devices)
    /dev/mapper/vg0-lv_home /home ext3 defaults,noatime 0 1
    /dev/mapper/vg0-lv_root / ext3 defaults,noatime 0 1
    /dev/mapper/vg0-lv_swap swap swap defaults,noatime 0 0
    /dev/mapper/vg0-lv_var /var ext3 defaults,noatime 0 1
    UUID=a7d625c6-0fb9-41f5-bdba-6d306c90739a /boot ext2 defaults 0 1
    UUID=a802d8f4-f70e-4ed5-ab72-65bb0ebdca9b /media/sandbox ext3 defaults,users,noatime 1 2
    ## Memory card at /dev/mmcblk0p1 /media/memorycard
    UUID=238db34b-8bf3-4510-b8ee-1aa46e04f17d /media/memorycard vfat defaults,users,noauto,noatime 0 0
    The error I get when I issue a "mount -a" as root or just let the computer boot up with the "sandbox" in fstab -
    mount: special device UUID=a802d8f4-f70e-4ed5-ab72-65bb0ebdca9b does not exist

    Having the same problem with flash memory set as /dev/sdb1. It refuses to mount claiming the device doesn't exist.
    # /etc/fstab: static file system information
    # <file system> <dir> <type> <options> <dump> <pass>
    none /dev/pts devpts defaults 0 0
    none /dev/shm tmpfs defaults 0 0
    /dev/sda2 / reiserfs defaults,noatime 0 1
    /dev/sda1 /boot ext2 defaults,noatime 0 1
    /dev/sda3 swap swap defaults 0 0
    /dev/sdb1 /media/flash auto ro,user,noauto,unhide 0 0
    /dev/cdrom /media/cdrom auto ro,user,noauto,unhide 0 0
    /dev/dvd /media/dvd auto ro,user,noauto,unhide 0 0
    P.S.
    Yuuhuuuuu post #600

  • Printing quality problem

    We spend incredible amount of time to find out how to how to make
    reliable print from EXE done in LV6.0.2 under W9x,WinNT, W2K. But we
    have no solution.
    First we used direct print VI panel, after VI competition, but there
    are many problems with it. Then we left it and switched to report
    generation, now we are at the same situation.
    -Report generation does under WinNT and W2K different size of report
    on printer printout, NI-support suggest: LET USE W98.
    -Using W98, printing on printer with page format A4, EXE crashed.
    NI-support
    suggest: LET USE WinNT,W2K
    -Another problem: after printing to printer, the memory space used by
    LV is growing while using report generation VIs after every print even
    though I closed report reference. Each print make
    app. or LV allocated
    memory 3 MB higher. The newly allocated memory is no more released and
    all VI's are after 3to 5 printouts really slow.
    Seems to me probably nobody is using report generation VI's, because
    there is no way to use it.
    Seems to me also, that the only way (but painful) how to print from
    LV6.0.2 is the same, which exists since LV4 - print panel after
    competition (the same solution as 4 years ago...). Even this solution
    is really bad under W98 printing to HP printers - we can see very
    often that EXE crashed after printing, or sometimes fonts have correct
    size and sometimes not.
    The only reliable way is: using VI server function, generate
    physically BMP file on hard disk and then this BMP print out using
    paint.exe(MS-paintbrush). Printouts are reliable, but because of
    generated BMP they look like from ZX Spectrum or Atari age. Also we
    can generate HTML physically to HDD, but there is no way how to ensure
    the same size of each item on print (HTML <-> MSexplorer problem)
    , so
    it is unusable. Also unusable is to force customer to buy and use
    MS-word to be able print from our application done in LabVIEW.
    Maybe we are doing something wrong, but we cannot to find the problem.
    Thanks for any help.

    I don't have any complaints about printing from LV - well, not many, anyway.
    First things first - there is a known bug in the 'Print Panel at Completion' method of printing, under LV6.0.2, when running under Win95/98. It involves LV not releasing resources, causes font corruption, and ultimately an assert/crash. It DOES NOT happen under WinNT/2K. If you MUST run W95/98, you can specify 'bitmap printing' as a workaround, but this is very slow.
    Apart from that, I have generally excellent results using print on completion under LV6, usually to an HP LaserJet. A few things I've learned:
    1) Disable scaling in the VI print setup - this just confuses things. Size the objects on the VI panel to fit the printable area (LV uses 72 pixels/inch).
    2) Create
    the 'print on completion' VI as something that is never shown onscreen - don't try to make one VI do onscreen presentation and printing.
    3) Paint the background of the printing VI white.
    4) If you drop a graphic on the printing VI's FP (like a company logo), get a BIG, high res image. After pasting it, shrink/resize it w/in LV. When it prints, the full resolution is retained and used.
    5) Paint control/indicator frames and 'stuff' either white or transparent. These things can really clutter the printed results.
    Hope this helps - I've used this method to produce some really sharp test reports, certificates of conformance, etc.
    Regards,
    Dave
    David Boyd
    Sr. Test Engineer
    Philips Respironics
    Certified LabVIEW Developer

  • [SOLVED, kind of] UEFI bootable USB from ISO doesn't start

    Hi there,
    out of curiosity I wanted to create an UEFI bootable usb stick with the latest Archiso 2013.01.04. I've followed https://wiki.archlinux.org/index.php/UE … B_from_ISO
    and created two directories
    # mkdir -p /mnt/{usb,iso}
    Then I've mounted Archiso to /mnt/iso
    # mount -o loop Download/ISO-Images/archlinux-2013.01.04-dual.iso /mnt/iso
    After this I used cfdisk to create a FAT32 filesystem /dev/sdb1 on the usb stick, followed by
    # awk 'BEGIN {FS="="} /archisolabel/ {print $3}' /mnt/iso/loader/entries/archiso-x86_64.conf | xargs mkfs.vfat /dev/sdb1 -n
    Then I've mounted /dev/sdb1 to /mnt/usb and copied all iso-files there:
    # mount /dev/sdb1 /mnt/usb
    # cp -r /mnt/iso/* /mnt/usb
    Followed by:
    # umount /mnt/{usb,iso}
    # sync
    After rebooting and hitting F11 I was presented with the UEFI firmware-tool from which I can choose UEFI (and other) applications to start. I could choose my usb stick in UEFI mode, but - only the screen turned blank for the blink of a second and the UEFI tool was on again.
    Because my system is already booting in UEFI mode using rEFInd, I wanted to try rEFInd on the usb stick instead of gummiboot.
    Following https://wiki.archlinux.org/index.php/UE … B_from_ISO I've copied /usr/lib/refind/refind_x64.efi (from refind-efi 0.6.4-1) to /mnt/usb/EFI/boot/bootx64.efi and created a /mnt/usb/EFI/boot/refind.conf with this text:
    timeout 5
    textonly
    showtools about,reboot,shutdown,exit
    # scan_driver_dirs EFI/tools/drivers_x64
    scanfor manual,internal,external,optical
    scan_delay 1
    dont_scan_dirs EFI/boot
    max_tags 0
    default_selection "Arch Linux Archiso x86_64 UEFI USB"
    menuentry "Arch Linux Archiso x86_64 UEFI USB" {
      loader /arch/boot/x86_64/vmlinuz
      initrd /arch/boot/x86_64/archiso.img
      ostype Linux
      graphics off
      options "pci=nocrs add_efi_memmap archisobasedir=arch archisolabel=ARCH_201301"
    menuentry "UEFI x86_64 Shell v2" {
      loader /EFI/shellx64_v2.efi
      graphics off
    menuentry "UEFI x86_64 Shell v1" {
      loader /EFI/shellx64_v1.efi
      graphics off
    And yes, I've checked the "loader" and "initrd"-Paths - they are correct, as well as the archisolabel
    But - again - after rebooting and hitting F11 I could select my usb stick as UEFI boot device, but all that happened was the screen going blank for the glimpse of a second and returning to the UEFI chooser.
    Even my last attempt - keeping the original name refind_x64.efi in /mnt/usb/EFI/boot didn't help.
    Via efibootmgr I can see:
    $ sudo efibootmgr
    BootCurrent: 0001
    Timeout: 5 seconds
    BootOrder: 0001,0002,0007,0005,0006
    Boot0001* rEFInd 0.6.4-1
    Boot0002* rEFInd_recover
    Boot0005* Hard Drive
    Boot0006* USB
    Boot0007* UEFI: TOSHIBA TransMemory PMAP
    with "Boot0007" as my usb stick.
    So my question is: Did I miss something or have I found a bug ?
    Last edited by swordfish (2013-01-13 12:43:33)

    Hm, funny thing - now it's working, but I don't know why
    I've tried to convert the partition table of the usb stick from MBR to GPT using cgdisk. There I had a problem with setting the partition type to EF00. It worked under cgdisk, but then I couldn't mount my usb stick (dev/sdb1) anymore to /mnt/usb. Then I've tried to set the partition type to vfat, but couldn't identify what is vfat under cgdisk . I've tried different types of "Windows" but whatever I tried, the usb stick won't mount on /mnt/usb.
    Journalctl always says:
    Jan 13 12:23:03 sushi sudo[727]: nihonto : TTY=pts/0 ; PWD=/home/nihonto ; USER=root ; COMMAND=/usr/bin/cgdisk /dev/sdb
    Jan 13 12:23:03 sushi sudo[727]: pam_unix(sudo:session): session opened for user root by nihonto(uid=0)
    Jan 13 12:23:11 sushi sudo[727]: pam_unix(sudo:session): session closed for user root
    Jan 13 12:24:00 sushi su[972]: (to root) nihonto on /dev/pts/0
    Jan 13 12:24:00 sushi su[972]: pam_unix(su:session): session opened for user root by nihonto(uid=1000)
    Jan 13 12:24:18 sushi kernel: loop: module loaded
    Jan 13 12:24:18 sushi kernel: ISO 9660 Extensions: RRIP_1991A
    Jan 13 12:24:35 sushi kernel: EXT4-fs (sdb1): VFS: Can't find ext4 filesystem
    Jan 13 12:24:35 sushi kernel: EXT4-fs (sdb1): VFS: Can't find ext4 filesystem
    Jan 13 12:24:35 sushi kernel: EXT4-fs (sdb1): VFS: Can't find ext4 filesystem
    Jan 13 12:24:35 sushi kernel: FAT-fs (sdb1): bogus number of reserved sectors
    Jan 13 12:24:35 sushi kernel: FAT-fs (sdb1): Can't find a valid FAT filesystem
    Jan 13 12:24:35 sushi kernel: ISOFS: Unable to identify CD-ROM format.
    So I tried it again with cfdisk which nagged about "unsupported GPT" but kept working. This time I choose "0C W95 FAT32 (LBA)" as partition type - maybe this did the trick because in my earlier attempts I did choose "0B W95 FAT32".
    Anyway - after following the advice stated in https://wiki.archlinux.org/index.php/UE … B_from_ISO and installing rEFInd to the usb stick I could boot the usb stick in UEFI mode
    But - as I said earlier - I don't know what did the trick
    Last edited by swordfish (2013-01-13 12:38:18)

  • Cannot install GRUB.

    "parted" shows my partition table as follows:
    Number Start End Size Type File system Flags
    1 1049kB 106MB 105MB primary ntfs boot
    2 106MB 64.9GB 64.8GB primary ntfs
    4 64.9GB 456GB 391GB extended lba
    8 64.9GB 96.3GB 31.4GB logical ext4
    9 96.3GB 101GB 4277MB logical linux-swap(v1)
    7 101GB 105GB 4273MB logical linux-swap(v1)
    5 105GB 327GB 222GB logical ntfs
    6 327GB 456GB 129GB logical ntfs
    3 456GB 500GB 44.4GB primary ext4
    While fdisk shows my partition table as follows:
    Device Boot Start End Blocks Id System
    /dev/sda1 * 2048 206847 102400 7 HPFS/NTFS/exFAT
    /dev/sda2 206848 126852290 63322721+ 7 HPFS/NTFS/exFAT
    /dev/sda3 890126748 976772663 43322958 7 HPFS/NTFS/exFAT
    /dev/sda4 126853118 890123492 381635187+ f W95 Ext'd (LBA)
    /dev/sda5 204812685 638648009 216917662+ 7 HPFS/NTFS/exFAT
    /dev/sda6 638648073 890123492 125737710 7 HPFS/NTFS/exFAT
    /dev/sda7 196450304 204795903 4172800 82 Linux swap / Solaris
    /dev/sda8 126853120 188086271 30616576 83 Linux
    /dev/sda9 188088320 196442111 4176896 82 Linux swap / Solaris
    Partition table entries are not in disk order
    I have two linux partition installed at
    /dev/sda3 -> Arch Liuxx
    /dev/sda8 -> Ubuntu.
    GRUB is installed at ubuntu (version 2 grub).
    - First of all, why is fdisk not able to detect a ext4 partition. It only shows one partition as Linux ie /dev/sda8.
    - When I try to install grub by booting to live CD and I type $root (hd0,3), it shows unknown partition 0xf. Even if I use tabs to do autocomplete, I get this
    grub> root (hd0,
    Possible partitions are:
    Partition num: 0, Filesystem type unknown, partition type 0x7
    Partition num: 1, Filesystem type unknown, partition type 0x7
    Partition num: 2, Filesystem type unknown, partition type 0x7
    Partition num: 4, Filesystem type unknown, partition type 0x7
    Partition num: 5, Filesystem type unknown, partition type 0x7
    Partition num: 6, Filesystem type unknown, partition type 0x82
    Partition num: 7, Filesystem type is ext2fs, partition type 0x83
    Partition num: 8, Filesystem type unknown, partition type 0x82
    grub> root (hd0,
    God  knows why it shows partition number 7 as ext2fs. I cannot choose either 8 or 3 partition
    grub> root (hd0,3)
    Filesystem type unknown, partition type 0xf
    grub> root (hd0,8)
    Filesystem type unknown, partition type 0x82
    Also, I need to install grub on /dev/sda3 (my arch linux partition) which is currently on UBUNTU's partition so its also not able to find any boot files if I try to mount arch partition and do $root-install --root-directory=/mnt/myarchmounted --recheck /dev/sda.
    So, how should I proceed?
    TL/DR: I want a way to
    - Format ubuntu partition and remove it completely (including its own grub)
    - Install GRUB on Arch's partition, so that I can boot it after ubuntu's partition is removed.

    shadyabhi wrote:
    "parted" shows my partition table as follows:
    Number Start End Size Type File system Flags
    1 1049kB 106MB 105MB primary ntfs boot
    2 106MB 64.9GB 64.8GB primary ntfs
    4 64.9GB 456GB 391GB extended lba
    8 64.9GB 96.3GB 31.4GB logical ext4
    9 96.3GB 101GB 4277MB logical linux-swap(v1)
    7 101GB 105GB 4273MB logical linux-swap(v1)
    5 105GB 327GB 222GB logical ntfs
    6 327GB 456GB 129GB logical ntfs
    3 456GB 500GB 44.4GB primary ext4
    While fdisk shows my partition table as follows:
    Device Boot Start End Blocks Id System
    /dev/sda1 * 2048 206847 102400 7 HPFS/NTFS/exFAT
    /dev/sda2 206848 126852290 63322721+ 7 HPFS/NTFS/exFAT
    /dev/sda3 890126748 976772663 43322958 7 HPFS/NTFS/exFAT
    /dev/sda4 126853118 890123492 381635187+ f W95 Ext'd (LBA)
    /dev/sda5 204812685 638648009 216917662+ 7 HPFS/NTFS/exFAT
    /dev/sda6 638648073 890123492 125737710 7 HPFS/NTFS/exFAT
    /dev/sda7 196450304 204795903 4172800 82 Linux swap / Solaris
    /dev/sda8 126853120 188086271 30616576 83 Linux
    /dev/sda9 188088320 196442111 4176896 82 Linux swap / Solaris
    Partition table entries are not in disk order
    I have two linux partition installed at
    /dev/sda3 -> Arch Liuxx
    /dev/sda8 -> Ubuntu.
    GRUB is installed at ubuntu (version 2 grub).
    - First of all, why is fdisk not able to detect a ext4 partition. It only shows one partition as Linux ie /dev/sda8.
    Type code of /dev/sda3 is wrong, it should be 0x83, not 0x07 (type code for FAT/NTFS partitions)
    - When I try to install grub by booting to live CD and I type $root (hd0,3), it shows unknown partition 0xf. Even if I use tabs to do autocomplete, I get this
    grub legacy numbers partitions from 0 , wherein (hd0,3) corresponds to /dev/sda4 (the extended partition in your disk). IN your case you should try (hd0,2) for /dev/sda3 (after changing the part type code to 0x83)
    God  knows why it shows partition number 7 as ext2fs. I cannot choose either 8 or 3 partition
    grub> root (hd0,3)
    Filesystem type unknown, partition type 0xf
    grub> root (hd0,8)
    Filesystem type unknown, partition type 0x82
    (hd0,7) == /dev/sda8 == ext4
    (hd0,3) == /dev/sda4 == extended part
    (hd0,8) == /dev/sda9 == linux swap
    Also, I need to install grub on /dev/sda3 (my arch linux partition) which is currently on UBUNTU's partition so its also not able to find any boot files if I try to mount arch partition and do $root-install --root-directory=/mnt/myarchmounted --recheck /dev/sda.
    So, how should I proceed?
    TL/DR: I want a way to
    - Format ubuntu partition and remove it completely (including its own grub)
    - Install GRUB on Arch's partition, so that I can boot it after ubuntu's partition is removed.
    Your question is not clear. But you can boot into Arch, install its grub2 package (recommended over grub legacy), install grub2 to /boot in Arch, and finally format ubuntu completely. Follow the Archwiki GRUB2 page. It explains everything.

  • Problem with USB External Hard Disk Drive

    I have similar problem with hard disk MK6025GAS in Sweex casing connected via USB as Raistlfiren in this post but I am not sure if it has something to do with kernel. The problem is that when I plug the hard disk via USB it is not even shown with in /dev/ or by fdisk -l. I had similar problems with the drive before but it was always shown in /dev.
    I got same output from dmesg as Raistlfiren in the post before
    # dmesg | tail
    sd 4:0:0:0: [sdd] ASC=0x0 ASCQ=0x0
    sd 4:0:0:0: [sdd] Sense Key : 0x0 [current]
    Info fld=0x0
    I was browsing net for a lot of time to find a solution but nothing helped a lot. The problem is closes to the one described on Gentoo Forum
    I can see that it is recognized by computer since it is shown with lsusb
    # lsusb
    Bus 001 Device 005: ID 13fd:0540 Initio Corporation
    # lsusb -d 13fd:0540 -v
    Bus 001 Device 005: ID 13fd:0540 Initio Corporation
    Device Descriptor:
    bLength 18
    bDescriptorType 1
    bcdUSB 2.00
    bDeviceClass 0 (Defined at Interface level)
    bDeviceSubClass 0
    bDeviceProtocol 0
    bMaxPacketSize0 64
    idVendor 0x13fd Initio Corporation
    idProduct 0x0540
    bcdDevice 0.00
    iManufacturer 1 Initio
    iProduct 2 MK6025GAS
    iSerial 3 0010100500000000
    bNumConfigurations 1
    Configuration Descriptor:
    bLength 9
    bDescriptorType 2
    wTotalLength 32
    bNumInterfaces 1
    bConfigurationValue 1
    iConfiguration 0
    bmAttributes 0xc0
    Self Powered
    MaxPower 2mA
    Interface Descriptor:
    bLength 9
    bDescriptorType 4
    bInterfaceNumber 0
    bAlternateSetting 0
    bNumEndpoints 2
    bInterfaceClass 8 Mass Storage
    bInterfaceSubClass 6 SCSI
    bInterfaceProtocol 80 Bulk (Zip)
    iInterface 0
    Endpoint Descriptor:
    bLength 7
    bDescriptorType 5
    bEndpointAddress 0x81 EP 1 IN
    bmAttributes 2
    Transfer Type Bulk
    Synch Type None
    Usage Type Data
    wMaxPacketSize 0x0200 1x 512 bytes
    bInterval 0
    Endpoint Descriptor:
    bLength 7
    bDescriptorType 5
    bEndpointAddress 0x02 EP 2 OUT
    bmAttributes 2
    Transfer Type Bulk
    Synch Type None
    Usage Type Data
    wMaxPacketSize 0x0200 1x 512 bytes
    bInterval 1
    Device Qualifier (for other device speed):
    bLength 10
    bDescriptorType 6
    bcdUSB 2.00
    bDeviceClass 0 (Defined at Interface level)
    bDeviceSubClass 0
    bDeviceProtocol 0
    bMaxPacketSize0 64
    bNumConfigurations 1
    Device Status: 0x0001
    Self Powered
    From the beginning I though and I still think that the partition table is screwed up but the programs like TestDisk and fixdisktable work only with disks shown in /dev/
    Additionally, I have checked the content of /var/log/kernel.log
    Sep 16 22:03:58 hramat kernel: usb 1-2: new high speed USB device using ehci_hcd and address 5
    Sep 16 22:03:58 hramat kernel: usb 1-2: configuration #1 chosen from 1 choice
    Sep 16 22:03:58 hramat kernel: scsi4 : SCSI emulation for USB Mass Storage devices
    Sep 16 22:03:58 hramat kernel: usb-storage: device found at 5
    Sep 16 22:03:58 hramat kernel: usb-storage: waiting for device to settle before scanning
    Sep 16 22:04:03 hramat kernel: scsi 4:0:0:0: Direct-Access Initio MK6025GAS 2.23 PQ: 0 ANSI: 0
    Sep 16 22:04:03 hramat kernel: sd 4:0:0:0: Attached scsi generic sg4 type 0
    Sep 16 22:04:03 hramat kernel: usb-storage: device scan complete
    Sep 16 22:04:03 hramat kernel: sd 4:0:0:0: [sdd] 117210240 512-byte hardware sectors: (60.0 GB/55.8 GiB)
    Sep 16 22:04:03 hramat kernel: sd 4:0:0:0: [sdd] Write Protect is off
    Sep 16 22:04:03 hramat kernel: sd 4:0:0:0: [sdd] Mode Sense: 86 0b 00 02
    Sep 16 22:04:03 hramat kernel: sd 4:0:0:0: [sdd] Assuming drive cache: write through
    Sep 16 22:04:03 hramat kernel: sd 4:0:0:0: [sdd] Assuming drive cache: write through
    Sep 16 22:04:03 hramat kernel: sdd:<6>sd 4:0:0:0: [sdd] Sense Key : 0x0 [current]
    Sep 16 22:04:03 hramat kernel: Info fld=0x0
    Sep 16 22:04:03 hramat kernel: sd 4:0:0:0: [sdd] ASC=0x0 ASCQ=0x0
    Sep 16 22:04:03 hramat kernel: sd 4:0:0:0: [sdd] Sense Key : 0x0 [current]
    and /var/log/errors.log
    Sep 16 22:04:03 hramat kernel: sd 4:0:0:0: [sdd] Assuming drive cache: write through
    Sep 16 22:04:03 hramat kernel: sd 4:0:0:0: [sdd] Assuming drive cache: write through
    Sep 16 22:07:35 hramat kernel: INFO: task async/0:3957 blocked for more than 120 seconds.
    Sep 16 22:07:35 hramat kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
    The only thing I understand from these logs is that the disk is blocked, therefore not listed in /dev.
    Assuming the newer kernel problems I could try to use some older live linux CD to see if that would work. I am also thinking of connecting this hard drive directly to my laptop, using live linux CD and maybe check the output of hdparm. Is there anything else I could check or try?
    Thank you for any help or suggestions
    Matej

    Thank you nTia89 for response. Sorry for not providing enough information.
    I believe the problem is not system dependent. I have dual boot with windows and there the disk has also problems. However, I do have Arch32 with Kernel 2.6.30, using Gnome. hal and dbus are also running.
    I did not tried to connect the disk to the computer directly, I will try it today.
    Yesterday I have used SystemRescueCD 0.4.1 with Kernel 2.6.22. I wanted to see if it will be recognized by the system and placed in /dev/. Yes it was. This means that the problem highlighted in Gentoo forum can be true, but it doesn't solve my problem. I have tried to connect the drive several times to Arch and it was not shown in /dev/sd*, in SystemRescueCD it was placed as /dev/sdb. Now I am sure that the partition table is screwed up.
    So I have started to play with the drive in SystemRescueCD with TestDisk and FixDiskTable but without success.
    % fdisk -l
    Disk /dev/sda: 100.0 GB, 100030242816 bytes
    255 heads, 63 sectors/track, 12161 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Device Boot Start End Blocks Id System
    /dev/sda1 * 1 1530 12289693+ 7 HPFS/NTFS
    /dev/sda2 1531 6672 41303115 7 HPFS/NTFS
    /dev/sda3 6673 12161 44090392+ f W95 Ext'd (LBA)
    /dev/sda5 * 6673 11908 42058138+ 83 Linux
    /dev/sda6 11909 12161 2032191 82 Linux swap / Solaris
    Disk /dev/sdb: 60.0 GB, 60011642880 bytes
    64 heads, 32 sectors/track, 57231 cylinders
    Units = cylinders of 2048 * 512 = 1048576 bytes
    Disk /dev/sdb doesn't contain a valid partition table
    Manufacturer disk geometry: Heads: 16; Cylinders: 16383; Sectors: 63; Logical Blocks (LBA): 117210240
    TestDisk found only Linux partitions with 43Gb while disk had only one 60Gb partitioned with FAT32/NTFS.
    Also recognized 64 heads, 57231 cylinders and 32 sectors (same as from fdisk -l), which obviously differs from manufacturer disk geometry.
    testdisk.log:
    Thu Sep 17 19:09:26 2009
    Command line: TestDisk
    TestDisk 6.8, Data Recovery Utility, August 2007
    Christophe GRENIER
    Linux version (ext2fs lib: 1.40.2, ntfs lib: 9:0:0, reiserfs lib: 0.3.1-rc8, ewf lib: none)
    Using locale 'C'.
    Hard disk list
    Disk /dev/sda - 100 GB / 93 GiB - CHS 12161 255 63, sector size=512
    Disk /dev/sdb - 60 GB / 55 GiB - CHS 57231 64 32, sector size=512
    Disk /dev/sdb - 60 GB / 55 GiB
    Partition table type: Intel
    Interface Advanced
    New options :
    Dump : No
    Cylinder boundary : Yes
    Allow partial last cylinder : No
    Expert mode : No
    Analyse Disk /dev/sdb - 60 GB / 55 GiB - CHS 57231 64 32
    Current partition structure:
    Partition sector doesn't have the endmark 0xAA55
    Ask the user for vista mode
    Computes LBA from CHS for Disk /dev/sdb - 60 GB / 55 GiB - CHS 57232 64 32
    Allow partial last cylinder : Yes
    search_vista_part: 1
    search_part()
    Disk /dev/sdb - 60 GB / 55 GiB - CHS 57232 64 32
    Search for partition aborted
    Results
    interface_write()
    No partition found or selected for recovery
    search_part()
    Disk /dev/sdb - 60 GB / 55 GiB - CHS 57232 64 32
    Search for partition aborted
    Results
    interface_write()
    No partition found or selected for recovery
    simulate write!
    write_mbr_i386: starting...
    Store new MBR code
    write_all_log_i386: starting...
    No extended partition
    Analyse Disk /dev/sdb - 60 GB / 55 GiB - CHS 57232 64 32
    Current partition structure:
    Partition sector doesn't have the endmark 0xAA55
    Ask the user for vista mode
    Allow partial last cylinder : Yes
    search_vista_part: 1
    search_part()
    Disk /dev/sdb - 60 GB / 55 GiB - CHS 57232 64 32
    Results
    interface_write()
    No partition found or selected for recovery
    search_part()
    Disk /dev/sdb - 60 GB / 55 GiB - CHS 57232 64 32
    NTFS at 8956/63/32
    heads/cylinder 255 (NTFS) != 64 (HD)
    sect/track 63 (NTFS) != 32 (HD)
    filesystem size 24579387
    sectors_per_cluster 8
    mft_lcn 1024141
    mftmirr_lcn 1650676
    clusters_per_mft_record -10
    clusters_per_index_record 1
    NTFS part_offset=9392094720, part_size=12584646144, sector_size=512
    NTFS partition cannot be added (part_offset<part_size).
    recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
    recover_EXT2: boot_sector=0, s_blocksize=4096
    recover_EXT2: s_blocks_count 10514534
    recover_EXT2: part_size 84116272
    D Linux 34129 1 1 75201 26 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    This partition ends after the disk limits. (start=69896224, size=84116272, end=154012495, disk end=117211136)
    recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
    recover_EXT2: boot_sector=0, s_blocksize=4096
    recover_EXT2: s_blocks_count 10514534
    recover_EXT2: part_size 84116272
    D Linux 34632 2 1 75704 27 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    This partition ends after the disk limits. (start=70926400, size=84116272, end=155042671, disk end=117211136)
    recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
    recover_EXT2: boot_sector=0, s_blocksize=4096
    recover_EXT2: s_blocks_count 10514534
    recover_EXT2: part_size 84116272
    D Linux 34668 0 1 75740 25 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    This partition ends after the disk limits. (start=71000064, size=84116272, end=155116335, disk end=117211136)
    recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
    recover_EXT2: boot_sector=0, s_blocksize=4096
    recover_EXT2: s_blocks_count 10514534
    recover_EXT2: part_size 84116272
    D Linux 34673 1 1 75745 26 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    This partition ends after the disk limits. (start=71010336, size=84116272, end=155126607, disk end=117211136)
    recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
    recover_EXT2: boot_sector=0, s_blocksize=4096
    recover_EXT2: s_blocks_count 10514534
    recover_EXT2: part_size 84116272
    D Linux 34699 2 1 75771 27 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    This partition ends after the disk limits. (start=71063616, size=84116272, end=155179887, disk end=117211136)
    recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
    recover_EXT2: boot_sector=0, s_blocksize=4096
    recover_EXT2: s_blocks_count 10514534
    recover_EXT2: part_size 84116272
    D Linux 34708 2 1 75780 27 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    This partition ends after the disk limits. (start=71082048, size=84116272, end=155198319, disk end=117211136)
    recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
    recover_EXT2: boot_sector=0, s_blocksize=4096
    recover_EXT2: s_blocks_count 10514534
    recover_EXT2: part_size 84116272
    D Linux 36338 0 1 77410 25 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    This partition ends after the disk limits. (start=74420224, size=84116272, end=158536495, disk end=117211136)
    recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
    recover_EXT2: boot_sector=0, s_blocksize=4096
    recover_EXT2: s_blocks_count 10514534
    recover_EXT2: part_size 84116272
    D Linux 36367 0 1 77439 25 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    This partition ends after the disk limits. (start=74479616, size=84116272, end=158595887, disk end=117211136)
    recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
    recover_EXT2: boot_sector=0, s_blocksize=4096
    recover_EXT2: s_blocks_count 10514534
    recover_EXT2: part_size 84116272
    D Linux 36401 2 1 77473 27 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    This partition ends after the disk limits. (start=74549312, size=84116272, end=158665583, disk end=117211136)
    recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
    recover_EXT2: boot_sector=0, s_blocksize=4096
    recover_EXT2: s_blocks_count 10514534
    recover_EXT2: part_size 84116272
    D Linux 36414 2 1 77486 27 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    This partition ends after the disk limits. (start=74575936, size=84116272, end=158692207, disk end=117211136)
    recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
    recover_EXT2: boot_sector=0, s_blocksize=4096
    recover_EXT2: s_blocks_count 10514534
    recover_EXT2: part_size 84116272
    D Linux 37949 1 1 79021 26 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    This partition ends after the disk limits. (start=77719584, size=84116272, end=161835855, disk end=117211136)
    recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
    recover_EXT2: boot_sector=0, s_blocksize=4096
    recover_EXT2: s_blocks_count 10514534
    recover_EXT2: part_size 84116272
    D Linux 37955 1 1 79027 26 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    This partition ends after the disk limits. (start=77731872, size=84116272, end=161848143, disk end=117211136)
    recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
    recover_EXT2: boot_sector=0, s_blocksize=4096
    recover_EXT2: s_blocks_count 10514534
    recover_EXT2: part_size 84116272
    D Linux 37989 1 1 79061 26 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    This partition ends after the disk limits. (start=77801504, size=84116272, end=161917775, disk end=117211136)
    recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
    recover_EXT2: boot_sector=0, s_blocksize=4096
    recover_EXT2: s_blocks_count 10514534
    recover_EXT2: part_size 84116272
    D Linux 38404 0 1 79476 25 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    This partition ends after the disk limits. (start=78651392, size=84116272, end=162767663, disk end=117211136)
    recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
    recover_EXT2: boot_sector=0, s_blocksize=4096
    recover_EXT2: s_blocks_count 10514534
    recover_EXT2: part_size 84116272
    D Linux 39636 2 1 80708 27 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    This partition ends after the disk limits. (start=81174592, size=84116272, end=165290863, disk end=117211136)
    recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
    recover_EXT2: boot_sector=0, s_blocksize=4096
    recover_EXT2: s_blocks_count 10514534
    recover_EXT2: part_size 84116272
    D Linux 41263 1 1 82335 26 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    This partition ends after the disk limits. (start=84506656, size=84116272, end=168622927, disk end=117211136)
    recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
    recover_EXT2: boot_sector=0, s_blocksize=4096
    recover_EXT2: s_blocks_count 10514534
    recover_EXT2: part_size 84116272
    D Linux 41266 1 1 82338 26 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    This partition ends after the disk limits. (start=84512800, size=84116272, end=168629071, disk end=117211136)
    recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
    recover_EXT2: boot_sector=0, s_blocksize=4096
    recover_EXT2: s_blocks_count 10514534
    recover_EXT2: part_size 84116272
    D Linux 41660 0 1 82732 25 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    This partition ends after the disk limits. (start=85319680, size=84116272, end=169435951, disk end=117211136)
    recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
    recover_EXT2: boot_sector=0, s_blocksize=4096
    recover_EXT2: s_blocks_count 10514534
    recover_EXT2: part_size 84116272
    D Linux 42898 0 1 83970 25 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    This partition ends after the disk limits. (start=87855104, size=84116272, end=171971375, disk end=117211136)
    recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
    recover_EXT2: boot_sector=0, s_blocksize=4096
    recover_EXT2: s_blocks_count 10514534
    recover_EXT2: part_size 84116272
    D Linux 43244 1 1 84316 26 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    This partition ends after the disk limits. (start=88563744, size=84116272, end=172680015, disk end=117211136)
    recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
    recover_EXT2: boot_sector=0, s_blocksize=4096
    recover_EXT2: s_blocks_count 10514534
    recover_EXT2: part_size 84116272
    D Linux 44870 2 1 85942 27 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    This partition ends after the disk limits. (start=91893824, size=84116272, end=176010095, disk end=117211136)
    recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
    recover_EXT2: boot_sector=0, s_blocksize=4096
    recover_EXT2: s_blocks_count 10514534
    recover_EXT2: part_size 84116272
    D Linux 44930 2 1 86002 27 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    This partition ends after the disk limits. (start=92016704, size=84116272, end=176132975, disk end=117211136)
    recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
    recover_EXT2: boot_sector=0, s_blocksize=4096
    recover_EXT2: s_blocks_count 10514534
    recover_EXT2: part_size 84116272
    D Linux 46961 0 1 88033 25 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    This partition ends after the disk limits. (start=96176128, size=84116272, end=180292399, disk end=117211136)
    recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
    recover_EXT2: boot_sector=0, s_blocksize=4096
    recover_EXT2: s_blocks_count 10514534
    recover_EXT2: part_size 84116272
    D Linux 47312 0 1 88384 25 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    This partition ends after the disk limits. (start=96894976, size=84116272, end=181011247, disk end=117211136)
    recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
    recover_EXT2: boot_sector=0, s_blocksize=4096
    recover_EXT2: s_blocks_count 10514534
    recover_EXT2: part_size 84116272
    D Linux 48393 2 1 89465 27 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    This partition ends after the disk limits. (start=99108928, size=84116272, end=183225199, disk end=117211136)
    recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
    recover_EXT2: boot_sector=0, s_blocksize=4096
    recover_EXT2: s_blocks_count 10514534
    recover_EXT2: part_size 84116272
    D Linux 49633 2 1 90705 27 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    This partition ends after the disk limits. (start=101648448, size=84116272, end=185764719, disk end=117211136)
    recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
    recover_EXT2: boot_sector=0, s_blocksize=4096
    recover_EXT2: s_blocks_count 10514534
    recover_EXT2: part_size 84116272
    D Linux 50767 1 1 91839 26 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    This partition ends after the disk limits. (start=103970848, size=84116272, end=188087119, disk end=117211136)
    recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
    recover_EXT2: boot_sector=0, s_blocksize=4096
    recover_EXT2: s_blocks_count 10514534
    recover_EXT2: part_size 84116272
    D Linux 51150 1 1 92222 26 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    This partition ends after the disk limits. (start=104755232, size=84116272, end=188871503, disk end=117211136)
    recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
    recover_EXT2: boot_sector=0, s_blocksize=4096
    recover_EXT2: s_blocks_count 10514534
    recover_EXT2: part_size 84116272
    D Linux 51941 1 1 93013 26 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    This partition ends after the disk limits. (start=106375200, size=84116272, end=190491471, disk end=117211136)
    recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
    recover_EXT2: boot_sector=0, s_blocksize=4096
    recover_EXT2: s_blocks_count 10514534
    recover_EXT2: part_size 84116272
    D Linux 52759 0 1 93831 25 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    This partition ends after the disk limits. (start=108050432, size=84116272, end=192166703, disk end=117211136)
    recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
    recover_EXT2: boot_sector=0, s_blocksize=4096
    recover_EXT2: s_blocks_count 10514534
    recover_EXT2: part_size 84116272
    D Linux 53069 1 1 94141 26 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    This partition ends after the disk limits. (start=108685344, size=84116272, end=192801615, disk end=117211136)
    recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
    recover_EXT2: boot_sector=0, s_blocksize=4096
    recover_EXT2: s_blocks_count 10514534
    recover_EXT2: part_size 84116272
    D Linux 53768 0 1 94840 25 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    This partition ends after the disk limits. (start=110116864, size=84116272, end=194233135, disk end=117211136)
    recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
    recover_EXT2: boot_sector=0, s_blocksize=4096
    recover_EXT2: s_blocks_count 10514534
    recover_EXT2: part_size 84116272
    D Linux 54287 0 1 95359 25 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    This partition ends after the disk limits. (start=111179776, size=84116272, end=195296047, disk end=117211136)
    recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
    recover_EXT2: boot_sector=0, s_blocksize=4096
    recover_EXT2: s_blocks_count 10514534
    recover_EXT2: part_size 84116272
    D Linux 54493 2 1 95565 27 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    This partition ends after the disk limits. (start=111601728, size=84116272, end=195717999, disk end=117211136)
    recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
    recover_EXT2: boot_sector=0, s_blocksize=4096
    recover_EXT2: s_blocks_count 10514534
    recover_EXT2: part_size 84116272
    D Linux 54861 1 1 95933 26 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    This partition ends after the disk limits. (start=112355360, size=84116272, end=196471631, disk end=117211136)
    recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
    recover_EXT2: boot_sector=0, s_blocksize=4096
    recover_EXT2: s_blocks_count 10514534
    recover_EXT2: part_size 84116272
    D Linux 54890 2 1 95962 27 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    This partition ends after the disk limits. (start=112414784, size=84116272, end=196531055, disk end=117211136)
    recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
    recover_EXT2: boot_sector=0, s_blocksize=4096
    recover_EXT2: s_blocks_count 10514534
    recover_EXT2: part_size 84116272
    D Linux 54953 2 1 96025 27 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    This partition ends after the disk limits. (start=112543808, size=84116272, end=196660079, disk end=117211136)
    recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
    recover_EXT2: boot_sector=0, s_blocksize=4096
    recover_EXT2: s_blocks_count 10514534
    recover_EXT2: part_size 84116272
    D Linux 56330 1 1 97402 26 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    This partition ends after the disk limits. (start=115363872, size=84116272, end=199480143, disk end=117211136)
    recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
    recover_EXT2: boot_sector=0, s_blocksize=4096
    recover_EXT2: s_blocks_count 10514534
    recover_EXT2: part_size 84116272
    D Linux 56334 0 1 97406 25 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    This partition ends after the disk limits. (start=115372032, size=84116272, end=199488303, disk end=117211136)
    recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
    recover_EXT2: boot_sector=0, s_blocksize=4096
    recover_EXT2: s_blocks_count 10514534
    recover_EXT2: part_size 84116272
    D Linux 57203 0 1 98275 25 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    This partition ends after the disk limits. (start=117151744, size=84116272, end=201268015, disk end=117211136)
    Disk /dev/sdb - 60 GB / 55 GiB - CHS 57232 64 32
    Check the harddisk size: HD jumpers settings, BIOS detection...
    The harddisk (60 GB / 55 GiB) seems too small! (< 103 GB / 95 GiB)
    The following partitions can't be recovered:
    D Linux 34129 1 1 75201 26 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    D Linux 34632 2 1 75704 27 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    D Linux 34668 0 1 75740 25 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    D Linux 34673 1 1 75745 26 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    D Linux 34699 2 1 75771 27 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    D Linux 34708 2 1 75780 27 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    D Linux 36338 0 1 77410 25 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    D Linux 36367 0 1 77439 25 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    D Linux 36401 2 1 77473 27 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    D Linux 36414 2 1 77486 27 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    D Linux 37949 1 1 79021 26 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    D Linux 37955 1 1 79027 26 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    D Linux 37989 1 1 79061 26 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    D Linux 38404 0 1 79476 25 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    D Linux 39636 2 1 80708 27 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    D Linux 41263 1 1 82335 26 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    D Linux 41266 1 1 82338 26 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    D Linux 41660 0 1 82732 25 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    D Linux 42898 0 1 83970 25 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    D Linux 43244 1 1 84316 26 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    D Linux 44870 2 1 85942 27 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    D Linux 44930 2 1 86002 27 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    D Linux 46961 0 1 88033 25 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    D Linux 47312 0 1 88384 25 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    D Linux 48393 2 1 89465 27 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    D Linux 49633 2 1 90705 27 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    D Linux 50767 1 1 91839 26 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    D Linux 51150 1 1 92222 26 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    D Linux 51941 1 1 93013 26 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    D Linux 52759 0 1 93831 25 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    D Linux 53069 1 1 94141 26 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    D Linux 53768 0 1 94840 25 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    D Linux 54287 0 1 95359 25 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    D Linux 54493 2 1 95565 27 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    D Linux 54861 1 1 95933 26 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    D Linux 54890 2 1 95962 27 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    D Linux 54953 2 1 96025 27 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    D Linux 56330 1 1 97402 26 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    D Linux 56334 0 1 97406 25 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    D Linux 57203 0 1 98275 25 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    Results
    interface_write()
    No partition found or selected for recovery
    simulate write!
    write_mbr_i386: starting...
    Store new MBR code
    write_all_log_i386: starting...
    No extended partition
    Interface Advanced
    Disk /dev/sdb - 60 GB / 55 GiB
    Partition table type: Intel
    Disk /dev/sdb - 60 GB / 55 GiB
    Partition table type: Intel
    New options :
    Dump : No
    Cylinder boundary : Yes
    Allow partial last cylinder : No
    Expert mode : No
    New options :
    Dump : No
    Cylinder boundary : Yes
    Allow partial last cylinder : No
    Expert mode : No
    Analyse Disk /dev/sdb - 60 GB / 55 GiB - CHS 57232 64 32
    Current partition structure:
    Partition sector doesn't have the endmark 0xAA55
    Ask the user for vista mode
    Allow partial last cylinder : No
    search_vista_part: 0
    search_part()
    Disk /dev/sdb - 60 GB / 55 GiB - CHS 57232 64 32
    Search for partition aborted
    Results
    Can't open backup.log file: No such file or directory
    interface_load
    interface_write()
    No partition found or selected for recovery
    simulate write!
    write_mbr_i386: starting...
    Store new MBR code
    write_all_log_i386: starting...
    No extended partition
    TestDisk exited normally.
    fixdisktable first output:
    % ./fixdisktable -d /dev/sdb
    Getting hard disk geometry
    cylinders=57231, heads=64, sectors=32
    end_offset: 2147482624
    FfEeSsNnBbUuFfEeSsNnBbUuFfEeSsNnBbUuFfEeSsNnBbUuFfEeSsNnBbUuFfEeSsNnBbUuFfEeSsNnBbUuFfEeSs
    EXT2 partition at offset 56832, length=(41072.398 MB) 43067531264
    Sectors: start= 111, end= 84116382, length= 84116272
    Hd,Sec,Cyl: start(3,16,0) end(28,31,41072)
    Done searching for partitions.
    Nr AF Hd Sec Cyl Hd Sec Cyl Start Size ID
    1 80 3 16 0 63 32 1023 111 84116273 83 (Interpretted)
    1 80 3 16 0 63 224 255 111 84116273 83 (RAW)
    1: 8003 1000 833f e0ff 6f00 0000 3183 0305
    2: 0000 0000 0000 0000 0000 0000 0000 0000
    3: 0000 0000 0000 0000 0000 0000 0000 0000
    4: 0000 0000 0000 0000 0000 0000 0000 0000
    Do you wish to write this partition table to disk (yes/no)? no
    fixdisktable second output:
    % ./fixdisktable -d -r -v /dev/sdb
    Getting hard disk geometry
    cylinders=57231, heads=64, sectors=32
    end_offset: 2147482624
    FfEeSsNnBbUuFfEeSsNnBbUuFfEeSsNnBbUuFfEeSsNnBbUuFfEeSsNnBbUuFfEeSsNnBbUuFfEeSsNnBbUuFfEeSs
    NTFS partition at offset 17483776, length=(17592186043512.582 MB) 184467440727622 49216
    Sectors: start= 34148, end=36028797017147916, length=36028797017113768
    Hd,Sec,Cyl: start(43,5,16) end(16,12,2096265)
    Done searching for partitions.
    Nr AF Hd Sec Cyl Hd Sec Cyl Start Size ID
    1 80 43 5 16 63 32 1023 34148 -1850199 07 (Interpretted)
    1 80 43 5 16 63 224 255 34148 -1850199 07 (RAW)
    1: 802b 0510 073f e0ff 6485 0000 a9c4 e3ff
    2: 0000 0000 0000 0000 0000 0000 0000 0000
    3: 0000 0000 0000 0000 0000 0000 0000 0000
    4: 0000 0000 0000 0000 0000 0000 0000 0000
    Do you wish to write this partition table to disk (yes/no)? no
    This string "FfEeSsNnBbUu" was repeating there for longer time and it was most probably related to debugging or a verbose mode of fixdisktable
    As I have mentioned I will try to connect the disk directly to the computer and see what will happen.
    Shall I try to correct the disk geometry to the one specified by manufacturer? Is it possible?
    Any suggestions?

Maybe you are looking for

  • Webdynpro ABAP content authorization object in SAP portal ?

    Hi We are on EHP 6.06 , we have an authorization problem in sap portal for the webdynpro abap content. our standart users got the error "page can not be found" for the services provided from webdynpro abap. when I assign the user to administrator gro

  • Authorizations for Opportunity searches in CRM/EP?

    Need help restricting user results in Opportunity searches. Our authorizations scheme defines users by their sales group, but when doing searches in CRM/EP User 1 can see results for users 2 and 3 when doing an opportunity search which are defined ou

  • What does javaw do?

    What does javaw do. Does it let me run applications?

  • How to make the bookmark work within portal

    Dear all,   as we know, when we click bookmark button, the system will generate a url with bookmark id in the address bar. But within portal, since the query is only treated as an iview, the generated url will not display in the address bar.   anothe

  • DAQ Chat Support 'Beta' Program

    I tried the: Chat with an Engineer! Try out our LabVIEW Chat Support and DAQ Chat Support Beta Program Is there anyone at the other end?  I've been waiting 2 hours and nothing...  It just says "Waiting for technician" R