[ihatelolcats]

no, i don't want to use it like a livecd. yes, i am aware of the write wear issues

i tried to install debian to a usb flash drive but the drive isn't listed in the installer. my sata drives are. do i need to do something to make my flash drive recognized?
everything i try to google brings back stuff about pendrive livecd stuff

thanks

 

[xzarth]

What kind of pc are you using? Every time i install debian (and that happens to be quite often) i get all my flash drives detected in installer when i come to partitioning.

So i'll guess either weird flash drive, or weird (old) pc. Does your bios detect the drive?

Anyway, what you can do is start the text installer (i don't know about graphical installer, never used that), then press alt+F2 and press enter. That will open the console. Then plug in the flash drive and check dmesg to see what is happening.

 

[ihatelolcats]

I'll give that a try. its my sig rig with a 16gb patriot drive
Quote:

Originally Posted by xzarth

What kind of pc are you using? Every time i install debian (and that happens to be quite often) i get all my flash drives detected in installer when i come to partitioning.

So i'll guess either weird flash drive, or weird (old) pc. Does your bios detect the drive?

Anyway, what you can do is start the text installer (i don't know about graphical installer, never used that), then press alt+F2 and press enter. That will open the console. Then plug in the flash drive and check dmesg to see what is happening.

 

[ihatelolcats]

in answer to your question, yes my bios detects the drive
i tried what you said, i think debian detects it too but it doesn't show in the partition manager



do i have to mount it manually?

 

[xzarth]

I can't see your flash drive being detected in dmesg, i only see sda, sdb and sdc, which are your 1TB, 128GB and 320GB disks.

I would expect something like this (if you had it plugged in from start then it's somewhere before, just unplug it and replug it right before you do dmesg):

Code:

[323142.744025] usb 1-4: new high-speed USB device number 5 using ehci_hcd
[323142.880186] usb 1-4: New USB device found, idVendor=090c, idProduct=1000
[323142.880189] usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[323142.880191] usb 1-4: Product: USB DISK
[323142.880193] usb 1-4: Manufacturer: SMI Corporation
[323142.880194] usb 1-4: SerialNumber: AA12012700000056
[323142.880518] scsi13 : usb-storage 1-4:1.0
[323144.356967] scsi 13:0:0:0: Direct-Access     Sharkoon Flexi-Drive EC1  1100 PQ: 0 ANSI: 0 CCS
[323144.357418] sd 13:0:0:0: Attached scsi generic sg2 type 0
[323144.359451] sd 13:0:0:0: [sdc] 3915776 512-byte logical blocks: (2.00 GB/1.86 GiB)
[323144.360719] sd 13:0:0:0: [sdc] Write Protect is off
[323144.360722] sd 13:0:0:0: [sdc] Mode Sense: 43 00 00 00
[323144.361702] sd 13:0:0:0: [sdc] No Caching mode page present
[323144.361705] sd 13:0:0:0: [sdc] Assuming drive cache: write through
[323144.365706] sd 13:0:0:0: [sdc] No Caching mode page present
[323144.365709] sd 13:0:0:0: [sdc] Assuming drive cache: write through
[323144.369344]  sdc: sdc1
[323144.373713] sd 13:0:0:0: [sdc] No Caching mode page present
[323144.373717] sd 13:0:0:0: [sdc] Assuming drive cache: write through
[323144.373719] sd 13:0:0:0: [sdc] Attached SCSI removable disk

Maybe try another drive to see if that one gets detected. It's still weird that bios detects it and debian doesn't.

 

[ihatelolcats]

wow I feel kind of dumb for not trying this. I had it plugged in a usb3 slot. switched it to usb2 and its detected. thanks for the help

installing now

 

[Fateful_Ikkou]

Lol this reminds me of when I was 13 trying to install Ubuntu on a flash drive and use it as a Livecd, needless to say that was a bad move when it was done the drive split into like 10 partitions that were permanent.

 

[ihatelolcats]

lol. my dad was pretty mad when I installed Ubuntu on our family's computer. luckily I was able to remove it and grub

guess I was about 13 then too

 

[xzarth]

Quote:

Originally Posted by ihatelolcats

wow I feel kind of dumb for not trying this. I had it plugged in a usb3 slot. switched it to usb2 and its detected. thanks for the help

installing now

great, enjoy your new debian

 

[ihatelolcats]

all right so now im running linux mint...
what can i do to reduce read/write on my flash drive and extend its life? i only have an ext4 partition and no swap i think thats a good start

edit: is it even an issue i should worry about?

 

[Rookie1337]

Quote:

Originally Posted by ihatelolcats

all right so now im running linux mint...
what can i do to reduce read/write on my flash drive and extend its life? i only have an ext4 partition and no swap i think thats a good start

edit: is it even an issue i should worry about?

It might be an issue, but I'm thinking that is because flash drives don't have controllers and such to maintain them. You can have noatime in fstab if you're really worried about "unnecessary" writes and make sure you have the partition sector lined up.

EDIT: What filesystem did you use?

 

[ihatelolcats]

ext4

this is what im looking at, where do i put noatime
after nosuid?

Code:

# <file system> <mount point>   <type>  <options>       <dump>  <pass>
proc            /proc           proc    nodev,noexec,nosuid 0       0
# / was on /dev/sdd1 during installation
UUID=aeb4b8f5-1229-42fa-81bd-11d0eb497331 /               ext4    errors=remount-ro 0       1

 

[Rookie1337]

Quote:

Originally Posted by ihatelolcats

ext4

this is what im looking at, where do i put noatime
after nosuid?

Code:

# <file system> <mount point>   <type>  <options>       <dump>  <pass>
proc            /proc           proc    nodev,noexec,nosuid 0       0
# / was on /dev/sdd1 during installation
UUID=aeb4b8f5-1229-42fa-81bd-11d0eb497331 /               ext4    errors=remount-ro 0       1

Again...I honestly don't know how using a flash drive will turn out as they use TLC IIRC and I think have no controllers or other methods to keep the OS from wearing out the flash.

Just put the noatime like this "noatime,errors=remount-ro 0". TRIM is added by including "discard" in that same spot but I don't think it will work or help any with a flash drive.

My other methods may not work since you're running this in a flash drive.

Code:

# move cache to RAM
tmpfs /home/rez/.cache tmpfs defaults,noatime,nosuid 0 0
# move tmp to RAM
tmpfs /tmp tmpfs defaults,noatime,nosuid 0 0

Add those to fstab but be warned I have no clue how this will turn out. ALSO, they will increase RAM usage (though I don't think it shows up).

Again you also need to run gparted and check that the starting sector is divisible by 1024 or 2...I can't remember which.

 

[ihatelolcats]

ok, first sector 2048. trying what you said. thanks

Code:

-desktop ~ $ mount
/dev/sdd1 on / type ext4 (rw,noatime,errors=remount-ro)
proc on /proc type proc (rw,noexec,nosuid,nodev,noatime)
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
none on /sys/fs/fuse/connections type fusectl (rw)
none on /sys/kernel/debug type debugfs (rw)
none on /sys/kernel/security type securityfs (rw)
udev on /dev type devtmpfs (rw,mode=0755)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=0620)
tmpfs on /run type tmpfs (rw,noexec,nosuid,size=10%,mode=0755)
none on /run/lock type tmpfs (rw,noexec,nosuid,nodev,size=5242880)
none on /run/shm type tmpfs (rw,nosuid,nodev)
none on /run/user type tmpfs (rw,noexec,nosuid,nodev,size=104857600,mode=0755)
gvfsd-fuse on /run/user/kyle/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,user=kyle)
gvfsd-fuse on /root/.gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev)

 

[Rookie1337]

Quote:

Originally Posted by ihatelolcats

ok, first sector 2048. trying what you said. thanks

Code:

-desktop ~ $ mount
/dev/sdd1 on / type ext4 (rw,noatime,errors=remount-ro)
proc on /proc type proc (rw,noexec,nosuid,nodev,noatime)
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
none on /sys/fs/fuse/connections type fusectl (rw)
none on /sys/kernel/debug type debugfs (rw)
none on /sys/kernel/security type securityfs (rw)
udev on /dev type devtmpfs (rw,mode=0755)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=0620)
tmpfs on /run type tmpfs (rw,noexec,nosuid,size=10%,mode=0755)
none on /run/lock type tmpfs (rw,noexec,nosuid,nodev,size=5242880)
none on /run/shm type tmpfs (rw,nosuid,nodev)
none on /run/user type tmpfs (rw,noexec,nosuid,nodev,size=104857600,mode=0755)
gvfsd-fuse on /run/user/kyle/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,user=kyle)
gvfsd-fuse on /root/.gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev)

