** Reply to message from Felix Miata <[EMAIL PROTECTED]> on Thu, 01 Nov 2007 13:00:26 -0400
> On 2007/11/01 18:35 (GMT+0200) Stan Goodman apparently typed: > > > I'm sorry, that is the result of my clumsiness. There is only one HD, and > > it is > > a SATA drive. The DFSee report came back naming "hda" in both places above, > > and > > I replaced one of the instances with "sda" as I was mulling over the > > significance of what appears to be an error of some sort. I forgot to > > change it > > back when I sent my note to this forum. > > > The only "hda" on the machine is the CD/DVD drive. That is a certain, as you > > can see from the fact that, when I need to unmount the CD/DVD drive in > > order to > > eject a disk, my command is "umount /dev/hda". > > > I ran DFSee v9.xx from OS/2, because that is the only way I can do it. The > > whole problem, of course, is that I can't access Linux. I do not have a > > DFSee > > v9.xx bootable disk, but I do have one for v8.02, but I am sure this earlier > > version does not give a much detail as the new v9.xx does. Do you want me to > > run DFSDISK with DFSee v8? Or some other report? Nothing would be easier, > > just > > say the word. > > http://mrmazda.no-ip.com/tmp/dfsee/p-t18f.txt shows you what I was looking > for. Run from OS/2, it's simply the content of dfswork.log that DFSee tries > to generate when you start it, press <RETURN>, and then exit, except that > I've stripped away portions at the head of the file that are not useful for > our purposes here. The Linux version does the same thing, except that the > format of the table differs somewhat. 'part -b-' would simply append the > DOS/OS2/doz-style table to the rest of it. > > As long as you're appending files, include /etc/grub.conf. Better yet, attach > nothing, but instead post dfswork.log as dfswork1.txt in web space as I did > above, and, also as above, put a link to it in your reply. I do not know how you got the log file to get all that detail. The one I have is much simpler, even allowing for the fact that my hardware is much simplet than yours. Given its size, I think it's OK to just post it here. Here is the file: ***** Appending to log : 'H:\dfswork.log' (7-bit ASCII) Registration : none RgKey status : KEY not present! 22 days left for evaluation! ReadWrite Store 1 : PhysDisk : 1 PartId 00 = -- mode=FDISK 011107-193452 RC:0 <Enter> : 00000000 u=00000000 x=00000000 this=00000000 Base=00000000 ________________________________________________________________________________ 2 ________________________________________________________________________________ 1 Registration : none RgKey status : KEY not present! 22 days left for evaluation! Please install the registration 'DFSee.key' in a directory in the PATH. To get a registration, follow the registration links from: http://www.dfsee.com/dfsee/buynow NO VALID REGISTRATION KEY FOUND! Without a key, D:\DFSEE9\OS2\DFSOS2.EXE should be used for evaluation only! Use the <Enter> key or the mouse to confirm the message. UI TxWindows : 2.02 04-10-2007 (c) 1995-2007: Fsys Software OS version : OS/2 4.50 OS2kernel: 14.104a_W4 on drive C: ________________________________________________________________________________ 1 DFSee OS/2 9.02 : executing: map -M -m Command timestamp : Thursday 2007-11-01 19:34:54 Disk DFSee Disk Image filename or id type nr (Unix) device, and optional partitionable media description ==== ===== ==== =========================================================== 1 Phys 1 /dev/hda Physical disk 1 (IDE/SCSI/USB or PCCARD) 2 Phys 2 /dev/hdb Physical disk 2 (IDE/SCSI/USB or PCCARD) Number of disks : 2 P-Geo Disk 1 Cyl : 16383 H: 16 S:63 Bps:512 Size : 0x09962B80 = 78533.4 MiB Geometry D1 from : LVM info (DLAT) sector at 0x3e L-Geo Disk 1 Cyl : 10011 H:255 S:63 Bps:512 Size : 0x0996055B = 78528.7 MiB BIOS Int13 limit : 1024, I13X support needed beyond : 8032.5 MiB MBR crc 054b4eb9 : 0x0c8ca699 = DFSee generic MBR, English messages, I13X L-Geo Disk 2 Cyl : 512 H: 12 S:32 Bps:512 Size : 0x00030000 = 96.0 MiB DUMMY, disk 2 seems reserved with no media present (USB/PCCARD etc) +-<disk 1>--</dev/hda >--<[ D1 ]>-------------------------------------------+ | |+===+=======================================================================| | || |+-----++-------------++---+| |+------++------++-------++------+| |m||1 ||2 ||3 ||4 ||5 ||5 ||6 ||7 ||8 || |b|| || || || || ||C: ||D: ||H: ||W: || |r||BMG||SWAP ||XFS ||EXT||FreeSpace||HPFS ||JFS ||JFS ||JFS || | || |+-----++-------------++---+| |+------++------++-------++------+| | |+===+=======================================================================| +------------------------------------------------------------------------------+ ________________________________________________________________________________ 1 DFSee OS/2 9.02 : executing: fdisk -r- Command timestamp : Thursday 2007-11-01 19:34:54 EBR02= warning : A windows-compatible extended-partition type 0x0f is used, Old operating systems might not see all logical partitions. +---+--+-----------------+--+--------+--------+-----------+----------+--------+ |ID |Dr|Type, description|ux|Format |Related |VolumeLabel|LVM Volume|Size MiB| +---+--<disk 1></dev/hda >--------+--------+-----------<[ D1 ] >--------+ |01>| |Prim 0a IBM-BMGR | 2|BMGR |LVM |I13Xneeded |., BootMan| 7.8| |02 | |Log 82 SunS/SWAP| 5|SWAP |LinuxV1 |SWAPSPACE2 |, LinuxSwa| 502.0| |03 | |Log 83 LinuxNatv| 6|XFS |Linux | |SuSE, SuSE| 50007.0| |04*| |Log 83 LinuxNatv| 7|EXT2 |GRUB | |SuSE v10.2| 7.8| |05 | |FreeSpace Logical| |-- -- --|-- -- --|- - - - - -| | 21987.4| |05*|C:|Log 07 Inst-FSys| 8|HPFS |IBM 4.50|ECS |eCS v1.1, | 1004.0| |06 |D:|Log 35 Warp-LVM | 9|JFS |IBM 4.50| |OS/2 Apps,| 1506.1| |07 |H:|Log 35 Warp-LVM |10|JFS |IBM 4.50|INFO |Info, Info| 2502.3| |08 |W:|Log 35 Warp-LVM |11|JFS |IBM 4.50|DATAFILES |DataFiles,| 1004.0| +---+--+-----------------+--+--------+--------+-----------+----------+--------+ > = Active/Startable * = Bootable r = Removable R = Removable+Active/Bootable ________________________________________________________________________________ 1 Despite what the heading says, I HAVE registered it, but not yet put the key file in -- I am leaving the country in three days, and am panicked with things left to do, which is why this could not have happened at a worse time. Jan has explained to me that DFSee calls ALL disks e.g. "hda" rather than "sda", because it doesn't see the interface anyway. I did not ask him what happens in a system with both serial and parallel HDs. If I have misunderstood your instructions, please give me more detailed ones, and I will follow them as well as I can. -- Stan Goodman Qiryat Tiv'on Israel I hate puns. Except synonym puns, which are good with coffee for breakfast. -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
