Re: [ARMedslack] File system on my Freeagent Dockstar got corrupted
This is probably not the cause of your problems but it's something you want to keep in mind anyway: Running non flash oriented journaled file-systems on flash based devices can ware them out very quickly especially if you are using MLB flash based device with a typical 1 cycle rewrite capability. To minimize damage on flash devices at least make sure you mount the file-system with noatime option to avoid rewriting an entire erase block just because something accessed a file. Best regards David --- Ven 6/5/11, Thorsten Mühlfelder thenk...@gmx.de ha scritto: Da: Thorsten Mühlfelder thenk...@gmx.de Oggetto: Re: [ARMedslack] File system on my Freeagent Dockstar got corrupted A: armedslack@lists.armedslack.org Data: Venerdì 6 maggio 2011, 01:29 Am Fri, 18 Feb 2011 09:20:44 + (GMT) schrieb Stuart Winter m-li...@biscuit.org.uk: The problem could be anywhere -- perhaps take out the disc from the usb caddy and put it onto a bare IDE interface and try SMART? The disc or USB caddy could be faulty. I'm quite sure now that the USB disk is faulty. After running for some month now a similiar error occured: Dockstar was still running, the DSL connection was up and it did route to the internet. But all daemons apparently have crashed: no ssh login anymore, no dhcpd service and http server crashed, too. When I plug the disk to my PC or notebook I'm getting these messages in /var/log/messages in an endless loop: ay 5 20:54:33 pinkfloyd kernel: [ 440.520511] sd 15:0:0:0: [sdd] Attached SCSI disk May 5 20:54:36 pinkfloyd kernel: [ 442.989369] sd 15:0:0:0: [sdd] Unhandled sense code May 5 20:54:36 pinkfloyd kernel: [ 442.989373] sd 15:0:0:0: [sdd] Result: hostbyte=0x00 driverbyte=0x08 May 5 20:54:36 pinkfloyd kernel: [ 442.989376] sd 15:0:0:0: [sdd] Sense Key : 0x3 [current] May 5 20:54:36 pinkfloyd kernel: [ 442.989379] sd 15:0:0:0: [sdd] ASC=0x11 ASCQ=0x0 May 5 20:54:36 pinkfloyd kernel: [ 442.989381] sd 15:0:0:0: [sdd] CDB: cdb[0]=0x28: 28 00 00 41 73 4c 00 00 07 00 May 5 20:54:39 pinkfloyd kernel: [ 445.794887] sd 15:0:0:0: [sdd] Unhandled sense code May 5 20:54:39 pinkfloyd kernel: [ 445.794890] sd 15:0:0:0: [sdd] Result: hostbyte=0x00 driverbyte=0x08 May 5 20:54:39 pinkfloyd kernel: [ 445.794893] sd 15:0:0:0: [sdd] Sense Key : 0x3 [current] May 5 20:54:39 pinkfloyd kernel: [ 445.794896] sd 15:0:0:0: [sdd] ASC=0x11 ASCQ=0x0 May 5 20:54:39 pinkfloyd kernel: [ 445.794898] sd 15:0:0:0: [sdd] CDB: cdb[0]=0x28: 28 00 00 41 73 4c 00 00 07 00 -- Thorsten Mühlfelder Salix OS: www.salixos.org ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] File system on my Freeagent Dockstar got corrupted
Am Fri, 6 May 2011 07:59:14 +0100 (BST) schrieb Davide louigi...@yahoo.it: This is probably not the cause of your problems but it's something you want to keep in mind anyway: Running non flash oriented journaled file-systems on flash based devices can ware them out very quickly No that's not the problem because this is a Seagate Freeagent Go hard disk. especially if you are using MLB flash based device with a typical 1 cycle rewrite capability. To minimize damage on flash devices at least make sure you mount the file-system with noatime option to avoid rewriting an entire erase block just because something accessed a file. The error message indicates that the USB part of the hard disk is broken. Unfortunately I cannot open the USB case without damaging a warranty seal, so I cannot save my data. I have to find a Windows PC now to run the Seagate test tools. This is mandatory for a warranty request. --- Ven 6/5/11, Thorsten Mühlfelder thenk...@gmx.de ha scritto: Da: Thorsten Mühlfelder thenk...@gmx.de Oggetto: Re: [ARMedslack] File system on my Freeagent Dockstar got corrupted A: armedslack@lists.armedslack.org Data: Venerdì 6 maggio 2011, 01:29 Am Fri, 18 Feb 2011 09:20:44 + (GMT) schrieb Stuart Winter m-li...@biscuit.org.uk: The problem could be anywhere -- perhaps take out the disc from the usb caddy and put it onto a bare IDE interface and try SMART? The disc or USB caddy could be faulty. I'm quite sure now that the USB disk is faulty. After running for some month now a similiar error occured: Dockstar was still running, the DSL connection was up and it did route to the internet. But all daemons apparently have crashed: no ssh login anymore, no dhcpd service and http server crashed, too. When I plug the disk to my PC or notebook I'm getting these messages in /var/log/messages in an endless loop: ay 5 20:54:33 pinkfloyd kernel: [ 440.520511] sd 15:0:0:0: [sdd] Attached SCSI disk May 5 20:54:36 pinkfloyd kernel: [ 442.989369] sd 15:0:0:0: [sdd] Unhandled sense code May 5 20:54:36 pinkfloyd kernel: [ 442.989373] sd 15:0:0:0: [sdd] Result: hostbyte=0x00 driverbyte=0x08 May 5 20:54:36 pinkfloyd kernel: [ 442.989376] sd 15:0:0:0: [sdd] Sense Key : 0x3 [current] May 5 20:54:36 pinkfloyd kernel: [ 442.989379] sd 15:0:0:0: [sdd] ASC=0x11 ASCQ=0x0 May 5 20:54:36 pinkfloyd kernel: [ 442.989381] sd 15:0:0:0: [sdd] CDB: cdb[0]=0x28: 28 00 00 41 73 4c 00 00 07 00 May 5 20:54:39 pinkfloyd kernel: [ 445.794887] sd 15:0:0:0: [sdd] Unhandled sense code May 5 20:54:39 pinkfloyd kernel: [ 445.794890] sd 15:0:0:0: [sdd] Result: hostbyte=0x00 driverbyte=0x08 May 5 20:54:39 pinkfloyd kernel: [ 445.794893] sd 15:0:0:0: [sdd] Sense Key : 0x3 [current] May 5 20:54:39 pinkfloyd kernel: [ 445.794896] sd 15:0:0:0: [sdd] ASC=0x11 ASCQ=0x0 May 5 20:54:39 pinkfloyd kernel: [ 445.794898] sd 15:0:0:0: [sdd] CDB: cdb[0]=0x28: 28 00 00 41 73 4c 00 00 07 00 -- Thorsten Mühlfelder Salix OS: www.salixos.org ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack -- Thorsten Mühlfelder Salix OS: www.salixos.org ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] File system on my Freeagent Dockstar got corrupted
Am Fri, 18 Feb 2011 09:20:44 + (GMT) schrieb Stuart Winter m-li...@biscuit.org.uk: The problem could be anywhere -- perhaps take out the disc from the usb caddy and put it onto a bare IDE interface and try SMART? The disc or USB caddy could be faulty. I'm quite sure now that the USB disk is faulty. After running for some month now a similiar error occured: Dockstar was still running, the DSL connection was up and it did route to the internet. But all daemons apparently have crashed: no ssh login anymore, no dhcpd service and http server crashed, too. When I plug the disk to my PC or notebook I'm getting these messages in /var/log/messages in an endless loop: ay 5 20:54:33 pinkfloyd kernel: [ 440.520511] sd 15:0:0:0: [sdd] Attached SCSI disk May 5 20:54:36 pinkfloyd kernel: [ 442.989369] sd 15:0:0:0: [sdd] Unhandled sense code May 5 20:54:36 pinkfloyd kernel: [ 442.989373] sd 15:0:0:0: [sdd] Result: hostbyte=0x00 driverbyte=0x08 May 5 20:54:36 pinkfloyd kernel: [ 442.989376] sd 15:0:0:0: [sdd] Sense Key : 0x3 [current] May 5 20:54:36 pinkfloyd kernel: [ 442.989379] sd 15:0:0:0: [sdd] ASC=0x11 ASCQ=0x0 May 5 20:54:36 pinkfloyd kernel: [ 442.989381] sd 15:0:0:0: [sdd] CDB: cdb[0]=0x28: 28 00 00 41 73 4c 00 00 07 00 May 5 20:54:39 pinkfloyd kernel: [ 445.794887] sd 15:0:0:0: [sdd] Unhandled sense code May 5 20:54:39 pinkfloyd kernel: [ 445.794890] sd 15:0:0:0: [sdd] Result: hostbyte=0x00 driverbyte=0x08 May 5 20:54:39 pinkfloyd kernel: [ 445.794893] sd 15:0:0:0: [sdd] Sense Key : 0x3 [current] May 5 20:54:39 pinkfloyd kernel: [ 445.794896] sd 15:0:0:0: [sdd] ASC=0x11 ASCQ=0x0 May 5 20:54:39 pinkfloyd kernel: [ 445.794898] sd 15:0:0:0: [sdd] CDB: cdb[0]=0x28: 28 00 00 41 73 4c 00 00 07 00 -- Thorsten Mühlfelder Salix OS: www.salixos.org ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