Wait..that looks like a live image setup I think. What is your output from "cat /etc/fstab" after you add the things I suggested? I believe a reboot is needed for those changes to take effect though.

 

[ihatelolcats]

lol uh oh. it wont boot into gui
how can i edit that file back to the original from cli?
i tried chmod +w /etc/fstab that didnt seem to work

ok i did mount -n -o remount / and deleted the last lines and im back in a gui

Code:

[email protected] ~ $ cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
proc            /proc           proc    nodev,noexec,nosuid 0       0
# / was on /dev/sdd1 during installation
UUID=aeb4b8f5-1229-42fa-81bd-11d0eb497331 /               ext4    noatime,errors=remount-ro 0       1

Code:

[email protected] ~ $ mount
/dev/sdd1 on / type ext4 (rw,noatime,errors=remount-ro)
proc on /proc type proc (rw,noexec,nosuid,nodev)
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
none on /sys/fs/fuse/connections type fusectl (rw)
none on /sys/kernel/debug type debugfs (rw)
none on /sys/kernel/security type securityfs (rw)
udev on /dev type devtmpfs (rw,mode=0755)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=0620)
tmpfs on /run type tmpfs (rw,noexec,nosuid,size=10%,mode=0755)
none on /run/lock type tmpfs (rw,noexec,nosuid,nodev,size=5242880)
none on /run/shm type tmpfs (rw,nosuid,nodev)
none on /run/user type tmpfs (rw,noexec,nosuid,nodev,size=104857600,mode=0755)
gvfsd-fuse on /run/user/kyle/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,user=kyle)

 

