Hi,

I'm not sure where to ask for help on this, so I
thought I'd try here first.
I'm running RH6.2 on a 450mz Pentium III on an ASUS P3B-F.
I have Redhat on one scsi drive and Solaris 7 on a seperate
scsi drive off the same controller.
I can boot through lilo successfully to either operating system.
I have both UFS file system read and write, and Sun (Solaris 7 x86)
partition support compiled into the (2.4.0) kernel.

I have been unable to mount the solaris drive. I have found
(I think) all the relevant info on the web about mounting
solaris 7 under linux. I've attached a file with (I think)
all the relevant output from the boot process and attempts
at mounting the solaris drive.
If there is a mailing list that would be more specific
for this type of problem or somewhere on the web that can
addresses this issue, I'd be glad to know about it.
Thanks in advance.

David

__________________________________________________
Do You Yahoo!?
Get personalized email addresses from Yahoo! Mail - only $35 
a year!  http://personal.mail.yahoo.com/

-------------------------------------------------------------------
I'm running RH6.2 on a 450mz Pentium III on an ASUS P3B-F
---------------------------------------------------------------------------
I have both UFS file system read and write, and Sun (Solaris 7) partition
support compiled into the (2.4.0) kernel
------------------------------------------------------------------------
My notes from booting: The kernel always says this:


 scsi0 : setting target 2 to period 100ns offset 8 10.00MHz FAST SCSI-II
Jan 26 00:10:00 localhost kernel:   Vendor: HP        Model: 4.26GB B 68-5541  Rev: 
5541
Jan 26 00:10:00 localhost kernel:   Type:   Direct-Access         ANSI SCSI revision: 
02
Jan 26 00:10:00 localhost kernel: Detected scsi disk sda at scsi0, channel 0, id 0, 
lun 0
Jan 26 00:10:00 localhost kernel: Detected scsi disk sdb at scsi0, channel 0, id 2, 
lun 0
Jan 26 00:10:00 localhost kernel: SCSI device sda: 4110480 512-byte hdwr sectors (2105 
MB)
Jan 26 00:10:00 localhost kernel: Partition check:
Jan 26 00:10:00 localhost kernel:  sda: sda1 sda2 sda3 < sda5 sda6 >
Jan 26 00:10:01 localhost kernel: SCSI device sdb: 8330543 512-byte hdwr sectors (4265 
MB)
Jan 26 00:10:01 localhost kernel:  sdb: sdb1
Jan 26 00:10:01 localhost kernel:  sdb1: <solaris: [s0] sdb5 [s1] sdb6 [s2] sdb7 [s6] 
sdb8 [s7] sdb9 >

---------------------------------------------------------------------------------
If the relevant line in /etc/fstab (line 10, which is the last line) reads:

/dev/sdb1       /solaris                ufs     defaults        0 0

Then the kernel message during bootup says:

Jan 26 00:10:03 localhost kernel: You didn't specify the type of your ufs
filesystem Jan 26 00:10:03 localhost kernel:
Jan 26 00:10:04 localhost kernel: mount -t ufs -o 
ufstype=sun|sunx86|44bsd|old|hp|nextstep|netxstep-cd|openstep ...
Jan 26 00:10:04 localhost kernel:
Jan 26 00:10:04 localhost kernel: >>>WARNING<<< Wrong ufstype may corrupt your 
filesystem, default is ufstype=old
Jan 26 00:10:04 localhost kernel: ufstype=old is supported read-only
Jan 26 00:10:04 localhost kernel: ufs_read_super: bad magic number
Jan 26 00:10:04 localhost kernel: Installing knfsd (copyright (C) 1996 
[EMAIL PROTECTED]).
Jan 26 00:10:04 localhost kernel: You didn't specify the type of your ufs filesystem
Jan 26 00:10:04 localhost kernel:
Jan 26 00:10:04 localhost kernel: mount -t ufs -o 
ufstype=sun|sunx86|44bsd|old|hp|nextstep|netxstep-cd|openstep ...
Jan 26 00:10:04 localhost rc: Starting linuxconf succeeded
Jan 26 00:10:04 localhost kernel:
Jan 26 00:10:04 localhost kernel: >>>WARNING<<< Wrong ufstype may corrupt your 
filesystem, default is ufstype=old
Jan 26 00:10:04 localhost kernel: ufstype=old is supported read-only
Jan 26 00:10:05 localhost kernel: ufs_read_super: bad magic number
-------------------------------------------------------------------------------------
If the relevant line in /etc/fstab (line 10, which is the last line) reads:

