Mounted Fat32. But Read Only

Hello,

i mounted a fat32 partition located in my external 500GB USB Hard Disk to /mnt/fat32 using su root at shell.

then i see it is read only for my user account. the gnome file manager shows all the files and folders, but i cannot past or create anything.

so i #chmod 777 /mnt/fat32

but problem still remain same.


Similar Content



HOW-TO: FAT32/NTFS/ext3 For Windows/Linux Cross-compatible

I own a NAS D-Link DNS-320 running fun_plug 0.7 & transmissionBT.

I just bought a Transcend 2.5 inch 2TB USB HDD which is preformatted to NTFS.

Just wondering whether my NAS(linux) can write to my USB HDD for a reliable storage for transmissionBT.

Otherwise, if writing to NTFS is unstable in linux, how should I format my USB HDD. I know I could format as FAT32... but FAT32 has a 4GB file size limit.
Is it possible to format USB HDD as ext3 (linux file system)... and still compatible/read/write by Windows XP/7/8?

Do I Have To Use EXT 4 Instead Of FAT32 Formatting For Backups Using Luckybackup?

(BTW I'm running Xubuntu 15.04)

I'm starting to understand Luckybackup. And gold_finger said:

Quote:
Assuming your Xubuntu filesystem is Ext4, example of doing initial backup would be something like this:

* Spare USB with large partition formatted as Ext4 and labeled "BACKUPS"
I know the EXT4 is more friendly to Linux but all my flash drives are FAT32 (and I'll be backing up to those flash drives) and I'd really like to keep them that way (because sometimes I do plug them into Windows machines--and I know FAT32 works with both Windows and Linux). So is there any reason I would have to use Ext4 and not FAT32 in backing up stuff in LuckyBackup?

I confess to great ignorance about the difference between the EXT and FAT formats. Like if I do format a flash drive to EXT 4 and want to plug the flash drive into a Windows computer it just doesn't work? Like, what's the advantage to using EXT4 then if FAT 32 works with Linux and Windows? What are the disadvantages to using EXT4?

Thanks.

Convert FAT32 To NTFS Without Format.

Hello.
How can I Convert FAT32 to NTFS without format? In windows I can use below command and it work very nice but how about Linux?

convert Drive: /FS:NTFS

Thanks.

Permission Denied When Trying To Execute An Application On A SD Card

Hi,
I made some little applications with qt creator and i wanted to run them on an embedded linux board (linux 2.6.24). To transfer the files i use a SD card. If i move the applications to "/bin" after having mounted the SD card and then "chmod a+x" them then i have no problem running them.
But if i mount the SD card and try to run the applications directly in the folder where i mount it i have an error : "Permission denied". Also when using the command "ls" i notice that if i keep the files in the mounting folder and try to "chmod a+x" them, the modification don't happen. They stay "greyed" and don't go "green". (I don't know if this color code is a standart for linux terminal but maybe this could help you understand the problem).
When mounting the SD card i use the command :
Code:
mount -t vfat /dev/mmcblk0p1 /mnt/SD

So the files are located in /mnt/SD.

Am i missing something or is it not possible to run something like that ?

EDIT :
I tried "mount -t vfat -o umask=0000 /dev/mmcblk0p1 /mnt/SD" to chnage how i am mounting the SD card.

Still "Permission Denied".

With "ls -l" i can see that the permissions are staying :
-rw-rw-rw-

Even if i try something like "chmod 777".

It seems to be a problem related to the fact that the sd card is formated as fat32 but it must stay like that.

Dual-boot Grub Boot-repair Issue

Hello there,

I tried to install kali alongside windows and did it wrong probably. Now whenever I boot, grub loader sees only Kali and Free-DOS and doesn't see Windows.

I can still see the Windows partition in Kali and access the files however.
Searched online for a solution and saw that boot-repair could help me, however because some new update issue I cannot install it under Kali directly( see below link, it doesnt work for me).
askubuntu.com/questions/449818/cant-find-boot-repair-package-for-the-newest-version-of-ubuntu]

Long story short, I downloaded the iso version of boot-repair and tried to burn it onto a live-usb, but it doesn't load. All I get is a black screen with a terminal line running where I can't do anything.
I burned the iso using the terminal and the command below.
sudo dd bs=4M if=file.iso of=/dev/sdc
I burned the iso using unetbootin a couple of times and the same issue.


Any ideas? am I doing something wrong? How can I burn the iso disk to a live USB to run boot-repair? Or any other alternatives?

PS: first time linux user, I have no idea what am I doing so please be patient with me.





This is my output for running sfdisk -l.

Code:
sfdisk -l

Disk /dev/sda: 60801 cylinders, 255 heads, 63 sectors/track
Warning: extended partition does not start at a cylinder boundary.
DOS and Linux will interpret the contents differently.
Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0

   Device Boot Start     End   #cyls    #blocks   Id  System
/dev/sda1   *      0+    118     119-    955836    c  W95 FAT32 (LBA)
/dev/sda2      59654   60801-   1148-   9215829    c  W95 FAT32 (LBA)
/dev/sda3        119+  59653   59535- 478214340    f  W95 Ext'd (LBA)
/dev/sda4          0       -       0          0    0  Empty
/dev/sda5        119+  51030   50912- 408950091+   7  HPFS/NTFS/exFAT
/dev/sda6      58934+  59653     720-   5783368+  82  Linux swap / Solaris
/dev/sda7      51031+  58933    7903-  63479131   83  Linux
		start: (c,h,s) expected (1023,254,63) found (855,54,32)
		end: (c,h,s) expected (1023,254,63) found (565,254,63)

Disk /dev/sdb: 1020 cylinders, 240 heads, 62 sectors/track
Warning: The partition table looks like it was made
  for C/H/S=*/104/54 (instead of 1020/240/62).
For this listing I'll assume that geometry.
Units = cylinders of 2875392 bytes, blocks of 1024 bytes, counting from 0

   Device Boot Start     End   #cyls    #blocks   Id  System
/dev/sdb1   *      0+   2704-   2705-   7592960    b  W95 FAT32
		start: (c,h,s) expected (0,37,51) found (0,32,33)
		end: (c,h,s) expected (1023,103,54) found (945,103,54)
/dev/sdb2          0       -       0          0    0  Empty
/dev/sdb3          0       -       0          0    0  Empty
/dev/sdb4          0       -       0          0    0  Empty

Mounting An External USB Hard Drive

My attempts to back-up to an external hard disk finally met with apparent success but I cannot now mount the target drive.

To summarize:-
1. Installing a SATA hard disk, identical to my computer's main drive, in a USB 2.0 caddy and attaching this to the computer resulted in qualified recognition. 'fdisk' 'saw' both the main drive, as sda, and the USB drive, as sdb, respectively but initially noted that the latter, “... doesn't contain a valid partition table.” This was hardly surprising. At the point of first connection the external drive was essentially a 'bare metal' device, having had its data wiped. Nevertheless, 'fdisk' correctly reported its size, number of heads and cylinders, etc.
2. 'dmesg' also correctly identified the external disk as sdb, reporting its type and the USB port to which it is connected.
3. 'df' ignores the second hard drive, reporting only the main disk.
4. Attempts to clone/back-up the main disk to the external disk using the recommended tools EaseUS Todo back-up and RedoBackup, booting respectively from appropriate USB memory sticks, both failed. Neither utility was prepared to write to the external disk. EaseUS acknowledged the latter but crashed the whole computer when instructed to perform the clone. RedoBackup failed to recognize the external disk.
5. Then came the break-through. A bit more Net browsing led me to try the command 'dd if=/dev/sda of=/dev/sdb'. The main disk was bit-copied (cloned) to the external disk at roughly 20Gb per hour, meaning that my 80Gb disk was copied in just under 4 hours. Checking 'dd's resulting report showed what appeared to be a perfect copy.

So far, so good. I now have a back-up which, being identical to the main disk, should, I assume, be bootable. In the event of trouble with the main disk I should be able simply to exchange it for the external disk and carry on from the point at which I made my last back-up. I cannot, however, access and read the external disk. I assume that it must have a partition table and be mounted. The first requirement appears to have been resolved by the cloning operation. 'fdisk' reports no trouble with the partition table on the cloned external disk. It lists /dev/sb1 as the bootable Linux partition, /dev/sdb2 as the Extended partition and /dev/sdb5 as the Linux swap / Solaris partition, exactly mirroring the corresponding entries for the main, sda, drive.

My attempts to mount the external disk have all failed, however. I clearly do not understand the syntax of the mount command or have failed to meet some other requirement. 'mount' objected without hesitation to my early mistakes but “mount -t dev/sdb” was instantly accepted. No error messages or other output resulted and the command prompt was immediately redisplayed but 'mount' then failed to show that the external drive had been mounted. If I try something like 'mount -t /dev/sdb1 /mnt/xdisk', where xdisk is a directory I have been told to create, then I am presented with a prolix description of 'mount's syntax, most of which leaves me bewildered. 'mount' then once again confirms that sdb1 does not feature in the list of mounted devices.

Can someone offer any suggestions? I have read one or two of the other posts on this topic but none of the details match my problem too well and I did not understand some of the replies. If I try to add a line to /etc/fstab, for example, I find that I do not have a directory called 'fstab', only 'fstab.d' and that is empty.

I have roughly one year's experience with Linux Mint 13 which I chose because it so closely resembled Windows XP.

Trying To Dd A Server With LVM To Another Ext HD, Then To Another Server

I have Linux enterprise server 11 sp3 with 3 250 GB WD blue drives in a raid 5 configuration.

Server “A” (external drive not plugged in):
Code:
Disk /dev/sda: 499.0 GB, 499021512704 bytes
255 heads, 63 sectors/track, 60669 cylinders, total 974651392 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00059fd2

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *        2048     1028095      513024   83  Linux
/dev/sda2         1028096    21993471    10482688   82  Linux swap / Solaris
/dev/sda3        21993472   974651391   476328960   8e  Linux LVM

Disk /dev/mapper/VG_SYSTEM-ROOT: 487.8 GB, 487755612160 bytes
255 heads, 63 sectors/track, 59299 cylinders, total 952647680 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Disk /dev/mapper/VG_SYSTEM-ROOT doesn't contain a valid partition table

I am trying to clone this machine to another server, both servers are Dell Poweredge 1900, with 3 – 250 WD drives (the only difference is the ‘B’ server has WD Cavier drives), pretty much identical machines, same processor and ram. I have a 2TB ext hard drive that I am using to store the output of DD. I have booted from the CD to a rescue system, then mounted my 2TB ext and did the following:
Code:
    # dd if=/dev/sda conv=sync,noerror bs=64k | gzip –c | split –a3 –b 2G –verbose - /mnt/exthd/

This gives me the following files on my external hard drive:
Code:
    
-rwxr-xr-x 1 root root 2147483648 Jan 10 21:00 aaa
-rwxr-xr-x 1 root root 2147483648 Jan 10 21:31 aab
-rwxr-xr-x 1 root root 2147483648 Jan 10 21:53 aac
-rwxr-xr-x 1 root root 2147483648 Jan 10 22:05 aad
-rwxr-xr-x 1 root root 2147483648 Jan 10 22:10 aae
-rwxr-xr-x 1 root root 2147483648 Jan 10 22:17 aaf
-rwxr-xr-x 1 root root 2147483648 Jan 10 22:24 aag
-rwxr-xr-x 1 root root 2147483648 Jan 10 22:31 aah
-rwxr-xr-x 1 root root 2147483648 Jan 10 22:37 aai
-rwxr-xr-x 1 root root 2147483648 Jan 10 22:43 aaj
-rwxr-xr-x 1 root root 2147483648 Jan 10 22:50 aak
-rwxr-xr-x 1 root root 2147483648 Jan 10 22:56 aal
-rwxr-xr-x 1 root root 2147483648 Jan 10 23:02 aam
-rwxr-xr-x 1 root root 2147483648 Jan 10 23:06 aan
-rwxr-xr-x 1 root root 2147483648 Jan 10 23:12 aao
-rwxr-xr-x 1 root root 2147483648 Jan 10 23:32 aap
-rwxr-xr-x 1 root root  324998512 Jan 10 23:35 aaq

Now, I boot to the rescue system on server ‘B’ with the external drive plugged in, and run fdisk:
Code:
Disk /dev/sda: 498.8 GB, 498753077248 bytes
255 heads, 63 sectors/track, 60636 cylinders, total 974127104 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00059fd2

   Device Boot      Start         End      Blocks   Id  System

Disk /dev/sdb: 2000.4 GB, 2000398933504 bytes
255 heads, 63 sectors/track, 243201 cylinders, total 3907029167 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00015a3d

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1            2048  3907028991  1953513472    c  W95 FAT32 (LBA)

Notice sda is only 498.8GB where on server ’A’, it was 499.0. when I try to restore my files from the DD, I get an out of space error. To restore, I use the following:
Code:
    # cat /mnt/exthd/aa* | gunzip –c | dd of=/dev/sda
    
dd: writing to ‘/dev/sda’:  No space left on device
974127105+0 records in
974127104+0 records out
498753077248 bytes (499 GB) copied, 37067.3 s, 13.5MB/s

My guess, is that although the drives are the same capacity (3 – 250GB in RAID 5 array), the number of cylinders is different because it is a different model, and that is where it is running out of space, although I wouldn’t think it would.

Please correct me if I am wrong as I am a newbie, but if I do “# dd if=/dev/sda” that will take all the partitions with it? Such as sda1, sda2, sda3 correct?

Installing 17.1 Mate With Windows 8.1

Hello, I hope someone can assist. I have installed 17 on 2 laptops and 17.1 on another all with windows 8 upgraded to 8.1 Now I have a new PC with 8.1 and cannot get 17.1 to install. I go thru all the steps but when I get past "something else" and choose the "free space" that I partitioned in windows and hit install the window pops up with "no root file system is defined" "Please correct from partitioning menu.. I have never had this happen, did I not do something? There is 1 300mb(fat32, efi) partition, ntfa, free space(which is where I am trying to install Linux), 1 small and 1 large "free space". Then the define for boot loader installation, which I do not remember needing to do before. Can someone please help. The PC is an Acer Aspire, amd10, 3.7ghz, quad core, radeon hd 8670 graphics , 1 terabyte hdd, 4gb ram, windows 8.1

File Permission

I am writing a script to check the log file in /var/log , some files are only read by root , but the script use general user to access the system ( as the system do not accept root to ssh directly ) , therefore , it could not read such files .

Would advise what is the best method to solve this problem , copy the file to a special folder ? allow root to ssh ? create a user with root permission ?

very thanks

Flash Drive Read-only Half Solved

Lots of posts on internet about flash drives ending up read-only in Linux after using on a windows or mac systme. Gather it is a problem with incorrectly ejecting or the ejection being poorly done.

Usually I can go back to the box and re-eject and all is well. This time even GParted and the resident fedora 21 Disk Utility programs did not even see the drive (which Was visible under "files").

Using disk utility on the "offending" machine, it seems there were many files that were truncated (due to some eject issue? Note the ejection was done "according to Hoyle" ); regardless the flash drive was still read-only. Howeverk, re-trying GParted, which now recognized the drive, the drive was unmounted checked. Some repair was necessary. Currently, I can read, write and copy within the drive.

However, the drive itself is still only read-only for all but the owner (which is not even root). I cannot copy any file to the flash drive. Chmod does nothing (no matter if root or other user tries). I suppose I should be satisfied for the access there is, but if anyone has any more suggestions, it would be great.

Thanks in advance for any info/interest