You are not logged in.
Hullo there.!
I got myself a 8 Gb Usb flash drive formatted in FAT32 filesystem.I checked it in all 3 OSes I have on my PC i.e. Mandriva, Arch and XP.It Worked flawlessly in all three....for a day or two.
Now the flash drive refuses to work in Arch.Here are a few terminal outputs to help you guys get a understanding of the issue.:
fdisk -l
[root@myhost mnt]# fdisk -l
Disk /dev/sda: 40.0 GB, 40016019456 bytes
255 heads, 63 sectors/track, 4865 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x37233722
Device Boot Start End Blocks Id System
/dev/sda1 1 769 6176961 83 Linux
/dev/sda2 * 770 1422 5245222+ 7 HPFS/NTFS
/dev/sda3 1423 4865 27655897+ 5 Extended
/dev/sda5 1423 2075 5245191 83 Linux
/dev/sda6 2076 4734 21358386 83 Linux
/dev/sda7 4735 4865 1052226 82 Linux swap / Solaris
Unable to read /dev/sdb
mount -t vfat /dev/sdb1 /mnt/flash
mount: /dev/sdb1: can't read superblock
dmesg|tail
[root@myhost arch]# dmesg | tail
sdb: rw=0, want=8216, limit=1
Buffer I/O error on device sdb1, logical block 2
attempt to access beyond end of device
sdb: rw=0, want=8224, limit=1
Buffer I/O error on device sdb1, logical block 3
attempt to access beyond end of device
sdb: rw=0, want=8200, limit=1
Buffer I/O error on device sdb1, logical block 0
FAT: invalid media value (0x00)
VFS: Can't find a valid FAT filesystem on dev sdb.
As I said, the drive works fine in Mandriva and XP and even worked well in Arch for a day or two.I am clueless as to what suddenly went wrong.:|
Last edited by Poisonblack (2008-08-05 14:59:37)
It's a miracle that curiosity survives formal education.
Offline
[root@myhost mnt]# fdisk -l ... Unable to read /dev/sdb
That's strange - does it still work in the other O/S's? That makes me think the device is faulty...
Are you familiar with our Forum Rules, and How To Ask Questions The Smart Way?
BlueHackers // fscanary // resticctl
Offline
Poisonblack wrote:[root@myhost mnt]# fdisk -l ... Unable to read /dev/sdb
That's strange - does it still work in the other O/S's? That makes me think the device is faulty...
Yep...checked again in Mandriva and XP.Working fine in both.
Not sure if it's needed, but here's the output of fdisk -l from Mandriva
[root@localhost jay]# fdisk -l
Disk /dev/hda: 40.0 GB, 40016019456 bytes
255 heads, 63 sectors/track, 4865 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x37233722
Device Boot Start End Blocks Id System
/dev/hda1 1 769 6176961 83 Linux
/dev/hda2 * 770 1422 5245222+ 7 HPFS/NTFS
/dev/hda3 1423 4865 27655897+ 5 Extended
/dev/hda5 1423 2075 5245191 83 Linux
/dev/hda6 2076 4734 21358386 83 Linux
/dev/hda7 4735 4865 1052226 82 Linux swap / Solaris
Disk /dev/sda: 8178 MB, 8178892800 bytes
92 heads, 57 sectors/track, 3046 cylinders
Units = cylinders of 5244 * 512 = 2684928 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/sda1 2 3047 7983104 b W95 FAT32
It's a miracle that curiosity survives formal education.
Offline
dump file /etc/fstab in arch and mandriva
I am sorry but my English isn´t good....Thx
Offline
Found the solution.!
Turns out the culprit was the kernel version 2.6.26 that I got with pacman -Syu.So, I just did a pacman -Ud <path to previous kernel 2.6.25> and the problem disappeared.
Last edited by Poisonblack (2008-08-05 14:59:12)
It's a miracle that curiosity survives formal education.
Offline
Found the solution.!
Turns out the culprit was the kernel version 2.6.26 that I got with pacman -Syu.So, I just did a pacman -Ud <path to previous kernel 2.6.25> and the problem disappeared.
I have the same problem. Everything works fine on Windows and 2.6.25 kernel but not with 2.6.26
In my opinion this issue isn't solved.
Last edited by irfan (2008-08-13 23:48:09)
Offline
Poisonblack wrote:Found the solution.!
Turns out the culprit was the kernel version 2.6.26 that I got with pacman -Syu.So, I just did a pacman -Ud <path to previous kernel 2.6.25> and the problem disappeared.I have the same problem. Everything works fine on Windows and 2.6.25 kernel but not with 2.6.26
In my opinion this issue isn't solved.
Same here. Of course this issue isn't solved by downgrading the kernel.
Offline
No it's not solved, and it's not restricted to flash drives..........................
I have Arch installed on an ide(pata) drive as sdb1 (hd1,0) - runs fine. Newest kernel runs fine. Upgraded Arch on usb drive (parallel ide) (hd1,5) sdb6 and arch is dead. From the "crash prompt" in /dev directory, nothing exists beyond sdb4. Not seeing anything beyond the 4th partition - here is a some examples using sfdisk and fdisk:
From archlinux (hd1,0) generic ide pata drive
\>> sfdisk -l
Disk /dev/sda: 14589 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+ 14587 14588- 117178078+ 7 HPFS/NTFS <---windoz
/dev/sda2 0 - 0 0 0 Empty
/dev/sda3 0 - 0 0 0 Empty
/dev/sda4 0 - 0 0 0 Empty
Disk /dev/sdb: 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/sdb1 0+ 2676 2677- 21502971 83 Linux <---archlinux
/dev/sdb2 2677 5353 2677 21503002+ 83 Linux <---fedora 8
/dev/sdb3 5354 8030 2677 21503002+ 83 Linux <--- ubuntu
/dev/sdb4 8031 19456 11426 91779345 5 Extended
/dev/sdb5 8031+ 8298 268- 2152678+ 82 Linux swap / Solaris
/dev/sdb6 8299+ 19456 11158- 89626603+ 7 HPFS/NTFS
Disk /dev/sdc: 0 cylinders, 255 heads, 63 sectors/track <---USB drive - O cylinders?
lseek: Invalid argumentsfdisk: seek error on /dev/sdc - cannot seek to 122897250
Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0Device Boot Start End #cyls #blocks Id System
/dev/sdc1 0+ 2549 2550- 20482874+ 83 Linux
/dev/sdc2 2550 5099 2550 20482875 83 Linux
/dev/sdc3 5100 7649 2550 20482875 83 Linux
/dev/sdc4 7650 14592 6943 55769647+ 5 Extended
\>> fdisk -l
Disk /dev/sda: 120.0 GB, 120000000000 bytes
255 heads, 63 sectors/track, 14589 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xb84cb84c
Device Boot Start End Blocks Id System
/dev/sda1 * 1 14588 117178078+ 7 HPFS/NTFS
Disk /dev/sdb: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xfd6a1e00
Device Boot Start End Blocks Id System
/dev/sdb1 1 2677 21502971 83 Linux
/dev/sdb2 2678 5354 21503002+ 83 Linux
/dev/sdb3 5355 8031 21503002+ 83 Linux
/dev/sdb4 8032 19457 91779345 5 Extended
/dev/sdb5 8032 8299 2152678+ 82 Linux swap / Solaris
/dev/sdb6 8300 19457 89626603+ 7 HPFS/NTFS
Unable to read /dev/sdc <------------------
\>> cat /proc/partitions
major minor #blocks name
8 0 117187500 sda
8 1 117178078 sda1
8 16 156290904 sdb
8 17 21502971 sdb1
8 18 21503002 sdb2
8 19 21503002 sdb3
8 20 1 sdb4
8 21 2152678 sdb5
8 22 89626603 sdb6
8 32 0 sdc <------------------???????
8 33 20482874 sdc1
8 34 20482875 sdc2
8 35 20482875 sdc3
8 36 1 sdc4
missing sdb5,sdb6,sdb7,sdb8
This from fedora:
Disk /dev/sdc: 120.0 GB, 120034123776 bytes
255 heads, 63 sectors/track, 14593 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00568327
Device Boot Start End Blocks Id System
/dev/sdc1 1 2550 20482874+ 83 Linux
/dev/sdc2 2551 5100 20482875 83 Linux
/dev/sdc3 5101 7650 20482875 83 Linux
/dev/sdc4 7651 14593 55769647+ 5 Extended
/dev/sdc5 7651 7780 1044224+ 82 Linux swap / Solaris
/dev/sdc6 7781 10330 20482874+ 83 Linux
/dev/sdc7 10331 12412 16723633+ 83 Linux
/dev/sdc8 12413 14593 17518851 7 HPFS/NTFS
\>> cat /proc/partitions
major minor #blocks name
1 0 16384 ram0
1 1 16384 ram1
1 2 16384 ram2
1 3 16384 ram3
1 4 16384 ram4
1 5 16384 ram5
1 6 16384 ram6
1 7 16384 ram7
1 8 16384 ram8
1 9 16384 ram9
1 10 16384 ram10
1 11 16384 ram11
1 12 16384 ram12
1 13 16384 ram13
1 14 16384 ram14
1 15 16384 ram15
8 0 117187500 sda
8 1 117178078 sda1
8 16 156290904 sdb
8 17 21502971 sdb1
8 18 21503002 sdb2
8 19 21503002 sdb3
8 20 1 sdb4
8 21 2152678 sdb5
8 22 89626603 sdb6
8 32 117220824 sdc
8 33 20482874 sdc1
8 34 20482875 sdc2
8 35 20482875 sdc3
8 36 1 sdc4
8 37 1044224 sdc5
8 38 20482874 sdc6
8 39 16723633 sdc7
8 40 17518851 sdc8
Fedora and ubuntu read and mount and automount just fine.
If I try mount -t ext3 /dev/sdc1 /media/sdc1 it fails. Dmesg | tail says (as was happening to Poisonblack)
\>> dmesg | tail
attempt to access beyond end of device
sdc: rw=0, want=5, limit=1
EXT3-fs: unable to read superblock
usb 3-3: USB disconnect, address 5
attempt to access beyond end of device
sdc: rw=0, want=5, limit=1
EXT3-fs: unable to read superblock
attempt to access beyond end of device
sdc: rw=0, want=5, limit=1
EXT3-fs: unable to read superblock
So, until the kernel is fixed, axel could do me a a great favor explaining <path to previous kernel 2.6.25>.
Not that that's going to help w/ the usb drive..............
Unless somebody come up w/ an idea. How can I downgrade a kernel on a partition the operating system can't see??
thanks,
lynnevan
Last edited by lynnevan (2008-08-18 08:57:42)
Offline
Same problem on this machine. Please don´t mark this topic solved.
Offline
So, until the kernel is fixed, axel could do me a a great favor explaining <path to previous kernel 2.6.25>.
Not that that's going to help w/ the usb drive..............
Unless somebody come up w/ an idea. How can I downgrade a kernel on a partition the operating system can't see??
thanks,
lynnevan
This is the <path to previous kernel 2.6.25>, pacman's cache. Previous kernel versions should be there unless you have cleared the cache with pacman -Scc
$ ls /var/cache/pacman/pkg/ | grep kernel26
kernel26-2.6.24.1-2-i686.pkg.tar.gz
kernel26-2.6.24.3-1-i686.pkg.tar.gz
kernel26-2.6.24.3-3-i686.pkg.tar.gz
kernel26-2.6.24.4-1-i686.pkg.tar.gz
kernel26-2.6.25.10-1-i686.pkg.tar.gz
kernel26-2.6.25.11-1-i686.pkg.tar.gz
kernel26-2.6.25.4-1-i686.pkg.tar.gz
kernel26-2.6.25.6-1-i686.pkg.tar.gz
kernel26-2.6.26.2-1-i686.pkg.tar.gz
However I don't know how this can help you...
Since your post is the most detailed here why don't you post a bug report for kernel26? A don't see any in http://bugs.archlinux.org/ and I don't see a new kernel in testing repository either...
Offline
It's fixed in 2.6.26.3, I hope this is built soon since I cannot use any of my flashdrives.. And I dont want tot go back to .25
Offline
It's fixed in 2.6.26.3, I hope this is built soon since I cannot use any of my flashdrives.. And I dont want tot go back to .25
Thanks for a great news
EDIT:
confirmed ...my memory stick work again
Last edited by irfan (2008-08-21 11:00:32)
Offline
Is it worth an afford to install kernel 2.6.26-3 from testing or is it better to wait until it will be moved to core?
BTW - Thanks God it's only a bug. I was recently trying to 'improve' my Arch, and I thought that it is my fault that USB stick stopped working
Some applications are WYSIWYG, and some are WYSIWTF.
Offline
2.6.26.3 from testing works well for me
Offline
Okay - question not valid. new kernel just hit to core. Time to download it...
Thanks for answer anyway. Now I'll have a looong looong way to clean up the mess I made in my system
Some applications are WYSIWYG, and some are WYSIWTF.
Offline