Getting Started | Visit the WIKI | IRC Logs | Forum Rules/Policy


Debian Jessie Images (3.10.102 BSP Kernel) New Release
#21
Reply
#22
how long before you rebooted after doing the update/install?

I think it's a matter of restarting the device before all data is written to disk that maybe affecting things Sad.

On a separate note I have a work around on getting 720 desktop resolution mentioned in my first post for anyone to try with any of the Debian images I posted. It should work until we get a proper driver in place for display (mali).
If you like my work be sure to check out my site or wish to donate to the cause visit https://www.pine64.pro/.

Cheers Big Grin
Reply
#23
(04-06-2016, 10:34 PM)lenny.raposo Wrote: how long before you rebooted after doing the update/install?

I think it's a matter of restarting the device before all data is written to disk that maybe affecting things Sad.

On a separate note I have a work around on getting 720 desktop resolution mentioned in my first post for anyone to try with any of the Debian images I posted. It should work until we get a proper driver in place for display (mali).

Hmmm I dont think it should have been sill writing, I wasnt moving that fast. I am currently running h2testw on the card it may be going bad perhaps. I have a new one on the way but no clue when it will get here.

Ugh...

[ 90.500942] FAT-fs (mmcblk0p1): error, fat_get_cluster: invalid cluster chain (i_pos 0)
[ 90.509752] FAT-fs (mmcblk0p1): Filesystem has been set read-only
[ 202.644912] FAT-fs (mmcblk0p1): error, fat_get_cluster: invalid cluster chain (i_pos 0)

The above is what happens when I do a ls /boot
Reply
#24
Just letting everyone know I have a workaround to the audio issues in linux. it is located on the first post of this discussion.

This is a temporary until I can get things patched up with PulseAudio.

Big Grin
If you like my work be sure to check out my site or wish to donate to the cause visit https://www.pine64.pro/.

Cheers Big Grin
Reply
#25
(04-06-2016, 10:34 PM)lenny.raposo Wrote: how long before you rebooted after doing the update/install?

I think it's a matter of restarting the device before all data is written to disk that maybe affecting things Sad.

On a separate note I have a work around on getting 720 desktop resolution mentioned in my first post for anyone to try with any of the Debian images I posted. It should work until we get a proper driver in place for display (mali).

Ok still having odd corruption like issues here. I have use the SD consortiums SD card formatter v4.0 to format my card. Then I ran h2testw.exe and got no errors or issues from it, then I coped over a fresh image using win32diskimage. On login I ran a ls /boot -al and get this

Code:
pine64user@debianpine64:~$ ls /boot -al
ls: cannot access /boot/pine64: Input/output error
total 1076
drwxr-xr-x  4 root root   16384 Jan  1  1970 .
drwxr-xr-x 21 root root    4096 Apr  6 00:13 ..
-rwxr-xr-x  1 root root 1076058 Apr  3 11:16 initrd.img
d?????????  ? ?    ?          ?            ? pine64
drwxr-xr-x  2 root root    2048 Apr  8 07:56 System Volume Information
-rwxr-xr-x  1 root root     137 Jan  1  2010 uEnv.txt
pine64user@debianpine64:~$ ls /boot/pine64 -al
ls: cannot access /boot/pine64: Input/output error
pine64user@debianpine64:~$
On my serial console I see this;
Code:
[  198.044915] FAT-fs (mmcblk0p1): error, fat_get_cluster: invalid cluster chain (i_pos 0)
[  198.053813] FAT-fs (mmcblk0p1): Filesystem has been set read-only
I am going to try to download another of your images and see if I have the same issue. If I do I suspect I have a faulty/flaky card or perhaps something wrong with my pine. Before anyone asks voltage in is showing as 5.05 and out on the usb ports is 5.03. Wink

BTW. Any idea why with every new image install to my flash card the pine uses a new MAC address for DHCP?


EDIT 
Definitely think my copy of the XFCE image is corrupt. (hard to tell without md5's hint hint). After a wipe of my card, windows disk check, win32 image install and then boot during boot I get;
Code:
[   14.208113] systemd[1]: Started Journal Service.
[  OK  ] Mounted FUSE Control File System.
[  OK  ] Mounted Configuration File System.
[  OK  ] Started udev Kernel Device Manager.
[  OK  ] Started udev Coldplug all Devices.
[  OK  ] Started Apply Kernel Variables.
        Starting Copy rules generated while the root was ro...
        Starting LSB: Set preliminary keymap...
[  OK  ] Started Copy rules generated while the root was ro.
[  OK  ] Started LSB: Set preliminary keymap.
[  OK  ] Created slice system-systemd\x2drfkill.slice.
        Starting Remount Root and Kernel File Systems...
[  OK  ] Found device /dev/ttyS0.
[  OK  ] Reached target Sound Card.
[  OK  ] Found device /dev/mmcblk0p1.
        Starting File System Check on /dev/mmcblk0p1...
[   15.014258] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
[  OK  ] Started Remount Root and Kernel File Systems.
        Starting Load/Save RF Kill Switch Status of rfkill0...
        Starting Various fixups to make systemd work better on Debian...
        Starting Load/Save Random Seed...
[  OK  ] Reached target Local File Systems (Pre).
[  OK  ] Started Load/Save RF Kill Switch Status of rfkill0.
[  OK  ] Started Various fixups to make systemd work better on Debian.
[  OK  ] Started Load/Save Random Seed.
[    8.482132] systemd-fsck[1465]: fsck.fat 3.0.27 (2014-11-12)
[    8.483625] systemd-fsck[1465]: /PINE64
[  OK  ] Started File System Check on /dev/mmcblk0p1.
[    8.521418] systemd-fsck[1465]: Has a large number of bad entries. (2/5)
[    8.560686] systemd-fsck[1465]: Not dropping it in auto-mode.
[    8.561319] systemd-fsck[1465]: /PINE64/.
[    8.561849] systemd-fsck[1465]: Bad short file name (.).
[    8.562415] systemd-fsck[1465]: Auto-renaming it.
[    8.562944] systemd-fsck[1465]: Renamed to FSCK0000.000
[    8.563474] systemd-fsck[1465]: /PINE64/..
[    8.564004] systemd-fsck[1465]: Bad short file name (..).
[    8.564531] systemd-fsck[1465]: Auto-renaming it.
[    8.565073] systemd-fsck[1465]: Renamed to FSCK0000.001
        Mounting /boot...
[    8.565672] systemd-fsck[1465]: /PINE64/FSCK0000.000
[    8.660727] systemd-fsck[1465]: File size is 0 bytes, cluster chain length is > 0 bytes.
[    8.661383] systemd-fsck[1465]: Truncating file to 0 bytes.
[    8.661915] systemd-fsck[1465]: Performing changes.
[    8.662457] systemd-fsck[1465]: /dev/mmcblk0p1: 9 files, 6117/25541 clusters
[  OK  ] Mounted /boot.
[  OK  ] Reached target Local File Systems.
EDIT2
Ok pulled the lxde image and that too is giving me errors.
Code:
[  OK  ] Started Load/Save RF Kill Switch Status of rfkill0.
[  OK  ] Started Various fixups to make systemd work better on Debian.
[  OK  ] Started Load/Save Random Seed.
[    8.274966] systemd-fsck[1474]: fsck.fat 3.0.27 (2014-11-12)
[    8.276396] systemd-fsck[1474]: /PINE64
[    8.321241] systemd-fsck[1474]: Has a large number of bad entries. (2/5)
[    8.322399] systemd-fsck[1474]: [Not dropping it in auto-mode.  OK
] Started File System Check on /dev/mmcblk0p1.
[    8.341476] systemd-fsck[1474]: /PINE64/.
        Mounting /boot...
[    8.380717] systemd-fsck[1474]: Bad short file name (.).
[    8.420791] systemd-fsck[1474]: Auto-renaming it.
[    8.440722] systemd-fsck[1474]: Renamed to FSCK0000.000
[    8.441506] systemd-fsck[1474]: /PINE64/..
[    8.442036] systemd-fsck[1474]: Bad short file name (..).
[    8.442593] systemd-fsck[1474]: Auto-renaming it.
[    8.443142] systemd-fsck[1474]: Renamed to FSCK0000.001
[    8.443675] systemd-fsck[1474]: /PINE64/FSCK0000.000
[    8.444205] systemd-fsck[1474]: File size is 0 bytes, cluster chain length is > 0 bytes.
[    8.444740] systemd-fsck[1474]: Truncating file to 0 bytes.
[    8.445280] systemd-fsck[1474]: Performing changes.
[    8.445813] systemd-fsck[1474]: /dev/mmcblk0p1: 9 files, 6117/25541 clusters
[  OK  ] Mounted /boot.
So if no one else sees the fsck issues on their first boot then I will have to assume I have a card issue.
Reply
#26
The images are not the factor here as they work for others. There can be 4 possibilities here.

1) Faulty SD Card(s).
2) Faulty PC MMC Drive.
3) Premature ejection of disk before write is completely flushed to disk (likely in most cases).
4) Faulty Pine64 MMC drive.

