Poster une réponse à un sujet: Synology diskstation: rootfs full but 2Go missing !
Attention, ce sujet est un sujet ancien (5091 jours sans réponse)
jeezho
Pour info, le problème est revenu et j'ai finalement trouvé d'où ça venait.
A chaque arrêt de la machine, un fichier core (voire plusieurs) allait se mettre dans le dossier /volume1, au moment où celui-ci est démonté.
Les fichiers core proviennent de rails_cluster qui, je l'imagine, n'est pas arrêté correctement (i.e. pas du tout) lors de l'extinction de la machine, ce qui provoquerait les fichiers core.
Je ne suis pas vraiment allé plus loin dans l'investigation du problème, vu que l'analyse m'oblige à arrêter tous les services et démonter le dossier /volume1.
A chaque arrêt de la machine, un fichier core (voire plusieurs) allait se mettre dans le dossier /volume1, au moment où celui-ci est démonté.
Les fichiers core proviennent de rails_cluster qui, je l'imagine, n'est pas arrêté correctement (i.e. pas du tout) lors de l'extinction de la machine, ce qui provoquerait les fichiers core.
Je ne suis pas vraiment allé plus loin dans l'investigation du problème, vu que l'analyse m'oblige à arrêter tous les services et démonter le dossier /volume1.
jeezho
Bon, bin, voilà, réinstallation du firmware avec formatage de la partition root (le truc du double reset).
Par contre, je n'arrive pas à récupérer ipkg. Impossible d'accéder à l'url.
Est-ce que vous y arrivez ?
http://ipkg.nslu2-linux.org/feeds/optware/syno-e500/cross/unstable/syno-e500-bootstrap_1.2-7_powerpc.xsh
ou son mirroir ?
http://nslu2-linux.dyoung-mirror.net/feeds/optware/
Par contre, je n'arrive pas à récupérer ipkg. Impossible d'accéder à l'url.
Est-ce que vous y arrivez ?
http://ipkg.nslu2-linux.org/feeds/optware/syno-e500/cross/unstable/syno-e500-bootstrap_1.2-7_powerpc.xsh
ou son mirroir ?
http://nslu2-linux.dyoung-mirror.net/feeds/optware/
jeezho
Mouais, je m'informe encore sur les moyens de résoudre ça et j'arrive de plus en plus à la conclusion qu'à part réinitialiser le système...
Apparemment, la réparation du système root n'a jamais été faite par quiconque
Apparemment, la réparation du système root n'a jamais été faite par quiconque
![:ohwell: :ohwell:](images/smileys/ohwell.gif)
jeezho
DiskStation> mount -o remount,ro /
mount: Mounting /dev/root on / failed: Device or resource busy
Snif
mount: Mounting /dev/root on / failed: Device or resource busy
Snif
![:pleurer: :pleurer:](images/smileys/pleurer.gif)
philfr
Pour remonter read only:
mount -o remount,ro /
puis laisse faire fsck
mount -o remount,ro /
puis laisse faire fsck
jeezho
1 large file > ce serait peut-être ce fichier-là que je cherche ? (s'il est foireux...)
jeezho
Je sais pas si c'est vraiment correct mais j'ai ceci :
(Disque toujours monté normalement...)
Apparemment, /dev/md0 serait la première partition qui est utilisée pour /dev/root alias rootfs.
DiskStation> e2fsck -v -n -f /dev/md0
e2fsck 1.40.3 (05-Dec-2007)
Warning! /dev/md0 is mounted.
Warning: skipping journal recovery because doing a read-only filesystem check.
Pass 1: Checking inodes, blocks, and sizes
Inode 68223 has INDEX_FL flag set on filesystem without htree support.
Clear HTree index? no
Inode 70302 has INDEX_FL flag set on filesystem without htree support.
Clear HTree index? no
Inode 114689 has INDEX_FL flag set on filesystem without htree support.
Clear HTree index? no
Inode 229377 has INDEX_FL flag set on filesystem without htree support.
Clear HTree index? no
Inode 230483 has INDEX_FL flag set on filesystem without htree support.
Clear HTree index? no
Deleted inode 278786 has zero dtime. Fix? no
Pass 2: Checking directory structure
Problem in HTREE directory inode 68223: node (1) has bad max hash
Problem in HTREE directory inode 68223: node (2) has bad min hash
Invalid HTREE directory inode 68223 (/usr/syno/synoman/webman/images). Clear? n o
Problem in HTREE directory inode 70302: node (1) has bad max hash
Problem in HTREE directory inode 70302: node (2) has bad min hash
Invalid HTREE directory inode 70302 (/usr/syno/synoman/surveillance/images). Cl ear? no
Problem in HTREE directory inode 114689: node (1) has bad max hash
Problem in HTREE directory inode 114689: node (2) has bad min hash
Problem in HTREE directory inode 114689: node (2) has bad max hash
Problem in HTREE directory inode 114689: node (3) has bad min hash
Problem in HTREE directory inode 114689: node (3) has bad max hash
Problem in HTREE directory inode 114689: node (4) has bad min hash
Problem in HTREE directory inode 114689: node (4) has bad max hash
Problem in HTREE directory inode 114689: node (5) has bad min hash
Problem in HTREE directory inode 114689: node (5) has bad max hash
Problem in HTREE directory inode 114689: node (6) has bad min hash
Problem in HTREE directory inode 114689: node (6) has bad max hash
Problem in HTREE directory inode 114689: node (7) has bad min hash
Problem in HTREE directory inode 114689: node (7) has bad max hash
Problem in HTREE directory inode 114689: node (8) has bad min hash
Invalid HTREE directory inode 114689 (/dev). Clear? no
Problem in HTREE directory inode 229377: node (1) has bad max hash
Problem in HTREE directory inode 229377: node (2) has bad min hash
Invalid HTREE directory inode 229377 (/lib). Clear? no
Problem in HTREE directory inode 230483: node (1) has bad max hash
Problem in HTREE directory inode 230483: node (2) has bad min hash
Invalid HTREE directory inode 230483 (/lib/perl5/5.8.6/unicore/lib/gc_sc). Clea r? no
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Block bitmap differences: -(587505--587506) -(607544--607552) -(607554--607590) -(607609--607882) -(607884--608008)
Fix? no
Inode bitmap differences: -278786
Fix? no
1.39-Dec272008: ********** WARNING: Filesystem still has errors **********
16278 inodes used (5.23%)
433 non-contiguous inodes (2.7%)
# of inodes with ind/dind/tind blocks: 1111/55/0
616634 blocks used (99.06%)
0 bad blocks
1 large file
12977 regular files
1514 directories
59 character device files
1321 block device files
0 fifos
4 links
395 symbolic links (395 fast symbolic links)
2 sockets
--------
16272 files
(Disque toujours monté normalement...)
Apparemment, /dev/md0 serait la première partition qui est utilisée pour /dev/root alias rootfs.
DiskStation> e2fsck -v -n -f /dev/md0
e2fsck 1.40.3 (05-Dec-2007)
Warning! /dev/md0 is mounted.
Warning: skipping journal recovery because doing a read-only filesystem check.
Pass 1: Checking inodes, blocks, and sizes
Inode 68223 has INDEX_FL flag set on filesystem without htree support.
Clear HTree index? no
Inode 70302 has INDEX_FL flag set on filesystem without htree support.
Clear HTree index? no
Inode 114689 has INDEX_FL flag set on filesystem without htree support.
Clear HTree index? no
Inode 229377 has INDEX_FL flag set on filesystem without htree support.
Clear HTree index? no
Inode 230483 has INDEX_FL flag set on filesystem without htree support.
Clear HTree index? no
Deleted inode 278786 has zero dtime. Fix? no
Pass 2: Checking directory structure
Problem in HTREE directory inode 68223: node (1) has bad max hash
Problem in HTREE directory inode 68223: node (2) has bad min hash
Invalid HTREE directory inode 68223 (/usr/syno/synoman/webman/images). Clear? n o
Problem in HTREE directory inode 70302: node (1) has bad max hash
Problem in HTREE directory inode 70302: node (2) has bad min hash
Invalid HTREE directory inode 70302 (/usr/syno/synoman/surveillance/images). Cl ear? no
Problem in HTREE directory inode 114689: node (1) has bad max hash
Problem in HTREE directory inode 114689: node (2) has bad min hash
Problem in HTREE directory inode 114689: node (2) has bad max hash
Problem in HTREE directory inode 114689: node (3) has bad min hash
Problem in HTREE directory inode 114689: node (3) has bad max hash
Problem in HTREE directory inode 114689: node (4) has bad min hash
Problem in HTREE directory inode 114689: node (4) has bad max hash
Problem in HTREE directory inode 114689: node (5) has bad min hash
Problem in HTREE directory inode 114689: node (5) has bad max hash
Problem in HTREE directory inode 114689: node (6) has bad min hash
Problem in HTREE directory inode 114689: node (6) has bad max hash
Problem in HTREE directory inode 114689: node (7) has bad min hash
Problem in HTREE directory inode 114689: node (7) has bad max hash
Problem in HTREE directory inode 114689: node (8) has bad min hash
Invalid HTREE directory inode 114689 (/dev). Clear? no
Problem in HTREE directory inode 229377: node (1) has bad max hash
Problem in HTREE directory inode 229377: node (2) has bad min hash
Invalid HTREE directory inode 229377 (/lib). Clear? no
Problem in HTREE directory inode 230483: node (1) has bad max hash
Problem in HTREE directory inode 230483: node (2) has bad min hash
Invalid HTREE directory inode 230483 (/lib/perl5/5.8.6/unicore/lib/gc_sc). Clea r? no
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Block bitmap differences: -(587505--587506) -(607544--607552) -(607554--607590) -(607609--607882) -(607884--608008)
Fix? no
Inode bitmap differences: -278786
Fix? no
1.39-Dec272008: ********** WARNING: Filesystem still has errors **********
16278 inodes used (5.23%)
433 non-contiguous inodes (2.7%)
# of inodes with ind/dind/tind blocks: 1111/55/0
616634 blocks used (99.06%)
0 bad blocks
1 large file
12977 regular files
1514 directories
59 character device files
1321 block device files
0 fifos
4 links
395 symbolic links (395 fast symbolic links)
2 sockets
--------
16272 files
jeezho
Je peux installer des packages via ipkg.
Pour e2fsck, j'ai pourtant pris la version ext3. Ils m'auraient menti en mettant le .ext3 derrière fsck ?
Par contre, aucune idée de comment remonter le rootfs en readonly.
(Oui, je sais faire des choses sous linux mais pas trop l'habitude de jouer avec les partitions)
Pour e2fsck, j'ai pourtant pris la version ext3. Ils m'auraient menti en mettant le .ext3 derrière fsck ?
![:alarmclock117: :alarmclock117:](images/smileys/alarmclock117.gif)
Par contre, aucune idée de comment remonter le rootfs en readonly.
(Oui, je sais faire des choses sous linux mais pas trop l'habitude de jouer avec les partitions)
philfr
WARNING!!! Running e2fsck on a mounted filesystem may cause
SEVERE filesystem damage.
Il faut remonter ton device en read-only avant de faire un fsck...
![:wink: :wink:](images/smileys/wink.gif)
Mais ici ton problème est que la partition est ext3 et que tu n'as pas le fsck correspondant (seulement celui pour ext2). C'est une distro standard de ton NAS ? Tu sais y ajouter des packages ?
jeezho
Oui, pareil au redémarrage (qui se fait tous les matins)
DiskStation> fsck.ext3 /dev/root
e2fsck 1.40.3 (05-Dec-2007)
/dev/root is mounted.
WARNING!!! Running e2fsck on a mounted filesystem may cause
SEVERE filesystem damage.
Do you really want to continue (y/n)? yes
fsck.ext3: No such file or directory while trying to open /dev/root
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>
J'ai essayé au lieu de /dev/root : / et rootfs => même chose.
Et bizarrement, /dev/root n'existe pas...
DiskStation> fsck.ext3 /dev/root
e2fsck 1.40.3 (05-Dec-2007)
/dev/root is mounted.
WARNING!!! Running e2fsck on a mounted filesystem may cause
SEVERE filesystem damage.
Do you really want to continue (y/n)? yes
fsck.ext3: No such file or directory while trying to open /dev/root
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>
J'ai essayé au lieu de /dev/root : / et rootfs => même chose.
Et bizarrement, /dev/root n'existe pas...