subject:"fdisk"

Le lun. 17 déc. 2018 à 17:26, steve  a écrit :
>
> Le 17-12-2018, à 17:16:35 +0100, ajh-valmer a écrit :
>
> >> Le 17-12-2018, à 15:01:42 +0100, A. Valmer a écrit :
> >> >  C'est ce que j'ai fait sur un serveur avec un seul disque dur.
> >> >UUID et /dev/disk/by-label/my_data_part,
> >> > Lorsque je fais un reboot, une fois sur deux il devient /dev/sdc
> >> > et l'autre fois, /dev/sda.
> >
> >On Monday 17 December 2018 15:47:45 steve wrote:
> >> Difficile de croire que ça soit possible vu qu'il n'y a qu'un seul
> >> disque. Et même si c'était bien le cas, ce ne serait pas grave vu que
> >> tu as utilisé le UUID et que le nom (aléatoire) du disque n'est pas
> >> utilisé pour monter la partition.
> >
> >Si, c'est la réalité.
> >
> >/dev/disk# ls -l by-label/
> >lrwxrwxrwx 1 root root 10 déc.  15 00:45 sda1 -> ../../sda1
> >lrwxrwxrwx 1 root root 10 déc.  15 00:45 sda2 -> ../../sda2
> >lrwxrwxrwx 1 root root 10 déc.  15 00:45 sda5 -> ../../sda5
> >lrwxrwxrwx 1 root root 10 déc.  15 00:45 sda6 -> ../../sda6
> >lrwxrwxrwx 1 root root 10 déc.  15 00:45 sda7 -> ../../sda7
> >lrwxrwxrwx 1 root root 10 déc.  15 00:45 swap -> ../../sda3
> >
> >Ici, impeccable et au prochain reboot, j'aurai ces lignes,
> >mais, avec ../../sdc.
>
> Si c'est vraiment le cas, je serais vraiment intéressé d'en connaître la
> raison. Et pourquoi sdc et pas sdb ou sdk par exemple ?
>
> >D'accord, l'UUID ne change pas, donc pas bien grave,
> >ça n'empêche pas le système de bien fonctionner,
> >mais je préférerais que le DD = /dev/sda et s'y tienne.
>
> Pas sûr que ça soit possible, mais clairement non recommendable.
> Peut-être qu'avec une règle udev tu pourrais y parvenir. J'ai
> personnellement laissé tomber après avoir lu et relu que c'était perdu
> d'avance (by design).
>
> >Bonne soirée.
>
> De même.
>
J'ai eu ce cas sur un desktop à cause d'un lecteur de carte devenu capricieux :
=> s'il marchait bien, il enfonçait les HDD en termes de temps
d'initialisation, donc les 4 devices correspondant aux lecteurs de
carte étaient énumérés /dev/sda ... /dev/sdd, et les HDD /dev/sde et
/dev/sdf
=> s'il "ratait" au démarrage, les HDD se retrouvaient premiers
énumérés et donc reconnus comme /dev/sda et /dev/sdb
Les clefs USB peuvent éventuellement avoir cet effet aussi...

Pour savoir pourquoi il suffit peut-être de lister les /dev/sd* et de
voir /dev/disk/by-label et /dev/disk/by-uuid pour voir qui "est
devant" ...

Quoi qu'il en soit, compter sur ces noms de device bruts n'a jamais
été vraiment fiable (sachant que le matériel ou le bios introduisent
dans certains cas de l'aléa dans les temps de réponse pour éviter les
collisions entre périphériques sur un bus...), et les distributions
ont donc cessé de compter dessus.

Cordialement
__
Éric Dégenètais
Henix

http://www.henix.com
http://www.squashtest.org

Re: souci imprimante usb (fdisk -l , hddtemp )

2018-12-17 Thread steve

Le 17-12-2018, à 17:16:35 +0100, ajh-valmer a écrit :

Le 17-12-2018, à 15:01:42 +0100, A. Valmer a écrit :
>  C'est ce que j'ai fait sur un serveur avec un seul disque dur.
>UUID et /dev/disk/by-label/my_data_part,
> Lorsque je fais un reboot, une fois sur deux il devient /dev/sdc
> et l'autre fois, /dev/sda.

On Monday 17 December 2018 15:47:45 steve wrote:

Difficile de croire que ça soit possible vu qu'il n'y a qu'un seul
disque. Et même si c'était bien le cas, ce ne serait pas grave vu que
tu as utilisé le UUID et que le nom (aléatoire) du disque n'est pas
utilisé pour monter la partition.

Si, c'est la réalité.

/dev/disk# ls -l by-label/
lrwxrwxrwx 1 root root 10 déc.  15 00:45 sda1 -> ../../sda1
lrwxrwxrwx 1 root root 10 déc.  15 00:45 sda2 -> ../../sda2
lrwxrwxrwx 1 root root 10 déc.  15 00:45 sda5 -> ../../sda5
lrwxrwxrwx 1 root root 10 déc.  15 00:45 sda6 -> ../../sda6
lrwxrwxrwx 1 root root 10 déc.  15 00:45 sda7 -> ../../sda7
lrwxrwxrwx 1 root root 10 déc.  15 00:45 swap -> ../../sda3

Ici, impeccable et au prochain reboot, j'aurai ces lignes,
mais, avec ../../sdc.

Si c'est vraiment le cas, je serais vraiment intéressé d'en connaître la
raison. Et pourquoi sdc et pas sdb ou sdk par exemple ?

D'accord, l'UUID ne change pas, donc pas bien grave,
ça n'empêche pas le système de bien fonctionner,
mais je préférerais que le DD = /dev/sda et s'y tienne.

Pas sûr que ça soit possible, mais clairement non recommendable.
Peut-être qu'avec une règle udev tu pourrais y parvenir. J'ai
personnellement laissé tomber après avoir lu et relu que c'était perdu
d'avance (by design).

Bonne soirée.

De même.

Re: souci imprimante usb (fdisk -l , hddtemp )

2018-12-17 Thread ajh-valmer

> Le 17-12-2018, à 15:01:42 +0100, A. Valmer a écrit :
> >  C'est ce que j'ai fait sur un serveur avec un seul disque dur.
> >UUID et /dev/disk/by-label/my_data_part,
> > Lorsque je fais un reboot, une fois sur deux il devient /dev/sdc
> > et l'autre fois, /dev/sda.

On Monday 17 December 2018 15:47:45 steve wrote:
> Difficile de croire que ça soit possible vu qu'il n'y a qu'un seul
> disque. Et même si c'était bien le cas, ce ne serait pas grave vu que
> tu as utilisé le UUID et que le nom (aléatoire) du disque n'est pas
> utilisé pour monter la partition.

Si, c'est la réalité.

/dev/disk# ls -l by-label/
lrwxrwxrwx 1 root root 10 déc.  15 00:45 sda1 -> ../../sda1
lrwxrwxrwx 1 root root 10 déc.  15 00:45 sda2 -> ../../sda2
lrwxrwxrwx 1 root root 10 déc.  15 00:45 sda5 -> ../../sda5
lrwxrwxrwx 1 root root 10 déc.  15 00:45 sda6 -> ../../sda6
lrwxrwxrwx 1 root root 10 déc.  15 00:45 sda7 -> ../../sda7
lrwxrwxrwx 1 root root 10 déc.  15 00:45 swap -> ../../sda3

Ici, impeccable et au prochain reboot, j'aurai ces lignes,
mais, avec ../../sdc.

D'accord, l'UUID ne change pas, donc pas bien grave,
ça n'empêche pas le système de bien fonctionner,
mais je préférerais que le DD = /dev/sda et s'y tienne.

C'est juste pour comprendre pourquoi ce changement ? :
sans doute la console KVM qui peut prendre le nommage 
/dev/sda lorsqu'elle est lancée. Je ferai un test pour voir.

Bonne soirée.

Re: souci imprimante usb (fdisk -l , hddtemp )

Le lun. 17 déc. 2018 à 15:48, steve  a écrit :

> Le 17-12-2018, à 15:01:42 +0100, infos SX a écrit :
>
> >On Monday 17 December 2018 14:47:03 Eric Degenetais wrote:
> >> > certains ne sont plus reconnus et d'autres décalés d'une lettre .
> >
> >> ça vient peut-être d'un certain manque de robustesse de la
> configuration :
> >> si je comprends bien la configuration utilise des device names du type
> >> /dev/sda1, dev/sda2, /dev/sdb ...
> >> Or ces lettres dépendent de l'ordre dans lequel les périphériques
> répondent
> >> lors de leur énumération, ordre dont la stabilité n'est pas (n'a jamais
> >> été) garantie.
> >> Il est aujourd'hui recommandé de référencer les périphériques
> >> - soit par l'UUID de la partition (ce que font normalement les
> >> installeurs, mais il faut le faire soi-même si c'est une migration)
> >> soit par un 'label' descriptif (/dev/disk/by-label/my_data_part) créé
> >> avec les outils de gestion de FS (un peu plus de travail, mais a
> >> l'avantage  d'être immédiatement lisible)
> >
> >C'est ce que j'ai fait sur un serveur avec un seul disque dur.
> >UUID et /dev/disk/by-label/my_data_part,
> >
> >Lorsque je fais un reboot, une fois sur deux il devient /dev/sdc
> >et l'autre fois, /dev/sda.
>
> Difficile de croire que ça soit possible vu qu'il n'y a qu'un seul
> disque. Et même si c'était bien le cas, ce ne serait pas grave vu que
> tu as utilisé le UUID et que le nom (aléatoire) du disque n'est pas
> utilisé pour monter la partition.
>
> >/dev/disk/by-label/my_data_part :
> >je n'ai pas ce fichier "my_data_part".
>
> Sauf erreur, il n'y a pas de fichier nommé ainsi. Ici par exemple, j'ai
>
> Coquille de ma part, j'avais l'intention d'écrire (EXEMPLE :
/dev/disk/by-label/my_data_part). L'outil d'installation peut créer des
labels, ou bien on peut les créer manuellement.
Il n'y a pas de contenu standard à /dev/disk/by-label à ma connaissance, ce
sont des étiquettes descriptives créées à la demande de l'utilisateur
(qu'on peut aussi ajouter a posteriori avec les outils de manipulation de
filesystem).

> lrwxrwxrwx 1 root root 10 déc 14 21:40 BOOT -> ../../sda1
>
> et
>
> lrwxrwxrwx 1 root root 10 déc 14 21:40
> 3148652c-4040-4348-9022-22250d497fcd -> ../../sda1
>
> où BOOT est le nom de l'étiquette de /dev/sda1 et
> 3148652c-4040-4348-9022-22250d497fcd son uuid.
>
>
> __
Éric Dégenètais
Henix

http://www.henix.com
http://www.squashtest.org

Re: souci imprimante usb (fdisk -l , hddtemp )

2018-12-17 Thread steve


Le 17-12-2018, à 15:01:42 +0100, infos SX a écrit :


On Monday 17 December 2018 14:47:03 Eric Degenetais wrote:

> certains ne sont plus reconnus et d'autres décalés d'une lettre .



ça vient peut-être d'un certain manque de robustesse de la configuration :
si je comprends bien la configuration utilise des device names du type
/dev/sda1, dev/sda2, /dev/sdb ...
Or ces lettres dépendent de l'ordre dans lequel les périphériques répondent
lors de leur énumération, ordre dont la stabilité n'est pas (n'a jamais
été) garantie.
Il est aujourd'hui recommandé de référencer les périphériques
- soit par l'UUID de la partition (ce que font normalement les
installeurs, mais il faut le faire soi-même si c'est une migration)
soit par un 'label' descriptif (/dev/disk/by-label/my_data_part) créé
avec les outils de gestion de FS (un peu plus de travail, mais a
l'avantage  d'être immédiatement lisible)


C'est ce que j'ai fait sur un serveur avec un seul disque dur.
UUID et /dev/disk/by-label/my_data_part,

Lorsque je fais un reboot, une fois sur deux il devient /dev/sdc
et l'autre fois, /dev/sda.


Difficile de croire que ça soit possible vu qu'il n'y a qu'un seul
disque. Et même si c'était bien le cas, ce ne serait pas grave vu que
tu as utilisé le UUID et que le nom (aléatoire) du disque n'est pas
utilisé pour monter la partition.


/dev/disk/by-label/my_data_part :
je n'ai pas ce fichier "my_data_part".


Sauf erreur, il n'y a pas de fichier nommé ainsi. Ici par exemple, j'ai

lrwxrwxrwx 1 root root 10 déc 14 21:40 BOOT -> ../../sda1

et

lrwxrwxrwx 1 root root 10 déc 14 21:40 3148652c-4040-4348-9022-22250d497fcd -> 
../../sda1

où BOOT est le nom de l'étiquette de /dev/sda1 et 
3148652c-4040-4348-9022-22250d497fcd son uuid.

Re: souci imprimante usb (fdisk -l , hddtemp )

