Installation / Removal > Sandisk - Installation/Removal

Sansapatcher doesn't recognize e250

<< < (2/4) > >>

cpchan:

--- Quote from: coarse.sand on May 18, 2007, 01:03:02 AM ---I had the same problem as those above where the Sansa wasn't being detected by the ./sansapatcher command, and it also happened to be in standard FAT. I've switched the filing system to FAT32 now and it hasn't resolved anything. When inputed as "sudo ./sansapatcher", this is what appeared:
--- End quote ---

coarse.sand, I see what you are trying to do now. The problem is that your system is set to auto-mount. You must unmount /dev/sda1 first and then run sansapatcher. If you still have problems, post the output of the command:

lsusb

Charles

linuxstb:
If you type "fdisk -l" (the letter "ell") you should see the partition tables of all attached disks displayed.  Can you copy and paste the partition table of your Sansa into a messsage here so I can see what Sansapatcher should be looking for?

cpchan:

--- Quote from: linuxstb on May 18, 2007, 03:26:48 AM ---If you type "fdisk -l" (the letter "ell") you should see the partition tables of all attached disks displayed.  Can you copy and paste the partition table of your Sansa into a messsage here so I can see what Sansapatcher should be looking for?

--- End quote ---

His Sansa is attached to /dev/sda. I know this because I taught the OP how to make a vfat filesystem on /dev/sda1. So Linux is seeing the device. However, sansapatcher needs raw access to the device so he should unmount first.

Charles
 

coarse.sand:
Output from fdisk -l

62 heads, 62 sectors/track, 1021 cylinders
Units = cylinders of 3844 * 512 = 1968128 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1               1        1011     1942270+   6  FAT16
Partition 1 has different physical/logical beginnings (non-Linux?):
     phys=(0, 8, 12) logical=(0, 8, 20)
Partition 1 has different physical/logical endings:
     phys=(241, 212, 35) logical=(1010, 42, 12)
Partition 1 does not end on cylinder boundary.
/dev/sda2            1011        1022       20480   84  OS/2 hidden C: drive
Partition 2 has different physical/logical beginnings (non-Linux?):
     phys=(241, 212, 36) logical=(1010, 42, 13)
Partition 2 has different physical/logical endings:
     phys=(244, 97, 45) logical=(1021, 20, 52)
Partition 2 does not end on cylinder boundary.


Ouput from lsusb

Bus 003 Device 015: ID 0781:7421 SanDisk Corp.
Bus 003 Device 001: ID 0000:0000  
Bus 002 Device 001: ID 0000:0000  
Bus 001 Device 001: ID 0000:0000  


Under the Ubuntu properties GUI, the Sansa is claiming that it's using the vfat FAT32 filing system, yet the output above from fdisk indicates that it's still in FAT16. Also, unmounting hasn't fixed the issue yet, probably because for whatever reason it's still in FAT16.

cpchan:

--- Quote from: coarse.sand on May 18, 2007, 05:02:05 PM ---Under the Ubuntu properties GUI, the Sansa is claiming that it's using the vfat FAT32 filing system, yet the output above from fdisk indicates that it's still in FAT16.

--- End quote ---

OK, remake the filesystem by using the command:

mkfs.vfat -F 32 /dev/sda1

while the filesystem is umounted. I forgot to include the "-F 32" last time.

Charles

Navigation

[0] Message Index

[#] Next page

[*] Previous page