please make a space(blank) between fdisk and -l
please make a space(blank) between fdisk and -l
"Every Setback is a Set Up for a Comeback"
SPARK:~# fdisk -l
Disk /dev/sda: 16.0 GB, 16008609792 bytes
64 heads, 32 sectors/track, 15267 cylinders
Units = cylinders of 2048 * 512 = 1048576 bytes
Device Boot Start End Blocks Id System
/dev/sda1 1 15266 15632368 83 Linux
SPARK:~#
OK - do the next please:
then reboot the boxCode:mkdir /tmp/hdd umount /dev/sda1 tune2fs /dev/sda1 -L RECORD mount /dev/sda1 /tmp/hdd mkdir /tmp/hdd/movie
"Every Setback is a Set Up for a Comeback"
I have rebooted the box and nothing
SPARK:~# mkdir / tmp / hdd
mkdir: can't create directory '/': File exists
mkdir: can't create directory '/': File exists
SPARK:~# umount / dev/sda1
umount: can't umount /: Device or resource busy
umount: can't umount dev/sda1: No such file or directory
SPARK:~# tune2fs / dev/sda1-L RECORD
tune2fs 1.42.9 (28-Dec-2013)
Usage: tune2fs [-c max_mounts_count] [-e errors_behavior] [-g group]
[-i interval[d|m|w]] [-j] [-J journal_options] [-l]
[-m reserved_blocks_percent] [-o [^]mount_options[,...]] [-p mmp_update_
interval]
[-r reserved_blocks_count] [-u user] [-C mount_count] [-L volume_label]
[-M last_mounted_dir] [-O [^]feature[,...]]
[-E extended-option[,...]] [-T last_check_time] [-U UUID]
[ -I new_inode_size ] device
SPARK:~# mount / dev/sda1 / tmp / hdd
BusyBox v1.22.1 (2014-05-11 1509 CEST) multi-call binary.
Usage: mount [OPTIONS] [-o OPTS] DEVICE NODE
Mount a filesystem. Filesystem autodetection requires /proc.
-a Mount all filesystems in fstab
-f Update /etc/mtab, but don't mount
-i Don't run mount helper
-n Don't update /etc/mtab
-v Verbose
-r Read-only mount
-w Read-write mount (default)
-t FSTYPE[,...] Filesystem type(s)
-O OPT Mount only filesystems with option OPT (-a only)
-o OPT:
loop Ignored (loop devices are autodetected)
[a]sync Writes are [a]synchronous
[no]atime Disable/enable updates to inode access times
[no]diratime Disable/enable atime updates to directories
[no]relatime Disable/enable atime updates relative to modification ti
me
[no]dev (Dis)allow use of special device files
[no]exec (Dis)allow use of executable files
[no]suid (Dis)allow set-user-id-root programs
[r]shared Convert [recursively] to a shared subtree
[r]slave Convert [recursively] to a slave subtree
[r]private Convert [recursively] to a private subtree
[un]bindable Make mount point [un]able to be bind mounted
[r]bind Bind a file or directory [recursively] to another locati
on
move Relocate an existing mount point
remount Remount a mounted filesystem, changing flags
ro/rw Same as -r/-w
There are filesystem-specific -o flags.
SPARK:~# mkdir / tmp / hdd / movie
mkdir: can't create directory '/': File exists
mkdir: can't create directory 'tmp': File exists
mkdir: can't create directory '/': File exists
mkdir: can't create directory 'hdd': File exists
mkdir: can't create directory '/': File exists
SPARK:~#
please copy and paste exactly my commands,
you add spaces where no spaces are allowed!
so: copy and paste line by line - then everything is working
"Every Setback is a Set Up for a Comeback"
I'm copying and pasting by line and it doesn't work
umount /dev/sda1
SPARK:~# umount /dev/sda1
umount: can't umount /dev/sda1: Invalid argument
Ignore this error as the device seems not to be mounted at current. Continue with the tune2fs command in morly's list
I can see now in the receiver /hdd/movie folder I created and I have copied the movie to it from receiver and still it doesn't show in Filezilla
- - - Aktualisiert - - -
It just fail to mount device
SPARK:~# tune2fs /dev/sda1 -L RECORD
tune2fs 1.42.9 (28-Dec-2013)
SPARK:~# mount /dev/sda1 /tmp/hdd
mount: mounting /dev/sda1 on /tmp/hdd failed: Device or resource busy
SPARK:~#
Do a refresh in filezilla's list of the destination folder or reconnect/reopen filezilla, it loads the directory structure on startup but does not detect automatically changes in the file system of the destination if those are not done via filezilla
Give one more command
to see if the device is already mounted. If you try to do the same mount operation twice you get this kind of errorCode:mount
Geändert von Mikam_0815 (03.06.2014 um 21:59 Uhr)
shutdown box, unplug hdd, boot hdmu image, plug hdd in and try my commands once more
- - - Aktualisiert - - -
didn't you forget the umount at the beginning? important!!
"Every Setback is a Set Up for a Comeback"