Tiny Core Linux
Tiny Core Base => TCB Bugs => Topic started by: Onyarian on December 14, 2009, 03:07:57 PM
-
In all other releases mi 8Gb pen drive is detected as /dev/sdb and mounted in /mnt/sdb.
In this release 2.6.1 this pen drive is not detected, so I can't mount it. Other pens, per example, detected as /dev/sdc1 are mounted in /mnt/sdc1, but this sdb no, so finally I have to turn back to 2.6 version.
Is perhaps the updated rebuildfstab of 2.6.1?
-
What does fdisk -l show ?
What filesystem is on the pendrive that does not use a partition?
Be sure to test 2.7rc1 when it appears.
-
The pendrive is a LaCie 8Gb original formated with vfat.
The results with tc 2.6:
in fstab
/dev/sdb /mnt/sdb vfat noauto,users,exec,umask=000 0 0 # Added by TC
--
in fdisk -l
Disk /dev/sdb: 8086 MB, 8086618112 bytes
249 heads, 62 sectors/track, 1023 cylinders
Units = cylinders of 15438 * 512 = 7904256 bytes
Device Boot Start End Blocks Id System
/dev/sdb1 ? 125407 245362 925929529+ 68 Unknown
Partition 1 has different physical/logical beginnings (non-Linux?):
phys=(116, 100, 32) logical=(125406, 168, 29)
Partition 1 has different physical/logical endings:
phys=(288, 101, 46) logical=(245361, 67, 59)
Partition 1 does not end on cylinder boundary
/dev/sdb2 ? 86163 121076 269488144 79 Unknown
Partition 2 has different physical/logical beginnings (non-Linux?):
phys=(357, 32, 43) logical=(86162, 245, 47)
Partition 2 has different physical/logical endings:
phys=(0, 13, 10) logical=(121075, 74, 42)
Partition 2 does not end on cylinder boundary
/dev/sdb3 ? 34914 125493 699181456 53 Unknown
Partition 3 has different physical/logical beginnings (non-Linux?):
phys=(345, 32, 19) logical=(34913, 40, 18)
Partition 3 has different physical/logical endings:
phys=(324, 77, 19) logical=(125492, 109, 49)
Partition 3 does not end on cylinder boundary
/dev/sdb4 ? 90338 90339 10668+ 49 Unknown
Partition 4 has different physical/logical beginnings (non-Linux?):
phys=(87, 1, 0) logical=(90337, 81, 36)
Partition 4 has different physical/logical endings:
phys=(335, 78, 2) logical=(90338, 176, 44)
Partition 4 does not end on cylinder boundary
Partition table entries are not in disk order
----------
and with tc 2.6.1:
No entry in fstab
--
in fdisk -l
Disk /dev/sdb: 8086 MB, 8086618112 bytes
249 heads, 62 sectors/track, 1023 cylinders
Units = cylinders of 15438 * 512 = 7904256 bytes
Device Boot Start End Blocks Id System
/dev/sdb1 ? 125407 245362 925929529+ 68 Unknown
Partition 1 has different physical/logical beginnings (non-Linux?):
phys=(116, 100, 32) logical=(125406, 168, 29)
Partition 1 has different physical/logical endings:
phys=(288, 101, 46) logical=(245361, 67, 59)
Partition 1 does not end on cylinder boundary
/dev/sdb2 ? 86163 121076 269488144 79 Unknown
Partition 2 has different physical/logical beginnings (non-Linux?):
phys=(357, 32, 43) logical=(86162, 245, 47)
Partition 2 has different physical/logical endings:
phys=(0, 13, 10) logical=(121075, 74, 42)
Partition 2 does not end on cylinder boundary
/dev/sdb3 ? 34914 125493 699181456 53 Unknown
Partition 3 has different physical/logical beginnings (non-Linux?):
phys=(345, 32, 19) logical=(34913, 40, 18)
Partition 3 has different physical/logical endings:
phys=(324, 77, 19) logical=(125492, 109, 49)
Partition 3 does not end on cylinder boundary
/dev/sdb4 ? 90338 90339 10668+ 49 Unknown
Partition 4 has different physical/logical beginnings (non-Linux?):
phys=(87, 1, 0) logical=(90337, 81, 36)
Partition 4 has different physical/logical endings:
phys=(335, 78, 2) logical=(90338, 176, 44)
Partition 4 does not end on cylinder boundary
Partition table entries are not in disk order
---------
perhaps, as a solution, it has to be newly formated, but it can happen with others too, and in the previous releases is well detected.
I will wait to test it with 2.7rc1.
-
Therein lies the problem, you do have psrtitions on the drive, but no filesystem can be detected in any of those partitions.
-
I have a similar problem - a usb device with no partitions.
mounting /dev/sda manually does work.
I guess the problem is in the device - but other systems (windows and linux) detect it.
Is there a way to modify rebuildfstab to detect such devices?
Ophir
-
Unless you are running 2.6.1, you should start a new thread.
If you are running 2.6.1, you should update to 2.11.
-
Since 2.6.1, it relies on `fdisk -l` which requires partitions.