[Rookie1337]

Quote:

Originally Posted by ihatelolcats

lol uh oh. it wont boot into gui
how can i edit that file back to the original from cli?
i tried chmod +w /etc/fstab that didnt seem to work

ok i did mount -n -o remount / and deleted the last lines and im back in a gui

Code:

[email protected] ~ $ cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
proc            /proc           proc    nodev,noexec,nosuid 0       0
# / was on /dev/sdd1 during installation
UUID=aeb4b8f5-1229-42fa-81bd-11d0eb497331 /               ext4    noatime,errors=remount-ro 0       1

Code:

[email protected]top ~ $ mount
/dev/sdd1 on / type ext4 (rw,noatime,errors=remount-ro)
proc on /proc type proc (rw,noexec,nosuid,nodev)
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
none on /sys/fs/fuse/connections type fusectl (rw)
none on /sys/kernel/debug type debugfs (rw)
none on /sys/kernel/security type securityfs (rw)
udev on /dev type devtmpfs (rw,mode=0755)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=0620)
tmpfs on /run type tmpfs (rw,noexec,nosuid,size=10%,mode=0755)
none on /run/lock type tmpfs (rw,noexec,nosuid,nodev,size=5242880)
none on /run/shm type tmpfs (rw,nosuid,nodev)
none on /run/user type tmpfs (rw,noexec,nosuid,nodev,size=104857600,mode=0755)
gvfsd-fuse on /run/user/kyle/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,user=kyle)

Damn I'm sorry. I really think you've got some kind of live image running and not an install but I'd have to try doing what you're doing to know for sure.

Easy way is just get to the CLI and then " sudo nano /etc/fstab" and then delete the lines that cause problems which should just be the two extras about moving stuff to RAM.

 

[ihatelolcats]

"Easy way is just get to the CLI and then " sudo nano /etc/fstab" and then delete the lines that cause problems which should just be the two extras about moving stuff to RAM."
yes but there was a permissions problem

why do you think its a livecd? im fairly certain its installed onto my flash drive

 

[Rookie1337]

Quote:

Originally Posted by ihatelolcats

"Easy way is just get to the CLI and then " sudo nano /etc/fstab" and then delete the lines that cause problems which should just be the two extras about moving stuff to RAM."
yes but there was a permissions problem

why do you think its a livecd? im fairly certain its installed onto my flash drive

What was the permission problem? If you have your account setup with sudo it should grant you the permissions to edit the file.

IDK...thought I saw something in the mount that screamed out live system but after comparing it with my SSD install everything seems fine. So...is everything good now or is there something else I missed?

 

[ihatelolcats]

its all good. aside from trying to install opencl to use with boinc but that's a separate issue
thanks for the help