Try an Android/Remix OS image and see if it is yielding the same results in terms of FS/partition corruption (try multiple cards). Remember to safely eject the cards when using windows (right click on drive > Eject in Explorer). For good measure wait a few minutes after the write to disk is completed.

If you are seeing the same issues on multiple cards even going through the paces of safe image writes then I would have to say the MMC card slot is faulty on either the PC or the Pine (not an uncommon thing). Try writing images from another system with a different MMC slot (this should help rule out your PCs if the same is still occurring leaving the Pine as the culprit)

Just a thought Wink

I wanted to ask if you have resized the RootFS after burning to disk?

If not then when you first login into your pine (linux image)

run

sudo -i
/usr/local/sbin/resize-rootfs.sh

That should resize the rootfs partition.

Let me know if you have any issues with corruption after doing that

Wink
If you like my work be sure to check out my site or wish to donate to the cause visit https://www.pine64.pro/.

Cheers Big Grin
Reply
#27
(04-08-2016, 07:20 AM)lenny.raposo Wrote: The images are not the factor here as they work for others. There can be 4 possibilities here.

1) Faulty SD Card(s).
2) Faulty PC MMC Drive.


Try an Android/Remix OS image and see if it is yielding the same results in terms of FS/partition corruption (try multiple cards). Remember to safely eject the cards when using windows (right click on drive > Eject in Explorer). For good measure wait a few minutes after the write to disk is completed.

I wanted to ask if you have resized the RootFS after burning to disk?

If not then when you first login into your pine (linux image)

run

sudo -i
/usr/local/sbin/resize-rootfs.sh

That should resize the rootfs partition.

Let me know if you have any issues with corruption after doing that
I am starting to think its my card reader. I have grabbed another microsd from a different device (didnt want to use this one as it was already in use for something else). Before I installed your image I wanted to backup what I had on it. So I was using win32 Disk Imager to do just that, when in the middle of reading it, windows reported an error and win32 imager did as well. So isntead of using just the microsd card slot on my reader I have moved the microsd into a microsd to sdcard adapter and I am trying that. Will let you know.
Reply
#28
Let me know how it goes.
If you like my work be sure to check out my site or wish to donate to the cause visit https://www.pine64.pro/.

Cheers Big Grin
Reply
#29
Have tried the 2 Microsd I have on hand both of which pass h2testw with flying colors. Have tried them with my usb3 microsd reader, in both its microsd slots and both its SD card slots. I have tried the microsd in another computer (laptop) that has a sd card slot in its adapter. 

Every one of them has these errors on boot. They only show for me on my serial display, since I have only one tv that the pine works on and its not handy at the moment all I have is my serial connection and on boot fsck always finds an error on a fresh image. dmesg does not show these errors. 

Code:
        Starting Remount Root and Kernel File Systems...
[  OK  ] Found device /dev/ttyS0.
[  OK  ] Reached target Sound Card.
[   14.715627] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
[  OK  ] Started Remount Root and Kernel File Systems.
[  OK  ] Found device /dev/mmcblk0p1.
        Starting File System Check on /dev/mmcblk0p1...
        Starting Load/Save RF Kill Switch Status of rfkill0...
        Starting Various fixups to make systemd work better on Debian...
        Starting Load/Save Random Seed...
[  OK  ] Reached target Local File Systems (Pre).
[  OK  ] Started Load/Save RF Kill Switch Status of rfkill0.
[  OK  ] Started Various fixups to make systemd work better on Debian.
[  OK  ] Started Load/Save Random Seed.
[    8.154628] systemd-fsck[1467]: fsck.fat 3.0.27 (2014-11-12)
[    8.156107] systemd-fsck[1467]: /PINE64
[  OK  ] Started File System Check on /dev/mmcblk0p1.
[    8.191370] systemd-fsck[1467]: Has a large number of bad entries. (2/5)
        Mounting /boot...