Le lun. 17 déc. 2018 à 15:27, infos SX  a écrit :
>
> On Monday 17 December 2018 14:47:03 Eric Degenetais wrote:
> > > certains ne sont plus reconnus et d'autres décalés d'une lettre .
>
> > ça vient peut-être d'un certain manque de robustesse de la configuration :
> > si je comprends bien la configuration utilise des device names du type
> > /dev/sda1, dev/sda2, /dev/sdb ...
> > Or ces lettres dépendent de l'ordre dans lequel les périphériques répondent
> > lors de leur énumération, ordre dont la stabilité n'est pas (n'a jamais
> > été) garantie.
> > Il est aujourd'hui recommandé de référencer les périphériques
> > - soit par l'UUID de la partition (ce que font normalement les
> > installeurs, mais il faut le faire soi-même si c'est une migration)
> > soit par un 'label' descriptif (/dev/disk/by-label/my_data_part) créé
> > avec les outils de gestion de FS (un peu plus de travail, mais a
> > l'avantage  d'être immédiatement lisible)
>
> C'est ce que j'ai fait sur un serveur avec un seul disque dur.
> UUID et /dev/disk/by-label/my_data_part,
>
Identifier par UUDI n'empêche pas que la lettre change. Simplement,
comme on n'utilise pas la lettre pour référencer la partition,
on se fiche qu'elle change.
> Lorsque je fais un reboot, une fois sur deux il devient /dev/sdc
> et l'autre fois, /dev/sda.
>
l'identificatio
> /dev/disk/by-label/my_data_part :
> je n'ai pas ce fichier "my_data_part".
Ce n'est peut-être pas évident dans mon message précédent, mais :
> > soit par un 'label' descriptif (/dev/disk/by-label/my_data_part) créé
> > avec les outils de gestion de FS (un peu plus de travail, mais a
> > l'avantage  d'être immédiatement lisible)
indique que c'est manuel.
> A. V.
>
Cordialement.
__
Éric Dégenètais
Henix

http://www.henix.com
http://www.squashtest.org

Re: souci imprimante usb (fdisk -l , hddtemp )

2018-12-17 Thread infos SX

On Monday 17 December 2018 14:47:03 Eric Degenetais wrote:
> > certains ne sont plus reconnus et d'autres décalés d'une lettre .

> ça vient peut-être d'un certain manque de robustesse de la configuration :
> si je comprends bien la configuration utilise des device names du type
> /dev/sda1, dev/sda2, /dev/sdb ...
> Or ces lettres dépendent de l'ordre dans lequel les périphériques répondent
> lors de leur énumération, ordre dont la stabilité n'est pas (n'a jamais
> été) garantie.
> Il est aujourd'hui recommandé de référencer les périphériques
> - soit par l'UUID de la partition (ce que font normalement les
> installeurs, mais il faut le faire soi-même si c'est une migration)
> soit par un 'label' descriptif (/dev/disk/by-label/my_data_part) créé
> avec les outils de gestion de FS (un peu plus de travail, mais a
> l'avantage  d'être immédiatement lisible)

C'est ce que j'ai fait sur un serveur avec un seul disque dur.
UUID et /dev/disk/by-label/my_data_part,

Lorsque je fais un reboot, une fois sur deux il devient /dev/sdc
et l'autre fois, /dev/sda.

/dev/disk/by-label/my_data_part :
je n'ai pas ce fichier "my_data_part".

A. V.

Re: souci imprimante usb (fdisk -l , hddtemp )

Le lun. 17 déc. 2018 à 13:45, alain-buster  a écrit :

> bonjour , je rencontre un souci avec mon imprimante usb HP ENVY 5536 .
>
> je ne sais à quel(s) paquet se rapporte le souci :
>
> description :
>
> 1) j'allume l'imprimante
>
> 2) j'allume le pc
>
> 3) arrivé sous testing , les disques sont tous mélangés .
>
> certains ne sont plus reconnus et d'autres décalés d'une lettre .
>
bonjour,
ça vient peut-être d'un certain manque de robustesse de la configuration :
si je comprends bien la configuration utilise des device names du type
/dev/sda1, dev/sda2, /dev/sdb ...
Or ces lettres dépendent de l'ordre dans lequel les périphériques répondent
lors de leur énumération, ordre dont la stabilité n'est pas (n'a jamais
été) garantie.
Il est aujourd'hui recommandé de référencer les périphériques

   - soit par l'UUID de la partition (ce que font normalement les
   installeurs, mais il faut le faire soi-même si c'est une migration)
   - soit par un 'label' descriptif (/dev/disk/by-label/my_data_part) créé
   avec les outils de gestion de FS (un peu plus de travail, mais a l'avantage
   d'être immédiatement lisible)


> fdisk -l se mélange les pinceaux.
>
Ce qui sera évité avec la technique ci-dessus.

>
> deuxième cas de figure :
>
> 1) j'allume le pc
>
> 2) j'allume l'imprimante
>
> 3) pas de souci . tout fonctionne parfaitement .
>
>
aucun disque ne disparait , tous sont reconnus dans l'ordre.
>
> En ce qui concerne les disques qui "disparaissent", il faudrait vérifier
s'ils sont intégralement "non-reconnus" ou simplement changés
d'identifiants.

> je me suis bien exprimé ? besoin d' éclaircissements ?
>
> je me tiens à votre disposition .
>
> je ne sais ni quand , ni où , ni comment poster ???
>
> merci
>
> alain
>
> alain_bel...@bbox.fr
>
> __
Éric Dégenètais
Henix

http://www.henix.com
http://www.squashtest.org

souci imprimante usb (fdisk -l , hddtemp )

2018-12-17 Thread alain-buster


bonjour , je rencontre un souci avec mon imprimante usb HP ENVY 5536 .

je ne sais à quel(s) paquet se rapporte le souci :

description :

1) j'allume l'imprimante

2) j'allume le pc

3) arrivé sous testing , les disques sont tous mélangés .

certains ne sont plus reconnus et d'autres décalés d'une lettre .

fdisk -l se mélange les pinceaux.

deuxième cas de figure :

1) j'allume le pc

2) j'allume l'imprimante

3) pas de souci . tout fonctionne parfaitement .

aucun disque ne disparait , tous sont reconnus dans l'ordre.

je me suis bien exprimé ? besoin d' éclaircissements ?

je me tiens à votre disposition .

je ne sais ni quand , ni où , ni comment poster ???

merci

alain

alain_bel...@bbox.fr

Re: fdisk via console locale, défilement manuel ?

2018-01-06 Thread Pierre L.

Merci à vous!

Ca sent le petit bloc-note avec tous ces raccourcis :)

Sinon à propos des touches pgup+pgdown, on a un portable avec une touche
"fonction" + flèches pour les activer... je me méfie des histoires de
compatibilité ? En me disant que ce n'est pas une touche "physique"...
Bref, il y a plusieurs moyens d'arriver à se déplacer dans cet écran,
c'est top !



Le 06/01/2018 à 13:49, Jean-Michel OLTRA a écrit :
> Bonjour,
>
>
> Le samedi 06 janvier 2018, Pierre L. a écrit...
>
>
>> @Michel, je testerai "shift + pgdwn ou pgup".
>> Mais je vais quand même garder le "less" en mémoire, des claviers
>> d'ordis portables n'ayant pas ces 2 touches physiques...
> Tu peux faire défiler le texte avec les touches 'j' et 'k', mais également
> 'Ctrl-n' et 'Ctrl-p' et par "page" avec 'Ctrl-B' et 'Ctrl-F'.
> Pour aller tout en haut : gg
> Tout en bas : G
> L'aide : h
>




signature.asc
Description: OpenPGP digital signature

Re: fdisk via console locale, défilement manuel ?

2018-01-06 Thread Jean-Michel OLTRA


Bonjour,


Le samedi 06 janvier 2018, Pierre L. a écrit...


> @Michel, je testerai "shift + pgdwn ou pgup".
> Mais je vais quand même garder le "less" en mémoire, des claviers
> d'ordis portables n'ayant pas ces 2 touches physiques...

Tu peux faire défiler le texte avec les touches 'j' et 'k', mais également
'Ctrl-n' et 'Ctrl-p' et par "page" avec 'Ctrl-B' et 'Ctrl-F'.
Pour aller tout en haut : gg
Tout en bas : G
L'aide : h

-- 
jm

Re: fdisk via console locale, défilement manuel ?

2018-01-06 Thread hamster

Le 06/01/2018 à 09:11, Pierre L. a écrit :
> Merci à tous pour votre aide !
> "less" a l'ai assez sympa dans ce cas, avec la touche "q" pour en sortir...
> La navigation est un peu déroutante au début, j'ai l'impression qu'il
> n'y a pas moyen de remonter une fois dans le bas ?

On peut descendre et remonter d'une ligne a la fois avec les fleches bas
et haut.
On peut descendre et remonter d'une hauteur d'écran a la fois avec les
touches "page down" et "page up".
On peut aller tout a la fin ou tout au début avec les touches "fin de
page" et "debut de page".

Tout cela fonctionne meme quand on a atteint la fin.

> @Michel, je testerai "shift + pgdwn ou pgup".

Chez moi ca marche, mais sur un nombre de lignes moins grand que ne sait
le faire less.

> Mais je vais quand même garder le "less" en mémoire, des claviers
> d'ordis portables n'ayant pas ces 2 touches physiques...

Tous les ordis portables que j'ai eus ont ces touches.

PS : si tu veux voir la sortie d'une commande, tu la renvoie sur less
avec le pipe. Si tu veux voir un fichier, pas la peine de faire
cat lefichier.txt | less
tu peux faire directement
less lefichier.txt

Re: fdisk via console locale, défilement manuel ?

2018-01-06 Thread Pierre L.

Merci à tous pour votre aide !
"less" a l'ai assez sympa dans ce cas, avec la touche "q" pour en sortir...
La navigation est un peu déroutante au début, j'ai l'impression qu'il
n'y a pas moyen de remonter une fois dans le bas ?
A voir ce que ca va donner sur la machine en question ;)

@Michel, je testerai "shift + pgdwn ou pgup".
Mais je vais quand même garder le "less" en mémoire, des claviers
d'ordis portables n'ayant pas ces 2 touches physiques...

Merci à vous



signature.asc
Description: OpenPGP digital signature

Re: fdisk via console locale, défilement manuel ?

2018-01-05 Thread Randy11


Le 05/01/2018 à 12:35, Bernard Schoenacker a écrit :


serait il possible d'employer cfdisk ?

illustrations :
http://manual.aptosid.com/fr/part-cfdisk-fr.htm

slt
bernard


Cela faisait longtemps que je n'avais pas regardé
"cfdisk", l'interface à bien progressée, l'affichage des
UUID est pratique.

Mais attention, tel quel les actions sont possibles, donc
risque de modification des partitions par rapport à
"fdisk -l".

Re: fdisk via console locale, défilement manuel ?

2018-01-05 Thread Randy11


Le 05/01/2018 à 11:46, Pierre L. a écrit :

Bonjour,

En mode console, est-il possible d'avoir une option qui permette d'avoir
une "liste déroulante", plutôt que d'avoir le résultat d'une commande
qui défile d'un coup à l'écran ?
Clavier/écran directement branchés sur la machine.

Je tente de m'expliquer car probablement assez peu clair (d'ailleurs je
ne vois pas comment trouver l'info, car quel mot clé utiliser ?!) :
- la commande fdisk affiche toutes les partitions reconnues par le
système (si je ne me trompe pas). Dans mon cas, seule la fin est
lisible, pas moyen de remonter...
Certes via ssh il est possible d'avoir un ascenseur dans une interface
type XFCE, mais en local directement sur la console de la machine,
est-ce possible ?

En vous remerciant par avance,

Et au passage les bons voeux à la liste :)


J'ai découvert "most" : apt-get install most.

fdisk -l | most

L'aide en ligne indique qu'il faut appuyer sur "Q" pour quitter
et "H" pour l'aide. Cela permet de monter et descendre.

Pour avoir les pages de manuel en couleur, dans mon ".bashrc" :
PAGER=most
export PAGER

Re: fdisk via console locale, défilement manuel ?

2018-01-05 Thread Michel

Le 05/01/2018 à 12:30, daniel huhardeaux a écrit :
> Le 05/01/2018 à 11:46, Pierre L. a écrit :
>> Bonjour,
> 
> Bonjour
> 
>>
>> En mode console, est-il possible d'avoir une option qui permette d'avoir
>> une "liste déroulante", plutôt que d'avoir le résultat d'une commande
>> qui défile d'un coup à l'écran ?
> more
> 
> Ex: ls -al|more
> 
> [...]
> 
shift + pgdwn ou pgup ?

Re: fdisk via console locale, défilement manuel ?

2018-01-05 Thread hamster

Le 05/01/2018 à 12:29, Raphaël POITEVIN a écrit :
> daniel huhardeaux  writes:
>> more
> less est préférable car on peut défiler dans les deux sens.

Petit dicton : il faut arriver a se convaincre que "less is better than
more".

Re: fdisk via console locale, défilement manuel ?

2018-01-05 Thread hamster

