Re: NTLDR + bootdisk from CVS (kernel 2.6.17/parted 1.7.1)

[Falko T. <ftr...@sm...>]

> As I see it, we have 3 options:
> 
> 1. Fix the kernel
> 2. Fix all the other tools (parted, dosemu)
> 3. a Workaround witch patches mbr and partition tables.
> 
> The first one is a solution for SATA in the same manner as the existing PATA 
> fix.
> See this post in LKML: 
> http://www.ussg.iu.edu/hypermail/linux/kernel/0602.1/0898.html
> Maybe we should contact Seewer Philippe..??
Might be a good idea.

> The Unattended Project is THE user for a patch like this!
> 
> Second one: Pat tried this in 2004.. !! Who want to take a dive into Dosemu??
> 
> Third: This is the ugly one. I have briefly looked into it, but I do not 
> understand all the hairy details.
> 
> Please comment :-)
> 

I'd suggest analysis first:

We need a tool/script/whatever which summarizes all relevant data of
a drive in this situation.

It should kick in before/after dosemu runs so we can _really_ check
what's the problem of a certain drive/bios/board/whatever combination.

So the situation perhaps should be reproducible (I think of e.g.
doing a dd of the partition sectors of this drive), and may be we
need the view from the windows side (e.g using BartPE), too.

For the script I could think of at least output from

  uname -a
  fdisk -l ; fdisk -v
  parted /dev/dsk print ; parted --version
  cat /sys/block/?da/settings

what else would be needed here?

Of course there should be a way to write it on a network drive
for reporting.

Falko

-- 
Falko Trojahn                     fon +49-341-3581294
Dipl.-Ingenieur Netzwerke/Support fax +49-341-3581295
SMI Softmark Informationstechnologien GmbH
www.smi-softmark.de