Home of the Squeezebox™ & Transporter® network music players.
Results 1 to 10 of 10
  1. #1
    Junior Member
    Join Date
    Oct 2018
    Posts
    18

    Extreme SD card support flakiness

    Is there anything that can be done with SD card issues on PCP and RPi in general?

    Today, after a couple of days of doing nothing (no power loss inbetween!) I tried to do something with LMS - and got message about lack of write permissions to settings directory on mmcblk0p2. Rebooted - bang! - EXT4-fs error. Nothing can be done except reimaging the card, which is actually in perfect state according to any possible fsck checks...

    I got such issues sometimes even just after rebooting RPi with PCP - and I've tried 3 different cards so far. They seem to be unfortunately well known.

    While PCP is very well thought out software, RPi seems to be unfortunately very unreliable hardware. Pity Logitech devices are not available anymore..

  2. #2
    Senior Member
    Join Date
    Apr 2005
    Location
    UK/London
    Posts
    1,277
    Iĺve rarely had SD card problems including running LMS under pCP with LMS using the SD card.
    However, you could experiment with USB stick formatted as Ext4 and move LMS data over to that.
    Paul Webster
    http://dabdig.blogspot.com
    Author Radio France (FIP etc) plugin

  3. #3
    Senior Member
    Join Date
    Sep 2005
    Posts
    2,790
    hmm...

    my harddisk from the "new" LMS Server is already 10682 Hours old.
    2 years earlier i bought and installed my last SD Card for my RPIs _running std. Rasbian with a small /tmp as ramdisk.
    These SD Cards have no issues at all.
    And these RPIs are at least updated every month with the latest rasbian packages.


    The only hint is: The guy who buys cheap (sd cards) will end in buying more than one card.

  4. #4
    Senior Member
    Join Date
    Jun 2010
    Posts
    100
    Quote Originally Posted by Xyzzy View Post
    Is there anything that can be done with SD card issues on PCP and RPi in general?
    Not disputing your experience but it differs from mine. I have been using Pis for over two years now, one as a player and the other as server. Been using the same SD cards all the time and have never experienced a problem. The server works quite hard, as well as LMS for the music, it hosts a LAMP server which streams content for videos, a big virtual art collection and all our photos.

    I am using Kingston 32GB cards, I don't know if the size has any bearing on their robustness?

    Regards

    Jerry

  5. #5
    Junior Member
    Join Date
    Oct 2018
    Posts
    18
    Used Samsung Evo Plus and two different lines of Kingston.

    The only thing that may be related is that I have another NTFS-formatted microSD as /dev/sda1 and it somehow confuses PCP.
    Below is inifinite reboot loop that went away after physically removing the 2nd card.


  6. #6
    Junior Member
    Join Date
    Oct 2018
    Posts
    18
    Unfortunately it doesn't go away - I think I'll just sell it and buy some android box with digital output...
    Here is how it dies (just tried to refresh LMS library after some time idle):
    [660378.888722] mmc0: fsm 1, hsts 1
    [660378.888725] mmc0: PIO read timeout - EDM 10861
    [660378.888804] mmc0: Problem switching card into high-speed mode!
    [660378.892522] mmc0: unexpected command 25 error
    [660378.892605] mmcblk0: error -84 sending status command, retrying
    [660378.892629] mmcblk0: error -84 sending status command, retrying
    [660378.892652] mmcblk0: error -84 sending status command, aborting
    [660378.892749] EXT4-fs warning (device mmcblk0p2): ext4_end_bio:323: I/O error 10 writing to inode 32782 (offset 0 size 0 starting block 63461)
    [660378.892761] Buffer I/O error on device mmcblk0p2, logical block 26593
    [660378.892764] Buffer I/O error on device mmcblk0p2, logical block 26594
    [660378.892767] Buffer I/O error on device mmcblk0p2, logical block 26595
    [660378.892770] Buffer I/O error on device mmcblk0p2, logical block 26596
    [660378.892801] EXT4-fs warning (device mmcblk0p2): ext4_end_bio:323: I/O error 10 writing to inode 32782 (offset 0 size 0 starting block 63489)
    [660378.892805] Buffer I/O error on device mmcblk0p2, logical block 26609
    [660378.892808] Buffer I/O error on device mmcblk0p2, logical block 26610
    [660378.892812] Buffer I/O error on device mmcblk0p2, logical block 26611
    [660378.892815] Buffer I/O error on device mmcblk0p2, logical block 26612
    [660378.892820] Buffer I/O error on device mmcblk0p2, logical block 26613
    [660378.892823] Buffer I/O error on device mmcblk0p2, logical block 26614
    [660378.892841] EXT4-fs warning (device mmcblk0p2): ext4_end_bio:323: I/O error 10 writing to inode 32779 (offset 0 size 0 starting block 111299)
    [660378.892855] EXT4-fs warning (device mmcblk0p2): ext4_end_bio:323: I/O error 10 writing to inode 32779 (offset 0 size 0 starting block 111547)
    [660378.893024] EXT4-fs warning (device mmcblk0p2): ext4_end_bio:323: I/O error 10 writing to inode 32779 (offset 0 size 0 starting block 111550)
    [660378.893130] EXT4-fs warning (device mmcblk0p2): ext4_end_bio:323: I/O error 10 writing to inode 32812 (offset 420864 size 45056 starting block 134088)
    [660378.893146] print_req_error: I/O error, dev loop9, sector 21912
    [660378.893163] Aborting journal on device mmcblk0p2-8.
    [660378.893191] SQUASHFS error: squashfs_read_data failed to read block 0xaae9ee
    [660378.893196] SQUASHFS error: Unable to read fragment cache entry [aae9ee]
    [660378.893200] SQUASHFS error: Unable to read page, block aae9ee, size 7faa
    [660378.893204] print_req_error: I/O error, dev loop9, sector 21914
    [660378.893226] SQUASHFS error: Unable to read fragment cache entry [aae9ee]
    [660378.893229] SQUASHFS error: Unable to read page, block aae9ee, size 7faa
    [660378.893233] print_req_error: I/O error, dev loop9, sector 21916
    [660378.893241] SQUASHFS error: Unable to read fragment cache entry [aae9ee]
    [660378.893244] SQUASHFS error: Unable to read page, block aae9ee, size 7faa
    [660378.893248] SQUASHFS error: Unable to read fragment cache entry [aae9ee]
    [660378.893251] SQUASHFS error: Unable to read page, block aae9ee, size 7faa
    [660378.893264] print_req_error: I/O error, dev loop9, sector 21918
    [660378.893269] JBD2: Error -5 detected when updating journal superblock for mmcblk0p2-8.
    [660378.893271] SQUASHFS error: Unable to read fragment cache entry [aae9ee]
    [660378.893273] SQUASHFS error: Unable to read page, block aae9ee, size 7faa
    [660378.893278] SQUASHFS error: Unable to read fragment cache entry [aae9ee]
    [660378.893281] SQUASHFS error: Unable to read page, block aae9ee, size 7faa
    [660378.893287] print_req_error: I/O error, dev loop9, sector 21920
    [660378.893292] SQUASHFS error: Unable to read fragment cache entry [aae9ee]
    [660378.893295] SQUASHFS error: Unable to read page, block aae9ee, size 7faa
    [660378.893300] SQUASHFS error: Unable to read fragment cache entry [aae9ee]
    [660378.893303] SQUASHFS error: Unable to read page, block aae9ee, size 7faa
    [660378.893307] SQUASHFS error: Unable to read fragment cache entry [aae9ee]
    [660378.893309] JBD2: Detected IO errors while flushing file data on mmcblk0p2-8
    [660378.893312] SQUASHFS error: Unable to read page, block aae9ee, size 7faa
    [660378.893315] print_req_error: I/O error, dev loop9, sector 21922
    [660378.893319] mmc0: card 0007 removed
    [660378.893324] SQUASHFS error: Unable to read fragment cache entry [aae9ee]
    [660378.893327] SQUASHFS error: Unable to read page, block aae9ee, size 7faa
    [660378.893332] SQUASHFS error: Unable to read fragment cache entry [aae9ee]
    [660378.893335] SQUASHFS error: Unable to read page, block aae9ee, size 7faa
    [660378.893341] print_req_error: I/O error, dev loop9, sector 21924
    [660378.893346] SQUASHFS error: Unable to read fragment cache entry [aae9ee]
    [660378.893349] SQUASHFS error: Unable to read page, block aae9ee, size 7faa
    [660378.893354] SQUASHFS error: Unable to read fragment cache entry [aae9ee]
    [660378.893357] SQUASHFS error: Unable to read page, block aae9ee, size 7faa
    [660378.893361] SQUASHFS error: Unable to read fragment cache entry [aae9ee]
    [660378.893364] SQUASHFS error: Unable to read page, block aae9ee, size 7faa
    [660378.893367] print_req_error: I/O error, dev loop9, sector 21926
    [660378.893374] SQUASHFS error: Unable to read fragment cache entry [aae9ee]
    [660378.893377] SQUASHFS error: Unable to read page, block aae9ee, size 7faa
    [660378.893411] print_req_error: I/O error, dev loop9, sector 21928
    [660378.893419] SQUASHFS error: Unable to read fragment cache entry [aae9ee]
    [660378.893422] SQUASHFS error: Unable to read page, block aae9ee, size 7faa
    [660378.893428] SQUASHFS error: Unable to read fragment cache entry [aae9ee]
    [660378.893430] SQUASHFS error: Unable to read page, block aae9ee, size 7faa
    [660378.893531] EXT4-fs warning (device mmcblk0p2): ext4_end_bio:323: I/O error 10 writing to inode 32965 (offset 0 size 0 starting block 62913)
    [660378.893557] EXT4-fs warning (device mmcblk0p2): ext4_end_bio:323: I/O error 10 writing to inode 32965 (offset 0 size 0 starting block 62929)
    [660378.893603] Buffer I/O error on dev mmcblk0p2, logical block 1, lost sync page write
    [660378.893608] EXT4-fs error (device mmcblk0p2): ext4_journal_check_start:61: Detected aborted journal
    [660378.893619] EXT4-fs (mmcblk0p2): Remounting filesystem read-only
    [660378.893629] EXT4-fs (mmcblk0p2): previous I/O error to superblock detected
    [660378.893635] Buffer I/O error on dev mmcblk0p2, logical block 1, lost sync page write
    [660378.893641] EXT4-fs (mmcblk0p2): ext4_writepages: jbd2_start: 2147483643 pages, ino 32965; err -30
    [660379.071055] mmc0: host does not support reading read-only switch, assuming write-enable
    [660379.073490] mmc0: new high speed SDHC card at address 0007
    [660379.073849] mmcblk0: mmc0:0007 SD16G 14.5 GiB
    [660379.075218] mmcblk0: p1 p2
    [660477.037331] blk_partition_remap: fail for partition 2
    [660477.037346] EXT4-fs error (device mmcblk0p2): ext4_find_entry:1437: inode #11: comm sh: reading directory lblock 0
    [660510.168219] blk_partition_remap: fail for partition 2
    [660510.168234] EXT4-fs error (device mmcblk0p2): ext4_find_entry:1437: inode #11: comm about.cgi: reading directory lblock 0
    [660515.320472] blk_partition_remap: fail for partition 2
    [660515.320488] EXT4-fs error (device mmcblk0p2): ext4_find_entry:1437: inode #11: comm squeezelite: reading directory lblock 0
    [660517.508499] blk_partition_remap: fail for partition 2
    [660517.508514] EXT4-fs error (device mmcblk0p2): ext4_find_entry:1437: inode #11: comm lms.cgi: reading directory lblock 0
    [660522.627745] blk_partition_remap: fail for partition 2
    [660522.627759] EXT4-fs warning (device mmcblk0p2): htree_dirblock_to_tree:977: inode #2: lblock 0: comm find: error -5 reading directory block
    [660522.942280] blk_partition_remap: fail for partition 2
    [660522.942295] EXT4-fs error (device mmcblk0p2): ext4_find_entry:1437: inode #11: comm squeezelite: reading directory lblock 0

  7. #7
    Senior Member
    Join Date
    May 2010
    Location
    London, UK
    Posts
    238
    It doesn't look very happy.

    Assuming it is the card that is at fault, maybe reformatting it with the SD Association software would help. There again, maybe not.
    https://www.sdcard.org/downloads/index.html

    I destroyed my first two cards about 8 years ago (before RPi's were born). Since then I've never had a problem. I make sure to have no swap partition, and all logging is kept off the card with the following in my (Debian/Raspbian) fstab. Other distributions might want different permissions. I don't know what PCP does.

    Code:
    # Ramdisks for frequently written areas. This relieves stress on flash drives.
    # /var/log must be root writeable only
    tmpfs /var/log  tmpfs mode=0755,defaults 0 0

  8. #8
    Senior Member paul-'s Avatar
    Join Date
    Jan 2013
    Posts
    1,598
    There are no logs on persistent memory in pCP.

    Have you ever tested your cards fresh out of the box with a card validator. There are many counterfeit cards out there.
    piCorePlayer a small player for the Raspberry Pi in RAM.
    Homepage: https://www.picoreplayer.org

    Please donate if you like the piCorePlayer

  9. #9
    Senior Member Greg Erskine's Avatar
    Join Date
    Sep 2006
    Location
    Sydney, Australia
    Posts
    1,569
    Quote Originally Posted by Xyzzy View Post
    Unfortunately it doesn't go away - I think I'll just sell it and buy some android box with digital output...
    You seem to have a lot of trouble with SD cards even though other people have none, so it might be easier to look for a solution that doesn't use SD cards.

    The process can't be simpler.

    1. Buy known brand SD card. (10 minutes)
    2. Write image to SD card (10 seconds)
    3. Insert into RPi and boot. (1 minute)

    Do not format SD card (even if Windows prompts you to).
    Do not partition SD card. Leave partitions alone.

    If that doesn't work, then your RPi is faulty.

    Once your confidence is restored, then you could investigate your current SD cards. As "mrw" recommends, if your SD card is screwed up or has been repurposed from some other application then SD formatter is the way to get it back to the original formatting.

    Other than people using fake SD cards, we have not seen people with SD card issues. I create new pCP images on an almost daily basis, my batch of SD cards are years old and I would assume get a heavier usage than the normal pCP users.

    regards
    Greg

  10. #10
    Junior Member
    Join Date
    Oct 2018
    Posts
    18
    Month later and I think I have a good ending to this story.

    First, RPi support for SD cards HAS issues: https://elinux.org/RPi_SD_cards

    Having seen this page the day of my last post, in a last ditch effort I ransacked all nearby devices and discovered Toshiba card in one of family phones. After short break in the phone's usage I put the card into the RPi, set up PCP and...
    no issues whatsoever for the whole month!

    So I guess this case is solved - hardware incompatibility.
    Last edited by Xyzzy; 2019-01-12 at 13:32.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •