Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #187201 > unrolled thread
| Started by | Gdsi <gdsi11@aol.com> |
|---|---|
| First post | 2017-09-25 20:30 +0200 |
| Last post | 2017-09-26 09:20 +0200 |
| Articles | 4 — 2 participants |
Back to article view | Back to linux.debian.user
I already had wrote into here Gdsi <gdsi11@aol.com> - 2017-09-25 20:30 +0200
Re: I already had wrote into here "Thomas Schmitt" <scdbackup@gmx.net> - 2017-09-25 21:10 +0200
Fwd: I already had wrote into here Gdsi <gdsi11@aol.com> - 2017-09-26 00:10 +0200
Re: I already had wrote into here "Thomas Schmitt" <scdbackup@gmx.net> - 2017-09-26 09:20 +0200
| From | Gdsi <gdsi11@aol.com> |
|---|---|
| Date | 2017-09-25 20:30 +0200 |
| Subject | I already had wrote into here |
| Message-ID | <utGiK-1D4-11@gated-at.bofh.it> |
Hi again. I already had wrote into here (lists.debian.org/debian-user/2017/09/msg00790.html), but did not may to explain my problem, because himself was not understanding nothing. But thanks to the got advices, and numerous attempts to solve the problem I began foggy guessed about causes my problem.
Reminding: I may not mount usb-stick for copying a data (directories) into the usb-stick.
Earlier this usb-stick held 'Deb-8..iso' file, and it mount/umoun exactly.
A long time I tried getting rid of the iso file for, using (rm, dd, rmdir, shred, etc, .), and could not remove it from the disk, but then used the `dd if=/dev/null of=/file.iso' command, and thought that the iso file was deleted. But after the correct remark ". Now reading from /dev/null just gives an End-Of-File.
So an empty /file.iso will emerge." , I think that there is something left on the flash drive, it's just that usb stopped appearing in "Thunar"!
Thinking that the flash drive was empty, I was trying to transfer to it the new folder I needed. Again I used a zoo of commands (cat, mv, cp, mkdir, etc. )- all was not successful. Then I had been using 'fdisk' a long time and with varying ways (gpt/dos modes, multi-partitions, vary booting etc...).
But after all 'mount' doesn't work, and answer:
--------------------------
root@debian:~# mount -v /dev/sdb /mnt
mount: wrong fs type, bad option, bad superblock on /dev/sdb,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so.
root@debian:~#
--------------------
any (/sdb, /sdb1, /sdb2,..., /mnt, /media..) had been tried.
I think all guess about my skills, but hope to a help.
Quickly I am not write, but will read carefully.
Thank all.
[toc] | [next] | [standalone]
| From | "Thomas Schmitt" <scdbackup@gmx.net> |
|---|---|
| Date | 2017-09-25 21:10 +0200 |
| Message-ID | <utGVs-27d-9@gated-at.bofh.it> |
| In reply to | #187201 |
Hi,
Gdsi wrote:
> Reminding: I may not mount usb-stick for copying a data (directories) into
> the usb-stick.
> Earlier this usb-stick held 'Deb-8..iso' file, and it mount/umoun exactly.
As long as the ISO is recognizable, a mounted /dev/sdb will be read-only,
because ISO 9660 is a read-only filesystem.
You can make the ISO unrecognizable by
dd if=/dev/zero bs=2048 count=1 seek=16 of=/dev/sdb
Nevertheless, this will not make /dev/sdb mountable as writable filesystem.
You need a suitable partitioning and in the partition (or several partitions)
you need a writable filesystem (or several of them).
> root@debian:~# mount -v /dev/sdb /mnt
> mount: wrong fs type, bad option, bad superblock on /dev/sdb,
> missing codepage or helper program, or other error
So the ISO is successfully defaced meanwhile.
Now you need to check the partitionining. Is it still like last week ?
Device Start End Sectors Size Type
/dev/sdb1 2048 4196351 4194304 2G Linux filesystem
/dev/sdb2 4196352 8390655 4194304 2G Linux filesystem
/dev/sdb3 8390656 12584959 4194304 2G Linux filesystem
/dev/sdb4 12584960 15431304 2846345 1.4G Linux filesystem
If so:
Is it intentional that you have 4 distinct filesystems ?
If yes:
Check whether /dev/sdb1 already has a mountable filesystem:
mount /dev/sdb1 /mnt
If yes:
Try whether this filesystem suits your needs:
Long filenames, distinction between upper and lower case, ...
If not mountable:
Then you need to create a filesystem partition /dev/sdb1.
If not:
Then you need to change the partitioning to what you want.
For example one large partition from block 2048 to 15431304.
Then you need to create a filesystem in the newly defined partition.
/sbin/fdisk can do deletion and creation of partitions. Take care not
to re-partition the wrong device.
If a new filesystem is needed, then program /sbin/mkfs may be used.
Important is to choose a suitable type. If MS-Windows shall be able to
read the files, then FAT on a small partition might be useful.
Else consider type "ext2".
If i google "linux make partition" i get valid advice about fdisk usage.
>From "linux make partition gui" i get to "Gnome Disk Utility",
"KDE Partition Manager", "GParted", and others.
The same way "linux make filesystem" and "linux make filesystem gui"
lead to mkfs examples and again to the GUI partitioning and formatting
tools above.
In any case, /dev/sdb1, not /dev/sdb is the device to mount.
> Again I used a zoo of commands (cat, mv, cp, mkdir, [...]
> any (/sdb, /sdb1, /sdb2,..., /mnt, /media..) had been tried.
Be cautious with several of the possible combinations.
Have a nice day :)
Thomas
[toc] | [prev] | [next] | [standalone]
| From | Gdsi <gdsi11@aol.com> |
|---|---|
| Date | 2017-09-26 00:10 +0200 |
| Message-ID | <utJJD-43z-3@gated-at.bofh.it> |
| In reply to | #187203 |
Very thank for advices, the general undestanding are got. Now I can not write with good spelling. Week back there was: '''''''''''''''''''''''''''' Disklabel type: gpt Disk identifier: B9CE4505-2CC9-4A28-AFE5-6D007A023AB2 Device Start End Sectors Size Type /dev/sdb1 2048 4196351 4194304 2G Linux filesystem /dev/sdb2 4196352 8390655 4194304 2G Linux filesystem /dev/sdb3 8390656 12584959 4194304 2G Linux filesystem /dev/sdb4 12584960 15431304 2846345 1.4G Linux filesystem '''''''''''''''''''''''''''''' Now there are: '''''''''''''' Disklabel type: dos Disk identifier: 0xc6c9dfed Device Boot Start End Sectors Size Id Type /dev/sdb1 * 62 4194366 4194305 2G 83 Linux /dev/sdb2 * 4194367 8388671 4194305 2G 83 Linux /dev/sdb3 * 8388672 12582976 4194305 2G 83 Linux /dev/sdb4 * 12582977 15431337 2848361 1.4G 83 Linux ''''''''''''''''''''''''' To work with 'fdisk' I have seem learned, but is not know which file systems are better used for usb-stick. Again many thanks.
[toc] | [prev] | [next] | [standalone]
| From | "Thomas Schmitt" <scdbackup@gmx.net> |
|---|---|
| Date | 2017-09-26 09:20 +0200 |
| Message-ID | <utSjV-1vB-21@gated-at.bofh.it> |
| In reply to | #187215 |
Hi, now that you seem ok with the partitioning and the partition 1 is not yet mountable, it is time to create a filesystem on it. As superuser or via "sudo": mkfs -t ext2 /dev/sdb1 When this is done, you should be able to mount the filesystem mount /dev/sdb1 /mnt The filesystem should be empty. So you need to make a directory which you want to populate with files: mkdir /mnt/photos and give it to the user who shall be able to write to it: chown gdsi /mnt/photos Of course the user name "gdsi" is just a guess. Give the ownership to the user id which runs your shells in the terminals. You may inquire it by this command: whoami Mine says "thomas". Now it should be possible for your normal user id to copy files into the directory: cp "$HOME"/photos/house*.jpg /mnt/photo or to create further directories underneath /mnt/photo mkdir /mnt/photo/landscapes /mnt/photo/trees /mnt/photos/clouds Before you pull the USB stick from the computer, you need to unmount it so that any still pending changes get written to the stick. As superuser or via sudo: umount /dev/sdb1 Each time after you plugged the stick into the computer, you need to mount it, if not your desktop automats do this without asking you (somewhere underneath /media, normally): mount /dev/sdb1 /mnt Have a nice day :) Thomas
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.user
csiph-web