Can't Mount Nero Multisession Data DVD
I am having trouble mounting some of my data dvd's. My friend runs Suse 10 and he can mount the same disk that I cannot. The disk that I am having trouble with is a multisesson disk created with nero on windows. I have had trouble with nero multisession disk in the past and left it alone.
My error when I try to mount the disk: Quote:
Quote:
Now here is the fstab on the Suse 10 that will mount the disk: Quote:
|
Well, did you try expirementing as root with fs type? -t udf, -t iso9660 maybe something else? Also, did you try adding session= -o option (in root command-line)?
|
My drives:
Code:
bruce@silas:~$ dmesg | grep -i atapi Code:
/dev/cdrom /mnt/cdrom auto noauto,owner,ro 0 0 |
Thanks for the replies. I tried -t udf, -t iso9660 (-t udf crashed my computer). I tried:
Quote:
Quote:
Thanks for the advice. |
Did you try commenting out your previous line
Code:
/dev/hdc /media/cdrecorder auto pamconsole,fscontext=system_ubject_r:removable_t,exec,noauto,man$ 0 0 Code:
/dev/hdc /media/cdrecorder auto noauto,users,ro 0 0 Code:
mount: block device /dev/hdc is write-protected, mounting read-only Your real problem with that line is you're not getting the correct filesystem for the media you're trying to mount, or you're trying to mount something that shouldn't be mounted. What is the data on this disc you're trying to mount? Perhaps some of the filesystems aren't mountable? When you post data such as your /etc/fstab output, use [_code_] before it and [_/code_] after it, without those underscores, and you will eliminate the smiley. |
Quote:
The data on the disc is my digital camera backup pics. I created the disc originally when I used windows. Now I am using a different Windows computer to fill up the disc. Normally I would agree that something is wrong with the disc, but I can mount it on a different computer that is running Suse 10. When I replaced your line with mine. I didn't get the write protected error, but I still can't mount the disk. |
Windows CD's have joliet extensions, but no rock ridge extensions. Multisession disks require some sort of extensions. SuSE must be able to use joliet extensions for some reason unknown to me. Without rock ridge extensions on the multisession CD, most linux distros won't be able to read the multisession info.
|
If all you need is joliet extensions, as AwesomeMachine (tell us about it) said, then issue:
Code:
mingdao@silas:~$ cat /usr/src/linux-2.6.16.2/.config | grep -i joliet If it returns "# CONFIG_JOLIET is not set", you need to rebuild your kernel. If it returns "CONFIG_JOLIET=m", then issue "modprobe joliet" as root and see if that will insert the module into your kernel. |
Its says:
Quote:
|
I haven't a clue, primarily since I burn CD/VCD/DVDs in Slackware.
But the lack of joliet extensions wasn't your problem. I would suggest burning them in Linux rather than with Nero in Windows. You'll probably find that any OS can read them afterwards. If you can't use "cdrecord" or another tool from CLI, then use K3B. It's a GUI tool similar to Nero. There is also Nero for Linux now, iirc, but I've never used it. Also keep in mind that SuSE doesn't have an original kernel from Kernel.org, but a hacked SuSE version. Therefore, some things in that kernel and the SuSE distro are designed to work differently than the Linux standards. I think the same is true of CentOS. |
Thanks for all of your help. I'll have to figure something out.
A couple Slackware Questions: Is Slackware hard for a newbie? Do you have to compile the programs you want from source? |
Slackware is hard for a newbie, but worth every bit of effort for the superior Linux system you will get -- but not hard if you're willing to read and learn -- definitely hard if you want to just click and play.
In June 2003 I started with RedHat. That was hard to me, because it was mostly GUIs doing everything, and they hide what's happening. It seemed too much like Windows. Then I tried Debian. I did't know how to compile programs from source, and their "apt-get" system was broken at the time because 2 developers were arguing about an app, so it wasn't available except in the Woody (ultra stable, but also old) branch. I'd noticed that most of the mods, and most of the posters I'd read with correct answers, were using Slackware. I read this: Quote:
I'm glad. Yes, it was difficult in the beginning to learn what was happening. I also didn't use a desktop environment like KDE, but rather, the lightweight window manager Fluxbox. So there were no little icons to click and see what happened. Slackware requires that you learn your system. Slackware doesn't have GUI frontends for anything. It requires that you learn how to do things on your own. This knowledge will be applicable on any Linux distro. So the saying: "When you learn Slackware, you learn Linux" still holds true, and always will. If you want to install and learn Slackware, I'll post some links to help get you started. There are guides to follow that you can install and configure the basics of your system very easily. The best online IMO is by danieldk (LQ nick) titled Slackware Linux Basics and that version is for Slackware Linux 10.2 (the present stable version). You don't have to compile anything from source, but you can if you would like. Slackware provides a C compiler, and kernel headers, and everything else you need. I've never had to add anything to my Slackware systems to compile. Slackware's package system is very standard. It uses "tarballs" so you can use the package utilities, add them by hand, view their contents, and change them. You can get official "Slackpacks" directly from Slackware, or you can get packages from trusted sources. My favorite package repository is Eric Hameleer's repository (Alien_Bob in LQ). His track record for building packages that work is impeccable. In fact, he's contributed so much to Slackware that Pat has given him that space to store his contributions to the Slackware community. Slackware packages are easy to install. In a terminal as root you issue "installpkg <package_name>" and it gets installed. And if you don't want a package, or it didn't work with your system for some reason, you issue "removepkg <package_name>" and everything installed is uninstalled. If you want to upgrade an app in your system, you issue "upgradepkg <package_name>" and it does. NB: There are sources, such as LinuxPackages.net, that people will suggest to you. However, their packages aren't always reliable, and aren't necessarily built to the Slackware standards. I'd stick to official packages, or those from someone like Eric. |
Slackware does sound cool.
At distowatch it says KDE is the default desktop. Will it start KDE after I install it? I am interested in Slackware, but I couldn't find a dvd iso at the website. |
Slackware after a default install brings you to a command prompt that says "login :"
At that point you must login as root, then enter your password. The very next thing you should do is type "adduser natewlew" or whatever you'd like for the user account. Then after creating it, type "exit" to get the login prompt again, then login as natewlew. Then type "xwmconfig" and you can choose from about 8 window managers/desktop environments. Then when returned to a prompt, type "startx" to start the X server. You haven't read Daniël de Kok's guide yet, I see. ;) Don't get the Slackware CDs anywhere but from Slackware. There is no official DVD, but I do make some of my own. If you have a running Linux system, you can get the sources with a script of Eric's that will make a DVD for you. You can get it here and it will require a little editing. If you want to do that, download the script and then post back that you're ready to edit it. |
I am downloading the 4 iso images right now. I am ready to edit the script.:study:
|
All times are GMT -5. The time now is 04:17 AM. |