Renaming issues ...
3 participantes
Página 1 de 1.
Renaming issues ...
Hello,
Sorry for the english, I am still not speaking spanish
I wanted to share an issue I spotted with some special characters (I think).
I regularly record Dr House on the French HD DTT and the last time I did, I got a fil I could not play (with the film roll and the interrogation mark). I therefore launched the FTP, to get the file back on my pc and to check what was happening (I had a similar issue with a film that began to record when my aerial was "down" and then back, and it was previewed ok, played by vlc on my pc, but I couldn't launch it with the normal PLAY command, nor edit it with TS Doctor _except in RAW Mode_ etc.).
I then saw it was a 11G file (cool, there are data in it ), and tried to FTP it with Filezilla.
I couldn't!
I thought this was related to the name of the File: Dr House. _EcorchÃs vifs__20100511_2045.ts (I already had issue with that earlier, FTPing a file with special characters in the name and getting a blank icon, with a partial name and no mean to delete it or rename it).
So I decided to rename it via FTP. I couldn't.
Ok, so I decided to rename it via a telnet sessions:
mv ./Dr\ House.\ _EcorchÃs\ vifs__20100511_2045.ts ./DrHouse.ts
mv: unable to rename `./Dr House. _EcorchÃs vifs__20100511_2045.ts': Operation not permitted
(I even chmod ugoa+rwx in case, also tried cp rather than mv...).
I couldn't.
So I decided to rename it via LG interface on my TV ... I still couldn't. (Echec de renommer!)
I think I more or less did everything I could there till modyfing my default busybox (if mv/cp/etc. are commands in it) hoping there is one dealing better with bloody characters that are sent via EPG and not understood correctly by the system.
If anyone has a magic command I couldn't think of, before modifying my system :-( , I would be more than thankful!
I am pretty sure I already had the issue with other programs.
Cheers,
Matt
PS: I also tried via Samba, since the file name looks better (identical, I think, to how it looks on the LG interface): Dr House. _Ecorchés vifs__20100511_2045.ts
"You need an authorisation to perform that action" (free translation from french error message )
Of course in all cases, my target name was very simple: DH.ts (no space, no special characters, etc.)
PPS: I just wondered why I do not go to the LG SAV about this rather than coming here ... I think you know why
Sorry for the english, I am still not speaking spanish
I wanted to share an issue I spotted with some special characters (I think).
I regularly record Dr House on the French HD DTT and the last time I did, I got a fil I could not play (with the film roll and the interrogation mark). I therefore launched the FTP, to get the file back on my pc and to check what was happening (I had a similar issue with a film that began to record when my aerial was "down" and then back, and it was previewed ok, played by vlc on my pc, but I couldn't launch it with the normal PLAY command, nor edit it with TS Doctor _except in RAW Mode_ etc.).
I then saw it was a 11G file (cool, there are data in it ), and tried to FTP it with Filezilla.
I couldn't!
I thought this was related to the name of the File: Dr House. _EcorchÃs vifs__20100511_2045.ts (I already had issue with that earlier, FTPing a file with special characters in the name and getting a blank icon, with a partial name and no mean to delete it or rename it).
So I decided to rename it via FTP. I couldn't.
Ok, so I decided to rename it via a telnet sessions:
mv ./Dr\ House.\ _EcorchÃs\ vifs__20100511_2045.ts ./DrHouse.ts
mv: unable to rename `./Dr House. _EcorchÃs vifs__20100511_2045.ts': Operation not permitted
(I even chmod ugoa+rwx in case, also tried cp rather than mv...).
I couldn't.
So I decided to rename it via LG interface on my TV ... I still couldn't. (Echec de renommer!)
I think I more or less did everything I could there till modyfing my default busybox (if mv/cp/etc. are commands in it) hoping there is one dealing better with bloody characters that are sent via EPG and not understood correctly by the system.
If anyone has a magic command I couldn't think of, before modifying my system :-( , I would be more than thankful!
I am pretty sure I already had the issue with other programs.
Cheers,
Matt
PS: I also tried via Samba, since the file name looks better (identical, I think, to how it looks on the LG interface): Dr House. _Ecorchés vifs__20100511_2045.ts
"You need an authorisation to perform that action" (free translation from french error message )
Of course in all cases, my target name was very simple: DH.ts (no space, no special characters, etc.)
PPS: I just wondered why I do not go to the LG SAV about this rather than coming here ... I think you know why
matthelas- Mensajes : 145
Fecha de inscripción : 08/02/2010
Re: Renaming issues ...
Phewww,
not sure if I understood.
When you use the mv command, you write the long filename by hand, or completed with TAB ?
Try to mv like this : mv Dr*.ts new_file.ts
But I am afraid you have a kind of corruption in that file.
Does it allow to delete the file?
not sure if I understood.
When you use the mv command, you write the long filename by hand, or completed with TAB ?
Try to mv like this : mv Dr*.ts new_file.ts
But I am afraid you have a kind of corruption in that file.
Does it allow to delete the file?
vic1972- Mensajes : 2260
Fecha de inscripción : 09/12/2009
Edad : 52
Localización : Malaga
Re: Renaming issues ...
Did not work with busybox 1.9.1 i got on moviecube.free.fr:
./busybox1.9.1 mv ../REC/Dr House. _EcorchÃs vifs__20100511_2045.ts ../REC/DR_HOUSE.ts
mv: cannot rename '../REC/Dr House. _EcorchÃs vifs__20100511_2045.ts': Operation not permitted
./busybox1.9.1 cp ../REC/Dr House. _EcorchÃs vifs__20100511_2045.ts ../REC/DR_HOUSE.ts
cp: cannot stat '../REC/Dr House. _EcorchÃs vifs__20100511_2045.ts': Value too large for defined data type
./busybox1.9.1 mv "../REC/Dr House. _EcorchÃs vifs__20100511_2045.ts" ../REC/DR_HOUSE.ts
mv: cannot rename '../REC/Dr House. _EcorchÃs vifs__20100511_2045.ts': Operation not permitted
I run out of ideas to test ^^ If you have any...
@Victor, thanks but not working :-/
I indeed used tab to complete the name, but also tried earlier with *
Here is the result:
mv ./Dr*.ts ./DrH.ts
mv: unable to rename `./Dr House. _EcorchÃs vifs__20100511_2045.ts': Operation not permitted
And I did not dare trying deleting the file want to get it to analyze it first :p
./busybox1.9.1 mv ../REC/Dr House. _EcorchÃs vifs__20100511_2045.ts ../REC/DR_HOUSE.ts
mv: cannot rename '../REC/Dr House. _EcorchÃs vifs__20100511_2045.ts': Operation not permitted
./busybox1.9.1 cp ../REC/Dr House. _EcorchÃs vifs__20100511_2045.ts ../REC/DR_HOUSE.ts
cp: cannot stat '../REC/Dr House. _EcorchÃs vifs__20100511_2045.ts': Value too large for defined data type
./busybox1.9.1 mv "../REC/Dr House. _EcorchÃs vifs__20100511_2045.ts" ../REC/DR_HOUSE.ts
mv: cannot rename '../REC/Dr House. _EcorchÃs vifs__20100511_2045.ts': Operation not permitted
I run out of ideas to test ^^ If you have any...
@Victor, thanks but not working :-/
I indeed used tab to complete the name, but also tried earlier with *
Here is the result:
mv ./Dr*.ts ./DrH.ts
mv: unable to rename `./Dr House. _EcorchÃs vifs__20100511_2045.ts': Operation not permitted
And I did not dare trying deleting the file want to get it to analyze it first :p
matthelas- Mensajes : 145
Fecha de inscripción : 08/02/2010
Re: Renaming issues ...
Hmmm
No, I can not even detele it ^^
No, I can not even detele it ^^
matthelas- Mensajes : 145
Fecha de inscripción : 08/02/2010
Re: Renaming issues ...
Now you have plenty of time to analize
Interesting...
I think this issue can happen to anyone, and you will have a nice file there for ever.
Let me test later at home a : fsck to see if it is installed in the system.
Interesting...
I think this issue can happen to anyone, and you will have a nice file there for ever.
Let me test later at home a : fsck to see if it is installed in the system.
vic1972- Mensajes : 2260
Fecha de inscripción : 09/12/2009
Edad : 52
Localización : Malaga
Re: Renaming issues ...
Lol, indeed!!
I am wondering whether I had a journal issue, or something similar. But I don't know how to force a check with the usfd type of the partition.
fsck is in the system:
/tmp/hdd/volumes/HDD1 # fsck
fsck 1.38 (30-Jun-2005)
But no help, gonna look for this command on Internet
Ok, should I try:
fsck /tmp/hdd/volumes/HDD1
I am wondering whether I had a journal issue, or something similar. But I don't know how to force a check with the usfd type of the partition.
fsck is in the system:
/tmp/hdd/volumes/HDD1 # fsck
fsck 1.38 (30-Jun-2005)
But no help, gonna look for this command on Internet
Ok, should I try:
fsck /tmp/hdd/volumes/HDD1
matthelas- Mensajes : 145
Fecha de inscripción : 08/02/2010
Re: Renaming issues ...
!!!!! Attention!!!
do not fun the fsck command will the disk is mounted!!! you can loose all your Dr. House's chapters and all
Let me test this later at home with the test unit.
also interesting will be if exist the command e2fsck.
do not fun the fsck command will the disk is mounted!!! you can loose all your Dr. House's chapters and all
Let me test this later at home with the test unit.
also interesting will be if exist the command e2fsck.
vic1972- Mensajes : 2260
Fecha de inscripción : 09/12/2009
Edad : 52
Localización : Malaga
Re: Renaming issues ...
Ok, I'll wait then
Yep, the command exists:
e2fsck -h
e2fsck: illegal option -- h
BusyBox v1.1.3 (2009.11.18-08:46+0000) multi-call binary
Usage: e2fsck [-panyrcdfvstDFSV] [-b superblock] [-B blocksize] [-I inode_buffer_blocks] [-P process_inode_size] [-l|-L bad_blocks_file] [-C fd] [-j external_journal] [-E extended-options] device
Check a Linux ext2/ext3 file system.
Options:
-p Automatic repair (no questions)
-n Make no changes to the filesystem
-y Assume 'yes' to all questions
-c Check for bad blocks and add them to the badblock list
-f Force checking even if filesystem is marked clean
-v Be verbose
-b superblock Use alternative superblock
-B blocksize Force blocksize when looking for superblock
-j journal Set location of the external journal
-l file Add to badblocks list
-L file Set badblocks list
But as far as I know, the filesystem is not ext2/3, is it?
Yep, the command exists:
e2fsck -h
e2fsck: illegal option -- h
BusyBox v1.1.3 (2009.11.18-08:46+0000) multi-call binary
Usage: e2fsck [-panyrcdfvstDFSV] [-b superblock] [-B blocksize] [-I inode_buffer_blocks] [-P process_inode_size] [-l|-L bad_blocks_file] [-C fd] [-j external_journal] [-E extended-options] device
Check a Linux ext2/ext3 file system.
Options:
-p Automatic repair (no questions)
-n Make no changes to the filesystem
-y Assume 'yes' to all questions
-c Check for bad blocks and add them to the badblock list
-f Force checking even if filesystem is marked clean
-v Be verbose
-b superblock Use alternative superblock
-B blocksize Force blocksize when looking for superblock
-j journal Set location of the external journal
-l file Add to badblocks list
-L file Set badblocks list
But as far as I know, the filesystem is not ext2/3, is it?
matthelas- Mensajes : 145
Fecha de inscripción : 08/02/2010
Re: Renaming issues ...
OK,
do not have the solution yet,
but let me explain what i have found so far.
My mount command shows:
/ # mount
/dev/root on / type squashfs (ro)
none on /dev type devfs (rw)
none on /proc type proc (rw,nodiratime)
devpts on /dev/pts type devpts (rw)
none on /sys type sysfs (rw)
/dev/mtdblock/2 on /usr/local/etc type jffs2 (rw,noatime)
none on /tmp type ramfs (rw)
/dev/rd/0 on /mnt/rd type vfat (rw,nodiratime,fmask=0022,dmask=0022,codepage=cp437,iocharset=iso8859-1)
/dev/scsi/host1/bus0/target0/lun0/part1 on /tmp/hdd/volumes/HDD1 type ufsd (rw,nodiratime)
/dev/scsi/host1/bus0/target0/lun0/part3 on /tmp/hdd/livepause type udf (rw)
/dev/scsi/host1/bus0/target0/lun0/part4 on /tmp/hdd/root type ext3 (rw)
so, first, lets umount HDD1 with:
/ # umount /tmp/hdd/volumes/HDD1/
Now the mount command shows all, but HDD1:
/ # mount
/dev/root on / type squashfs (ro)
none on /dev type devfs (rw)
none on /proc type proc (rw,nodiratime)
devpts on /dev/pts type devpts (rw)
none on /sys type sysfs (rw)
/dev/mtdblock/2 on /usr/local/etc type jffs2 (rw,noatime)
none on /tmp type ramfs (rw)
/dev/rd/0 on /mnt/rd type vfat (rw,nodiratime,fmask=0022,dmask=0022,codepage=cp437,iocharset=iso8859-1)
/dev/scsi/host1/bus0/target0/lun0/part3 on /tmp/hdd/livepause type udf (rw)
/dev/scsi/host1/bus0/target0/lun0/part4 on /tmp/hdd/root type ext3 (rw)
Now I have tried several commands to check the filesysetm but no success yet:
/ # fsck /dev/scsi/host1/bus0/target0/lun0/part1
fsck 1.38 (30-Jun-2005)
fsck: fsck.ntfs: not found
/sbin # fsck.ext3 /dev/scsi/host1/bus0/target0/lun0/part1
e2fsck 1.38 (30-Jun-2005)
Couldn't find ext2 superblock, trying backup blocks...
fsck.ext3: while trying to open /dev/scsi/host1/bus0/target0/lun0/part1
/sbin # fsck.ext2 /dev/scsi/host1/bus0/target0/lun0/part1
e2fsck 1.38 (30-Jun-2005)
Couldn't find ext2 superblock, trying backup blocks...
fsck.ext2: while trying to open /dev/scsi/host1/bus0/target0/lun0/part1
We are near the solution
too tired now, ...
probably taking off the hard disck and checking from a PC ... ??
do not have the solution yet,
but let me explain what i have found so far.
My mount command shows:
/ # mount
/dev/root on / type squashfs (ro)
none on /dev type devfs (rw)
none on /proc type proc (rw,nodiratime)
devpts on /dev/pts type devpts (rw)
none on /sys type sysfs (rw)
/dev/mtdblock/2 on /usr/local/etc type jffs2 (rw,noatime)
none on /tmp type ramfs (rw)
/dev/rd/0 on /mnt/rd type vfat (rw,nodiratime,fmask=0022,dmask=0022,codepage=cp437,iocharset=iso8859-1)
/dev/scsi/host1/bus0/target0/lun0/part1 on /tmp/hdd/volumes/HDD1 type ufsd (rw,nodiratime)
/dev/scsi/host1/bus0/target0/lun0/part3 on /tmp/hdd/livepause type udf (rw)
/dev/scsi/host1/bus0/target0/lun0/part4 on /tmp/hdd/root type ext3 (rw)
so, first, lets umount HDD1 with:
/ # umount /tmp/hdd/volumes/HDD1/
Now the mount command shows all, but HDD1:
/ # mount
/dev/root on / type squashfs (ro)
none on /dev type devfs (rw)
none on /proc type proc (rw,nodiratime)
devpts on /dev/pts type devpts (rw)
none on /sys type sysfs (rw)
/dev/mtdblock/2 on /usr/local/etc type jffs2 (rw,noatime)
none on /tmp type ramfs (rw)
/dev/rd/0 on /mnt/rd type vfat (rw,nodiratime,fmask=0022,dmask=0022,codepage=cp437,iocharset=iso8859-1)
/dev/scsi/host1/bus0/target0/lun0/part3 on /tmp/hdd/livepause type udf (rw)
/dev/scsi/host1/bus0/target0/lun0/part4 on /tmp/hdd/root type ext3 (rw)
Now I have tried several commands to check the filesysetm but no success yet:
/ # fsck /dev/scsi/host1/bus0/target0/lun0/part1
fsck 1.38 (30-Jun-2005)
fsck: fsck.ntfs: not found
/sbin # fsck.ext3 /dev/scsi/host1/bus0/target0/lun0/part1
e2fsck 1.38 (30-Jun-2005)
Couldn't find ext2 superblock, trying backup blocks...
fsck.ext3: while trying to open /dev/scsi/host1/bus0/target0/lun0/part1
/sbin # fsck.ext2 /dev/scsi/host1/bus0/target0/lun0/part1
e2fsck 1.38 (30-Jun-2005)
Couldn't find ext2 superblock, trying backup blocks...
fsck.ext2: while trying to open /dev/scsi/host1/bus0/target0/lun0/part1
We are near the solution
too tired now, ...
probably taking off the hard disck and checking from a PC ... ??
vic1972- Mensajes : 2260
Fecha de inscripción : 09/12/2009
Edad : 52
Localización : Malaga
Re: Renaming issues ...
vic1972 escribió:
We are near the solution
too tired now, ...
probably taking off the hard disck and checking from a PC ... ??
Hi Victor,
Many thanks for your investigations!
The issue is that I have a MS450H and as far as I understood this partition is on the internal disk, so I should open the box to check it.
I'll do it as a last option (we are still using it for the time being ^^).
Cheers,
Matt
matthelas- Mensajes : 145
Fecha de inscripción : 08/02/2010
Re: Renaming issues ...
yes,
lets see if among everybody we are able to scan/fix a HD, because I am sure this is very usefull.
I will try later to scan in a mounted HDD1 in test unit, to see what happens.
lets see if among everybody we are able to scan/fix a HD, because I am sure this is very usefull.
I will try later to scan in a mounted HDD1 in test unit, to see what happens.
vic1972- Mensajes : 2260
Fecha de inscripción : 09/12/2009
Edad : 52
Localización : Malaga
Re: Renaming issues ...
still investigation,
see what do we have so far:
/ # mount
/dev/root on / type squashfs (ro)
none on /dev type devfs (rw)
none on /proc type proc (rw,nodiratime)
devpts on /dev/pts type devpts (rw)
none on /sys type sysfs (rw)
/dev/mtdblock/2 on /usr/local/etc type jffs2 (rw,noatime)
none on /tmp type ramfs (rw)
/dev/rd/0 on /mnt/rd type vfat (rw,nodiratime,fmask=0022,dmask=0022,codepage=cp437,iocharset=iso8859-1)
/dev/scsi/host1/bus0/target0/lun0/part1 on /tmp/hdd/volumes/HDD1 type ufsd (rw,nodiratime)
/dev/scsi/host1/bus0/target0/lun0/part3 on /tmp/hdd/livepause type udf (rw)
/dev/scsi/host1/bus0/target0/lun0/part4 on /tmp/hdd/root type ext3 (rw)
/ # fsck /dev/scsi/host1/bus0/target0/lun0/part1
fsck 1.38 (30-Jun-2005)
fsck: fsck.ntfs: not found
fsck: Error 2 while executing fsck.ntfs for /dev/scsi/host1/bus0/target0/lun0/part1
/ # fsck /tmp/hdd/volumes/HDD1/
fsck 1.38 (30-Jun-2005)
e2fsck 1.38 (30-Jun-2005)
fsck.ext2: while trying to open /tmp/hdd/volumes/HDD1/
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
fsck.ext2: Warning... fsck.ext2 for device /tmp/hdd/volumes/HDD1/ exited with signal 11.
/ # e2fsck /dev/scsi/host1/bus0/target0/lun0/part1
e2fsck 1.38 (30-Jun-2005)
/dev/scsi/host1/bus0/target0/lun0/part1 is mounted.
WARNING!!! Running e2fsck on a mounted filesystem may cause
SEVERE filesystem damage.
Do you really want to continue (y/n)? n
no
check aborted.
/ #
/ # umount /tmp/hdd/volumes/HDD1/
/ # e2fsck /dev/scsi/host1/bus0/target0/lun0/part1
e2fsck 1.38 (30-Jun-2005)
Couldn't find ext2 superblock, trying backup blocks...
e2fsck: while trying to open /dev/scsi/host1/bus0/target0/lun0/part1
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
e2fsck: Segmentation fault (core dumped)
/ #
So whentryging to check while mounted, it says wants to continy, very dangerous yes or no?
very scary
, but if i try having it unmounted it trhows out a segmentaion error.
strange
see what do we have so far:
/ # mount
/dev/root on / type squashfs (ro)
none on /dev type devfs (rw)
none on /proc type proc (rw,nodiratime)
devpts on /dev/pts type devpts (rw)
none on /sys type sysfs (rw)
/dev/mtdblock/2 on /usr/local/etc type jffs2 (rw,noatime)
none on /tmp type ramfs (rw)
/dev/rd/0 on /mnt/rd type vfat (rw,nodiratime,fmask=0022,dmask=0022,codepage=cp437,iocharset=iso8859-1)
/dev/scsi/host1/bus0/target0/lun0/part1 on /tmp/hdd/volumes/HDD1 type ufsd (rw,nodiratime)
/dev/scsi/host1/bus0/target0/lun0/part3 on /tmp/hdd/livepause type udf (rw)
/dev/scsi/host1/bus0/target0/lun0/part4 on /tmp/hdd/root type ext3 (rw)
/ # fsck /dev/scsi/host1/bus0/target0/lun0/part1
fsck 1.38 (30-Jun-2005)
fsck: fsck.ntfs: not found
fsck: Error 2 while executing fsck.ntfs for /dev/scsi/host1/bus0/target0/lun0/part1
/ # fsck /tmp/hdd/volumes/HDD1/
fsck 1.38 (30-Jun-2005)
e2fsck 1.38 (30-Jun-2005)
fsck.ext2: while trying to open /tmp/hdd/volumes/HDD1/
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
fsck.ext2: Warning... fsck.ext2 for device /tmp/hdd/volumes/HDD1/ exited with signal 11.
/ # e2fsck /dev/scsi/host1/bus0/target0/lun0/part1
e2fsck 1.38 (30-Jun-2005)
/dev/scsi/host1/bus0/target0/lun0/part1 is mounted.
WARNING!!! Running e2fsck on a mounted filesystem may cause
SEVERE filesystem damage.
Do you really want to continue (y/n)? n
no
check aborted.
/ #
/ # umount /tmp/hdd/volumes/HDD1/
/ # e2fsck /dev/scsi/host1/bus0/target0/lun0/part1
e2fsck 1.38 (30-Jun-2005)
Couldn't find ext2 superblock, trying backup blocks...
e2fsck: while trying to open /dev/scsi/host1/bus0/target0/lun0/part1
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
e2fsck: Segmentation fault (core dumped)
/ #
So whentryging to check while mounted, it says wants to continy, very dangerous yes or no?
very scary
, but if i try having it unmounted it trhows out a segmentaion error.
strange
vic1972- Mensajes : 2260
Fecha de inscripción : 09/12/2009
Edad : 52
Localización : Malaga
Re: Renaming issues ...
if i say yes, same error
/ # e2fsck /dev/scsi/host1/bus0/target0/lun0/part1
e2fsck 1.38 (30-Jun-2005)
/dev/scsi/host1/bus0/target0/lun0/part1 is mounted.
WARNING!!! Running e2fsck on a mounted filesystem may cause
SEVERE filesystem damage.
Do you really want to continue (y/n)? y
yes
Couldn't find ext2 superblock, trying backup blocks...
e2fsck: while trying to open /dev/scsi/host1/bus0/target0/lun0/part1
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
e2fsck: Segmentation fault (core dumped)
/ #
So, it seems HDD1 is not ext2, I think some where is specifiy the type of format, i do not remember now. NTFS ????
/ # e2fsck /dev/scsi/host1/bus0/target0/lun0/part1
e2fsck 1.38 (30-Jun-2005)
/dev/scsi/host1/bus0/target0/lun0/part1 is mounted.
WARNING!!! Running e2fsck on a mounted filesystem may cause
SEVERE filesystem damage.
Do you really want to continue (y/n)? y
yes
Couldn't find ext2 superblock, trying backup blocks...
e2fsck: while trying to open /dev/scsi/host1/bus0/target0/lun0/part1
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
e2fsck: Segmentation fault (core dumped)
/ #
So, it seems HDD1 is not ext2, I think some where is specifiy the type of format, i do not remember now. NTFS ????
vic1972- Mensajes : 2260
Fecha de inscripción : 09/12/2009
Edad : 52
Localización : Malaga
Re: Renaming issues ...
vic1972 escribió:
So, it seems HDD1 is not ext2, I think some where is specifiy the type of format, i do not remember now. NTFS ????
It seems so, UFSD would then be related to the Paragon UFSD NTFS (Universal File System Driver, rather than Unix File System D???).
I also checked by connecting an NTFS formatted USB key on the MS450H:
~ # mount
/dev/root on / type squashfs (ro)
none on /dev type devfs (rw)
none on /proc type proc (rw,nodiratime)
devpts on /dev/pts type devpts (rw)
none on /sys type sysfs (rw)
/dev/mtdblock/2 on /usr/local/etc type jffs2 (rw,noatime)
none on /tmp type ramfs (rw)
/dev/rd/0 on /mnt/rd type vfat (rw,nodiratime,fmask=0022,dmask=0022,codepage=cp437,iocharset=iso8859-1)
/dev/scsi/host1/bus0/target0/lun0/part1 on /tmp/usbmounts/sdb1 type ufsd (ro,nodiratime)
/dev/scsi/host0/bus0/target0/lun0/part1 on /tmp/hdd/volumes/HDD1 type ufsd (rw,nodiratime)
/dev/scsi/host0/bus0/target0/lun0/part3 on /tmp/hdd/livepause type udf (rw)
/dev/scsi/host0/bus0/target0/lun0/part4 on /tmp/hdd/root type ext3 (rw)
/dev/scsi/host2/bus0/target0/lun0/part1 on /tmp/usbmounts/sdc1 type ufsd (ro,nodiratime)
So, I am now searching on the Internet how to check/repair the NTFS filesystem under linux xD
fsck.ntfs <= does not exist on the LG
but ntfsfix does:
ntfsfix -h
ntfsfix v1.13.1 (libntfs 9:0:0)
Usage: ntfsfix [options] device
Attempt to fix an NTFS partition.
-h, --help Display this help
-V, --version Display version information
For example: ntfsfix /dev/hda6
Developers' email address: linux-ntfs-dev@lists.sf.net
Linux NTFS homepage: http://www.linux-ntfs.org
I'll look for the man pages...
Cheers,
Matt
matthelas- Mensajes : 145
Fecha de inscripción : 08/02/2010
Re: Renaming issues ...
I first try on my USB key
Umounting it (tried without at first and some failures plus terrible messages as expected ):
umount /tmp/usbmounts/sdc1
Then "fixing":
ntfsfix /dev/scsi/host2/bus0/target0/lun0/part1
Log:
Mounting volume... OK
Processing of $MFT and $MFTMirr completed successfully.
NTFS volume version is 3.1.
Setting required flags on partition... OK
Going to empty the journal ($LogFile)... OK
NTFS partition /dev/scsi/host2/bus0/target0/lun0/part1 was processed successfully.
Do you think I should try on my HDD1 partition?
ntfsfix doc pages:
FR: http://doc.ubuntu-fr.org/ntfsfix
EN: http://man.linux-ntfs.org/ntfsfix.8.html
I am afraid this is not a very powerful tool ...
Umounting it (tried without at first and some failures plus terrible messages as expected ):
umount /tmp/usbmounts/sdc1
Then "fixing":
ntfsfix /dev/scsi/host2/bus0/target0/lun0/part1
Log:
Mounting volume... OK
Processing of $MFT and $MFTMirr completed successfully.
NTFS volume version is 3.1.
Setting required flags on partition... OK
Going to empty the journal ($LogFile)... OK
NTFS partition /dev/scsi/host2/bus0/target0/lun0/part1 was processed successfully.
Do you think I should try on my HDD1 partition?
ntfsfix doc pages:
FR: http://doc.ubuntu-fr.org/ntfsfix
EN: http://man.linux-ntfs.org/ntfsfix.8.html
I am afraid this is not a very powerful tool ...
matthelas- Mensajes : 145
Fecha de inscripción : 08/02/2010
Re: Renaming issues ...
Hello,
very interesting.
I have done to my HDD1, of course unmounted, anyway I also tried mounted
See the trace below:
/ # umount /tmp/hdd/volumes/HDD1
/ # ntfsfix /tmp/hdd/volumes/HDD1
Mounting volume... Error opening partition device : Is a directory
Failed to startup volume : Is a directory
FAILED
Attempting to correct errors... Error opening partition device : Is a directory
FAILED
Failed to startup volume : Is a directory
Volume is corrupt. You should run chkdsk.
/ # chkdsk
-sh: chkdsk: not found
/ # ntfsfix /dev/scsi/host1/bus0/target0/lun0/part1
Mounting volume... OK
Processing of $MFT and $MFTMirr completed successfully.
NTFS volume version is 3.1.
Setting required flags on partition... OK
Going to empty the journal ($LogFile)... OK
NTFS partition /dev/scsi/host1/bus0/target0/lun0/part1 was processed successfully.
So, ntfsfix seems to be working
After, that i have rebooted, and media in HDD1 if fine, as i have been able to reproduce.
very interesting.
I have done to my HDD1, of course unmounted, anyway I also tried mounted
See the trace below:
/ # umount /tmp/hdd/volumes/HDD1
/ # ntfsfix /tmp/hdd/volumes/HDD1
Mounting volume... Error opening partition device : Is a directory
Failed to startup volume : Is a directory
FAILED
Attempting to correct errors... Error opening partition device : Is a directory
FAILED
Failed to startup volume : Is a directory
Volume is corrupt. You should run chkdsk.
/ # chkdsk
-sh: chkdsk: not found
/ # ntfsfix /dev/scsi/host1/bus0/target0/lun0/part1
Mounting volume... OK
Processing of $MFT and $MFTMirr completed successfully.
NTFS volume version is 3.1.
Setting required flags on partition... OK
Going to empty the journal ($LogFile)... OK
NTFS partition /dev/scsi/host1/bus0/target0/lun0/part1 was processed successfully.
So, ntfsfix seems to be working
After, that i have rebooted, and media in HDD1 if fine, as i have been able to reproduce.
vic1972- Mensajes : 2260
Fecha de inscripción : 09/12/2009
Edad : 52
Localización : Malaga
Re: Renaming issues ...
Thanks ^^
I just tried:
~ # umount /tmp/hdd/volumes/HDD1
~ # ntfsfix /dev/scsi/host0/bus0/target0/lun0/part1
Mounting volume... OK
Processing of $MFT and $MFTMirr completed successfully.
NTFS volume version is 3.1.
Setting required flags on partition... OK
Going to empty the journal ($LogFile)... OK
NTFS partition /dev/scsi/host0/bus0/target0/lun0/part1 was processed successfully.
~ # reboot
Then loging again:
/tmp/hdd/volumes/HDD1/REC # ls
BIENVENUE CHEZ LES ROZES_20100110_2035.ts
C'est ma terre_20100512_2035.ts
Dr House. _EcorchÃs vifs__20100511_2045.ts
MÃtÃo_20100511_2042.ts
/tmp/hdd/volumes/HDD1/REC # mv Dr\ House.\ _EcorchÃs\ vifs__20100511_2045.ts DH.ts
mv: unable to rename `Dr House. _EcorchÃs vifs__20100511_2045.ts': Operation not permitted
/tmp/hdd/volumes/HDD1/REC #
I just tried:
~ # umount /tmp/hdd/volumes/HDD1
~ # ntfsfix /dev/scsi/host0/bus0/target0/lun0/part1
Mounting volume... OK
Processing of $MFT and $MFTMirr completed successfully.
NTFS volume version is 3.1.
Setting required flags on partition... OK
Going to empty the journal ($LogFile)... OK
NTFS partition /dev/scsi/host0/bus0/target0/lun0/part1 was processed successfully.
~ # reboot
Then loging again:
/tmp/hdd/volumes/HDD1/REC # ls
BIENVENUE CHEZ LES ROZES_20100110_2035.ts
C'est ma terre_20100512_2035.ts
Dr House. _EcorchÃs vifs__20100511_2045.ts
MÃtÃo_20100511_2042.ts
/tmp/hdd/volumes/HDD1/REC # mv Dr\ House.\ _EcorchÃs\ vifs__20100511_2045.ts DH.ts
mv: unable to rename `Dr House. _EcorchÃs vifs__20100511_2045.ts': Operation not permitted
/tmp/hdd/volumes/HDD1/REC #
matthelas- Mensajes : 145
Fecha de inscripción : 08/02/2010
Re: Renaming issues ...
so, it seems is doing something, but it seems no effect ....
strange, well, out of ideas for the moment.
strange, well, out of ideas for the moment.
vic1972- Mensajes : 2260
Fecha de inscripción : 09/12/2009
Edad : 52
Localización : Malaga
Re: Renaming issues ...
I tried to read a bit Parangon stuff:
http://download.paragon-software.com/doc/manual_ntfsl_eng.pdf
I then tried to umount / remount partition with different codepage, iocharset, etc. to try to have names with no weird characters (in case) but it seems I do not mount things correctly, since I can umount a ufsd/ntfs partition, but I am not able to remount it, despite using mount -t ufsd /dev/... /tmp/... (with ... replaced by the right paths )
Wondering about moving the working movies from the folder to the other HDD and to reset it via the LG "installation" menus
Cheers,
Matt
http://download.paragon-software.com/doc/manual_ntfsl_eng.pdf
I then tried to umount / remount partition with different codepage, iocharset, etc. to try to have names with no weird characters (in case) but it seems I do not mount things correctly, since I can umount a ufsd/ntfs partition, but I am not able to remount it, despite using mount -t ufsd /dev/... /tmp/... (with ... replaced by the right paths )
Wondering about moving the working movies from the folder to the other HDD and to reset it via the LG "installation" menus
Cheers,
Matt
matthelas- Mensajes : 145
Fecha de inscripción : 08/02/2010
Re: Renaming issues ...
Hello,
yes, that is of course the best solution, at this moment ....
It will be nice to be able to "fix" the hard disk errors, we will have to keep investigations.
Yes, move the staff to the other hard disk, then extrack it from lg (just to be sure which is the disk you are formating), then format, and then
copy back the movies ...
I understand this would take a lot of time the copy process, probably best if you leave it in the night in the copy process.
See you
Victor
yes, that is of course the best solution, at this moment ....
It will be nice to be able to "fix" the hard disk errors, we will have to keep investigations.
Yes, move the staff to the other hard disk, then extrack it from lg (just to be sure which is the disk you are formating), then format, and then
copy back the movies ...
I understand this would take a lot of time the copy process, probably best if you leave it in the night in the copy process.
See you
Victor
vic1972- Mensajes : 2260
Fecha de inscripción : 09/12/2009
Edad : 52
Localización : Malaga
Re: Renaming issues ...
Hi,
What I did is the following: I moved the files not corrupted (by that time, only one remained uncorrupted, the three others were not movable ...) and lauched two "initialisation" via the LG menu on my internal hard disk.
Will monitor whether I have the issue again or not, and if yes will extract the HDD and plug it to a pc...
Weird.
Cheers,
Matt
What I did is the following: I moved the files not corrupted (by that time, only one remained uncorrupted, the three others were not movable ...) and lauched two "initialisation" via the LG menu on my internal hard disk.
Will monitor whether I have the issue again or not, and if yes will extract the HDD and plug it to a pc...
Weird.
Cheers,
Matt
matthelas- Mensajes : 145
Fecha de inscripción : 08/02/2010
Re: Renaming issues ...
Imdeed, I have just unxuccessfully triedmatthelas escribió:I tried to read a bit Parangon stuff:
http://download.paragon-software.com/doc/manual_ntfsl_eng.pdf
I then tried to umount / remount partition with different codepage, iocharset, etc. to try to have names with no weird characters (in case) but it seems I do not mount things correctly, since I can umount a ufsd/ntfs partition, but I am not able to remount it, despite using mount -t ufsd /dev/... /tmp/... (with ... replaced by the right paths :) ) [...]
- Código:
umount /tmp/hdd/volumes/HDD1/
mount /dev/sda1 /tmp/hdd/volumes/HDD1/ -t ufsd
Thanks,
evr- Mensajes : 279
Fecha de inscripción : 12/10/2010
Re: Renaming issues ...
evr escribió:
Has Anybody found how to mount the ntfs partition (/dev/sda1 on /tmp/hdd/volumes/HDD1/) ??
Hi!
Not me, unfortunately :-/
Cheers,
Matt
matthelas- Mensajes : 145
Fecha de inscripción : 08/02/2010
Re: Renaming issues ...
I reply to myself: The missing option to mount was "-o force". This is the minimal expression:evr escribió:Has Anybody found how to mount the ntfs partition (/dev/sda1 on /tmp/hdd/volumes/HDD1/) ??
- Código:
mount -t ufsd -o force /dev/sda1 /tmp/hdd/volumes/HDD1
- Código:
mount -t ufsd -o force -o rw -o sparse -o nls=utf8 -o umask=0000 /dev/sda1 /tmp/hdd/volumes/HDD1
evr- Mensajes : 279
Fecha de inscripción : 12/10/2010
Página 1 de 1.
Permisos de este foro:
No puedes responder a temas en este foro.