Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hi I am a non-expert user of Ubuntu 10.04. I've taken a disk out of a tru64 system and intalled it to my PC via an Adaptec AHA-2940uw SCSI card.
When I boot up, Ubuntu finds the partitions on the disk but does not recognise the file system (if I double click them in the computer folder I get the message:
mount: wrong fs type, bad option, bad superblock on /dev/sde3,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
I have tried this
sudo mount -t ufs sde3 /mnt/odyssey1
the reply is
special device sde3 does not exist
Any help greatly appreciated! Especially if I can understand it!
The error it gives now I am using the right path is the first message in my original post i.e.
mount: wrong fs type, bad option, bad superblock on /dev/sde3,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
Your first error is telling you that your system does not currently have the kernel modules to understand the tru64 filesystem. UFS is pretty old and the code has probably been cut to save space, so it will not be included in the kernel by default ( you will have to install it ). Look it up in your package manager.
The error mount is giving you means that you have the wrong device name. Make sure 'sde' is the right device ( perhaps sdc or sdb? ).
If you can read your data, then you can save it somewhere else (perhaps to a better supported filesystem). I suggest that you do this now, if you can.
If you really, really, want to write to this filesystem (and I admit I know nothing about ufs), then the hint is there:
Quote:
[ 6330.867118] ufs was compiled with read-only support, can't be mounted as read-write
So there is probably an option to compile your kernel ufs module with write-support for ufs enabled.
It's not offered, so perhaps support is unreliable. You can probably still compile your kernel to provide support for this, but it may not work, and may break the current partition you have.
So before you try this, or anything else, please make a copy of the existing partition with dd if=/dev/sdwhatever of=image_of_ufs_filesystem.partition
This way, you have a backup file of the original filesystem partition that you can later go back to if you need to.
I am a bit out of my depth here: I have no idea what a "tru64" filesystem is, so I am simply offering you "generic" advice.
At least you have (possibly) managed to get it mounted. Can you read the files there?
Why do you need write access to this partition, and why are you using such an outdated filesystem?
With a lot more information from you, there may be a simpler answer.
Hope this helps, but you need to supply more information, or I am wasting my time.
While trying to make some changes to the configuration files on a tru4 system (running on a DEC Alpha) I corrupted the fstab file and the full OS would not start up. If I could just edit a couple of lines in the fstab file I could restore it. These systems are somewhat unlike Linux and when some ideot does something like this to them you can still start up in "single user mode". But that is very limited and I was not even able to access vi in it. I am sure it is possible but I am out of my depth with it.
Tru64 was a Unix OS sold by Digital, they later sold it on to Compaq and they to HP (or something like that!)
The machine is a spare donated to me. I have another but this is in a very mission critical machine and I dare not plug this disk into that machine with my feeble grasp of the OS etc.
I thought Linux would easily deal with UFS so I borrowed the scsi adapter and plugged it into my PC running Ubuntu. As you see it did not turn out as easy as I expected.
There are some other alternatives (like asking a guy who has a similar machine which is not doing a mission critical job to plug my disk in his machine and edit the file for me.)
I also have the OS CD which may start up in a maintenance mode (if the CD drive in this elderly machine is working and if I can mount it while I am in single user mode.)
The Ubuntu route is getting too tough for me, it was worth a try. Seeing this: http://wikis.sun.com/display/BigAdmi...ndows+or+Linux makes me feel I am treading on the edge of the known universe and definitely not up to exploring these realms!
So thanks everyone for your guidance. I think I'll activate plan B or C
Thanks for the extra explanations, they help me make sense of your problem.
Some further research shows that the ufs module is (usually) compiled without write support. This link explains how to enable write-support with linux, and it seemed to work for him.
If you have problems following the instructions in that thread, we'll be happy to help you.
It would be a very good idea to use dd to take images of your ufs partition(s) before you try writing to them. That way you can always recover to your original position. You do not have to mount the partitions to make copies of them. Again, if you need help with this step, ask.
But perhaps the problem is already solved by other means?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.