LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware > Slackware - ARM
User Name
Password
Slackware - ARM This forum is for the discussion of Slackware ARM.

Notices


Reply
  Search this Thread
Old 04-01-2017, 10:50 AM   #1
jloco
LQ Newbie
 
Registered: Apr 2016
Posts: 6

Rep: Reputation: Disabled
odd issue on 14.2


Hello,

I'm running Slackware ARM 14.2 on a RPi2 and I've run into a bit of an issue that I cannot seem to solve.

Any changes to disk I make disappear like I never did them.

Example running slackpkg update slackpkg upgrade-all lists all patches I need to install, I install them, and upon reboot nothing changes. No errors are displayed, nothing seems out of the ordinary.

If I download the packages manually and use upgradepkg to install them, the same thing happens. Everything I did just disappears.

Use rpi-update to upgrade to 4.9 series kernel, it says everything was fine, reboot and I'm back on 4.4.38 again....

massively confused... can anyone shed some light on this for me??
 
Old 04-02-2017, 04:07 AM   #2
Penthux
Member
 
Registered: Dec 2008
Location: Middlesbrough, UK
Distribution: Slackware
Posts: 142

Rep: Reputation: 35
Quote:
Originally Posted by jloco View Post
Hello,

I'm running Slackware ARM 14.2 on a RPi2 and I've run into a bit of an issue that I cannot seem to solve.

Any changes to disk I make disappear like I never did them.

Example running slackpkg update slackpkg upgrade-all lists all patches I need to install, I install them, and upon reboot nothing changes. No errors are displayed, nothing seems out of the ordinary.

If I download the packages manually and use upgradepkg to install them, the same thing happens. Everything I did just disappears.

Use rpi-update to upgrade to 4.9 series kernel, it says everything was fine, reboot and I'm back on 4.4.38 again....

massively confused... can anyone shed some light on this for me??
Very odd indeed. Are you able to create a new file (just for testing purposes) and is it present after you reboot? For example:
Code:
echo "mumbojumbo" > /boot/testfile.txt
then reboot and check that this file has been saved and is readable.

What happens if you use the 'sync' command before and after installing and/or upgrading? Perhaps it's a cache issue and you need to flush the filesystem buffers.

Or it could be filesystem issue. Is your root partition mounted read only? Use the 'mount -l' command to check it.
Code:
root@slackarm:~# mount -l
/dev/mmcblk0p3 on / type ext4 (rw)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
tmpfs on /dev/shm type tmpfs (rw)
/dev/mmcblk0p1 on /boot type vfat (rw,fmask=177,dmask=077)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
You could also try a fsck scan to see if that brings up any errors. Adding the following code to the cmdline.txt file would force a fsck scan every time you (re)boot but that's not going to help if the file is not being saved.
Code:
fsck.mode=force fsck.repair=yes

There's always the possibility that the microSD card you are using is faulty. I would make an image of the current microSD card and write it to another card just to test. I'd also then re-install Slackware ARM to the current card to see if it produces the same issues/results.

Last edited by Penthux; 04-02-2017 at 04:12 AM. Reason: added text
 
Old 04-02-2017, 12:44 PM   #3
jloco
LQ Newbie
 
Registered: Apr 2016
Posts: 6

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by Penthux View Post
Very odd indeed. Are you able to create a new file (just for testing purposes) and is it present after you reboot? For example:
Code:
echo "mumbojumbo" > /boot/testfile.txt
then reboot and check that this file has been saved and is readable.
Tried this with files and making directories and saving files into them.... all always deleted upon reboot.


Quote:
Originally Posted by Penthux View Post
What happens if you use the 'sync' command before and after installing and/or upgrading? Perhaps it's a cache issue and you need to flush the filesystem buffers.

Or it could be filesystem issue. Is your root partition mounted read only? Use the 'mount -l' command to check it.
Code:
root@slackarm:~# mount -l
/dev/mmcblk0p3 on / type ext4 (rw)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
tmpfs on /dev/shm type tmpfs (rw)
/dev/mmcblk0p1 on /boot type vfat (rw,fmask=177,dmask=077)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
SD was listed as being rw, so I knew that it had to be something else.

Quote:
Originally Posted by Penthux View Post
You could also try a fsck scan to see if that brings up any errors. Adding the following code to the cmdline.txt file would force a fsck scan every time you (re)boot but that's not going to help if the file is not being saved.
Code:
fsck.mode=force fsck.repair=yes

There's always the possibility that the microSD card you are using is faulty. I would make an image of the current microSD card and write it to another card just to test. I'd also then re-install Slackware ARM to the current card to see if it produces the same issues/results.
In the end, I did clone the SD card and installed the result onto a new SD card and what I found then was that it did, in fact, write and keep changes made to the OS afterwards. It seems sometime on January 23rd, it stopped writing to the card, yet continued to operate without any real issue besides the inability to update anything. Very interesting behavior for a failed SD card. Now I know if this happens again, how a SD dies

Thank you for your valuable incites!
 
Old 04-02-2017, 04:34 PM   #4
Penthux
Member
 
Registered: Dec 2008
Location: Middlesbrough, UK
Distribution: Slackware
Posts: 142

Rep: Reputation: 35
Quote:
Originally Posted by jloco View Post
Thank you for your valuable incites!
Always welcome. Glad you were able to locate the cause of this issue and resolve it.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] Odd disk issue scratchyrat Linux - Hardware 5 08-10-2013 04:57 PM
Odd issue with df command protocol Linux - General 5 04-05-2010 12:01 PM
Odd Network Issue RobertNikic Linux - Networking 5 06-25-2008 12:36 PM
odd mandriva issue goofusbrain Linux - Networking 1 11-13-2005 06:09 PM
Odd *nix issue with c/c++ Will_C_T Programming 3 09-09-2004 11:17 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware > Slackware - ARM

All times are GMT -5. The time now is 11:16 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration