(OLD) (ARCHIVED) Puppy Linux Discussion Forum Forum Index (OLD) (ARCHIVED) Puppy Linux Discussion Forum
Puppy HOME page : puppylinux.com
"THE" alternative forum : puppylinux.info

This forum can also be accessed as http://oldforum.puppylinux.com
It is now read-only and serves only as archives.

Please register over the NEW forum
https://forum.puppylinux.com
and continue your work there. Thank you.

 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups    
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

The time now is Sat 19 Sep 2020, 03:12
All times are UTC - 4
 Forum index » Advanced Topics » Hardware
Using extern SSd Drive as a Cheap Substitute for Flashdrive
Moderators: Flash, Ian, JohnMurga
This forum is locked: you cannot post, reply to, or edit topics.   This topic is locked: you cannot edit posts or make replies. View previous topic :: View next topic
Page 2 of 2 [24 Posts]   Goto page: Previous 1, 2
Author Message
bigpup


Joined: 11 Oct 2009
Posts: 13981
Location: S.C. USA

PostPosted: Wed 20 Feb 2019, 12:18    Post subject:  

SSD's have load leveling built into their internal controllers.
This controls writes to drive to make them last as long as possible.
With normal use. The computer will probably die before the drive starts having write errors.

To limit puppy writting to the save file/folder.
If you see a save icon on the desktop.
Puppy is running in pupmode 13.
The save file/folder is loaded as read/write and also using a saveramdisk in memory.
Everything first writes to the saveramdisk.
Writes are only done to the save file/folder when the set save time activates, you click on the save icon, or at shutdown.
There is some control of this in menu>System>Puppy Event Manager>Save Session

The pupmode is controlled by the pmedia= option in the boot entry.
pmedia=usbflash is usually the one that makes Puppy run in pupmode 13.
So make sure that is the one in the boot menu entry you are using. This is in the kernel line of the entry.
Example:
kernel /bionicpup64798/vmlinuz psubdir=/bionicpup64798 pmedia=usbflash pfix=fsck

If you are not running in pupmode 13.
Change the pmedia= entry to pmedia=usbflash

_________________
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected Shocked
YaPI(any iso installer)
Back to top
View user's profile Send private message 
backi

Joined: 27 Feb 2011
Posts: 2007
Location: GERMANY

PostPosted: Wed 20 Feb 2019, 12:27    Post subject:  

Hi rcrsn51 !

root@live:~# lsusb
Bus 002 Device 005: ID 0a5c:5800 Broadcom Corp. BCM5880 Secure Applications Processor
Bus 002 Device 004: ID 152d:0578 JMicron Technology Corp. / JMicron USA Technology Corp.
Bus 002 Device 003: ID 2188:0ae1
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 004: ID 05ca:181e Ricoh Co., Ltd
Bus 001 Device 003: ID 413c:8187 Dell Computer Corp. DW375 Bluetooth Module
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Back to top
View user's profile Send private message 
rcrsn51


Joined: 05 Sep 2006
Posts: 13129
Location: Stratford, Ontario

PostPosted: Wed 20 Feb 2019, 12:40    Post subject:  

Compare the lists with the SSD plugged/unplugged.
Back to top
View user's profile Send private message 
backi

Joined: 27 Feb 2011
Posts: 2007
Location: GERMANY

PostPosted: Wed 20 Feb 2019, 13:30    Post subject:  

Booted from Usb Flash Drive using Bionic Dog :

SSD unpluggged (from Esata Port):

root@live:~# lsusb
Bus 002 Device 005: ID 0a5c:5800 Broadcom Corp. BCM5880 Secure Applications Processor
Bus 002 Device 004: ID 1307:0165 Transcend Information, Inc. 2GB/4GB/8GB Flash Drive
Bus 002 Device 003: ID 2188:0ae1
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 004: ID 05ca:181e Ricoh Co., Ltd
Bus 001 Device 003: ID 413c:8187 Dell Computer Corp. DW375 Bluetooth Module
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

SSD pluggged in (from Esata Port):

root@live:~# lsusb
Bus 002 Device 005: ID 0a5c:5800 Broadcom Corp. BCM5880 Secure Applications Processor
Bus 002 Device 006: ID 152d:0578 JMicron Technology Corp. / JMicron USA Technology Corp.
Bus 002 Device 004: ID 1307:0165 Transcend Information, Inc. 2GB/4GB/8GB Flash Drive
Bus 002 Device 003: ID 2188:0ae1
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 004: ID 05ca:181e Ricoh Co., Ltd
Bus 001 Device 003: ID 413c:8187 Dell Computer Corp. DW375 Bluetooth Module
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Back to top
View user's profile Send private message 
Marv


Joined: 04 May 2005
Posts: 1265
Location: SW Wisconsin

PostPosted: Wed 20 Feb 2019, 13:35    Post subject:  

@backi If you run mount with no arguments in terminal you can see how your various drives are mounted. My frugal install of upupcc looks like this:
Code:
/dev/sda1 on /initrd/mnt/dev_save type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,quiet,utf8,errors=remount-ro)
tmpfs on /initrd/mnt/tmpfs type tmpfs (rw,relatime)
unionfs on / type aufs (rw,relatime,si=3e0b7c6d)
/dev/loop0 on /initrd/pup_ro2 type squashfs (ro,noatime)
/dev/loop1 on /initrd/pup_f type squashfs (ro,noatime)
/dev/loop2 on /initrd/pup_z type squashfs (ro,noatime)
/dev/loop3 on /initrd/pup_ro1 type ext2 (rw,noatime,errors=continue,user_xattr)
tmpfs on /initrd/files type tmpfs (ro,relatime,size=5216k,mode=755)
devtmpfs on /dev type devtmpfs (rw,relatime,size=2497804k,nr_inodes=209617,mode=755)
none on /proc type proc (rw,relatime)
none on /dev/pts type devpts (rw,relatime,gid=2,mode=620,ptmxmode=000)
none on /sys type sysfs (rw,relatime)
shmfs on /dev/shm type tmpfs (rw,relatime,size=1115420k)
/dev/loop4 on /initrd/pup_ro3 type squashfs (ro,noatime)
/dev/sda2 on /mnt/sda2 type ext2 (rw,noatime,errors=continue,user_xattr)
I add an option in the mount line for my data drive in /etc/rc.d/rc.local that changes the /dev/sda2 mount (where all my data, profiles, caches etc. live) to noatime from relatime. It is an SSD.
Code:
mkdir -p /mnt/sda2; mount -t ext2 -o defaults,noatime /dev/sda2 /mnt/sda2    # pmount + Jim
Actually relatime isn't too bad on SSDs, way better than atime was. It updates the access date if either a write to that file was performed or, so far as I understand it, if more than 24 hours have elapsed since the last access to that file. relatime is the default in all the newer kernels and I haven't found a simple way to make noatime the default short of recompiling the kernel -not worth it IMO-.
_________________
Pups currently in kennel Very Happy Older LxPupSc and X-slacko-4.4 for my users; LxPupSc, LxPupSc64 and upupEF for me. All good pups indeed, and all running savefiles for look'n'feel only. Browsers, etc. solely from SFS.

Last edited by Marv on Wed 20 Feb 2019, 14:06; edited 1 time in total
Back to top
View user's profile Send private message 
rcrsn51


Joined: 05 Sep 2006
Posts: 13129
Location: Stratford, Ontario

PostPosted: Wed 20 Feb 2019, 13:47    Post subject:  

Quote:
Bus 002 Device 006: ID 152d:0578 JMicron Technology Corp. / JMicron USA Technology Corp.

That would appear to be the USB adapter with your SSD. So I'm guessing that it's working as a USB3 device, not an eSATA.
Back to top
View user's profile Send private message 
backi

Joined: 27 Feb 2011
Posts: 2007
Location: GERMANY

PostPosted: Wed 20 Feb 2019, 14:46    Post subject:  

Now booting and running Bionic Dog (with Porteus Boot Option--- save only on Demand ) from a SSD connected via Adapter to Esata Port of my Laptop.

mount in Terminal :

root@live:~# mount
tmpfs on /mnt/live type tmpfs (rw,relatime,mode=755)
proc on /mnt/live/proc type proc (rw,relatime)
sysfs on /mnt/live/sys type sysfs (rw,relatime)
none on /mnt/live/dev type devtmpfs (rw,relatime,size=4111916k,nr_inodes=197025,mode=755)
/dev/sdb1 on /mnt/live/mnt/sdb1 type ext4 (rw,noatime,nodiratime,data=ordered)
tmpfs on /mnt/live/memory/changes type tmpfs (rw,relatime,size=7004836k)
aufs on / type aufs (rw,relatime,si=1f7bd735,nowarn_perm)
/dev/loop0 on /mnt/live/memory/images/01-filesystem.squashfs type squashfs (ro,relatime)
/dev/loop1 on /mnt/live/memory/images/99-bionic_linux-firmware.squashfs type squashfs (ro,relatime)
/dev/loop2 on /mnt/live/memory/images/SMTUBE15.11BIONICDOG.squashfs type squashfs (ro,relatime)
/dev/loop3 on /mnt/live/memory/images/e17.squashfs type squashfs (ro,relatime)
/dev/loop4 on /mnt/live/memory/images/mplayer.squashfs type squashfs (ro,relatime)
/dev/loop5 on /mnt/live/memory/images/qt-4.8.2.squashfs type squashfs (ro,relatime)
/dev/loop6 on /mnt/live/memory/images/smplayer-19.1.0-i686-qt4.squashfs type squashfs (ro,relatime)
/dev/loop7 on /mnt/live/memory/images/vlc_qtwayland5.squashfs type squashfs (ro,relatime)
/dev/loop8 on /mnt/live/memory/images/xfe.squashfs type squashfs (ro,relatime)
/dev/sdb1 on /mnt/live/memory/images/changes-exit type ext4 (rw,noatime,nodiratime,data=ordered)
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
devtmpfs on /dev type devtmpfs (rw,nosuid,size=4111916k,nr_inodes=197025,mode=755)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,nodev,mode=755)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
cgroup on /sys/fs/cgroup/unified type cgroup2 (rw,nosuid,nodev,noexec,relatime,nsdelegate)
cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,name=systemd)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
cgroup on /sys/fs/cgroup/rdma type cgroup (rw,nosuid,nodev,noexec,relatime,rdma)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls,net_prio)
cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset)
cgroup on /sys/fs/cgroup/hugetlb type cgroup (rw,nosuid,nodev,noexec,relatime,hugetlb)
cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,relatime,pids)
cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory)
cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio)
cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=24,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=16807)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime,pagesize=2M)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
mqueue on /dev/mqueue type mqueue (rw,relatime)
fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)
configfs on /sys/kernel/config type configfs (rw,relatime)
/dev/sdb1 on /mnt/sdb1 type ext4 (rw,relatime,data=ordered)
tmpfs on /run/user/0 type tmpfs (rw,nosuid,nodev,relatime,size=824096k,mode=700)

Am i right as a noob........no need to take further Actions... regarding putting relatime etc. to fstab ?
Back to top
View user's profile Send private message 
Marv


Joined: 04 May 2005
Posts: 1265
Location: SW Wisconsin

PostPosted: Wed 20 Feb 2019, 16:12    Post subject:  

I'd say you're fine, especially since your sdb1 external drive is a journaled ext4. One access update in 24 hours is pretty minimal, certainly compared to hammering a database or cache with the older atime where every read forced a write to update the access time.

Cheers,

_________________
Pups currently in kennel Very Happy Older LxPupSc and X-slacko-4.4 for my users; LxPupSc, LxPupSc64 and upupEF for me. All good pups indeed, and all running savefiles for look'n'feel only. Browsers, etc. solely from SFS.
Back to top
View user's profile Send private message 
backi

Joined: 27 Feb 2011
Posts: 2007
Location: GERMANY

PostPosted: Wed 20 Feb 2019, 16:25    Post subject:  

Thanks everyone for Support ! Smile Smile Smile
Back to top
View user's profile Send private message 
Display posts from previous:   Sort by:   
Page 2 of 2 [24 Posts]   Goto page: Previous 1, 2
This forum is locked: you cannot post, reply to, or edit topics.   This topic is locked: you cannot edit posts or make replies. View previous topic :: View next topic
 Forum index » Advanced Topics » Hardware
Jump to:  

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You can download files in this forum


Powered by phpBB © 2001, 2005 phpBB Group
[ Time: 0.0807s ][ Queries: 12 (0.0325s) ][ GZIP on ]