Hi:

I bought an IOMEGA Screenplay Director HD and i want to mount a partition from it using my linux. When i ran fdisk, i get:

Disco /dev/sda: 1000.2 GB, 1000204886016 bytes
255 cabezas, 63 sectores/pista, 121601 cilindros
Unidades = cilindros de 16065 * 512 = 8225280 bytes

Disposit. Inicio Comienzo Fin Bloques Id Sistema
/dev/sda1 1 33 265072 82 Linux swap / Solaris
/dev/sda2 34 66 265072 83 Linux
/dev/sda3 67 99 265072 b W95 FAT32
/dev/sda4 100 121601 975964814+ 5 Extendida
/dev/sda5 100 231 1052226 83 Linux
/dev/sda6 231 121602 974912526 b W95 FAT32

I want to mount /dev/sda2 but i was unable to do it. I ran then dmesg:

usb 1-1: new full speed USB device using uhci_hcd and address 2
usb 1-1: configuration #1 chosen from 1 choice
Initializing USB Mass Storage driver...
scsi1 : SCSI emulation for USB Mass Storage devices
usbcore: registered new driver usb-storage
USB Mass Storage support registered.
usb-storage: device found at 2
usb-storage: waiting for device to settle before scanning
Vendor: ST310005 Model: 20AS Rev:
Type: Direct-Access ANSI SCSI revision: 02
usb-storage: device scan complete
SCSI device sda: 1953525168 512-byte hdwr sectors (1000205 MB)
sda: Write Protect is off
sda: Mode Sense: 00 38 00 00
sda: assuming drive cache: write through
SCSI device sda: 1953525168 512-byte hdwr sectors (1000205 MB)
sda: Write Protect is off
sda: Mode Sense: 00 38 00 00
sda: assuming drive cache: write through
sda: sda1 sda2 sda3 sda4 < sda5 sda6 >
sd 1:0:0:0: Attached scsi disk sda

Some of the errors:

VFS: Can't find ext3 filesystem on dev sda2.
VFS: Can't find an ext2 filesystem on dev sda2.
JFS: nTxBlock = 2007, nTxLock = 16060

jfs_fsck /dev/sda2
jfs_fsck version 1.1.12, 24-Aug-2007
processing started: 1/25/2010 21.27.45
Using default parameter: -p
The current device is: /dev/sda2

The superblock does not describe a correct jfs file system.

If device /dev/sda2 is valid and contains a jfs file system,
then both the primary and secondary superblocks are corrupt
and cannot be repaired, and fsck cannot continue.

Otherwise, make sure the entered device /dev/sda2 is correct.

I'm trying to figure out which is the format of that partition. I looked into the meaning of the ID: 83 of fdisk and found out this information:

http://www.win.tue.nl/~aeb/partition...n_types-1.html

But it states that is a linux filesystem but doesn´t specify which one or the way things are done.

Can anybody help me?

Thanks in advance!

Regards,

The filesystem tag under fdisk doesn't really mean anything, it is just a label in the partition table that is supposed to make things easier for the administrator. Just because sda2 is listed as Linux doesn't determine which filesystem it is using, indeed it could be a Windows partition, or even unformatted blank space. It all depends on the person who had it before.

Have you tried just mounting /dev/sda2 with no other options? If you just give mount a device and a mount point, it will try to automatically determine the filesystem type based on all the filesystems the OS is aware of. If that fails, there is a good chance the filesystem is damaged, or it is blank.

Are you trying to recover data from this drive? Do you know what is supposed to be on there?

It's a embedded device, the data partition is a fat and i've got also access to other partitions, but this one i'm just unable to mount it. Automatic mounting doesn't work in this case. How can i troubleshoot or identify the drive if that ID is more or less generic? Should i use hex editor or something? Can Gparted be handy in this situation?

Hello Guys,

I am new here and having exactly the same problem with my Screenplay Director, while trying to mount my Linux partitions /dev/sdc2 and /dev/sdc5!
so any update or solution on this mounting problem since Jan?



Thanks

Use "sudo file -s /dev/sdc2" and "sudo file -s /dev/sdc5" to determine what filesystems are on the partitions.

For some filesystems, you may need to determine if your kernel has support for it and if the module is loaded.

For example:
grep JFS /boot/config-2.6.31.12-0.1-desktop
CONFIG_JFS_FS=m
CONFIG_JFS_POSIX_ACL=y
CONFIG_JFS_SECURITY=y
# CONFIG_JFS_DEBUG is not set
CONFIG_JFS_STATISTICS=y
jschiwal@qosmio:~> lsmod | grep JFS

If I had an external drive with a JFS filesystem on it, I may need to:
sudo /sbin/modprobe jfs

before trying to mount it.

no luck man!

root@ubuntu:~# sudo file -s /dev/sdc2
/dev/sdc2: data

root@ubuntu:~# grep JFS /boot/config-2.6.31-14-generic
CONFIG_JFS_FS=m
CONFIG_JFS_POSIX_ACL=y
CONFIG_JFS_SECURITY=y
# CONFIG_JFS_DEBUG is not set
CONFIG_JFS_STATISTICS=y

root@ubuntu:~# lsmod |grep -i jfs
jfs 177380 0

root@ubuntu:~# sudo /sbin/modprobe jfs

root@ubuntu:~# mount -a -t jfs /dev/sdc2 /media/linux1g/
mount: wrong fs type, bad option, bad superblock on /dev/sdc2,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so

root@ubuntu:~# dmesg|egrep -e sdc -e scsi
[ 91.331125] scsi7 : SCSI emulation for USB Mass Storage devices
[ 96.330210] scsi 7:0:0:0: Direct-Access SAMSUNG HD103SI PQ: 0 ANSI: 2 CCS
[ 96.330823] sd 7:0:0:0: Attached scsi generic sg3 type 0
[ 96.331895] sd 7:0:0:0: [sdc] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB)
[ 96.334995] sd 7:0:0:0: [sdc] Write Protect is off
[ 96.335000] sd 7:0:0:0: [sdc] Mode Sense: 00 38 00 00
[ 96.335004] sd 7:0:0:0: [sdc] Assuming drive cache: write through
[ 96.339796] sd 7:0:0:0: [sdc] Assuming drive cache: write through
[ 96.339804] sdc: sdc1 sdc2 sdc3 sdc4 < sdc5 sdc6 >
[ 96.999132] sd 7:0:0:0: [sdc] Assuming drive cache: write through
[ 96.999138] sd 7:0:0:0: [sdc] Attached SCSI disk



I think I am getting to a dead end

The commands dealing with the JFS filesystem from jschiwal were just meant as an example; not as a solution for your problem.

I've spent a few hours into the night on this one & I've used Gparted on it to no avail, it sees the partitions as unknowns. However the filesystem does indeed seem to be JFS, I confirmed this with a quick look with a hexeditor. Are we missing something like a helper program or helper file?

The plain data on the disks is readable so i'm not sure that encryption is the issue.

Is it fesiable to say that these partitions could be written without their journal or superblock, can this data be substituted in at the time of mounting from another file?

The question is what's preventing the mount from happening?

====

Partially Related: Is it reasonable to assume that we can use the hexeditor to adjust the configuration of the smb.conf (whereever it resides on the raw partition) to enable external usb disk sharing on this device?

No, smb.conf is the configuration file for the samba server and has nothing to do with mounting usb drives. If your kernel has JFS support, the module is loaded, and the filesystem is JFS, then it sounds like the filesyste is corrupt.

Try running "sudo tail -f /var/log/messages". Then plug in the usb drive and post what is printed out by the kernel.

Are you certain that a propriety filesystem isn't used. Maybe it is encrypted, or uses a mysqlite database for the filesystem.

Cheers, I've been getting the same speil from the drive as the op.

Eventually this shows,
I'm pretty sure that it is JFS that's being used for this partition, as I've had a look at the source package for the drives firmware, and jfsutils-1.1.11 is in the package. Testdisk for osx identified it as JFS, Also through the hex editor the partitions header mentions JFS too. But there's something stopping it from being mounted.

The plain text on the partition can be read on a hex editor too. There's some trick being used to prevent the drive being mounted.

1 possibility is that when it's in mass storage mode that it disables those partitions somehow. [ Although I can still access them with the hex editor, which leaves me unsure if this is the case ]

Or else, I'm missing a helper program to mount the disk.

The reason I was asking about finding the smb.conf on the physical partition was to enable sharing of the linux partitions while the device is running in media player mode, this could be a viable alternative to mounting them!

You omitted information that might be useful. Such as discovering the partition on sdb, if there is one and any mention of a JFS filesystem.
The line with `JFS:' is a message coming from the jfs kernel module.

One possibility is that it doesn't have a partition table. Look at "sudo /sbin/fdisk -l" to see if sdb does. If not, you might try mounting the drive device as a partition. E.g: examining the partition with "sudo file -s /dev/sdb" and if a the jfs filesystem is found, sudo mount -t jfs /dev/sdb /mnt.

Hi all, new here with the same usb disk.

Just to clarify... it has data inside, the partition we want to access is the main OS partition.

Did not try sudo file -s /dev/sdb... but "mount -t jfs /dev/sdb /mnt/whatever" did not work at all.

mount: wrong fs type, bad option, bad superblock on /dev/sdc2,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so



Did anyone tried to mount it in mac osx?

Hello,

I have the same device and I was wondering if anyone was able to mount the OS partition?

Hi guys,
I have got the same media player (ScreenPlay Director Hd Tv Tuner).
I tried to mount the same partition on OSX with no luck.
I'm sure that in that partition there's the device's operative system, and I'm going crazy trying to mount it to correct some bugs...

If anyone is able to do that, please tell us. I don't want to give up! :-)

Is it possible that we're trying to mount an encrypted partition?