USB drive, was usable NTFS, now problematic ext3?
Forum rules
There are no such things as "stupid" questions. However if you think your question is a bit stupid, then this is the right place for you to post it. Stick to easy to-the-point questions that you feel people can answer fast. For long and complicated questions use the other forums in the support section.
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
There are no such things as "stupid" questions. However if you think your question is a bit stupid, then this is the right place for you to post it. Stick to easy to-the-point questions that you feel people can answer fast. For long and complicated questions use the other forums in the support section.
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
USB drive, was usable NTFS, now problematic ext3?
I formatted an external USB drive from NTFS to ext3 so I could archive my Humax Foxsat HDD recordings. Having watched my Cricket, I wanted to delete the files but bringing the drive and my trusty Linux laptop together does not seem to be working for me, even though I used GParted on the laptop to format the drive! Apparently, I don't have permission and access is denied! Although not the end of the world (I can use the Hummy to delete the files), it's a tad annoying to be told "you don't have permission". And does that mean I can't use the drive with my laptop ever again???
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 1 time in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
Re: USB drive, was usable NTFS, now problematic ext3?
The information in your fstab file is now incorrect.
It needs to be updated to reflect the change from NTFS to ext3 so the drive
will be auto mounted at boot time.
Take a look at Fred's tutorial to see how to make the changes.
http://forums.linuxmint.com/viewtopic.php?f=42&t=22093
If you get stuck then come back and post the output of these commands.
mick
It needs to be updated to reflect the change from NTFS to ext3 so the drive
will be auto mounted at boot time.
Take a look at Fred's tutorial to see how to make the changes.
http://forums.linuxmint.com/viewtopic.php?f=42&t=22093
If you get stuck then come back and post the output of these commands.
Code: Select all
sudo lshw -C disk
Code: Select all
sudo sfdisk -l
Code: Select all
cat /etc/fstab
mick
Re: USB drive, was usable NTFS, now problematic ext3?
mick55 thanks for the reply - couldn't make head or tail of Fred's instructions, got a message saying directory already exists! Anyway...
ian@ian-laptop ~ $ sudo lshw -C disk
*-cdrom
description: DVD-RAM writer
product: DVD RW AD-7530A
vendor: Optiarc
physical id: 0.0.0
bus info: scsi@4:0.0.0
logical name: /dev/cdrom
logical name: /dev/cdrw
logical name: /dev/dvd
logical name: /dev/dvdrw
logical name: /dev/scd0
logical name: /dev/sr0
version: EX32
capabilities: removable audio cd-r cd-rw dvd dvd-r dvd-ram
configuration: ansiversion=5 status=nodisc
*-disk
description: ATA Disk
product: WDC WD800BEVS-22
vendor: Western Digital
physical id: 0.0.0
bus info: scsi@0:0.0.0
logical name: /dev/sda
version: 04.0
serial: WD-WXE407D61949
size: 74GiB (80GB)
capabilities: partitioned partitioned:dos
configuration: ansiversion=5 signature=3a092c2d
*-disk
description: SCSI Disk
physical id: 0.0.0
bus info: scsi@6:0.0.0
logical name: /dev/sdb
size: 465GiB (500GB)
capabilities: partitioned partitioned:dos
configuration: signature=fc1c3c8e
*-disk
description: SCSI Disk
physical id: 0.0.0
bus info: scsi@21:0.0.0
logical name: /dev/sdc
size: 149GiB (160GB)
capabilities: partitioned partitioned:dos
configuration: signature=8c0ed73f
ian@ian-laptop ~ $ sudo lshw -C disk
*-cdrom
description: DVD-RAM writer
product: DVD RW AD-7530A
vendor: Optiarc
physical id: 0.0.0
bus info: scsi@4:0.0.0
logical name: /dev/cdrom
logical name: /dev/cdrw
logical name: /dev/dvd
logical name: /dev/dvdrw
logical name: /dev/scd0
logical name: /dev/sr0
version: EX32
capabilities: removable audio cd-r cd-rw dvd dvd-r dvd-ram
configuration: ansiversion=5 status=nodisc
*-disk
description: ATA Disk
product: WDC WD800BEVS-22
vendor: Western Digital
physical id: 0.0.0
bus info: scsi@0:0.0.0
logical name: /dev/sda
version: 04.0
serial: WD-WXE407D61949
size: 74GiB (80GB)
capabilities: partitioned partitioned:dos
configuration: ansiversion=5 signature=3a092c2d
*-disk
description: SCSI Disk
physical id: 0.0.0
bus info: scsi@6:0.0.0
logical name: /dev/sdb
size: 465GiB (500GB)
capabilities: partitioned partitioned:dos
configuration: signature=fc1c3c8e
*-disk
description: SCSI Disk
physical id: 0.0.0
bus info: scsi@21:0.0.0
logical name: /dev/sdc
size: 149GiB (160GB)
capabilities: partitioned partitioned:dos
configuration: signature=8c0ed73f
Re: USB drive, was usable NTFS, now problematic ext3?
And...
ian@ian-laptop ~ $ sudo sfdisk -l
Disk /dev/sda: 9729 cylinders, 255 heads, 63 sectors/track
Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0
Device Boot Start End #cyls #blocks Id System
/dev/sda1 * 0+ 9357 9358- 75168103+ 83 Linux
/dev/sda2 9358 9728 371 2980057+ 5 Extended
/dev/sda3 0 - 0 0 0 Empty
/dev/sda4 0 - 0 0 0 Empty
/dev/sda5 9358+ 9728 371- 2980026 82 Linux swap / Solaris
Disk /dev/sdb: 60801 cylinders, 255 heads, 63 sectors/track
Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0
Device Boot Start End #cyls #blocks Id System
/dev/sdb1 0+ 60800 60801- 488384001 7 HPFS/NTFS
/dev/sdb2 0 - 0 0 0 Empty
/dev/sdb3 0 - 0 0 0 Empty
/dev/sdb4 0 - 0 0 0 Empty
Disk /dev/sdc: 19457 cylinders, 255 heads, 63 sectors/track
Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0
Device Boot Start End #cyls #blocks Id System
/dev/sdc1 0+ 19456 19457- 156288321 83 Linux
end: (c,h,s) expected (1023,254,63) found (1022,254,63)
/dev/sdc2 0 - 0 0 0 Empty
/dev/sdc3 0 - 0 0 0 Empty
/dev/sdc4 0 - 0 0 0 Empty
ian@ian-laptop ~ $ sudo sfdisk -l
Disk /dev/sda: 9729 cylinders, 255 heads, 63 sectors/track
Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0
Device Boot Start End #cyls #blocks Id System
/dev/sda1 * 0+ 9357 9358- 75168103+ 83 Linux
/dev/sda2 9358 9728 371 2980057+ 5 Extended
/dev/sda3 0 - 0 0 0 Empty
/dev/sda4 0 - 0 0 0 Empty
/dev/sda5 9358+ 9728 371- 2980026 82 Linux swap / Solaris
Disk /dev/sdb: 60801 cylinders, 255 heads, 63 sectors/track
Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0
Device Boot Start End #cyls #blocks Id System
/dev/sdb1 0+ 60800 60801- 488384001 7 HPFS/NTFS
/dev/sdb2 0 - 0 0 0 Empty
/dev/sdb3 0 - 0 0 0 Empty
/dev/sdb4 0 - 0 0 0 Empty
Disk /dev/sdc: 19457 cylinders, 255 heads, 63 sectors/track
Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0
Device Boot Start End #cyls #blocks Id System
/dev/sdc1 0+ 19456 19457- 156288321 83 Linux
end: (c,h,s) expected (1023,254,63) found (1022,254,63)
/dev/sdc2 0 - 0 0 0 Empty
/dev/sdc3 0 - 0 0 0 Empty
/dev/sdc4 0 - 0 0 0 Empty
Re: USB drive, was usable NTFS, now problematic ext3?
And finally...
ian@ian-laptop ~ $ cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid -o value -s UUID' to print the universally unique identifier
# for a device; this may be used with UUID= as a more robust way to name
# devices that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
# / was on /dev/sda1 during installation
UUID=8de25bfb-1a47-414f-994c-19027c260f36 / ext4 errors=remount-ro 0 1
# swap was on /dev/sda5 during installation
UUID=e5df5098-6bce-4a0f-9911-0cfb1a287082 none swap sw 0 0
/dev/scd0 /media/cdrom0 udf,iso9660 user,noauto,exec,utf8 0 0
ian@ian-laptop ~ $ cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid -o value -s UUID' to print the universally unique identifier
# for a device; this may be used with UUID= as a more robust way to name
# devices that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
# / was on /dev/sda1 during installation
UUID=8de25bfb-1a47-414f-994c-19027c260f36 / ext4 errors=remount-ro 0 1
# swap was on /dev/sda5 during installation
UUID=e5df5098-6bce-4a0f-9911-0cfb1a287082 none swap sw 0 0
/dev/scd0 /media/cdrom0 udf,iso9660 user,noauto,exec,utf8 0 0
- Midnighter
- Level 6
- Posts: 1327
- Joined: Tue May 22, 2007 1:52 pm
- Location: Western Australia
Re: USB drive, was usable NTFS, now problematic ext3?
I have a 1TB external drive i use for storage. Formatted to ext3 from ntfs. Find out what point it is mounted at. Mine is mounted at /media/STORAGE (I have it's label set to STORAGE), and so I run , to give my username:groupname full read/write access to the drive. Replace david:david with whatever your system username is. You'll have acces to it soon enough, it just resets all the permissions to you.
Code: Select all
sudo -R david:david /media/STORAGE
- Midnighter
- Level 6
- Posts: 1327
- Joined: Tue May 22, 2007 1:52 pm
- Location: Western Australia
Re: USB drive, was usable NTFS, now problematic ext3?
-R tells it to "recursively" change the file permission of everything from that point down. It should be an option, it has always worked. What is happening? What have you done, and what response have you gotten? Your reply is far too vague for me to work with.
Re: USB drive, was usable NTFS, now problematic ext3?
Well, excuse me!
ian@ian-laptop ~ $ sudo -R ian /media/Toshiba160gb
sudo: invalid option -- 'R'
usage: sudo [-n] -h | -K | -k | -L | -V | -v
usage: sudo -l[l] [-AnS] [-g groupname|#gid] [-U username] [-u username|#uid]
[-g groupname|#gid] [command]
usage: sudo [-AbEHnPS] [-C fd] [-g groupname|#gid] [-p prompt] [-u
username|#uid] [-g groupname|#gid] [VAR=value] [-i|-s] [<command>]
usage: sudo -e [-AnS] [-C fd] [-g groupname|#gid] [-p prompt] [-u
username|#uid] file ...
ian@ian-laptop ~ $ sudo -R ian /media/Toshiba160gb
sudo: invalid option -- 'R'
usage: sudo [-n] -h | -K | -k | -L | -V | -v
usage: sudo -l[l] [-AnS] [-g groupname|#gid] [-U username] [-u username|#uid]
[-g groupname|#gid] [command]
usage: sudo [-AbEHnPS] [-C fd] [-g groupname|#gid] [-p prompt] [-u
username|#uid] [-g groupname|#gid] [VAR=value] [-i|-s] [<command>]
usage: sudo -e [-AnS] [-C fd] [-g groupname|#gid] [-p prompt] [-u
username|#uid] file ...
- Midnighter
- Level 6
- Posts: 1327
- Joined: Tue May 22, 2007 1:52 pm
- Location: Western Australia
Re: USB drive, was usable NTFS, now problematic ext3?
No need be snooty, I'm trying to help here. Now, re-read what you tried, and compare it to what i told you to do. You left something out.
Re: USB drive, was usable NTFS, now problematic ext3?
Code: Select all
sudo chown -R user:group /path/to/file
- Midnighter
- Level 6
- Posts: 1327
- Joined: Tue May 22, 2007 1:52 pm
- Location: Western Australia
Re: USB drive, was usable NTFS, now problematic ext3?
vincent wrote:Don't forget chown, it's the actual command Midnighter is referring to.Code: Select all
sudo chown -R user:group /path/to/file
D'oh! Ok, we both left something out.
My bad. I'd probably be more clear-headed if i got some sleep. Is now 6:12am, and i'm still up from last night.
Re: USB drive, was usable NTFS, now problematic ext3?
Based on your information you have 3 hard drives.
The 80GB drive Mint is installed on, formatted as Linux (/dev/sda)
A 500GB drive formatted NTFS (/dev/sdb)
And a 160GB drive formatted as Linux (/dev/sdc)
Open a terminal and enter these commands exactly as written.
Copy/paste the commands so you do not make a mistake.
sudo mkdir /media/Datasdc
then
sudo su
You will be asked for your user password. Enter your password and then enter the next command.
echo "/dev/sdc1 /media/Datasdc ext3 defaults,noatime 0 2" >> /etc/fstab
Now reboot and you will see that your ext3 drive is automatically mounted.
mick
The 80GB drive Mint is installed on, formatted as Linux (/dev/sda)
A 500GB drive formatted NTFS (/dev/sdb)
And a 160GB drive formatted as Linux (/dev/sdc)
Open a terminal and enter these commands exactly as written.
Copy/paste the commands so you do not make a mistake.
sudo mkdir /media/Datasdc
then
sudo su
You will be asked for your user password. Enter your password and then enter the next command.
echo "/dev/sdc1 /media/Datasdc ext3 defaults,noatime 0 2" >> /etc/fstab
Now reboot and you will see that your ext3 drive is automatically mounted.
mick
Re: USB drive, was usable NTFS, now problematic ext3?
nope, still no go
on reboot, there was a message that flashed up but it was too quick for me to read, but i thought i saw Datasdc
anyway i still can't delete anything from the drive
on reboot, there was a message that flashed up but it was too quick for me to read, but i thought i saw Datasdc
anyway i still can't delete anything from the drive
Re: USB drive, was usable NTFS, now problematic ext3?
A couple of questions.
Did you run the commands exactly as written?
Am I correct in assuming the drive we are talking about is the 160GB one?
Please provide the output of this command
And rerun this command again please to see if anything has changed.
thanks
mick
Did you run the commands exactly as written?
Am I correct in assuming the drive we are talking about is the 160GB one?
Please provide the output of this command
Code: Select all
cat /etc/fstab
Code: Select all
sudo sfdisk -l
mick
Re: USB drive, was usable NTFS, now problematic ext3?
Mick
a couple of answers;
I think so; although what you said would happen didn't quite - i was asked for the password after entering the first line rather than the second
you assume correctly
now for your requested outputs: ian@ian-laptop ~ $ cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid -o value -s UUID' to print the universally unique identifier
# for a device; this may be used with UUID= as a more robust way to name
# devices that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
# / was on /dev/sda1 during installation
UUID=8de25bfb-1a47-414f-994c-19027c260f36 / ext4 errors=remount-ro 0 1
# swap was on /dev/sda5 during installation
UUID=e5df5098-6bce-4a0f-9911-0cfb1a287082 none swap sw 0 0
/dev/scd0 /media/cdrom0 udf,iso9660 user,noauto,exec,utf8 0 0
/dev/sdc1 /media/Datasdc ext3 defaults,noatime 0 2
ian@ian-laptop ~ $
And: ian@ian-laptop ~ $ sudo sfdisk -l
[sudo] password for ian:
Disk /dev/sda: 9729 cylinders, 255 heads, 63 sectors/track
Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0
Device Boot Start End #cyls #blocks Id System
/dev/sda1 * 0+ 9357 9358- 75168103+ 83 Linux
/dev/sda2 9358 9728 371 2980057+ 5 Extended
/dev/sda3 0 - 0 0 0 Empty
/dev/sda4 0 - 0 0 0 Empty
/dev/sda5 9358+ 9728 371- 2980026 82 Linux swap / Solaris
Disk /dev/sdb: 60801 cylinders, 255 heads, 63 sectors/track
Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0
Device Boot Start End #cyls #blocks Id System
/dev/sdb1 0+ 60800 60801- 488384001 7 HPFS/NTFS
/dev/sdb2 0 - 0 0 0 Empty
/dev/sdb3 0 - 0 0 0 Empty
/dev/sdb4 0 - 0 0 0 Empty
Disk /dev/sdc: 19457 cylinders, 255 heads, 63 sectors/track
Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0
Device Boot Start End #cyls #blocks Id System
/dev/sdc1 0+ 19456 19457- 156288321 83 Linux
end: (c,h,s) expected (1023,254,63) found (1022,254,63)
/dev/sdc2 0 - 0 0 0 Empty
/dev/sdc3 0 - 0 0 0 Empty
/dev/sdc4 0 - 0 0 0 Empty
ian@ian-laptop ~ $
Hope this helps!
a couple of answers;
I think so; although what you said would happen didn't quite - i was asked for the password after entering the first line rather than the second
you assume correctly
now for your requested outputs: ian@ian-laptop ~ $ cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid -o value -s UUID' to print the universally unique identifier
# for a device; this may be used with UUID= as a more robust way to name
# devices that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
# / was on /dev/sda1 during installation
UUID=8de25bfb-1a47-414f-994c-19027c260f36 / ext4 errors=remount-ro 0 1
# swap was on /dev/sda5 during installation
UUID=e5df5098-6bce-4a0f-9911-0cfb1a287082 none swap sw 0 0
/dev/scd0 /media/cdrom0 udf,iso9660 user,noauto,exec,utf8 0 0
/dev/sdc1 /media/Datasdc ext3 defaults,noatime 0 2
ian@ian-laptop ~ $
And: ian@ian-laptop ~ $ sudo sfdisk -l
[sudo] password for ian:
Disk /dev/sda: 9729 cylinders, 255 heads, 63 sectors/track
Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0
Device Boot Start End #cyls #blocks Id System
/dev/sda1 * 0+ 9357 9358- 75168103+ 83 Linux
/dev/sda2 9358 9728 371 2980057+ 5 Extended
/dev/sda3 0 - 0 0 0 Empty
/dev/sda4 0 - 0 0 0 Empty
/dev/sda5 9358+ 9728 371- 2980026 82 Linux swap / Solaris
Disk /dev/sdb: 60801 cylinders, 255 heads, 63 sectors/track
Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0
Device Boot Start End #cyls #blocks Id System
/dev/sdb1 0+ 60800 60801- 488384001 7 HPFS/NTFS
/dev/sdb2 0 - 0 0 0 Empty
/dev/sdb3 0 - 0 0 0 Empty
/dev/sdb4 0 - 0 0 0 Empty
Disk /dev/sdc: 19457 cylinders, 255 heads, 63 sectors/track
Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0
Device Boot Start End #cyls #blocks Id System
/dev/sdc1 0+ 19456 19457- 156288321 83 Linux
end: (c,h,s) expected (1023,254,63) found (1022,254,63)
/dev/sdc2 0 - 0 0 0 Empty
/dev/sdc3 0 - 0 0 0 Empty
/dev/sdc4 0 - 0 0 0 Empty
ian@ian-laptop ~ $
Hope this helps!
Re: USB drive, was usable NTFS, now problematic ext3?
oh god now i can't unmount this blooming drive
message reads: Unable to unmount Toshiba160gb
Error unmounting: umount exited with exit code 1: helper failed with:
umount: only root can unmount /dev/sdc1 from /media/Datasdc
message reads: Unable to unmount Toshiba160gb
Error unmounting: umount exited with exit code 1: helper failed with:
umount: only root can unmount /dev/sdc1 from /media/Datasdc
Re: USB drive, was usable NTFS, now problematic ext3?
Hi Ian
You had 2 issues.
1)The drive needed to be auto mounted at boot.
2) The drive needs to be owned by you.
My instructions have successfully taken care of part 1 as evinced by the fact that
it is mounted, and you can't even unmount it.
The solution to problem 2 has already been proffered earlier in this thread
by both Midnighter and Vincent.
You need to Change Ownership of the drive.
The full command for you would be
I understand that you are new to Linux and that a lot of this appears difficult,
or arcane, therefore I have a recommendation.
Read as many of the tutorials here as you can, and also read other people's
posts about their problems. You will learn an amazing amount through osmosis.
All the answers to your issues were already here on the forum, the majority
in the first link I gave you to Fred's tutorial on auto mounting.
Just giving you the commands to enter does not teach you anything, but reading
the tutorials and figuring out how to apply it to your situation does.
Please accept this as advice not as criticism.
If this does not work, please let me know.
mick
You had 2 issues.
1)The drive needed to be auto mounted at boot.
2) The drive needs to be owned by you.
My instructions have successfully taken care of part 1 as evinced by the fact that
it is mounted, and you can't even unmount it.
The solution to problem 2 has already been proffered earlier in this thread
by both Midnighter and Vincent.
You need to Change Ownership of the drive.
The full command for you would be
Code: Select all
sudo chown -R ian:ian /media/Datasdc
or arcane, therefore I have a recommendation.
Read as many of the tutorials here as you can, and also read other people's
posts about their problems. You will learn an amazing amount through osmosis.
All the answers to your issues were already here on the forum, the majority
in the first link I gave you to Fred's tutorial on auto mounting.
Just giving you the commands to enter does not teach you anything, but reading
the tutorials and figuring out how to apply it to your situation does.
Please accept this as advice not as criticism.
If this does not work, please let me know.
mick
Re: USB drive, was usable NTFS, now problematic ext3?
There's always a need to be snooty.Midnighter wrote:No need be snooty
Have a nice day Midnighter.
Re: USB drive, was usable NTFS, now problematic ext3?
thanks mick
the chown command worked perfectly
case closed!
the chown command worked perfectly
case closed!