Le 05/01/2018 à 12:20, Raphaël POITEVIN a écrit :
> "Pierre L." <pet...@miosweb.mooo.com> writes:
>> En mode console, est-il possible d'avoir une option qui permette d'avoir
>> une "liste déroulante", plutôt que d'avoir le résultat d'une commande
>> qui défile d'un coup à l'écran ?
>> Clavier/écran directement branchés sur la machine.
> Piper dans less :
> fdisk -l | less

Ne jamais dire "less" a un débutant sans lui dire que pour en sortir
ensuite c'est la touche "q". C'est pareil quand on dit "RTFM" d'ailleurs.

Re: fdisk via console locale, défilement manuel ?

2018-01-05 Thread Bernard Schoenacker



- Mail original -
> De: "Pierre L." <pet...@miosweb.mooo.com>
> À: debian-user-french@lists.debian.org
> Envoyé: Vendredi 5 Janvier 2018 11:46:09
> Objet: fdisk via console locale, défilement manuel ?
> 
> Bonjour,
> 
> En mode console, est-il possible d'avoir une option qui permette
> d'avoir
> une "liste déroulante", plutôt que d'avoir le résultat d'une commande
> qui défile d'un coup à l'écran ?
> Clavier/écran directement branchés sur la machine.
> 
> Je tente de m'expliquer car probablement assez peu clair (d'ailleurs
> je
> ne vois pas comment trouver l'info, car quel mot clé utiliser ?!) :
> - la commande fdisk affiche toutes les partitions reconnues par le
> système (si je ne me trompe pas). Dans mon cas, seule la fin est
> lisible, pas moyen de remonter...
> Certes via ssh il est possible d'avoir un ascenseur dans une
> interface
> type XFCE, mais en local directement sur la console de la machine,
> est-ce possible ?
> 
> En vous remerciant par avance,
> 
> Et au passage les bons voeux à la liste :)
> 
> 
bonjour,


serait il possible d'employer cfdisk ?

illustrations :

http://manual.aptosid.com/fr/part-cfdisk-fr.htm

slt
bernard

Re: fdisk via console locale, défilement manuel ?

2018-01-05 Thread Raphaël POITEVIN

daniel huhardeaux  writes:
> more

less est préférable car on peut défiler dans les deux sens.
-- 
Raphaël POITEVIN

Re: fdisk via console locale, défilement manuel ?

2018-01-05 Thread daniel huhardeaux


Le 05/01/2018 à 11:46, Pierre L. a écrit :

Bonjour,


Bonjour



En mode console, est-il possible d'avoir une option qui permette d'avoir
une "liste déroulante", plutôt que d'avoir le résultat d'une commande
qui défile d'un coup à l'écran ?

more

Ex: ls -al|more

[...]

--
Daniel

Re: fdisk via console locale, défilement manuel ?

2018-01-05 Thread Raphaël POITEVIN

"Pierre L." <pet...@miosweb.mooo.com> writes:
> En mode console, est-il possible d'avoir une option qui permette d'avoir
> une "liste déroulante", plutôt que d'avoir le résultat d'une commande
> qui défile d'un coup à l'écran ?
> Clavier/écran directement branchés sur la machine.

Piper dans less :
fdisk -l | less
-- 
Raphaël

fdisk via console locale, défilement manuel ?

2018-01-05 Thread Pierre L.

Bonjour,

En mode console, est-il possible d'avoir une option qui permette d'avoir
une "liste déroulante", plutôt que d'avoir le résultat d'une commande
qui défile d'un coup à l'écran ?
Clavier/écran directement branchés sur la machine.

Je tente de m'expliquer car probablement assez peu clair (d'ailleurs je
ne vois pas comment trouver l'info, car quel mot clé utiliser ?!) :
- la commande fdisk affiche toutes les partitions reconnues par le
système (si je ne me trompe pas). Dans mon cas, seule la fin est
lisible, pas moyen de remonter...
Certes via ssh il est possible d'avoir un ascenseur dans une interface
type XFCE, mais en local directement sur la console de la machine,
est-ce possible ?

En vous remerciant par avance,

Et au passage les bons voeux à la liste :)



signature.asc
Description: OpenPGP digital signature

Re: Fdisk

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Fri, Jan 20, 2017 at 08:15:27PM +0100, Pascal Hambourg wrote:
> Le 20/01/2017 à 11:11, to...@tuxteam.de a écrit :
> >
> >>On 01/20/2017 11:54 AM, Gokan Atmaca wrote:
> >>>Pre:
> >>>root@debian:/home/gokan# fdisk  -l
> >>>
> >>>Disk /dev/sda:[b] 40 GiB[/b], 42949672960 bytes, 83886080 sectors
> (...)
> >>>Post:
> >>>root@debian:/home/gokan# fdisk -l
> >>>
> >>>Disk /dev/sda:[b] 50 GiB[/b], 53687091200 bytes, 104857600 sectors
> (...)
> >>>How can I grow this disc?
> 
> You just did. The disk size is now 50 GiB.
> Do not confuse disk, partition and filesystem.
> 
> > (3) you could try to add your new space to your existing root
> > partition (sda1). Problem is, the swap is on the way. So
> > first disable swap, remove swap partition (as in (2)), delete
> > swap partition (fdisk), enlarge sda1 (still fdisk), re-create
> > swap at the end (still fdisk). When finished, and all is
> > well, then you can resize your file system (resize2fs). Note
> > that root can't be mounted read/write for that.
> 
> Why not ? ext4 supports online growing.

You're right: only shrinking has to be done off-line these days.
Sorry for the confusion.

regards
- -- tomás
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAliDFE8ACgkQBcgs9XrR2kYFGwCeJhjxoy3LlVHhlm5+5cHXIEKI
FRMAn1GePzsYDhw6OUE/A30avXn9LU9k
=ROyC
-END PGP SIGNATURE-

Re: Fdisk

2017-01-20 Thread Pascal Hambourg


Le 20/01/2017 à 12:41, Gokan Atmaca a écrit :

Yeah, he's working right now. I've erased all the available parts.
(Disk) I did not write the configuration. (W) Then I created a new
primary partition and gave default values.
Then I ran "resize2fs". Of course, I recreated the deleted swap
partition with "dd". That's it ...


dd does not create partitions. Didn't you create a swap file instead ?

Re: Fdisk

2017-01-20 Thread Pascal Hambourg


Le 20/01/2017 à 11:11, to...@tuxteam.de a écrit :



On 01/20/2017 11:54 AM, Gokan Atmaca wrote:

Pre:
root@debian:/home/gokan# fdisk  -l

Disk /dev/sda:[b] 40 GiB[/b], 42949672960 bytes, 83886080 sectors

(...)

Post:
root@debian:/home/gokan# fdisk -l

Disk /dev/sda:[b] 50 GiB[/b], 53687091200 bytes, 104857600 sectors

(...)

How can I grow this disc?


You just did. The disk size is now 50 GiB.
Do not confuse disk, partition and filesystem.


 (3) you could try to add your new space to your existing root
 partition (sda1). Problem is, the swap is on the way. So
 first disable swap, remove swap partition (as in (2)), delete
 swap partition (fdisk), enlarge sda1 (still fdisk), re-create
 swap at the end (still fdisk). When finished, and all is
 well, then you can resize your file system (resize2fs). Note
 that root can't be mounted read/write for that.


Why not ? ext4 supports online growing.

Note : fdisk is not the best tool for such operation. It does not allow 
to directly resize partitions ; you must delete and recreate them at the 
exact same beginning position. Also, it cannot update the kernel's idea 
of the partition table if partitions of the disk are in use. So the 
reboot was required so that the kernel sees the new size


Parted would allow both resizing partitions and updating the kernel's view.


 (4-n) you could use LVM...


I'm afraid it it's too late now, the installation was done without LVM.

Re: Fdisk

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Fri, Jan 20, 2017 at 02:41:26PM +0300, Gokan Atmaca wrote:
> Yeah, he's working right now. I've erased all the available parts.
> (Disk) I did not write the configuration. (W) Then I created a new
> primary partition and gave default values.
> Then I ran "resize2fs". Of course, I recreated the deleted swap
> partition with "dd". That's it ...
> 
> Note: I fixed the fstab.

Great, then :-)

regards
- -- t
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAliCAToACgkQBcgs9XrR2kZCKgCeKPQLdEe8266xMwGa46UA1mkT
0sMAnRGMN0dWqSJ/jPiyiCCKBCSSPN3M
=TOnQ
-END PGP SIGNATURE-

Re: Fdisk

2017-01-20 Thread Gokan Atmaca

Yeah, he's working right now. I've erased all the available parts.
(Disk) I did not write the configuration. (W) Then I created a new
primary partition and gave default values.
Then I ran "resize2fs". Of course, I recreated the deleted swap
partition with "dd". That's it ...

Note: I fixed the fstab.

On Fri, Jan 20, 2017 at 2:27 PM,   wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Fri, Jan 20, 2017 at 02:05:26PM +0300, Gokan Atmaca wrote:
>> I did it. I first erased all parts. Without saying "W". Then I called
>> the new section and gave default values.
>> I've done it the next time I restart. :)
>>
>> #resize2fs /dev/sda1
>
> Sorry, I couldn't understand exactly what you mean. But I hope it
> worked for you!
>
> Cheers
> - -- t
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1.4.12 (GNU/Linux)
>
> iEYEARECAAYFAliB9BgACgkQBcgs9XrR2kbHDACdEdsrLVcmq4nLaLCmv6LAjbRL
> ivQAn1K0GbY1qMLYci66Brze0QqGhDh3
> =vxZR
> -END PGP SIGNATURE-

Re: Fdisk

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Fri, Jan 20, 2017 at 02:05:26PM +0300, Gokan Atmaca wrote:
> I did it. I first erased all parts. Without saying "W". Then I called
> the new section and gave default values.
> I've done it the next time I restart. :)
> 
> #resize2fs /dev/sda1

Sorry, I couldn't understand exactly what you mean. But I hope it
worked for you!

Cheers
- -- t
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAliB9BgACgkQBcgs9XrR2kbHDACdEdsrLVcmq4nLaLCmv6LAjbRL
ivQAn1K0GbY1qMLYci66Brze0QqGhDh3
=vxZR
-END PGP SIGNATURE-

Re: Fdisk

2017-01-20 Thread Gokan Atmaca

I did it. I first erased all parts. Without saying "W". Then I called
the new section and gave default values.
I've done it the next time I restart. :)

#resize2fs /dev/sda1

On Fri, Jan 20, 2017 at 1:11 PM,  <to...@tuxteam.de> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Fri, Jan 20, 2017 at 11:59:36AM +0200, Georgi Naplatanov wrote:
>> On 01/20/2017 11:54 AM, Gokan Atmaca wrote:
>> > Hello
>> >
>> > Debian is running as a VM on the KVM. I enlarged the disk with QEMU.
>> > But the disk is as follows.
>> > So he did not grow up.
>> >
>> > Pre:
>> > root@debian:/home/gokan# fdisk  -l
>> >
>> > Disk /dev/sda:[b] 40 GiB[/b], 42949672960 bytes, 83886080 sectors
>> > Units: sectors of 1 * 512 = 512 bytes
>> > Sector size (logical/physical): 512 bytes / 512 bytes
>> > I/O size (minimum/optimal): 512 bytes / 512 bytes
>> > Disklabel type: dos
>> > Disk identifier: 0x6845f24a
>> >
>> > Device BootStart  End  Sectors  Size Id Type
>> > /dev/sda1  *2048 80383999 80381952 38.3G 83 Linux
>> > /dev/sda2   80386046 83884031  3497986  1.7G  5 Extended
>> > /dev/sda5   80386048 83884031  3497984  1.7G 82 Linux swap / Solaris
>> >
>> > root@debian:/home/gokan#
>> > root@debian:/home/gokan# df -Th
>> > Filesystem Type  Size  Used Avail Use% Mounted on
>> > /dev/sda1  ext4   38G  908M   35G   3% /
>> > udev   devtmpfs   10M 0   10M   0% /dev
>> > tmpfs  tmpfs 201M  4.4M  196M   3% /run
>> > tmpfs  tmpfs 501M 0  501M   0% /dev/shm
>> > tmpfs  tmpfs 5.0M 0  5.0M   0% /run/lock
>> > tmpfs  tmpfs 501M 0  501M   0% /sys/fs/cgroup
>> >
>> > Post:
>> > root@debian:/home/gokan# fdisk -l
>> >
>> > Disk /dev/sda:[b] 50 GiB[/b], 53687091200 bytes, 104857600 sectors
>> > Units: sectors of 1 * 512 = 512 bytes
>> > Sector size (logical/physical): 512 bytes / 512 bytes
>> > I/O size (minimum/optimal): 512 bytes / 512 bytes
>> > Disklabel type: dos
>> > Disk identifier: 0x6845f24a
>> >
>> > Device BootStart  End  Sectors  Size Id Type
>> > /dev/sda1  *2048 80383999 80381952 38.3G 83 Linux
>> > /dev/sda2   80386046 83884031  3497986  1.7G  5 Extended
>> > /dev/sda5   80386048 83884031  3497984  1.7G 82 Linux swap / Solaris
>> >
>> > root@debian:/home/gokan#
>> > root@debian:/home/gokan# df -Th
>> > Filesystem Type  Size  Used Avail Use% Mounted on
>> > /dev/sda1  ext4   38G  908M   35G   3% /
>> > udev   devtmpfs   10M 0   10M   0% /dev
>> > tmpfs  tmpfs 201M  4.4M  196M   3% /run
>> > tmpfs  tmpfs 501M 0  501M   0% /dev/shm
>> > tmpfs  tmpfs 5.0M 0  5.0M   0% /run/lock
>> > tmpfs  tmpfs 501M 0  501M   0% /sys/fs/cgroup
>> >
>> > How can I grow this disc?
>>
>> Hi,
>>
>> after enlarging disk or logical volume (in case of LVM), you have to
>> enlarge file system.
>
> Exactly. The disk is bigger now, but you have to do something with
> this extra space.
>
>  (1) You could make an extra partition (that would go after sda5,
>  that is your swap space) and put a file system on it, then
>  e.g. mount it
>
>  (2) you could try to add your new space to your existing swap
>  partition. Just disable swap (swapoff), enlarge sda5 (fdisk),
>  make new swap (mkswap), re-enable swap (swapon).
>
>  (3) you could try to add your new space to your existing root
>  partition (sda1). Problem is, the swap is on the way. So
>  first disable swap, remove swap partition (as in (2)), delete
>  swap partition (fdisk), enlarge sda1 (still fdisk), re-create
>  swap at the end (still fdisk). When finished, and all is
>  well, then you can resize your file system (resize2fs). Note
>  that root can't be mounted read/write for that.
>
>  (4-n) you could use LVM...
>
> I guess you want (3).
>
> Regards
> - -- t
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1.4.12 (GNU/Linux)
>
> iEYEARECAAYFAliB4kcACgkQBcgs9XrR2kb80gCdEYOlD7WNf2PEujXXs6SCC3hP
> KLcAn0OcfH+JNlXFth5ftiIPRHJRlVXA
> =JUyi
> -END PGP SIGNATURE-
>

Re: Fdisk

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Fri, Jan 20, 2017 at 11:59:36AM +0200, Georgi Naplatanov wrote:
> On 01/20/2017 11:54 AM, Gokan Atmaca wrote:
> > Hello
> > 
> > Debian is running as a VM on the KVM. I enlarged the disk with QEMU.
> > But the disk is as follows.
> > So he did not grow up.
> > 
> > Pre:
> > root@debian:/home/gokan# fdisk  -l
> > 
> > Disk /dev/sda:[b] 40 GiB[/b], 42949672960 bytes, 83886080 sectors
> > Units: sectors of 1 * 512 = 512 bytes
> > Sector size (logical/physical): 512 bytes / 512 bytes
> > I/O size (minimum/optimal): 512 bytes / 512 bytes
> > Disklabel type: dos
> > Disk identifier: 0x6845f24a
> > 
> > Device BootStart  End  Sectors  Size Id Type
> > /dev/sda1  *2048 80383999 80381952 38.3G 83 Linux
> > /dev/sda2   80386046 83884031  3497986  1.7G  5 Extended
> > /dev/sda5   80386048 83884031  3497984  1.7G 82 Linux swap / Solaris
> > 
> > root@debian:/home/gokan#
> > root@debian:/home/gokan# df -Th
> > Filesystem Type  Size  Used Avail Use% Mounted on
> > /dev/sda1  ext4   38G  908M   35G   3% /
> > udev   devtmpfs   10M 0   10M   0% /dev
> > tmpfs  tmpfs 201M  4.4M  196M   3% /run
> > tmpfs  tmpfs 501M 0  501M   0% /dev/shm
> > tmpfs  tmpfs 5.0M 0  5.0M   0% /run/lock
> > tmpfs  tmpfs 501M 0  501M   0% /sys/fs/cgroup
> > 
> > Post:
> > root@debian:/home/gokan# fdisk -l
> > 
> > Disk /dev/sda:[b] 50 GiB[/b], 53687091200 bytes, 104857600 sectors
> > Units: sectors of 1 * 512 = 512 bytes
> > Sector size (logical/physical): 512 bytes / 512 bytes
> > I/O size (minimum/optimal): 512 bytes / 512 bytes
> > Disklabel type: dos
> > Disk identifier: 0x6845f24a
> > 
> > Device BootStart  End  Sectors  Size Id Type
> > /dev/sda1  *2048 80383999 80381952 38.3G 83 Linux
> > /dev/sda2   80386046 83884031  3497986  1.7G  5 Extended
> > /dev/sda5   80386048 83884031  3497984  1.7G 82 Linux swap / Solaris
> > 
> > root@debian:/home/gokan#
> > root@debian:/home/gokan# df -Th
> > Filesystem Type  Size  Used Avail Use% Mounted on
> > /dev/sda1  ext4   38G  908M   35G   3% /
> > udev   devtmpfs   10M 0   10M   0% /dev
> > tmpfs  tmpfs 201M  4.4M  196M   3% /run
> > tmpfs  tmpfs 501M 0  501M   0% /dev/shm
> > tmpfs  tmpfs 5.0M 0  5.0M   0% /run/lock
> > tmpfs  tmpfs 501M 0  501M   0% /sys/fs/cgroup
> > 
> > How can I grow this disc?
> 
> Hi,
> 
> after enlarging disk or logical volume (in case of LVM), you have to
> enlarge file system.

Exactly. The disk is bigger now, but you have to do something with
this extra space.

 (1) You could make an extra partition (that would go after sda5,
 that is your swap space) and put a file system on it, then
 e.g. mount it

 (2) you could try to add your new space to your existing swap
     partition. Just disable swap (swapoff), enlarge sda5 (fdisk),
 make new swap (mkswap), re-enable swap (swapon).

 (3) you could try to add your new space to your existing root
 partition (sda1). Problem is, the swap is on the way. So
 first disable swap, remove swap partition (as in (2)), delete
 swap partition (fdisk), enlarge sda1 (still fdisk), re-create
 swap at the end (still fdisk). When finished, and all is
 well, then you can resize your file system (resize2fs). Note
 that root can't be mounted read/write for that.

 (4-n) you could use LVM...

I guess you want (3).

Regards
- -- t
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAliB4kcACgkQBcgs9XrR2kb80gCdEYOlD7WNf2PEujXXs6SCC3hP
KLcAn0OcfH+JNlXFth5ftiIPRHJRlVXA
=JUyi
-END PGP SIGNATURE-

Re: Fdisk

2017-01-20 Thread Georgi Naplatanov

On 01/20/2017 11:54 AM, Gokan Atmaca wrote:
> Hello
> 
> Debian is running as a VM on the KVM. I enlarged the disk with QEMU.
> But the disk is as follows.
> So he did not grow up.
> 
> Pre:
> root@debian:/home/gokan# fdisk  -l
> 
> Disk /dev/sda:[b] 40 GiB[/b], 42949672960 bytes, 83886080 sectors
> Units: sectors of 1 * 512 = 512 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 bytes / 512 bytes
> Disklabel type: dos
> Disk identifier: 0x6845f24a
> 
> Device BootStart  End  Sectors  Size Id Type
> /dev/sda1  *2048 80383999 80381952 38.3G 83 Linux
> /dev/sda2   80386046 83884031  3497986  1.7G  5 Extended
> /dev/sda5   80386048 83884031  3497984  1.7G 82 Linux swap / Solaris
> 
> root@debian:/home/gokan#
> root@debian:/home/gokan# df -Th
> Filesystem Type  Size  Used Avail Use% Mounted on
> /dev/sda1  ext4   38G  908M   35G   3% /
> udev   devtmpfs   10M 0   10M   0% /dev
> tmpfs  tmpfs 201M  4.4M  196M   3% /run
> tmpfs  tmpfs 501M 0  501M   0% /dev/shm
> tmpfs  tmpfs 5.0M 0  5.0M   0% /run/lock
> tmpfs  tmpfs 501M 0  501M   0% /sys/fs/cgroup
> 
> Post:
> root@debian:/home/gokan# fdisk -l
> 
> Disk /dev/sda:[b] 50 GiB[/b], 53687091200 bytes, 104857600 sectors
> Units: sectors of 1 * 512 = 512 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 bytes / 512 bytes
> Disklabel type: dos
> Disk identifier: 0x6845f24a
> 
> Device BootStart  End  Sectors  Size Id Type
> /dev/sda1  *2048 80383999 80381952 38.3G 83 Linux
> /dev/sda2   80386046 83884031  3497986  1.7G  5 Extended
> /dev/sda5   80386048 83884031  3497984  1.7G 82 Linux swap / Solaris
> 
> root@debian:/home/gokan#
> root@debian:/home/gokan# df -Th
> Filesystem Type  Size  Used Avail Use% Mounted on
> /dev/sda1  ext4   38G  908M   35G   3% /
> udev   devtmpfs   10M 0   10M   0% /dev
> tmpfs  tmpfs 201M  4.4M  196M   3% /run
> tmpfs  tmpfs 501M 0  501M   0% /dev/shm
> tmpfs  tmpfs 5.0M 0  5.0M   0% /run/lock
> tmpfs  tmpfs 501M 0  501M   0% /sys/fs/cgroup
> 
> How can I grow this disc?

Hi,

after enlarging disk or logical volume (in case of LVM), you have to
enlarge file system.

HTH

Kind regards
Georgi

Fdisk

2017-01-20 Thread Gokan Atmaca

Hello

Debian is running as a VM on the KVM. I enlarged the disk with QEMU.
But the disk is as follows.
So he did not grow up.

Pre:
root@debian:/home/gokan# fdisk  -l

Disk /dev/sda:[b] 40 GiB[/b], 42949672960 bytes, 83886080 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x6845f24a

Device BootStart  End  Sectors  Size Id Type
/dev/sda1  *2048 80383999 80381952 38.3G 83 Linux
/dev/sda2   80386046 83884031  3497986  1.7G  5 Extended
/dev/sda5   80386048 83884031  3497984  1.7G 82 Linux swap / Solaris

root@debian:/home/gokan#
root@debian:/home/gokan# df -Th
Filesystem Type  Size  Used Avail Use% Mounted on
/dev/sda1  ext4   38G  908M   35G   3% /
udev   devtmpfs   10M 0   10M   0% /dev
tmpfs  tmpfs 201M  4.4M  196M   3% /run
tmpfs  tmpfs 501M 0  501M   0% /dev/shm
tmpfs  tmpfs 5.0M 0  5.0M   0% /run/lock
tmpfs  tmpfs 501M 0  501M   0% /sys/fs/cgroup

Post:
root@debian:/home/gokan# fdisk -l

Disk /dev/sda:[b] 50 GiB[/b], 53687091200 bytes, 104857600 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x6845f24a

Device BootStart  End  Sectors  Size Id Type
/dev/sda1  *2048 80383999 80381952 38.3G 83 Linux
/dev/sda2   80386046 83884031  3497986  1.7G  5 Extended
/dev/sda5   80386048 83884031  3497984  1.7G 82 Linux swap / Solaris

root@debian:/home/gokan#
root@debian:/home/gokan# df -Th
Filesystem Type  Size  Used Avail Use% Mounted on
/dev/sda1  ext4   38G  908M   35G   3% /
udev   devtmpfs   10M 0   10M   0% /dev
tmpfs  tmpfs 201M  4.4M  196M   3% /run
tmpfs  tmpfs 501M 0  501M   0% /dev/shm
tmpfs  tmpfs 5.0M 0  5.0M   0% /run/lock
tmpfs  tmpfs 501M 0  501M   0% /sys/fs/cgroup

How can I grow this disc?

Re: FDisk Help

2016-01-09 Thread Steve Matzura

Sven:

On Thu, 7 Jan 2016 16:12:51 +0100, you wrote:

>You said in your first mail that /dev/sda6 was swap. And since Linux
>always numbers the logical partitions beginning from 5 and /dev/sda1 was
>/, /dev/sda2 can only be the extended partition, containing sda5-8.
>Simple deduction (and experience with the matter of course).
>
>(Side-note: this is also why I really like GPT instead of MSDOS as a
>partition table. No primary, extended and logical partition nonsense,
>kist 128 possible partitions without any special conventions.)

Thanks. More of that esoteric knowledge again, comes with experience I
know.

Re: FDisk Help

2016-01-08 Thread Chris Bannister

On Thu, Jan 07, 2016 at 04:53:34PM +0100, jdd wrote:
> fdisk -l
> 
> gives all the necessary info
> 
> example:
> 
> Device Boot Start   End   Sectors   Size Id Type
> /dev/sdc1  * 2048  62910463  6290841630G 83 Linux
> /dev/sdc262910464 937701375 874790912 417,1G  f W95 Ext'd (LBA)
> /dev/sdc562912512 125820927  6290841630G 83 Linux
> /dev/sdc6   125822976 142591999  16769024 8G 82 Linux swap / Solaris
> /dev/sdc7   142594048 937701375 795107328 379,1G 83 Linux
> 
> 
> 
> (but all I have at hand is an openSUSE, the debian version may be different)

LOL, you do realise this is a list for Debian users, right?

-- 
"If you're not careful, the newspapers will have you hating the people
who are being oppressed, and loving the people who are doing the 
oppressing." --- Malcolm X

Re: FDisk Help

2016-01-08 Thread tomas

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Sat, Jan 09, 2016 at 02:54:44AM +1300, Chris Bannister wrote:
> On Thu, Jan 07, 2016 at 04:53:34PM +0100, jdd wrote:

[...]

> > (but all I have at hand is an openSUSE, the debian version may be different)
> 
> LOL, you do realise this is a list for Debian users, right?

But Debian users tend to be helpful and give others a hand (in my
experience, OpenSuSE users are very nice too. And don't get me
started on Arch: their wiki alone is a service to humankind so huge
that I've got no words for that :-)

- -- t
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlaPuk8ACgkQBcgs9XrR2kZ4ewCfVuzQKUF+fRI+ZIaeGCC8gxz5
SucAni76hcJi3j7dX6SVBDkP38Gv2xXM
=UXfg
-END PGP SIGNATURE-

Re: FDisk Help

2016-01-08 Thread jdd


Le 08/01/2016 14:54, Chris Bannister a écrit :

On Thu, Jan 07, 2016 at 04:53:34PM +0100, jdd wrote:

fdisk -l

gives all the necessary info

example:

Device Boot Start   End   Sectors   Size Id Type
/dev/sdc1  * 2048  62910463  6290841630G 83 Linux
/dev/sdc262910464 937701375 874790912 417,1G  f W95 Ext'd (LBA)
/dev/sdc562912512 125820927  6290841630G 83 Linux
/dev/sdc6   125822976 142591999  16769024 8G 82 Linux swap / Solaris
/dev/sdc7   142594048 937701375 795107328 379,1G 83 Linux



(but all I have at hand is an openSUSE, the debian version may be different)


LOL, you do realise this is a list for Debian users, right?

and? I also have Debian on some computers and there are several fdisk on 
the air


jdd

Re: FDisk Help

2016-01-07 Thread jdd


Le 07/01/2016 08:08, Steve Matzura a écrit :


I actually tried answering my own questions by looking at an other
running system to see how this is done, but the system is a different



df is not the right tool to lokk at partitions, simply use "sudo fdisk -l"

jdd

Re: FDisk Help

2016-01-07 Thread Sven Hartge

Steve Matzura  wrote:
> Sven: On Thu, 7 Jan 2016 08:29:46 +0100, you wrote:

>> /dev/sda5 to /dev/sda8 are logical partitions inside an extended
>> partition. The extended partition is /dev/sda2.

> How did you know that? sda6 isn't even a mounted filesystem--sda1, 5,
> 7 and 8 are the mounted filesystems for /, /tmp, /var, and /home
> respectively. How did /dev/sda6 get in there? It shows as swap.

You said in your first mail that /dev/sda6 was swap. And since Linux
always numbers the logical partitions beginning from 5 and /dev/sda1 was
/, /dev/sda2 can only be the extended partition, containing sda5-8.
Simple deduction (and experience with the matter of course).

(Side-note: this is also why I really like GPT instead of MSDOS as a
partition table. No primary, extended and logical partition nonsense,
kist 128 possible partitions without any special conventions.)

Grüße,
Sven.

-- 
Sigmentation fault. Core dumped.

Re: FDisk Help

2016-01-07 Thread Steve Matzura

Sven:

On Thu, 7 Jan 2016 08:29:46 +0100, you wrote:

>/dev/sda5 to /dev/sda8 are logical partitions inside an extended
>partition. The extended partition is /dev/sda2.

How did you know that? sda6 isn't even a mounted filesystem--sda1, 5,
7 and 8 are the mounted filesystems for /, /tmp, /var, and /home
respectively. How did /dev/sda6 get in there? It shows as swap.

>Hint: try the tool "lsblk" to see where which filesystem resides.

NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sda  8:00 111.8G  0 disk
tqsda1   8:10   8.4G  0 part /
tqsda2   8:20 1K  0 part
tqsda5   8:50   2.8G  0 part /var
tqsda6   8:60  13.4G  0 part [SWAP]
tqsda7   8:70   380M  0 part /tmp
mqsda8   8:80  86.9G  0 part /home
sdb  8:16   0 232.9G  0 disk
sr0 11:01  1024M  0 rom

OK, I see /dev/sdb is the 250G disk which probably needs partitioning
and formatting. Thanks for the hint. Always learning these
single-purpose tools is one of the ! joys of Linux.

Re: FDisk Help

2016-01-07 Thread jdd


Le 07/01/2016 16:43, David Christensen a écrit :


'lsblk' can tell you the relationship between kernel names (e.g. sda,
sda1, etc.) and mount points:

 $ lsblk



not always. I just tested: lsblk only flag as swap the active swap partition

fdisk -l

gives all the necessary info

example:

Device Boot Start   End   Sectors   Size Id Type
/dev/sdc1  * 2048  62910463  6290841630G 83 Linux
/dev/sdc262910464 937701375 874790912 417,1G  f W95 Ext'd (LBA)
/dev/sdc562912512 125820927  6290841630G 83 Linux
/dev/sdc6   125822976 142591999  16769024 8G 82 Linux swap / Solaris
/dev/sdc7   142594048 937701375 795107328 379,1G 83 Linux



(but all I have at hand is an openSUSE, the debian version may be 
different)


jdd

Re: FDisk Help

2016-01-06 Thread Sven Hartge

Steve Matzura <s...@noisynotes.com> wrote:

> I have three physical drives in my system--/dev/sda is presumably my
> boot drive, which shows up as six devices in /dev:
> /dev/sda1,2,5,6,7,8. Additionally, there's a CD-ROM drive, and a 250GB
> standard rotating disk. My boot partition is located on  a 120GB SSD,
> which I presume is /dev/sda, is divided as follows according to df:

> Filesystem  1K-blocks   Used Available Use% Mounted on
> /dev/sda1 8518920 879012   7184128  11% /
> /dev/sda7  368615   2058343005   1% /tmp
> /dev/sda5 2817056 178752   2475488   7% /var
> /dev/sda889493696  57076  84867532   1% /home

> What, then, are /dev/sda2 and /dev/sda6? I tried looking at them with
> FDisk and got the following:

> For /dev/sda2: Failed to read extended partition table
> (offset=5858805): Invalid argument

> For /dev/sda6: device contains a valid 'swap' signature, it's strongly
> recommended to wipe the device by command wipefs(8) if this setup is
> unexpected to avoid possible collisions.

/dev/sda5 to /dev/sda8 are logical partitions inside an extended
partition. The extended partition is /dev/sda2.

Hint: try the tool "lsblk" to see where which filesystem resides.

Grüße

-- 
Sigmentation fault. Core dumped.

gnu fdisk pour kfreebsd

2015-03-12 Thread Bernard Schoenacker

bonjour,


je recherche une doc pour pouvoir utiliser fdisk en mode chs afin de
préparer une install sur un ordi portable 

slt
bernard

-- 
Lisez la FAQ de la liste avant de poser une question :
http://wiki.debian.org/fr/FrenchLists

Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe
vers debian-user-french-requ...@lists.debian.org
En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org
Archive: 
https://lists.debian.org/20150313053036.446cbc94.bernard.schoenac...@free.fr

Re: PROBLEMA FDISK/KDE

2014-02-10 Thread Helio Loureiro

O que mostra a saída do comando fdisk -l /dev/sdX, onde X é o id do
pendrive?

Abs,
Helio Loureiro
http://helio.loureiro.eng.br
http://br.linkedin.com/in/helioloureiro
http://twitter.com/helioloureiro
http://gplus.to/helioloureiro


Em 6 de fevereiro de 2014 17:57, André Luiz andre4li...@gmail.comescreveu:

 Ja tentou o comando dd if=/dev/zero of=/dev/sdx bs=512 count=1 ?


 Em Thu, 6 Feb 2014 14:44:34 -0200
 Paulo Roberto shellcl...@gmail.com escreveu:

  Olá,
 
 
  Estou com problema ao tentar particionar/formatar um pendrive
  utilizando fdisk/cfdisk/parted.
 
  Utilizei recentemente um pendrive de 4Gb para criar um disco
  'bootavel' debian 7, dd if=imagem.iso of=/dev/sdx , o resultado foi
  uma imagem funcionando normalmente.
 
  O que acontece e que depois de instalar o sistema fui apagar o
  pendrive, particionar/formatar e tudo ocorreu normalmente...mass
  quando plugo o pendrive na porta usb o kdenotification mostra o
  pendrive como se fossem 2 pendrives
 
  ja deletei a tabela de partições várias vezes e formatei com
  vfat,ext4,ext3 e nada resolve, sempre acontece a mesma coisa...
 
  Acredito que seja um bug em algum pacote do kde... mas não encontrei
  nada relacionado, alguem ja conhece este problema?
 
  obs: testei em outros hosts com a mesma versão de pacotes e o problema
  acontece em todos...temente um pendrive de 4Gb para c
 
  em anexo o print...
 
  Versão do pacote que tem o fdisk
 
  # dpkg -l util-linux
  Desired=Unknown/Install/Remove/Purge/Hold
  |
 
 Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/
  Name  Version
  ArchitectureDescription
 
 +++-=-===-===-===
  ii  util-linux2.20.1-5.3
  amd64   Miscellaneous system utilities
 
  # fdisk -v
  fdisk (util-linux 2.20.1)
 



 --
 André Luiz Fraga Moreira
 ___
 AGORACRED -- Departamento de TI
 Tel: (27) 4009-0200 / ramal 0247
 andre.more...@agoracred.com.br


 --
 To UNSUBSCRIBE, email to debian-user-portuguese-requ...@lists.debian.org
 with a subject of unsubscribe. Trouble? Contact
 listmas...@lists.debian.org
 Archive: http://lists.debian.org/20140206145708.0...@gmail.com

PROBLEMA FDISK/KDE

2014-02-06 Thread Paulo Roberto

Olá,


Estou com problema ao tentar particionar/formatar um pendrive
utilizando fdisk/cfdisk/parted.

Utilizei recentemente um pendrive de 4Gb para criar um disco
'bootavel' debian 7, dd if=imagem.iso of=/dev/sdx , o resultado foi
uma imagem funcionando normalmente.

O que acontece e que depois de instalar o sistema fui apagar o
pendrive, particionar/formatar e tudo ocorreu normalmente...mass
quando plugo o pendrive na porta usb o kdenotification mostra o
pendrive como se fossem 2 pendrives

ja deletei a tabela de partições várias vezes e formatei com
vfat,ext4,ext3 e nada resolve, sempre acontece a mesma coisa...

Acredito que seja um bug em algum pacote do kde... mas não encontrei
nada relacionado, alguem ja conhece este problema?

obs: testei em outros hosts com a mesma versão de pacotes e o problema
acontece em todos...temente um pendrive de 4Gb para c

em anexo o print...

Versão do pacote que tem o fdisk

# dpkg -l util-linux
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name  Version
   ArchitectureDescription
+++-=-===-===-===
ii  util-linux2.20.1-5.3
   amd64   Miscellaneous system utilities

# fdisk -v
fdisk (util-linux 2.20.1)


cee05022016
Description: Binary data

Re: PROBLEMA FDISK/KDE

2014-02-06 Thread André Luiz

Ja tentou o comando dd if=/dev/zero of=/dev/sdx bs=512 count=1 ?


Em Thu, 6 Feb 2014 14:44:34 -0200
Paulo Roberto shellcl...@gmail.com escreveu:

 Olá,
 
 
 Estou com problema ao tentar particionar/formatar um pendrive
 utilizando fdisk/cfdisk/parted.
 
 Utilizei recentemente um pendrive de 4Gb para criar um disco
 'bootavel' debian 7, dd if=imagem.iso of=/dev/sdx , o resultado foi
 uma imagem funcionando normalmente.
 
 O que acontece e que depois de instalar o sistema fui apagar o
 pendrive, particionar/formatar e tudo ocorreu normalmente...mass
 quando plugo o pendrive na porta usb o kdenotification mostra o
 pendrive como se fossem 2 pendrives
 
 ja deletei a tabela de partições várias vezes e formatei com
 vfat,ext4,ext3 e nada resolve, sempre acontece a mesma coisa...
 
 Acredito que seja um bug em algum pacote do kde... mas não encontrei
 nada relacionado, alguem ja conhece este problema?
 
 obs: testei em outros hosts com a mesma versão de pacotes e o problema
 acontece em todos...temente um pendrive de 4Gb para c
 
 em anexo o print...
 
 Versão do pacote que tem o fdisk
 
 # dpkg -l util-linux
 Desired=Unknown/Install/Remove/Purge/Hold
 |
 Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
 |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/
 Name  Version
 ArchitectureDescription
 +++-=-===-===-===
 ii  util-linux2.20.1-5.3
 amd64   Miscellaneous system utilities
 
 # fdisk -v
 fdisk (util-linux 2.20.1)
 



-- 
André Luiz Fraga Moreira
___
AGORACRED -- Departamento de TI
Tel: (27) 4009-0200 / ramal 0247
andre.more...@agoracred.com.br


--
To UNSUBSCRIBE, email to debian-user-portuguese-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20140206145708.0...@gmail.com

Algo raro con fdisk -l

2013-05-30 Thread academia

Hola lista. Todas mis estaciones de trabajo están en Debian 6.0.7. En dos
de ellas ayer hice un fdisk y me salió algo que nunca había percibido
(debajo) Pudieran explicarme por qué ocurre esto, si mi HDD está en
peligro, además cómo solucionarlo.


root@informatico:/home/administrador# fdisk -l

Disk /dev/sda: 1000 GB, 1000202273280 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot  Start End  Blocks   Id  System
/dev/sda1   16527524280967  HPFS/NTFS
Warning: Partition 1 does not end on cylinder boundary.
/dev/sda2   *6527   1305352420095   83  Linux
Warning: Partition 2 does not end on cylinder boundary.
/dev/sda3   13053   13445 3148740   82  Linux swap
Warning: Partition 3 does not end on cylinder boundary.
/dev/sda4   13446  121602   8687630705  Extended
Warning: Partition 4 does not end on cylinder boundary.
/dev/sda5   13446   67524   4343815357  HPFS/NTFS
Warning: Partition 5 does not end on cylinder boundary.
/dev/sda6   67524  121602   4343815357  HPFS/NTFS
Warning: Partition 6 does not end on cylinder boundary.

Saludos



--
To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/55872.10.0.1.2.1369926781.squir...@www.correo.pinarte.cult.cu

Re: Algo raro con fdisk -l

2013-05-30 Thread Alfonso Camacho

Saludos:

 Hola lista. Todas mis estaciones de trabajo están en Debian 6.0.7. En dos
 de ellas ayer hice un fdisk y me salió algo que nunca había percibido
 (debajo) Pudieran explicarme por qué ocurre esto, si mi HDD está en
 peligro, además cómo solucionarlo.
 
 
 root@informatico:/home/administrador# fdisk -l
 
 Disk /dev/sda: 1000 GB, 1000202273280 bytes
 255 heads, 63 sectors/track, 121601 cylinders
 Units = cylinders of 16065 * 512 = 8225280 bytes
 
Device Boot  Start End  Blocks   Id  System
 /dev/sda1   16527524280967  HPFS/NTFS
 Warning: Partition 1 does not end on cylinder boundary.
 /dev/sda2   *6527   1305352420095   83  Linux
 Warning: Partition 2 does not end on cylinder boundary.
 /dev/sda3   13053   13445 3148740   82  Linux swap
 Warning: Partition 3 does not end on cylinder boundary.
 /dev/sda4   13446  121602   8687630705  Extended
 Warning: Partition 4 does not end on cylinder boundary.
 /dev/sda5   13446   67524   4343815357  HPFS/NTFS
 Warning: Partition 5 does not end on cylinder boundary.
 /dev/sda6   67524  121602   4343815357  HPFS/NTFS
 Warning: Partition 6 does not end on cylinder boundary.
 
 Saludos
 


Eso puede ocurrir en los discos modernos por una falta de alineación.
Repercute sólo en que las lecturas y estrituras en ese sector son más lentas.

Para corregir el problema deberias eliminar esas particiones y volverlas a 
crearlas con fdisk (cambiando las unidades de cilindros a sectores). Supongo 
que con un livecd y usando parted/gparted tambien lo podrias solucionar.

De este problema se ha hablado largo y tendido en los foros de OVH:

http://foros.ovh.es/showthread.php?t=9807
http://foros.ovh.es/showthread.php?t=10748



-- 
Alfonso alfo...@gnuino.net


--
To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/1820838367.817.1369927939957.javamail.r...@gnuino.net

Re: Algo raro con fdisk -l

2013-05-30 Thread Camaleón

El Thu, 30 May 2013 11:13:01 -0400, academia escribió:

 Hola lista. Todas mis estaciones de trabajo están en Debian 6.0.7. En
 dos de ellas ayer hice un fdisk y me salió algo que nunca había
 percibido (debajo) Pudieran explicarme por qué ocurre esto, si mi HDD
 está en peligro, además cómo solucionarlo.

Le habla el sistema automatizado de alertas smarmontools. Stop. Su disco 
duro está en peligro. Stop. Hemos detectado particiones con Windows. Stop. 
¿Hay algo más peligroso que eso? Stop. No. Stop.

(es broma :-P)

 root@informatico:/home/administrador# fdisk -l
 
 Disk /dev/sda: 1000 GB, 1000202273280 bytes 255 heads, 63 sectors/track,
 121601 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes
 
Device Boot  Start End  Blocks   Id  System
 /dev/sda1   16527524280967  HPFS/NTFS
 Warning: Partition 1 does not end on cylinder boundary. 
  ^^

(...)

Si te refieres a ese mensaje, ya te ha contestado Alfonso, a lo que 
simple (y maliciosamente) añado:

http://lmgtfy.com/?q=Warning%3A+Partition+1+does+not+end+on+cylinder+boundary

Saludos,

-- 
Camaleón


-- 
To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/ko7thd$5ni$1...@ger.gmane.org

Re: why would fdisk -l take so long?

2012-09-29 Thread Albretch Mueller

 Or (from hdparm's man page:  Disable  the  automatic power-saving
 function of certain Seagate drives...):
   hdparm -Z /dev/sda

# hdparm -Z /dev/sda

/dev/sda:
 disabling Seagate auto powersaving mode
 HDIO_DRIVE_CMD(seagatepwrsave) failed: Input/output error

 lbrtchx


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/cafakbwjz5c7lhwsegnntlk4ldc2dsuurbexdlvjnfguzn9z...@mail.gmail.com

Re: why would fdisk -l take so long?

2012-09-29 Thread Martin Steigerwald

Hi Albrecht!

Am Samstag, 29. September 2012 schrieb Albretch Mueller:
[…]
 [11750.572197] ata2: SATA link down (SStatus 0 SControl 300)
 [11750.572245] ata1: SATA link down (SStatus 0 SControl 300)
 [11750.676244] ata3.00: ACPI cmd ef/03:0c:00:00:00:a0 (SET FEATURES)
 filtered out
 [11750.676248] ata3.00: ACPI cmd ef/03:42:00:00:00:a0 (SET FEATURES)
 filtered out
 [11750.676252] ata3.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE
 LOCK) filtered out
 [11750.682804] ata3.00: configured for UDMA/33
 [11755.300321] psmouse serio1: hgpk: ID: 10 00 64
 [11757.745503]
 [11757.745504] floppy driver state
 [11757.745505] ---
 [11757.745513] now=3437324 last interrupt=1109734 diff=2327590 last
 called handler=recal_interrupt
 [11757.745515] timeout_message=lock fdc
 [11757.745517] last output bytes:
 [11757.745518] 18 80 4294884748
 [11757.745520]  8 80 4294884748
 [11757.745522]  8 80 4294884748
 [11757.745523]  8 80 4294884748
 [11757.745525]  8 80 4294884748
 [11757.745527] 12 80 1109103
 [11757.745528]  0 90 1109103
 [11757.745530] 13 90 1109103
 [11757.745531]  0 90 1109103
 [11757.745533] 1a 90 1109103
 [11757.745534]  0 90 1109103
 [11757.745536]  3 80 1109103
 [11757.745537] c1 90 1109103
 [11757.745539] 10 90 1109103
 [11757.745540]  7 80 1109103
 [11757.745542]  0 90 1109103
 [11757.745544]  8 81 1109416
 [11757.745545]  7 80 1109422
 [11757.745547]  0 90 1109422
 [11757.745548]  8 81 1109734
 [11757.745550] last result at 1109734
 [11757.745551] last redo_fd_request at 1121152
 [11757.745554] 70 00p.
 [11757.745564] status=0
 [11757.745566] fdc_busy=1
 [11757.745569] do_floppy=reset_interrupt
 [11757.745571] cont=f85786c8
 [11757.745572] current_req=  (null)
 [11757.745574] command_status=-1
 [11757.745575]
 [11757.745578] floppy0: floppy timeout called
 [11757.745604] PM: resume of devices complete after 7495.396 msecs
 [11757.745866] Restarting tasks ... done.
 [11758.374389] VFS: busy inodes on changed media or resized disk sr0
 [11758.376145] ADDRCONF(NETDEV_UP): eth0: link is not ready
 [11760.048064] tg3 :02:00.0: eth0: Link is up at 100 Mbps, full duplex
 [11760.048068] tg3 :02:00.0: eth0: Flow control is on for TX and on for RX
 [11760.048247] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
 [11770.228921] eth0: no IPv6 routers present
 [11952.768836] usb 1-8: new high-speed USB device number 4 using ehci_hcd
 [11952.898331] usb 1-8: New USB device found, idVendor=0930, idProduct=6545
 [11952.898334] usb 1-8: New USB device strings: Mfr=1, Product=2, 
 SerialNumber=3
 [11952.898337] usb 1-8: Product: DT 101 G2
 [11952.898340] usb 1-8: Manufacturer: Kingston
 [11952.898342] usb 1-8: SerialNumber: 001CC0C83B35EB61142A011A
 [11952.899440] scsi6 : usb-storage 1-8:1.0
 [11953.948116] scsi 6:0:0:0: Direct-Access Kingston DT 101 G2
   PMAP PQ: 0 ANSI: 0 CCS
 [11953.948296] sd 6:0:0:0: Attached scsi generic sg1 type 0
 [11954.607947] sd 6:0:0:0: [sda] 15638528 512-byte logical blocks:
 (8.00 GB/7.45 GiB)
 [11954.610064] sd 6:0:0:0: [sda] Write Protect is off
 [11954.610068] sd 6:0:0:0: [sda] Mode Sense: 23 00 00 00
 [11954.612344] sd 6:0:0:0: [sda] No Caching mode page present
 [11954.612347] sd 6:0:0:0: [sda] Assuming drive cache: write through
 [11954.619566] sd 6:0:0:0: [sda] No Caching mode page present
 [11954.619569] sd 6:0:0:0: [sda] Assuming drive cache: write through
 [11954.641593]  sda: sda1
 [11954.647337] sd 6:0:0:0: [sda] No Caching mode page present
 [11954.647342] sd 6:0:0:0: [sda] Assuming drive cache: write through
 [11954.647345] sd 6:0:0:0: [sda] Attached SCSI removable disk
 [12011.869055] end_request: I/O error, dev fd0, sector 0
 [12097.222509] end_request: I/O error, dev fd0, sector 0
 [12150.892906] end_request: I/O error, dev fd0, sector 0
 [12209.992320] end_request: I/O error, dev fd0, sector 0
 [22999.715096] usb 1-8: USB disconnect, device number 4
 [22999.974401] usb 1-8: new high-speed USB device number 5 using ehci_hcd
 [23000.494403] usb 1-8: device not accepting address 5, error -71
 [23000.547764] hub 1-0:1.0: unable to enumerate USB device on port 8
 [23431.424360] usb 1-8: new high-speed USB device number 7 using ehci_hcd
 [23431.553861] usb 1-8: New USB device found, idVendor=0930, idProduct=6545
 [23431.553866] usb 1-8: New USB device strings: Mfr=1, Product=2, 
 SerialNumber=3
 [23431.553869] usb 1-8: Product: DT 101 G2
 [23431.553871] usb 1-8: Manufacturer: Kingston
 [23431.553874] usb 1-8: SerialNumber: 001CC0C83B35EB61142A011A
 [23431.555077] scsi7 : usb-storage 1-8:1.0
 [23432.603528] scsi 7:0:0:0: Direct-Access Kingston DT 101 G2
   PMAP PQ: 0 ANSI: 0 CCS
 [23432.603703] sd 7:0:0:0: Attached scsi generic sg1 type 0
 [23433.241968] sd 7:0:0:0: [sda] 15638528 512-byte logical blocks:
 (8.00 GB/7.45 GiB)
 [23433.244088] sd 7:0:0:0: [sda] Write Protect is off
 [23433.244091] sd 7:0:0:0: [sda] Mode Sense: 23 00 00 00
 [23433.246215] sd 7:0:0:0: [sda] No Caching mode page present

Re: why would fdisk -l take so long?

2012-09-29 Thread Albretch Mueller

On 9/29/12, Jude DaShiell jdash...@shellworld.net wrote:
run d-ban on the disk and do a thorough cleaning of the disk then try
~
The only data erasure I know of is shredding your hard drives to
pieces, smashing them to dust and melting them. This is by the way
what US gov does with their hard drives and monitors
~
lbrtchx
~
http://en.wikipedia.org/wiki/Hysteresis
~
http://en.wikipedia.org/wiki/Data_remanence
~
http://en.wikipedia.org/wiki/Coercivity
~
http://en.wikipedia.org/wiki/Degaussing
For certain forms of computer data storage, however, such as modern
hard drives and some tape backup drives, degaussing renders the
magnetic media completely unusable and damages the storage system.
This is due to the devices having an infinitely variable read/write
head positioning mechanism which relies on special servo control data
(e.g. Gray Code) that is meant to be permanently embedded into the
magnetic media. This servo data is written onto the media a single
time at the factory using special-purpose servo writing hardware.
The servo patterns are normally never overwritten by the device for
any reason and are used to precisely position the read/write heads
over data tracks on the media, to compensate for sudden jarring device
movements, thermal expansion, or changes in orientation. Degaussing
indiscriminately removes not only the stored data but also the servo
control data, and without the servo data the device is no longer able
to determine where data is to be read or written on the magnetic
medium. The medium must be low-level formatted to become usable again;
with modern hard drives, this is generally not possible without
manufacturer-specific and often model-specific service equipment.
~

--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/CAFakBwj=pS0AT98ZjzPF1uVJ_X4NH=isxr4w1pavamvofd_...@mail.gmail.com

Re: why would fdisk -l take so long?

2012-09-29 Thread Albretch Mueller

On 9/29/12, Martin Steigerwald mar...@lichtvoll.de wrote:
 Hi Albrecht!

 Am Samstag, 29. September 2012 schrieb Albretch Mueller:

 Two ideas:

 1) floppy device activated in BIOS while no floppy device present

 2) floppy emulation for USB mass storage activated in BIOS
~
 that was it! Reset, checked and solved!
~
 thank you Martin et al
 lbrtchx


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAFakBwgGtMMFAja1zP8_0X=1qg8Wsf_NKQF=q_cqpts2od1...@mail.gmail.com

Re: why would fdisk -l take so long?

2012-09-28 Thread lee

Because your disk is sleeping?
-- 
Debian testing amd64


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/87k3ve4pyk@yun.yagibdah.de

Re: why would fdisk -l take so long?

2012-09-28 Thread Jude DaShiell

Could it be a missing swap partition is slowing down drive access?  I 
don't know if you were connected to the internet when you did this run, 
but if so, you might disconnect from the internet and run fdisk -l again 
and compare speeds.  It could be fdisk is checking for remote disks as 
well but I don't know that for sure.  hth.



--- 
jude jdash...@shellworld.net Adobe fiend for failing to Flash



-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/alpine.bsf.2.01.1209280326270.86...@freire1.furyyjbeyq.arg

Re: why would fdisk -l take so long?

2012-09-28 Thread Karl E. Jorgensen

Hi

On Fri, Sep 28, 2012 at 03:52:26AM +0100, Albretch Mueller wrote:
 $ date; fdisk -l; date
 Thu Sep 27 22:48:21 UTC 2012
 
 Disk /dev/sda: 250.1 GB, 250059350016 bytes
 255 heads, 63 sectors/track, 30401 cylinders, total 488397168 sectors
 Units = sectors of 1 * 512 = 512 bytes
 Sector size (logical/physical): 512 bytes / 512 bytes
 I/O size (minimum/optimal): 512 bytes / 512 bytes
 Disk identifier: 0x00052568
 
Device Boot  Start End  Blocks   Id  System
 /dev/sda1  633908614419543041c  W95 FAT32 (LBA)
 /dev/sda2390861457814015919527007+   c  W95 FAT32 (LBA)
 /dev/sda378140160   23442047978140160   83  Linux
 /dev/sda4   234420480   488396799   1269881605  Extended
 /dev/sda5   234420543   3534259504728+   c  W95 FAT32 (LBA)
 /dev/sda6   353430063   372981104 9775521c  W95 FAT32 (LBA)
 /dev/sda7   372981168   392516144 9767488+   c  W95 FAT32 (LBA)
 /dev/sda8   392516208   43157015919526976   83  Linux
 /dev/sda9   431570223   441353744 4891761   83  Linux
 /dev/sda10  441353808   446253569 2449881   83  Linux
 /dev/sda11  446253633   44981 1783183+  83  Linux
 /dev/sda12  449822720   48839679919287040   83  Linux
 Thu Sep 27 22:48:59 UTC 2012

So... fdisk -l took 38 seconds - which is a bit much.

Question: How long does fdisk -l /dev/sda take?  (note: specifying
/dev/sda explicitly, rather than fdisk figure it out)

If this is a lot shorter, then your problem may be related to how
fdisk chooses a default device to look at, and the contents of
/proc/partitions becomes interesting...

Hope this help
-- 
Karl E. Jorgensen


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120928103027.GA7383@hawking

Re: why would fdisk -l take so long?

 Failing boot sector?
 Some other sector it has to read is failing?
 Check the logs. Try (from smartmontools):
~
 I don't know exactly which of your questions/suggestions running:
~
 smartctl -A /dev/sda | egrep -i sector|realloc
~
 relates to, but it didn't report any error message. Without grep I got:
~
$ sudo smartctl -A /dev/sda
smartctl 5.43 2012-05-01 r3539 [i686-linux-3.3.7] (local build)
Copyright (C) 2002-12 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF READ SMART DATA SECTION ===
SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME  FLAG VALUE WORST THRESH TYPE
UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate 0x000f   115   082   006Pre-fail
Always   -   96695847
  3 Spin_Up_Time0x0003   096   095   000Pre-fail
Always   -   0
  4 Start_Stop_Count0x0032   100   100   020Old_age
Always   -   365
  5 Reallocated_Sector_Ct   0x0033   100   100   036Pre-fail
Always   -   0
  7 Seek_Error_Rate 0x000f   075   060   030Pre-fail
Always   -   17316569764
  9 Power_On_Hours  0x0032   097   097   000Old_age
Always   -   2678
 10 Spin_Retry_Count0x0013   100   100   097Pre-fail
Always   -   0
 12 Power_Cycle_Count   0x0032   100   100   020Old_age
Always   -   395
187 Reported_Uncorrect  0x0032   100   100   000Old_age
Always   -   0
189 High_Fly_Writes 0x003a   100   100   000Old_age
Always   -   0
190 Airflow_Temperature_Cel 0x0022   059   045   045Old_age
Always   In_the_past 41 (Min/Max 40/41)
194 Temperature_Celsius 0x0022   041   055   000Old_age
Always   -   41 (0 23 0 0 0)
195 Hardware_ECC_Recovered  0x001a   078   057   000Old_age
Always   -   102323103
197 Current_Pending_Sector  0x0012   100   100   000Old_age
Always   -   0
198 Offline_Uncorrectable   0x0010   100   100   000Old_age
Offline  -   0
199 UDMA_CRC_Error_Count0x003e   200   200   000Old_age
Always   -   0
200 Multi_Zone_Error_Rate   0x   100   253   000Old_age
Offline  -   0
202 Data_Address_Mark_Errs  0x0032   100   253   000Old_age
Always   -   0

$

 Because your disk is sleeping?
~
 That I think may be the reason why. I did notice and check that it
always seems to happen after suspending my box, even if you unmount
all drives before, but what I don't get is that may people would be
complaining about that same problem. I have seem people complaining
all the time about hardware-related issues with suspending a box, but
not such delays and I always thought when you awaken your box after
suspending it, it should go to its initial state. Is there a way to
awaken all harddrive/partitions you are using?
~
 Could it be a missing swap partition is slowing down drive access?
~
$ cat /proc/swaps
FilenameTypeSizeUsedPriority
/dev/zram0  partition   1942352 0   0
~
 I don't know if you were connected to the internet
~
 I wasn't, but I have notice weird things happening when I am and, of
course, my work horse box I don't connect to the Internet at all
~
 So... fdisk -l took 38 seconds - which is a bit much.
~
 Yep! Exactly 38 seconds!?!
~
$ date; fdisk -l; date
Fri Sep 28 07:13:45 UTC 2012

Disk /dev/sda: 250.1 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders, total 488397168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00052568

   Device Boot  Start End  Blocks   Id  System
/dev/sda1  633908614419543041c  W95 FAT32 (LBA)
/dev/sda2390861457814015919527007+   c  W95 FAT32 (LBA)
/dev/sda378140160   23442047978140160   83  Linux
/dev/sda4   234420480   488396799   1269881605  Extended
/dev/sda5   234420543   3534259504728+   c  W95 FAT32 (LBA)
/dev/sda6   353430063   372981104 9775521c  W95 FAT32 (LBA)
/dev/sda7   372981168   392516144 9767488+   c  W95 FAT32 (LBA)
/dev/sda8   392516208   43157015919526976   83  Linux
/dev/sda9   431570223   441353744 4891761   83  Linux
/dev/sda10  441353808   446253569 2449881   83  Linux
/dev/sda11  446253633   44981 1783183+  83  Linux
/dev/sda12  449822720   48839679919287040   83  Linux
Fri Sep 28 07:14:23 UTC 2012
knoppix@Microknoppix:~$ date; fdisk -l; date
Fri Sep 28 07:14:41 UTC 2012

Disk /dev/sda: 250.1 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders, total 488397168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk

Re: why would fdisk -l take so long?

2012-09-28 Thread Dom


On 28/09/12 11:30, Karl E. Jorgensen wrote:

Hi

On Fri, Sep 28, 2012 at 03:52:26AM +0100, Albretch Mueller wrote:

$ date; fdisk -l; date
Thu Sep 27 22:48:21 UTC 2012

Disk /dev/sda: 250.1 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders, total 488397168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00052568

Device Boot  Start End  Blocks   Id  System
/dev/sda1  633908614419543041c  W95 FAT32 (LBA)
/dev/sda2390861457814015919527007+   c  W95 FAT32 (LBA)
/dev/sda378140160   23442047978140160   83  Linux
/dev/sda4   234420480   488396799   1269881605  Extended
/dev/sda5   234420543   3534259504728+   c  W95 FAT32 (LBA)
/dev/sda6   353430063   372981104 9775521c  W95 FAT32 (LBA)
/dev/sda7   372981168   392516144 9767488+   c  W95 FAT32 (LBA)
/dev/sda8   392516208   43157015919526976   83  Linux
/dev/sda9   431570223   441353744 4891761   83  Linux
/dev/sda10  441353808   446253569 2449881   83  Linux
/dev/sda11  446253633   44981 1783183+  83  Linux
/dev/sda12  449822720   48839679919287040   83  Linux
Thu Sep 27 22:48:59 UTC 2012


So... fdisk -l took 38 seconds - which is a bit much.

Question: How long does fdisk -l /dev/sda take?  (note: specifying
/dev/sda explicitly, rather than fdisk figure it out)

If this is a lot shorter, then your problem may be related to how
fdisk chooses a default device to look at, and the contents of
/proc/partitions becomes interesting...

Hope this help


Also, try using time fdisk -l. The time command gives a slightly 
better idea of where the time is being spent that just using date before 
and after.


--
Dom


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Archive: http://lists.debian.org/50659554.5060...@rpdom.net

Re: why would fdisk -l take so long?

2012-09-28 Thread Dom


On 28/09/12 12:27, Albretch Mueller wrote:

Failing boot sector?
Some other sector it has to read is failing?
Check the logs. Try (from smartmontools):

~
  I don't know exactly which of your questions/suggestions running:
~
  smartctl -A /dev/sda | egrep -i sector|realloc
~
  relates to, but it didn't report any error message. Without grep I got:
~
$ sudo smartctl -A /dev/sda
smartctl 5.43 2012-05-01 r3539 [i686-linux-3.3.7] (local build)
Copyright (C) 2002-12 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF READ SMART DATA SECTION ===
SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME  FLAG VALUE WORST THRESH TYPE
UPDATED  WHEN_FAILED RAW_VALUE
   1 Raw_Read_Error_Rate 0x000f   115   082   006Pre-fail
Always   -   96695847


Ok, your disk is dying. The Raw_Read_Error_Rate should be zero, or very low.


   7 Seek_Error_Rate 0x000f   075   060   030Pre-fail
Always   -   17316569764


That is also seriously bad.


   9 Power_On_Hours  0x0032   097   097   000Old_age
Always   -   2678


Is this a fairly new disk? Only 2678 hours use.


195 Hardware_ECC_Recovered  0x001a   078   057   000Old_age
Always   -   102323103


It looks like many errors have been recovered using ECC, so you probably 
wouldn't have noticed those.


It *is* possible that smartctl is mis-interpretting the status of your 
disk, but given your slow fdisk command I suspect not.


Time to backup, backup, backup, buy a new disk and transfer the data 
over asap.


--
Dom


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Archive: http://lists.debian.org/506596df.7030...@rpdom.net

Re: why would fdisk -l take so long?

2012-09-28 Thread Jon Dowland

On Fri, Sep 28, 2012 at 01:23:59PM +0100, Dom wrote:
 It *is* possible that smartctl is mis-interpretting the status of
 your disk, but given your slow fdisk command I suspect not.
 
 Time to backup, backup, backup, buy a new disk and transfer the data
 over asap.

YES to backup, but it's worth changing your SATA cable before investing
in a new disk, or at least ensuring your current one is seated properly.
Try to measure the *rate* that Hardware_ECC_Recovered is increasing over
a set period of time, check/replace cable, measure again.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120928125241.GD5503@debian

Re: why would fdisk -l take so long?

2012-09-28 Thread lee

Albretch Mueller lbrt...@gmail.com writes:

 Because your disk is sleeping?
 ~
  That I think may be the reason why. I did notice and check that it
 always seems to happen after suspending my box, even if you unmount
 all drives before, but what I don't get is that may people would be
 complaining about that same problem. I have seem people complaining
 all the time about hardware-related issues with suspending a box, but
 not such delays and I always thought when you awaken your box after
 suspending it, it should go to its initial state.

It should go back to where you suspended or hibernated it, and it
doesn't.  If your disk is sleeping because its power management decided
to turn it off, it can take a while for it to wake up.  It might be a
good idea to check the power management settings with something like
hdparm.

 Is there a way to awaken all harddrive/partitions you are using?

fdisk -l seems to do that.  However, it's difficult to reasonably put to
sleep a disk which has partitions on it that are mounted, and it's very
questionable if it's reasonable to do so (unless it's an SSD maybe, if
those can be put to sleep at all).


How much money and energy do you actually save by putting disks to sleep
when you consider the possibility of increased wear and perhaps having
to replace them sooner than would otherwise be necessary?  Are there any
good studies aimed to answer this question?


-- 
Debian testing amd64


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/87txui2sgj@yun.yagibdah.de

Re: why would fdisk -l take so long?

 I just backed up all the data
~
 Yet, it seems something else may be (also?) somehow relating to those
delays. Since I start knoppix 7.0.2 as:
~
 knoppix no3d fromhd=/dev/sda9
~
 could these issues/problems relate to the fact that /dev/sda9 is
mounted read-only and knoppix keeps it to itself throughout its
running time?
~
 See bellow the fdisk -l timings when I run knoppix from the dvd
~
 lbrtchx

// __ fdisk -l

$ date; X=`(time fdisk -l) 21 | grep real`; echo $X
Fri Sep 28 10:20:26 UTC 2012
real 0m0.014s
$ date; X=`(time fdisk -l) 21 | grep real`; echo $X
Fri Sep 28 10:20:28 UTC 2012
real 0m0.012s
$ date; X=`(time fdisk -l) 21 | grep real`; echo $X
Fri Sep 28 10:20:29 UTC 2012
real 0m0.012s
$ date; X=`(time fdisk -l) 21 | grep real`; echo $X
Fri Sep 28 10:20:29 UTC 2012
real 0m0.013s

// __ fdisk -l /dev/sda

$ date; X=`(time fdisk -l /dev/sda) 21 | grep real`; echo $X
Fri Sep 28 10:20:35 UTC 2012
real 0m0.002s
$ date; X=`(time fdisk -l /dev/sda) 21 | grep real`; echo $X
Fri Sep 28 10:20:36 UTC 2012
real 0m0.002s
$ date; X=`(time fdisk -l /dev/sda) 21 | grep real`; echo $X
Fri Sep 28 10:20:37 UTC 2012
real 0m0.002s
$ date; X=`(time fdisk -l /dev/sda) 21 | grep real`; echo $X
Fri Sep 28 10:20:38 UTC 2012
real 0m0.002s


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAFakBwhnYgFAoEuuCFf-3oCsKJ+HiN=y4cgxcpefhnwm_vb...@mail.gmail.com

Re: why would fdisk -l take so long?

2012-09-28 Thread Dom


On 28/09/12 13:52, Jon Dowland wrote:

On Fri, Sep 28, 2012 at 01:23:59PM +0100, Dom wrote:

It *is* possible that smartctl is mis-interpretting the status of
your disk, but given your slow fdisk command I suspect not.

Time to backup, backup, backup, buy a new disk and transfer the data
over asap.


YES to backup, but it's worth changing your SATA cable before investing
in a new disk, or at least ensuring your current one is seated properly.
Try to measure the *rate* that Hardware_ECC_Recovered is increasing over
a set period of time, check/replace cable, measure again.



Good points, which I did think of *after* I'd posted my comment.

Good catch. :-)

--
Dom


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Archive: http://lists.debian.org/5065bdf9.1040...@rpdom.net

Re: why would fdisk -l take so long?

 in a box in which I use the fromhd stanza using a disk which smartclt
reports as being fine the results before and after suspending are the
same
~
 this is what the dying disk reports
~
$ date; X=`(time fdisk -l) 21 | grep real`; echo $X
Fri Sep 28 10:52:58 UTC 2012
real 0m0.191s
$ date; X=`(time fdisk -l) 21 | grep real`; echo $X
Fri Sep 28 10:52:59 UTC 2012
real 0m0.055s
$ date; X=`(time fdisk -l) 21 | grep real`; echo $X
Fri Sep 28 10:53:00 UTC 2012
real 0m0.052s
~
 it then stabilize around 0.050s
~
 For the good ones time consistently reports 0.003s
~
 the thing is (for more than one reason) I use a crappy box to go online
~
 Also, any comprehensive documentation regarding hd's health?
smartctl's is OK to get by, but you are telling me about logs I don't
know about and I would like to know more about the physics of it
~
 lbrtchx


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAFakBwjq=rD5G_SRLx=j7wakoctyp2nua9xgk-yeygexds1...@mail.gmail.com

Re: why would fdisk -l take so long?

2012-09-28 Thread Neal Murphy

On Friday, September 28, 2012 08:23:59 AM Dom wrote:
 1 Raw_Read_Error_Rate 0x000f   115   082   006Pre-fail
  
  Always   -   96695847
 
 Ok, your disk is dying. The Raw_Read_Error_Rate should be zero, or very
 low.


Not necessarily. At least one disk mfr (Seagate?) puts large values in these 
fields. Cause me a few moments' consternation the first time I saw it on my 
own drives


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201209281448.32568.neal.p.mur...@alum.wpi.edu

Re: why would fdisk -l take so long?

  1 Raw_Read_Error_Rate 0x000f   115   082   006Pre-fail
  
   Always   -   96695847
 
  Ok, your disk is dying. The Raw_Read_Error_Rate should be zero, or very
  low.

 Not necessarily. At least one disk mfr (Seagate?) puts large values in these
 fields. Cause me a few moments' consternation the first time I saw it on my
 own drives
~
 Indeed! Something spooky may be going on. After taking the drive
out in order to back it up, I have run fdisk -l with no disk and
sometimes with a pen drive inserted and these bellow are the results I
got.
~
 Don't you find all of this downright weird?
~
 I don't believe in ghosts ;-) What do you think I could do to
troubleshoot this further?
~
 lbrtchx
~

$ time fdisk -l

Disk /dev/sda: 8006 MB, 8006926336 bytes
39 heads, 39 sectors/track, 10281 cylinders, total 15638528 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xc3072e18

   Device Boot  Start End  Blocks   Id  System
/dev/sda1   *806415638527 7815232c  W95 FAT32 (LBA)

real0m38.106s
user0m0.000s
sys 0m0.000s

$ mount /media/sda1

$ time fdisk -l
konqueror(2828)/kdecore (KLibrary) findLibraryInternal: plugins should
not have a 'lib' prefix: libkhtmlpart.so
konqueror(2828)/kdecore (KLibrary) kde4Factory: The library
/usr/lib/kde4/khtml_kget.so does not offer a qt_plugin_instance
function.

Disk /dev/sda: 8006 MB, 8006926336 bytes
39 heads, 39 sectors/track, 10281 cylinders, total 15638528 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xc3072e18

   Device Boot  Start End  Blocks   Id  System
/dev/sda1   *806415638527 7815232c  W95 FAT32 (LBA)

real0m38.107s
user0m0.000s
sys 0m0.000s

$ sudo umount /media/sda1

$ time fdisk -l

real0m38.314s
user0m0.000s
sys 0m0.000s

$ _DT=`date +%Y%m%d%H%M%S`; dmesg  dmesg_${_DT}.log

$ date; time fdisk -l; date
Fri Sep 28 20:51:09 UTC 2012

real0m38.097s
user0m0.000s
sys 0m0.000s
Fri Sep 28 20:51:47 UTC 2012

$ _DT=`date +%Y%m%d%H%M%S`; dmesg  dmesg_${_DT}.log

$ ls -l dmesg_*.log
-rw-r--r-- 1 knoppix knoppix 15493 Sep 28 20:50 dmesg_20120928205055.log
-rw-r--r-- 1 knoppix knoppix 15490 Sep 28 20:51 dmesg_20120928205157.log

$ wc -l dmesg_*.log
  298 dmesg_20120928205055.log
  299 dmesg_20120928205157.log
  597 total

$ diff dmesg_20120928205055.log dmesg_20120928205157.log
1c1
 090] ehci_hcd :00:13.2: wake-up capability enabled by ACPI
---
 PI
298a299
 [26607.877660] end_request: I/O error, dev fd0, sector 0
$

$ cat dmesg_20120928205055.log
090] ehci_hcd :00:13.2: wake-up capability enabled by ACPI
[ 4008.172988] ohci_hcd :00:13.1: wake-up capability enabled by ACPI
[ 4008.173025] ohci_hcd :00:13.0: wake-up capability enabled by ACPI
[ 4008.173066] PM: late suspend of devices complete after 13.416 msecs
[ 4008.173239] ACPI: Preparing to enter system sleep state S3
[ 4008.173322] PM: Saving platform NVS memory
[ 4008.173361] Disabling non-boot CPUs ...
[ 4008.173361] ACPI: Low-level resume complete
[ 4008.173361] PM: Restoring platform NVS memory
[ 4008.173361] ACPI: Waking up from system sleep state S3
[ 4008.173361] ohci_hcd :00:13.0: wake-up capability disabled by ACPI
[ 4008.173361] ohci_hcd :00:13.1: wake-up capability disabled by ACPI
[ 4008.173361] ehci_hcd :00:13.2: wake-up capability disabled by ACPI
[ 4008.173361] PM: early resume of devices complete after 0.718 msecs
[ 4008.176363]  pci:00: wake-up capability disabled by ACPI
[ 4008.176442] radeon :01:00.0: f529d800 unpin not necessary
[ 4008.178326] serial 00:08: activated
[ 4008.178771] parport_pc 00:09: activated
[ 4008.189307] [drm] radeon: 1 quad pipes, 1 z pipes initialized.
[ 4008.201519] [drm] PCIE GART of 512M enabled (table at 0x0004).
[ 4008.201531] radeon :01:00.0: WB enabled
[ 4008.201534] [drm] fence driver on ring 0 use gpu addr 0x1000
and cpu addr 0xff885000
[ 4008.201621] [drm] radeon: ring at 0x10001000
[ 4008.201651] [drm] ring test succeeded in 7 usecs
[ 4008.201667] [drm] ib test succeeded in 0 usecs
[ 4008.496304] ata2: SATA link down (SStatus 0 SControl 300)
[ 4008.496352] ata1: SATA link down (SStatus 0 SControl 300)
[ 4008.600352] ata3.00: ACPI cmd ef/03:0c:00:00:00:a0 (SET FEATURES)
filtered out
[ 4008.600356] ata3.00: ACPI cmd ef/03:42:00:00:00:a0 (SET FEATURES)
filtered out
[ 4008.600360] ata3.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE
LOCK) filtered out
[ 4008.606911] ata3.00: configured for UDMA/33
[ 4013.233591] psmouse serio1: hgpk: ID: 10 00 64
[ 4015.679626]
[ 4015.679628] floppy driver state
[ 4015.679629] ---
[ 4015.679637] now=1114704 last interrupt=1109734 diff=4970 last
called handler=recal_interrupt
[ 4015.679639

Re: why would fdisk -l take so long?

2012-09-28 Thread Neal Murphy

On Friday, September 28, 2012 08:58:47 PM Albretch Mueller wrote:
   1 Raw_Read_Error_Rate 0x000f   115   082   006Pre-fail

Always   -   96695847
   
   Ok, your disk is dying. The Raw_Read_Error_Rate should be zero, or very
   low.
  
  Not necessarily. At least one disk mfr (Seagate?) puts large values in
  these fields. Cause me a few moments' consternation the first time I saw
  it on my own drives
 
 ~
  Indeed! Something spooky may be going on. After taking the drive
 out in order to back it up, I have run fdisk -l with no disk and
 sometimes with a pen drive inserted and these bellow are the results I
 got.
 ~
  Don't you find all of this downright weird?

Not yet.

 ~
  I don't believe in ghosts ;-) What do you think I could do to
 troubleshoot this further?

Have you tried fdisk -l /dev/sda? I think you did, to no avail. It might be 
searching some other drive or type of drive first that is slow to respond.

Check the drive's power state:
  hdparm -C /dev/sda

How about:
  tail -f /var/log/messages  # In a separate window
  time dd if=/dev/sda of=/dev/null bs=1024k count=1
  time fdisk -l /dev/sda
to see if the drive is dozing.

Or (from hdparm's man page:  Disable  the  automatic power-saving
function of certain Seagate drives...):
  hdparm -Z /dev/sda


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201209282134.29827.neal.p.mur...@alum.wpi.edu

Re: why would fdisk -l take so long?