Page 2 of 4 FirstFirst 1234 LastLast
Results 11 to 20 of 38

Thread: [SOLVED] Try hd(0,0): NTFS5: No wubildr

  1. #11
    Join Date
    May 2007
    Beans
    465

    Re: Try hd(0,0): NTFS5: No wubildr

    Quote Originally Posted by help_me_please View Post
    cat (hd0, [TAB] showed that i have 2 partitions of type ntsf. im assuming that the problem is that wubi is attempting to load from partition 0 while it is actually in partition 1. what do i have to edit to correct this?

    just in case, here is the info from ftest.exe:
    It's actually all right. The first partition is a vendor reserved partition, which correspond to the hd(0,0): NTFS5: No wubildr line. The second partition is your main partition. grldr DOES load properly, although there might be some efficiency issue.

    If I guess right, your primary MFT is stored in non resident attribute list, you can verify it with:

    fstest.exe inode C:\$MFT
    fstest.exe inode C:\.
    Last edited by bean123; May 19th, 2008 at 12:23 PM.

  2. #12
    Join Date
    May 2008
    Beans
    28

    Re: Try hd(0,0): NTFS5: No wubildr

    sorry dude, but i only understood about half of what you said... could you repeat that in english please

    i ran the fstest's u suggested, but i couldn't make heads of tails of the output.

  3. #13
    Join Date
    Feb 2005
    Beans
    5,138

    Re: Try hd(0,0): NTFS5: No wubildr

    Can you paste the output here?

  4. #14
    Join Date
    May 2008
    Beans
    28

    Re: Try hd(0,0): NTFS5: No wubildr

    output from fstest:

    fstest inode c:\

    ntfs_dir: 17

    fstest inode c:\$MFT
    Type: File
    Attr:
    $STANDARD_INFORMATION (0x10) (r,sz=72)
    $FILENAME (0x30) (r,sz=74)
    $MFT
    $DATA (0x80) (nr,sz=132317184)
    6291456+113280,118847360+7040,121304912+46224,1485 91136+47360,22049112+44528

    $BITMAP (0xB0) (nr,sz=16152)
    6291448+8,116169752+8,12540896+8,13641128+8

  5. #15
    Join Date
    May 2007
    Beans
    465

    Re: Try hd(0,0): NTFS5: No wubildr

    what is the result of

    fstest.exe inode C:\.

  6. #16
    Join Date
    May 2008
    Beans
    28

    Re: Try hd(0,0): NTFS5: No wubildr

    ntfs_dir: 17

  7. #17
    Join Date
    May 2007
    Beans
    465

    Re: Try hd(0,0): NTFS5: No wubildr

    What about

    fstest.exe inode C:\#5

  8. #18
    Join Date
    May 2008
    Beans
    28

    Re: Try hd(0,0): NTFS5: No wubildr

    output of fstest inode c:\#5

    Type: Directory
    Attr:
    $STANDARD_INFORMATION (0x10) (r,sz=72)
    $FILENAME (0x30) (r,sz=68 )
    .
    $INDEX_ROOT (0x90) (r,nm=$I30,sz=56)
    $INDEX_ALLOCATION (0xA0) (nr,nm=$I30,sz=20480)
    1843264+8,133022392+8,133023112+8,118816+16
    $BITMAP (0xB0) (r,nm=$I30,sz=8 )
    $UNKNOWN (0x0) (r,nm=$TXF_DATA,sz=56)

  9. #19
    Join Date
    May 2007
    Beans
    465

    Re: Try hd(0,0): NTFS5: No wubildr

    Thanks for your feedback, I figure it out now. Vista create a huge non resident root directory with only a handful of files, which cause grldr.mbr to load many useless sectors. I fixed this once in the ntfs driver. Unfortunately, grldr.mbr is already too crowded, there is no room for extra code, so can't fix it here.

    But there is another option. IIRC, vista support boot file up to 32K, which is enough for a grub2 core.img. If we use grub2, we can skip the real mode loader grldr.mbr and load the kernel directly.

  10. #20
    Join Date
    May 2008
    Beans
    28

    Re: Try hd(0,0): NTFS5: No wubildr

    so if i replace the vista boot file with the grub boot file the "Try hd(0,0): NTFS5: No wubildr" error will stop? might as well get rid of the wubi and install ubuntu on seperate partition...

    by the by, is there a way to save all updates, packages and configurations of wubi and apply them to a clean install?

Page 2 of 4 FirstFirst 1234 LastLast

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •