You are not logged in.
@Corenominal, thanks for sharing your iconic configuration of linux. Thanks for helping out the community, especially in the early days. It fostered the best Linux forum ever. I admit that when I borked my #! system, and it wouldn't reinstall, I again started to distrohop, which was kinda good for me since I could not install #! at work, but could install Debian. Your vision and the community you started helped me understand how to configure everything about linux. After a while, it becomes second nature. Which helps me maintain my Debian computational cluster at work.
I appreciate all you have done for the #! community, and also, for linux in general.
Thanks @bobobex for chiming in on the communities, and also for letting us have Philip for a bit!
But both of you, don't be strangers, stick around!! We benefit from you being here.
@dove I see Kindle on your dock (fbpanel? cairo?). So my question is, how'd you install kindle?
Nice wall too.
THX1138, one of my fav movies. Love the no frills configuration too, @hhh
this thread is supermagic
I have had recent install woes as well. However mine were due to the guided install making weird install choices to my 2 drives, similarly set as yours. Guided install did some weird things, different from yours though. My disks were partitioned and assigned / and /home in a strange fashion and none would automatically mount. So, not the same as yours. @ohnonot chimed in on my initial discussion diagnosing my partitioning.
On recommendation of @damo I first formatted from my bootable #! thumbdrive using gparted. I removed the partitions, applied the operations, then created new partitions making sure the full size of the drive was accounted for, no unused space, then applied those operations. Then booted out and into the Install option on the same drive and chose manual install.
Now things are perfect. Did you do a guided or manual install?
@damo, you know, when I have been in the installer, I have these nightmare memories of complex install instructions. I just assumed the memories were from #!'s installer, but, actually no. They must have been from a previous distro. Immediately after my last post, I decided to just do exactly what you said. The #! installer is quite easy. No problems with partitioning or installing things where I want. I am not sure why the guided installer made the choices it did previously. But for the sake of any total linux newbie out there considering whether it is difficult to install, not really, not even in a manual install.
@AndyinMokum, I have a few bootable thumbdrives (Mint, OpenSuse, #!, Mavericks, etc) all with gparted. They are the most excellent little things to carry around. Of bootable thumbdrives I have to say I like Suse the best but for my permanent install I of course like the #!
Thanks to you both for giving an assist!
@damo I was using guided because I was expecting, perhaps wrongly, that the guided install would optimize more knowledgeably than I. Possibly not though. I guess with the guided install, the installer makes a choice based on rules etc which may not necessarily apply to this machine though could not find information about the installer or a similar problem on the the debian forums.
I am having problems getting the installer to create and format partitions the way I select them. My laptop has a 500 gb HDD and 32 gb SSD. I have tried three fresh installs, each with different options as to how to install. But after every install, the 500 gb drive is always xfs2 with boot, and the 32 gb drive is xfs4 with /home, always reversed from how I want it to be.
The three methods I have tried were
1. guided install (no LVM or encryption) to 32 gb drive (everything: /, /home, etc)
2. guided install (no LVM or encryption) with / to 32 gb and /home to 500 gb
3. guided install with LVM & encryption to 32 gb drive (everything)
The reason I had to even reinstall the first time was that my computer would not boot after installing MBR, in preparation to reinstall MSW and sell the laptop. I am not sure if that is important though since I have formatted each drive several times since that point; but thought I should mention it.
#! on this same computer has been a dream for several months, and I need a bit of help or a point in the right direction. Thanks in advance.
It's been a while since this thread had a post but I'll try and revive.
On a recent reinstall, I decided to use guided encrypted LVN and I saw the LVN-partitioning dialogs for both the 32 gb SSD and the 500 gb HDD on my laptop. After install completed, only the 32 gb SSD was LV mapped. The 500 gb was not. (It's also only accessible via sudo.) Is there a reason LVM was unable to complete the mapping job on install? Shouldn't the install process and LVN's volume management be completed successfully during install?
@damo, thanks for the detailed description. It looks like lots of folks use and prefer the symlink method. I am still curious about what would make one method better or more/less efficient/preferred. @Ratcheer & @ohnonot, thanks for your help also.
I finally had a few hours between holiday events to format the drive and reinstall, this time preemptively partitioning the larger drive with gparted before reinstalling. I chose the guided encrypted LVN option. I have not had this type of setup on this particular laptop before but did have LVM on a previous single drive netbook, so it seemed a decent option. In the install process, I got messages from LVM regarding preparing each of the two drives (32 & 500 gb). I mention this because it may affect things.
I installed / and home to the 32 gb drive. Boot still appears on the 500 gb drive, yet the drive itself, which shows in Thunar but Thunar cannot perform operations on it, I have to use sudo in order to get into it and do stuff, and in fstab the drive appears not to be LV mapped. Here are relevant outputs again.
superwow@rlyeh:~$ 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>
/dev/mapper/rlyeh-root / ext4 errors=remount-ro 0 1
# /boot was on /dev/sdb1 during installation
UUID=bd83b222-421a-4303-9eea-e09f9f8babd0 /boot ext2 defaults 0 2
/dev/mapper/rlyeh-home /home ext4 defaults 0 2
/dev/mapper/rlyeh-swap_1 none swap sw 0 0
#/dev/sdc1 /media/usb0 auto rw,user,noauto 0 0
superwow@rlyeh:~$ sudo fdisk -l
Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00032414
Device Boot Start End Blocks Id System
/dev/sda1 * 2048 976771071 488384512 83 Linux
Disk /dev/sdb: 32.0 GB, 32017047552 bytes
255 heads, 63 sectors/track, 3892 cylinders, total 62533296 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00087d03
Device Boot Start End Blocks Id System
/dev/sdb1 2048 499711 248832 83 Linux
/dev/sdb2 501758 62531583 31014913 5 Extended
/dev/sdb5 501760 62531583 31014912 83 Linux
Disk /dev/mapper/sdb5_crypt: 31.8 GB, 31757172736 bytes
255 heads, 63 sectors/track, 3860 cylinders, total 62025728 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Disk /dev/mapper/sdb5_crypt doesn't contain a valid partition table
Disk /dev/mapper/rlyeh-root: 8019 MB, 8019509248 bytes
255 heads, 63 sectors/track, 974 cylinders, total 15663104 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Disk /dev/mapper/rlyeh-root doesn't contain a valid partition table
Disk /dev/mapper/rlyeh-swap_1: 1023 MB, 1023410176 bytes
255 heads, 63 sectors/track, 124 cylinders, total 1998848 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Disk /dev/mapper/rlyeh-swap_1 doesn't contain a valid partition table
Disk /dev/mapper/rlyeh-home: 22.7 GB, 22712156160 bytes
255 heads, 63 sectors/track, 2761 cylinders, total 44359680 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Disk /dev/mapper/rlyeh-home doesn't contain a valid partition table
superwow@rlyeh:~$ sudo lvdisplay
--- Logical volume ---
LV Path /dev/rlyeh/root
LV Name root
VG Name rlyeh
LV UUID me3SCW-6OTd-DMGW-pFJe-rNBL-ukZe-BY2hVf
LV Write Access read/write
LV Creation host, time rlyeh, 2013-12-22 18:14:33 -0800
LV Status available
# open 1
LV Size 7.47 GiB
Current LE 1912
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 254:1
--- Logical volume ---
LV Path /dev/rlyeh/swap_1
LV Name swap_1
VG Name rlyeh
LV UUID sU53FD-ddOf-QUY3-Mnzv-qcMq-McFZ-tXdTKo
LV Write Access read/write
LV Creation host, time rlyeh, 2013-12-22 18:14:33 -0800
LV Status available
# open 2
LV Size 976.00 MiB
Current LE 244
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 254:2
--- Logical volume ---
LV Path /dev/rlyeh/home
LV Name home
VG Name rlyeh
LV UUID pmbYvs-7mM2-oeHr-aPRf-1VFP-1hH0-2qLlJm
LV Write Access read/write
LV Creation host, time rlyeh, 2013-12-22 18:14:33 -0800
LV Status available
# open 1
LV Size 21.15 GiB
Current LE 5415
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 254:3
superwow@rlyeh:~$ blkid
/dev/sda1: UUID="a2fe459a-6b3f-4eb5-ae75-018cf6b97344" TYPE="ext4"
/dev/sdb5: UUID="6c235dd5-c07b-4efa-9717-bfb2ac87e6d8" TYPE="crypto_LUKS"
The 500 gb drive is shown in fstab, fdisk shows it as well though not as LVM mapped (despite LVM formatting it in the install process), and lvdisplay does not see it.
Questions:
1. Could a previously installed MBR (for MSW) be causing this?
2. Or do I just need to manually remove the boot item from dev/sda1 in fstab, try remapping with LVN, and manually adding a mountpoint? If so, why wasn't LVM able to do all this during install?
Currently reading through @El_Koraco's Monumental LVM guide (a great set of guides btw) to figure out why the drive is not LV mapped. But again, any help is welcome - and thanks.
Here is the IO of:
sudo fdisk -l
Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/sda1 * 2048 960397311 480197632 83 Linux
/dev/sda2 960399358 976771071 8185857 5 Extended
Partition 2 does not start on physical sector boundary.
/dev/sda5 960399360 976771071 8185856 82 Linux swap / Solaris
Disk /dev/sdb: 32.0 GB, 32017047552 bytes
255 heads, 63 sectors/track, 3892 cylinders, total 62533296 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000544ab
Device Boot Start End Blocks Id System
/dev/sdb1 2048 59895807 29946880 83 Linux
/dev/sdb2 59897854 62531583 1316865 5 Extended
/dev/sdb5 59897856 62531583 1316864 82 Linux swap / Solaris
@ohnonot, both drives have seen multiple installs, which is why they look 'weird', that and I believe because I must have chosen poorly on install.
But your comment harkens to my own personal suspicions that I will have to format both drives and reinstall, as there are a few other issues with the system now. So on to that now, and then will try @damo's symlink suggestion I think.
@Ratcheer, I just want home to be on the larger drive and don't want to overwrite the files I already have on that larger drive. It used to be my home drive on a previous (#!) install. I believe I must have misread the partitioning step instructions on this new install; I thought at the time I was choosing the options which would place the OS on the small sdd and home on the larger hdd.
I may wind up editing the fstab as you suggested (mkfs / mkdir / mount). Also, I appreciate CLI advice (better than GUI usually imo).
@damo thanks for the suggestion. A few questions for you:
1. Once the symlink is made, do both graphical and CLI programs both follow the link? I am wondering what will happen when I log in after symlinking and there are config files in both folders.
2. Are you symlinking your username folder? (I mean, /damo?) or symlinking each of the folders inside /damo? (documents, .config, etc)?
3. Is this better than modifying fstab? or the usermod option?
@ratcheer, thanks. How do you create the home? by writing to fstab or using symlinks or some other method?
It seems like with each of the above methods people on other forums have problems. I guess I am looking for the most error free version. Sorry for all the questions but thanks for the advice.
@ohnonot sorry about that. Output from CLI
fdisk -l
gives
Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00000000Device Boot Start End Blocks Id System
/dev/sda1 * 2048 960397311 480197632 83 Linux
/dev/sda2 960399358 976771071 8185857 5 Extended
Partition 2 does not start on physical sector boundary.
/dev/sda5 960399360 976771071 8185856 82 Linux swap / SolarisDisk /dev/sdb: 32.0 GB, 32017047552 bytes
255 heads, 63 sectors/track, 3892 cylinders, total 62533296 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000544abDevice Boot Start End Blocks Id System
/dev/sdb1 2048 59895807 29946880 83 Linux
/dev/sdb2 59897854 62531583 1316865 5 Extended
/dev/sdb5 59897856 62531583 1316864 82 Linux swap / Solaris
I want #! and boot on 32 gb drive, and home directory on the 500 gb drive (which contains all my files from the previous install).
Does that help?
Today I borked my computer and had to reinstall #! (was intending to reinstall MSW and sell this computer). My laptop has a 500 gb HDD (sda) and a 32 gb SSD (sdb). My previous install had home, boot, and swap on the 500 gb drive. This means all of my files are there (and it is where I want them to stay). On the reinstall, I wanted #! on the 32 gb drive, AND to leave my files where they are, on the 500 gb directory, which I also want as my home directory.
After all the install scripts have finished running, I realize I have chosen poorly. Thunar shows me that my home is now in the 32 gb directory. And Gparted shows me that boot is on the 500 gb directory. Razzlefrazzle dagnabbit. I searched and have found a few different methods to change my home directory to the different drive. Can anyone provide experienced advice as to which of the following is better?
1. usermod (this feels to me like the most straightforward way)
usermod -d /home/your_home_directory USERNAME
chown -R USERNAME /new_location/your_home_directory
2. modify fstab (if I do this, how should I comment the old home?)
sudo cp /etc/fstab /etc/fstab.bak
gksu geany /etc/fstab
and add a line to place my home directory there like so:
#/dev/sda1
UUID=<UUID of sda1> /home ext4 errors=remount-ro 0 1
3. mkdir / mount / umount combo (seems overly complex compared to usermod)
mkdir /mnt/newhome
mount /dev/sdb1 /mnt/newhome
cp -a /home/* /mnt/newhome/
log out as your user and switch to a terminal (Ctrl + Alt + F1 or similar)
mv /home /home.old
umount /mnt/newhome
mkdir /home
mount /dev/sdb1 /home
4. make a symlink (my intuition is not to do this though)
cp -R /home/whatever /path/to/destination
mv /home/whatever /home/whatever.orig
ln -s /path/to/destionation /home/whatever
rm -rf /home/whatever.orig
Thanks to everyone for reading and anyone for advice.
OLD TITLE: Help with external drive (suddenly read-only)
Hello all, I am having a problem with an external drive. I have tried to migrate files from several external backups to this one drive. Everytime I move new things to the drive, new permissions are assigned to folders and progressively more folders are locked as read only. I feel like this is a noob question but all the solutions googs gives me require wiping the drive. How can I fix this withought (formatting the drive and) losing my data?
Here's more information: The drive is a 2Tb external usb drive formatted to FAT32. I have used this drive predominantly with linux (mostly #! but previously *buntus). I migrated to nix from a brief stint on MSW and a decade of Mac usage. When I migrated, I of course backed up as much of my files as I could onto one drive, this 2Tb drive. So, it contains files from MSW, Mac OS (10.0, 10.1, 10.2, 10.4, 10.6, 10.8), and nixes.
Prior to yesterday and the day before, I kept the backup for each major OS in its own folder (so the drive had three folders in the top folder: Win-backup, Mac-backup, and nix-backup, with files from each OS NOT intermingled).
Yesterday, I was happily accessing an ancient external drive to load a picture frame with images from a very old backup. The only port of this drive was a Firewire 2 port. I found an old Macbook Pro with the appropriate port in the house running 10.8, connected to the drive, and began moving files from the ancient HDD to my 2TB drive. I was having a major problem keeping track of files on the drive so, after having pulled all the files I needed from the ancient drive using Mac OS 10.8, I ejected the drive and connected it to my #! laptop and I merged them all into topically organized folders (ie, Documents, Images, Videos, etc).
On top of this, I have again encountered the bane of Thunar, that is, its utter inability to eject an external volume. Kaaaahhhhnnn!!!
The message I get when trying to copy is: 'Error creating directory. Read only file system.' Although, before yesterday, the system was not read only. I do not know why it is read-only now. Is it because I have mixed files? or because Thunar does not eject properly?
All the files, regardless of Mac or nix origin, have the same permissions according to ls -l.
Some terminal output is below: fuser tells me lots of processes are using the drive (though I am not sure if I am reading the output correctly). I cannot force unmount with umount -f. And fdisk tells me that lots of processes are accessing the drive (but why?).
superwow@rlyeh:~$ sudo fdisk -l
Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x000ee99e
Device Boot Start End Blocks Id System
/dev/sda1 * 2048 960397311 480197632 83 Linux
/dev/sda2 960399358 976771071 8185857 5 Extended
Partition 2 does not start on physical sector boundary.
/dev/sda5 960399360 976771071 8185856 82 Linux swap / Solaris
Disk /dev/sdb: 32.0 GB, 32017047552 bytes
255 heads, 63 sectors/track, 3892 cylinders, total 62533296 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x8ddd6e47
Device Boot Start End Blocks Id System
/dev/sdb1 2048 8386559 4192256 84 OS/2 hidden C: drive
/dev/sdb2 * 8386560 62531583 27072512 83 Linux
Disk /dev/sdd: 2000.4 GB, 2000365289472 bytes
255 heads, 63 sectors/track, 243197 cylinders, total 3906963456 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x0005f107
Device Boot Start End Blocks Id System
/dev/sdd1 2048 3906963455 1953480704 7 HPFS/NTFS/exFAT
superwow@rlyeh:~$ sudo umount -f /dev/sdd1
umount2: Device or resource busy
umount: /media/F3E0-DC38: device is busy.
(In some cases useful info about processes that use
the device is found by lsof(8) or fuser(1))
umount2: Device or resource busy
superwow@rlyeh:~$ mount
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
udev on /dev type devtmpfs (rw,relatime,size=10240k,nr_inodes=493854,mode=755)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=396332k,mode=755)
/dev/disk/by-uuid/0e140173-ecb9-44ec-a834-6ccfe9d79062 on / type ext4 (rw,relatime,errors=remount-ro,user_xattr,barrier=1,data=ordered)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
tmpfs on /run/shm type tmpfs (rw,nosuid,nodev,noexec,relatime,size=2429820k)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,nosuid,nodev,noexec,relatime)
fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)
gvfs-fuse-daemon on /home/superwow/.gvfs type fuse.gvfs-fuse-daemon (rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)
/dev/sdd1 on /media/F3E0-DC38 type vfat (ro,nosuid,nodev,relatime,uid=1000,gid=1000,fmask=0022,dmask=0077,codepage=cp437,iocharset=utf8,shortname=mixed,showexec,utf8,flush,errors=remount-ro,uhelper=udisks)
superwow@rlyeh:~$ sudo umount /dev/sdd1
umount: /media/F3E0-DC38: device is busy.
(In some cases useful info about processes that use
the device is found by lsof(8) or fuser(1))
superwow@rlyeh:~$ fuser -m /dev/sdd1
/dev/sdd1: 2937 3013 3060 3061 3072 3073 3088 3089 3095 3100 3102 3106 3113 3118 3122 3125 3131 3141 3142 3143 3144 3146 3159 3180 3186 3194 3207 3213 3378 3383 3909 9632 9638 13253 17982 19511 20639 20640 20793
superwow@rlyeh:~$ fuser -mv /dev/sdd1
USER PID ACCESS COMMAND
/dev/sdd1: root kernel swap /dev/sda5
root kernel mount /dev
superwow 2937 f.... gnome-keyring-d
superwow 3013 F.... openbox
superwow 3060 F.... dbus-launch
superwow 3061 F.... dbus-daemon
superwow 3072 f.... tint2
superwow 3073 f.... pnmixer
superwow 3088 f.... xscreensaver
superwow 3089 f.... clipit
superwow 3095 F.... bluetooth-apple
superwow 3100 f.... syndaemon
superwow 3102 F.... xfce4-volumed
superwow 3106 F.... conky
superwow 3113 F.... xfce4-power-man
superwow 3118 F.... xfconfd
superwow 3122 F.... gvfsd
superwow 3125 F.... pulseaudio
superwow 3131 F.... gvfs-fuse-daemo
superwow 3141 f.... synapse
superwow 3142 f.... docky
superwow 3143 f.... nm-applet
superwow 3144 f.... system-config-p
superwow 3146 f.... zeitgeist-datah
superwow 3159 F.... zeitgeist-daemo
superwow 3180 F.... gconfd-2
superwow 3186 F.... gvfs-gdu-volume
superwow 3194 F.... zeitgeist-fts
superwow 3207 F.... gvfs-gphoto2-vo
superwow 3213 F.... gvfs-afc-volume
superwow 3378 F.... gvfsd-trash
superwow 3383 F.... compton
superwow 3909 F.... gvfsd-metadata
superwow 9632 f.... bash
superwow 9638 F.... banshee
superwow 13253 F.... dconf-service
superwow 17982 F.... x-www-browser
superwow 19511 F.... geany
superwow 20639 f.... sh
superwow 20640 F.... /usr/bin/termin
superwow 20793 F.... xfce4-notifyd
Finally I have unmounted the volume with (not sure if this is a good way to do it though):
sudo fuser -k /dev/sdd1 && sudo umount -f /dev/sdd1
but I want to know:
1. why the volume became read-only?
SOLVED: because Thunar never ejects drives
2. how to make Thunar unmount correctly (aside from using the terminal command above)?
UPDATE:
Turns out file permissions had nothing to do with the read-only mode of files/folders.
The problem is related to Thunar's inability to unmount the external drive. I do not know if Thunar is incapable because it is flawed inherently (seems possible), or because it is flawed on my machine (doubt this one since scads of people complain about Thunar's eject-impotence), or because so many processes were trying to access my external (seems logical).
So, I am appending a new question:
Why are 39 processes (list above, courtesy of fuser -mv) which have no logical need to do so accessing my external?
Welcome to #! forums.
1. I used to live in Texas. I miss it.
2. I had a Geology TA in undergrad. She was superawesome. Every class, she asked us the same question: class if you learn one thing from my class, what is it? Class: Don't build your house in a flood plane. LOL. I also learned it is ok to eat rocks. Awesome class.
3. #! is great on resources, Openbox a charm, and, there are very friendly folks here, who are also very smart
4. GOT is dern good. Can't wait for Winds of Winter.
Thanks for the tutorial. I have a question.
Using the first method above allows me to view my MotoX's photos. I was able to import the photos using Shotwell (veeerrrry slowly, for some reason). However, when I tried to unmount using 'fusermount -u gphotofs', I got unexpected results. A message was returned:
entry for /home/superwow/gphotofs not found in /etc/mtab
Umount -l /dev/sdb showed I had mounted several tmpfs (temp file systems I think, which should be Android). Lsusb showed I was attached to sda mountpoints, and several tmp folders.
I tried to troubleshoot and then left the computer for a couple of hours to run errands. It was not plugged in and shut itself down when the battery ran down. Reconnecting to power, rebooting the computer, and trying to access the drive again by repeating the steps, I get
superwow@rlyeh:~$ gphotofs ~/MotoX_gfilesystem
fusermount: failed to access mountpoint /home/superwow/MotoX_gfilesystem: Permission denied
Has shutdown and inappropriate unmounting borked my gphotofs? How to fix it?
Perelandra by CS Lewis.
@GekkoP, thanks for the info. I liked it so installed. YES! love ranger. Now I must figure out a way to install it in the Android Terminal Emulator!!
@Ututo, I like the chrome/android-style application icon. I was going to add something like that to my own tint2 but found right clicking the tint2 panel gave the Openbox menu, so I just skipped doing it. I am not sure if my right-click behavior is default or related to having launchers in the tint2 panel.
@superwow: it's conky...I can share the config, if you're interested.
If you wouldn't mind that would be nice.
@Ututo, that is a nice set up. What is running in the top right corner? Looks like a pager of some sort. And also, how about the panel at the bottom?
@Krop nice looking and ... what is that mail indicator?
@GekkoP also nice. What are you using as file manager in tmux?
Welcome to the forums, @Count_Zero. I used to live in Houston, and how I miss it, especially the museum district & the variety of restaurants. You can keep the hurricanes and gas smell though
For me, #! runs far more efficiently than any other of the distributions I've tried (the big heavies: Ubuntu, Suse, Fedora, etc). I love Openbox too, so easy to configure.
If you want to learn about linux stuff, I suggest you start at the #! wiki and then try the Quick Refrence Thread. The sections on tint2, conky, and openbox were particularly useful in the beginning. My advice, stick all the things you think you might need later (shortcut descriptions and hard to remember terminal commands, like wifi troubleshooting etc, in your conky).
If you are security conscious, check out the paranoid #! security guide.
Otherwise, just paruse the forums. Screenshot threads actually are a good place to get ideas. Everybody is super helpful and friendly.
@liquid, while I like your screenshot, very stylish, I like even better your wordpress (MrAlphaville) and github pages. Very useful. Thanks!
Thanks for the suggestions. I tried
apt-cache --installed rdepends java
and got:
E: No packages found
But when I try
apt-cache depends libreoffice
I got (editing out the chaff):
"
Dependencies:
... default-jre (16 (null)) gcj-jre (16 (null)) java-gcj-compat (16 (null)) openjdk-6-jre (16 (null)) openjdk-7-jre (16 (null)) sun-java5-jre (16 (null)) sun-java6-jre (16 (null)) java5-runtime (16 (null)) jre (0 (null)) ...
Provides:
1:3.5.4+dfsg2-0+deb7u2 -
Reverse Provides:
"
The depends call tells me that libreoffice depends on java. The rdepends call tells me no installed packages use java. Something is not right here. I suppose rdepends just reads a list from the apt-cache entry at the "Reverse Provides:" section, which was poorly written by the package developer. Is that right?
Thanks again for the help. Learning linux is fun. I just picked up a couple of apt oriented commands, from you and from reading forums. Apt is so superior to Mac or MS software update methods. I love it.
Copyright © 2012 CrunchBang Linux.
Proudly powered by Debian. Hosted by Linode.
Debian is a registered trademark of Software in the Public Interest, Inc.
Server: acrobat