[    8.230808] systemd-fsck[1467]: Not dropping it in auto-mode.
[    8.270802] systemd-fsck[1467]: /PINE64/.
[    8.290768] systemd-fsck[1467]: Bad short file name (.).
[    8.310839] systemd-fsck[1467]: Auto-renaming it.
[    8.330805] systemd-fsck[1467]: Renamed to FSCK0000.000
[    8.350876] systemd-fsck[1467]: /PINE64/..
[  OK  ] Mounted /boot.
[    8.370734] systemd-fsck[1467]: Bad short file name (..).
[    8.410742] systemd-fsck[1467]: Auto-renaming it.
[    8.411545] systemd-fsck[1467]: Renamed to FSCK0000.001
[    8.412073] systemd-fsck[1467]: /PINE64/FSCK0000.000
[    8.412609] systemd-fsck[1467]: File size is 0 bytes, cluster chain length is > 0 bytes.
[    8.413140] systemd-fsck[1467]: Truncating file to 0 bytes.
[    8.413668] systemd-fsck[1467]: Performing changes.
[    8.414194] systemd-fsck[1467]: /dev/mmcblk0p1: 9 files, 6117/25541 clusters
[  OK  ] Reached target Local File Systems.
        Starting Create Volatile Files and Directories...
        Starting LSB: Raise network interfaces....
[  OK  ] Reached target Remote File Systems.
        Starting Trigger Flushing of Journal to Persistent Storage...
        Starting LSB: Set console font and keymap...
[  OK  ] Started Create Volatile Files and Directories.
[  OK  ] Started LSB: Set console font and keymap.
[   15.484681] systemd-journald[1425]: Received request to flush runtime journal from PID 1
[  OK  ] Started Trigger Flushing of Journal to Persistent Storage.
Second boot on that clean install.
Code:
        Mounting /boot...
[    8.460764] systemd-fsck[1467]: /PINE64
[    8.500834] systemd-fsck[1467]: Contains a free cluster (2). Assuming EOF.
[    8.520785] systemd-fsck[1467]: Reclaimed 5587 unused clusters (11442176 bytes) in 3 chains.
[    8.540872] systemd-fsck[1467]: Performing changes.
[    8.560879] systemd-fsck[1467]: /dev/mmcblk0p1: 9 files, 6116/25541 clusters
[  OK  ] Mounted /boot.
Going to try the expansion.

I am friggin baffled, the resize ended with me unable to read the fs.

http://pastebin.com/kb84J77J

And the second SD card;
http://pastebin.com/D1RLC6nJ

Oddly enough I just tried the Arch image and no issue with the FS. I dunno wtf is up...
Reply
#30
Did you expand the rootfs with the scripts?

I am going to test the images again to see if this is an issue
If you like my work be sure to check out my site or wish to donate to the cause visit https://www.pine64.pro/.

Cheers Big Grin
Reply


Possibly Related Threads...
Thread Author Replies Views Last Post
  Debian Mate (3.10.102 BSP) janeku 18 1,625 01-15-2017, 01:48 PM
Last Post: mcrognale
  Adding a missing kernel module spz2k 8 437 01-10-2017, 06:22 AM
Last Post: xalius
Music Getting analog audio/sound to work (headphones socket) on debian pfeerick 7 1,874 12-30-2016, 07:37 AM
Last Post: Birneklub9
  debian i2c-dev pine.adam 6 392 12-16-2016, 04:21 PM
Last Post: pine.adam
  [SOLVED]Problem Compiling modules: Recipe | kernel-headers not found acenos 0 162 12-14-2016, 09:11 AM
Last Post: acenos
  Gambas3 installation on Debian image linusky 0 172 11-29-2016, 11:10 AM
Last Post: linusky
  NIC not visible after kernel update xleon 1 237 11-15-2016, 05:23 PM
Last Post: xleon
  Debian Base (3.10.102 BSP 2) won't boot without monitor Scion 7 868 09-16-2016, 03:58 PM
Last Post: Scion
  Tor on debian philips 1 323 09-11-2016, 02:31 AM
Last Post: Ghelorn
  Debian and Prolific pl2303 Castle 3 480 08-21-2016, 03:16 AM
Last Post: Castle

Forum Jump:


Users browsing this thread: 1 Guest(s)