Yes, the card has been in use for nearly two years and has 250G of data. The problem only began recently. It was purchased on Amazon for $110 +/- a couple of years ago. On Tue, 8 Aug 2023 12:33:13 -0500 Roger Heflin <rogerheflin@xxxxxxxxx> wrote: > Have you ever had this card work in anything? > > And if you have used this card for a long time how long have you used > it for ? > > And where did you purchase the card from and when, and how much did > it cost? > > On Tue, Aug 8, 2023 at 11:43 AM Geoffrey Leach > <geoffleach.gl@xxxxxxxxx> wrote: > > > > Answers to questions below. FWIW, on both systems a different SD > > card performs with no problem. That and the error message from > > e2fsck lead me to suspect that my problem is a bad superblock on > > the card. I've been unable to find any instructions on how to get > > e2fsck to mark the current superblock bad and create a new > > superblock. > > > > dmesg says > > [ +41.509460] EXT4-fs (mmcblk0p1): recovery complete > > [ +0.001206] EXT4-fs (mmcblk0p1): mounted filesystem > > 0fd984c4-cf88-408a-8ba5-15b64500bd5c r/w with ordered data mode. > > Quota mode: none. [Aug 7 20:36] EXT4-fs (mmcblk0p1): unmounting > > filesystem 0fd984c4-cf88-408a-8ba5-15b64500bd5c. [ +5.667580] > > EXT4-fs (mmcblk0p1): recovery complete [ +0.001092] EXT4-fs > > (mmcblk0p1): mounted filesystem > > 0fd984c4-cf88-408a-8ba5-15b64500bd5c r/w with ordered data mode. > > Quota mode: none. [ +12.728248] EXT4-fs (mmcblk0p1): unmounting > > filesystem 0fd984c4-cf88-408a-8ba5-15b64500bd5c. > > > > The two systems are intel-based laptops running up-to-date Fedora > > 37. The original problem system is a CLEVO W150HRM > > > > *-device > > description: SD Card > > product: SD01T > > vendor: SanDisk > > physical id: aaaa > > logical name: /dev/mmcblk0 > > version: 8.5 > > date: 07/2022 > > serial: 3601907256 > > size: 953GiB (1023GB) > > capabilities: sd partitioned partitioned:dos > > configuration: logicalsectorsize=512 > > sectorsize=512 signature=09ca262d > > *-volume > > description: EXT4 volume > > vendor: Linux > > physical id: 1 > > logical name: /dev/mmcblk0p1 > > logical name: /Media/SDXC > > version: 1.0 > > serial: 0fd984c4-cf88-408a-8ba5-15b64500bd5c > > size: 953GiB > > capacity: 953GiB > > capabilities: primary journaled > > extended_attributes large_files huge_files dir_nlink > > recover extents ext4 ext2 initialized > > configuration: created=2022-09-10 21:14:20 > > filesystem=ext4 label=MP4 > > lastmountpoint=/Media/SDXC modified=2022-10-07 > > 08:25:42 mount.fstype=ext4 > > mount.options=rw,nosuid,nodev,noexec,relatime > > mounted=2022-10-07 08:25:42 state=mounted > > > > The second system is a StarLabs StarLab mk III Aside from more > > memory, SD main storage, more recent Intel CPU ... not much > > different :-) Despite all of that, the problem with the SD is the > > same. > > > > On Mon, 7 Aug 2023 18:23:12 -0500 > > Roger Heflin <rogerheflin@xxxxxxxxx> wrote: > > > > > What is in messages? The sorts of errors you are getting indicate > > > that the card is simply not working at all for some reason on > > > linux. > > > > > > And how different were the 2 systems that you tried it on? > > > > > > I have a nice 256G UHS-II card that works fine in my camera, but > > > in the laptop with the fastest mmc reader it will get a hard read > > > error that shows in dmesg/messages that prevents it from working > > > at any level. > > > > > > You need the errors coming out of the kernel. Running commands > > > from userspace against the card won't tell you anything about > > > what the kernel itself thinks is wrong. > > > > > > On Mon, Aug 7, 2023 at 5:52 PM Geoffrey Leach > > > <geoffleach.gl@xxxxxxxxx> wrote: > > > > > > > > Thanks for the reply. > > > > > > > > The SD card behaves the same way on another system (F37) > > > > > > > > In desperation, I removed all of the date and used gparted to > > > > delete and recreate the file system. It did than, then restored > > > > all of the deleted files. > > > > > > > > I have the new result below. It appears that I need to replace > > > > the superblock, but I've been unable to discover how to do that. > > > > > > > > # e2fsck /dev/mmcblk0p1 > > > > e2fsck 1.46.5 (30-Dec-2021) > > > > MP4: recovering journal > > > > Superblock needs_recovery flag is clear, but journal has data. > > > > Run journal anyway<y>? yes > > > > e2fsck: unable to set superblock flags on MP4 > > > > MP4: ********** WARNING: Filesystem still has errors ********** > > > > > > > > > > > > On Mon, 7 Aug 2023 11:05:17 -0500 > > > > Roger Heflin <rogerheflin@xxxxxxxxx> wrote: > > > > > > > > > What does it show in messages after the mount? That is where > > > > > I would expect the underlying read errors to be. > > > > > > > > > > I have also had some issues with certain sdxc readers seeming > > > > > to not work well with some cards. There are also a > > > > > significant number of MMC changes going into the kernel > > > > > recently. There is an entire new set of code (not sure if > > > > > has made it into the latest released kernel yet) for the > > > > > UHS-II cards (All UHS-II cards are working backwards compat > > > > > for UHS-I). > > > > > > > > > > You might try a different machine/reader and see if it works > > > > > on a different one. The issues I saw only happened with the > > > > > larger and/or faster cards and only in some readers. > > > > > > > > > > On Mon, Aug 7, 2023 at 10:19 AM Geoffrey Leach > > > > > <geoffleach.gl@xxxxxxxxx> wrote: > > > > > > > > > > > > I have a 1TB SanDisk XC SD card, which has developed a > > > > > > reluctance to create files. > > > > > > > > > > > > UUID=0fd984c4-cf88-408a-8ba5-15b64500bd5c /Media/SDXC > > > > > > ext4 noauto,rw,user 0 0 > > > > > > > > > > > > % sudo mount /Media/SDXC > > > > > > % touch /Media/SDXC/foo > > > > > > % ls /Media/SDXC/foo > > > > > > /Media/SDXC/foo > > > > > > % sudo umount /Media/SDXC > > > > > > % sudo mount /Media/SDXC > > > > > > % ls /Media/SDXC/foo > > > > > > /bin/ls: cannot access '/Media/SDXC/foo': No such file or > > > > > > directory > > > > > > > > > > > > I used root to mount, just to be sure. User mount has the > > > > > > same problem. gparted reported a problem with the > > > > > > superblock which was resolved by re-formatting and > > > > > > re-creating the partition table. The card has just one > > > > > > partition. > > > > > > > > > > > > Suggestions for further diagnosis would be appreciated. > > > > > > > > > > _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
