> 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? What about MBR code - could this be relevant here, too?
> > 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 Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ unattended-devel mailing list unattended-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/unattended-devel