/dev/sdb1       /solaris         ufstype=sunx86 defaults        0 0

Then the kernel message during bootup says:

Jan 26 18:50:21 localhost fsck: WARNING: bad format on line 11 of /etc/fstab

Jan 26 00:21:46 localhost mount: mount: fs type ufstype=sunx86 not supported by kernel
                                           
--------------------------------------------------------------------------------------
After boot and login:

[root@localhost /root]# mount -t ufs -o ufstype=sunx86 /dev/sdb1  /solaris
mount: wrong fs type, bad option, bad superblock on /dev/sdb,
       or too many mounted file systems    
 
-----------------------------------------------------------------------------
cfdisk: /dev/sdb partition table:

Partition Table for /dev/sdb

         ---Starting---      ----Ending----    Start Number of
 # Flags Head Sect Cyl   ID  Head Sect Cyl    Sector  Sectors
-- ----- ---- ---- ---- ---- ---- ---- ---- -------- ---------
 1  0x80   80   11    0 0x82  103   16 1023     1290   8328240
 2  0x00    0    0    0 0x00    0    0    0        0         0
 3  0x00    0    0    0 0x00    0    0    0        0         0
 4  0x00    0    0    0 0x00    0    0    0        0         0

----------------------------------------------------------------------------

[root@localhost /root]# sfdisk -V -l /dev/sdb

Disk /dev/sdb: 1017 cylinders, 132 heads, 62 sectors/track
Warning: The first partition looks like it was made
  for C/H/S=*/104/16 (instead of 1017/132/62).
For this listing I'll assume that geometry.
Units = cylinders of 851968 bytes, blocks of 1024 bytes, counting from 0
 
   Device Boot Start     End   #cyls   #blocks   Id  System
/dev/sdb1   *      0+   5005-   5005-  4164120   82  Linux swap
                start: (c,h,s) expected (0,80,11) found (0,20,51)
                end: (c,h,s) expected (1023,103,16) found (1017,103,16)
/dev/sdb2          0       -       0         0    0  Empty
/dev/sdb3          0       -       0         0    0  Empty
/dev/sdb4          0       -       0         0    0  Empty
Warning: partition 1 extends past end of disk                
------------------------------------------------------------------------------

[root@localhost /root]# fdisk /dev/sdb
 
Command (m for help): p
 
Disk /dev/sdb: 132 heads, 62 sectors, 1017 cylinders
Units = cylinders of 8184 * 512 bytes
 
   Device Boot    Start       End    Blocks   Id  System
/dev/sdb1   *         1      1018   4164120   82  Linux swap
Partition 1 does not end on cylinder boundary:
     phys=(1017, 103, 16) should be (1017, 131, 62)
-------------------------------------------------------------------------------
/etc/fstab:

/dev/sda2       /                       ext2    defaults        1 1
/dev/sda1       /C:                     vfat    defaults        0 0
/dev/cdrom      /mnt/cdrom              iso9660 noauto,owner,ro 0 0
/dev/sdc1       /syquest                vfat    defaults        0 0
/dev/sda5       /usr                    ext2    defaults        1 2
/dev/fd0        /mnt/floppy             auto    noauto,owner    0 0
none            /proc                   proc    defaults        0 0
none            /dev/pts                devpts  gid=5,mode=620  0 0
/dev/sda6       swap                    swap    defaults        0 0
/dev/sdb1       /solaris        ufstype=sunx86  defaults        0 0
          
---------------------------------------------------------------------------
---------------------------------------------------------------------------
With the relevant line in /etc/fstab saying:

/dev/sdb1       /solaris         ufstype=sunx86 defaults        0 0

[root@localhost /root]# mount -a 
mount: fs type ufstype=sunx86 not supported by kernel 
--------------------------------------------------------------------------------
-------------------------------------------------------------------------------
With the relevant  line of /etc/fstab changed to:

/dev/sdb1       /solaris                ufs     defaults        0 0

or:

/dev/sdb1       /solaris                ufs     ufstype=sunx86  0 0

[root@localhost /root]# mount -a 
mount: wrong fs type, bad option, bad superblock on /dev/sdb1,
       or too many mounted file systems                      

Reply via email to