Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
it changed from sdb to sdc when i tried pulling it out and sticking it back in. kubuntu automounted it to /media/STICK.
dd just sais opening '/dev/sdc': read-only file system
fdisk -l /dev/sdc sais:
Disk /dev/sdc: 4160 MB, 4160749568 bytes
128 heads, 62 sectors/track, 1024 cylinders
Units = cylinders of 7936 * 512 = 4063232 bytes
This doesn't look like a partition table
Probably you selected the wrong device.
Device Boot Start End Blocks Id System
/dev/sdc1 ? 98052 241891 570754815+ 72 Unknown
Partition 1 has different physical/logical beginnings (non-Linux?):
phys=(357, 116, 40) logical=(98051, 51, 11)
Partition 1 has different physical/logical endings:
phys=(357, 32, 45) logical=(241890, 104, 51)
Partition 1 does not end on cylinder boundary.
/dev/sdc2 ? 21257 265212 968014120 65 Novell Netware 386
Partition 2 has different physical/logical beginnings (non-Linux?):
phys=(288, 115, 43) logical=(21256, 30, 47)
Partition 2 has different physical/logical endings:
phys=(367, 114, 50) logical=(265211, 52, 42)
Partition 2 does not end on cylinder boundary.
/dev/sdc3 ? 235621 479576 968014096 79 Unknown
Partition 3 has different physical/logical beginnings (non-Linux?):
phys=(366, 32, 33) logical=(235620, 18, 30)
Partition 3 has different physical/logical endings:
phys=(357, 32, 43) logical=(479575, 39, 39)
Partition 3 does not end on cylinder boundary.
/dev/sdc4 ? 363620 363627 27749+ d Unknown
Partition 4 has different physical/logical beginnings (non-Linux?):
phys=(372, 97, 50) logical=(363619, 12, 25)
Partition 4 has different physical/logical endings:
phys=(0, 10, 0) logical=(363626, 11, 33)
Partition 4 does not end on cylinder boundary.
Partition table entries are not in disk order
mount with no options sais:
mount: block device /dev/sdc is write-protected, mounting read-only
and yes i was sure to unmount it defore running fdisk.
This leads me to believe there is security partition still on the device which may be causing the lock issue. Although I had a drive with u3 on it that acted the same way at first, once I zeroed the boot sector I was able to do as I pleased with the drive in linux. Upon plugging it back into a windows machine it locked the box up, apparently the u3 software was embedded. I had to run the u3 removal tool from windows to use the drive across platforms. I don't know if this will solve your problem but, I'm fresh out of ideas.
Good luck. ;-)