Shell Programming and Scripting

Is that file system actually mounted on /media/usb0?

That media or usb-storage is not mounted actually on the wheezy machine. If so, it appears in the file-manager, but it remains the error. While booting that laptop the GRUB loader tells me he is expecting that device, because I changed the fstab-file to that content as follows

Code:

root@rechenknecht2:/etc# cat 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>
# / was on /dev/sda1 during installation
UUID=71d40357-4318-4e08-a4f3-ab3f019c194f /               ext4    errors=remount-ro 0       1
# swap was on /dev/sda5 during installation
UUID=c95dabb2-85b9-4778-b9cb-8bd7727fd77a none            swap    sw              0       0
/dev/sr0        /media/cdrom0   udf,iso9660 user,noauto     0       0
/dev/sdb1       /media/usb0     auto    rw,user,auto  0       0
#UUID=641ea5c8-47d2-4473-ae01-6499d2f7ccba  /media/usb0  ext3 auto, defaults 0 2

As far as I know these values defaults 0 and 2 are for checking the media and the number of boots or not. But anyway it is still there on the wheezy-laptop, while shutting down the same message appears that there has been a failure to that specific device. So I still will find out how to recover, but....with little hope, 'cause on the squeeze system there appears just nothing plugging it in. Anyway it has been a backup for some data, that does not mean for me to make a backup for a backup or even going for any cloud service.

---------- Post updated 02-04-15 at 07:51 AM ---------- Previous update was 02-03-15 at 09:29 PM ----------

After re-writing the /etc/fstab-file changing

Code:

/dev/sdb1       /media/usb0     auto    rw,user,auto  0       0

to

Code:

/dev/sdb1       /media/sdb1    auto    rw,user,auto  0       0

and saving it, it is overwritten to the first line, (re-writing as root) somehow, and appears at wheezy, but the media itself appears empty and doesn't show up as or at usb0, although changing to /etc
typing ls there shoud be. As root I got no permission to make this changes. So first chmod. To be continued.
But

Code:

 find /etc -type f -exec chmod 777 {} +

or

Code:

 find /etc -type d -exec chmod 777 {} +

just tells me that I got no permission, as root, to change this file. This remembers me of sudo. rrrubbish. sorry

If you had done this without -type d, the effects on your system would have been absolutely ruinous.

As is, you should still probably reinstall from scratch. Strange things are likely to happen from here on out. You have tampered with the permissions of many important folders. 777 is not the magic sledgehammer to fix all permissions problems.

What folder did it tell you you didn't have permission to change, by the way...?

The fstab isn't magic. All it does is mount. If mount doesn't work, fstab isn't going to help.

At this point I would recommend sending your USB drive to a specialist data recovery service to see if they can undo your destructive changes.

Code:

find /etc -type d -exec chmod 777 {} +

Sure, you are right, I should improve the original, this specific line I used to handle the archive themself, just for using this media on several machines, so it would be e.g., sorry for the misunderstanding.

Code:

find /media/usb0/sounds5 -type f -exec chmod 777 {} +

to get this straight.

777 is not the magic sledgehammer to fix all permissions problems.

Try 750.

Okay, I'll remember, 'cause apart of this, it is an endless journey. :-)

I hope you realize that completely compromises your machine.

Anyone who can access the box can now replace files such as /etc/passwd or /etc/shadow, change out SSH keys, have init and services run arbitrary code, and a slew of other things.

Anything and everything under /etc can be replaced. By anyone.