MOD Drive disk reading in linux

Which filesystem is on the disk? What does

sudo fdisk -l

reports on that drive?

After connecting the drive, could you pls post here:

cat /etc/mtab

if i am giving command "sudo fdisk -l"            output like this

ubuntu@ubuntu:-$ sudo fdisk -l
Note : sector size is 1024 (not 512)
Disk /dev/sda : 2375 MB
64 heads 32 sector/track 1132 cylenders
units = cylenders of 2048 * 1024 = 20971552
Disk identifier 0xa5a5a5a5
Device boot Start
Disk /dev/sdb/ 73.5GB
255 heads 63 sectors/track  8936
disk identifier 0x012urfsps
device        boot  start   end        blocks          id
/dev/sdb1     *      1        8752    70300408+  83
       "      2           8753    8936    1477980       5
       "      5           8753    8936       "               82

if i am removing MOD disk from MOD drive than "/dev/sda" is not showing

 

From fdisk it looks like the system doesn't detect any valid partition on that disk

cat /etc/mtab output...

proc /proc proc rw 0 0
sysfs /sys sysfs rw 00
tmpfs /lib/modules/2.6.28 -11 generic/volatile tmpfs rw node =075500
tmpfs/  "         "         "                                         "
tmpfs /lib/init/rw/tmpfs rw nosvid, node = 075500
varran /var/run/tmpfs rw nosvid mode = 755  0 0
udev /dev/ tmpfs rw mode =755 0  0
tmpfs /dev/shm/       tmpfs rw nosvid      nodev 0 0
devpts /dev/pts devpts  rw, no exec no suid gid =5 mode =620 0 0
rootfs /rootfs rw 0 0
/dev/sro/cdrom iso9660 ro noa time 0 0
/dev/loop0 / rofs /squash ro noa time 0 0
fusectl /sys/fs/fuse/connections fusesectl rw 0 0
tmpfs /tmp tmpfs rw no suid no dev 00
/dev /sdui /target/proc none rw
/proc/sdui/target/proc bind 0 0
/dev /target /dev none r w bind 0 0
bindfmt mix /proc/sys/fs/ bindfmt...
.........

as you said from fdisk system doen't detected any valid partion...
i have lot of MOD disks all showing like this only...

regards
nivasnet

the disks that was created on sco
what file system is it ?
 also check out this thread

https://www.experts-exchange.com/questions/24387605/how-read-MOD-disk-in-sco-unix.html

the thread which you mentioned above is created by me only....
because problem not solved, that is why I installed Linux ubuntu and trying....
we don't know which file system it is created in sco unix....

i think its ufs
see if the kernel module is loaded by using cat /proc/filesystems
if no ufs then check thats the module exist.
modprobe -l | grep ufs
to load the module to the kernel
modprobe ufs
try to mount it now
mount -r -t ufs -o ufstype=ufs2 device mountpoint

SCO Unix should use Extended Acer Fast Filesystem EAFS...

if i am typing command 'modprobe -l | grep ufs' it is giving error like 'command not found'
if i am trying to mount it is telling only root can do this....

i don't root password.... what is the root password.

regards
nivasnet

if its ubuntu then you can switch to root by running
sudo su -
and then enter your password
to reset root password run
passwd

you must do all the above ( load modules and so on ) as root

if i am giving this command 'mount -r -t ufs -o ufstype=ufs2 Mod  1'  i am getting this error..
mount point 1 does not exist....


regards

srini

the syntax is

mount <options> <device> <mount point>

In your command string "1" is not a mount point, and maybe "Mod" does not point to the device

how to find pointed devices for UFS filesystem....

Device should be /dev/sda (as per your fdisk results). The mount point must be first created:

sudo mkdir /media/mymountpoint

the statement you given 'the mount point must be first created' means what ?
because these MOD disks having very important data already....we are not creating any filesystem,
we want to see (read) existing files.
in the command 'sudo mkdir /media/mymountpoint'  mymountpoint should be what ? i mean which number.
the disk /dev/sda details below.
Disk /dev/sda : 2375 MB
64 heads 32 sector/track 1132 cylenders
units = cylenders of 2048 * 1024 = 20971552
Disk identifier 0xa5a5a5a5

I think you missed what the command mount is...

man mount

In order to read a device, your fisrt need to "mount" it on you local filesystem, on a specific mount point (arbitrary( that must be created before launching the mount command.

i didn't find what is the file system in mod