You are not logged in.

Pages: 1

#1 2012-10-28 23:02:38

Radfahrer
Member
Registered: 2008-04-29
Posts: 31

[Solved] Hard Drive failure ?

Hello everyone,
recently I am having problems with my ext4 home partition. My laptop freezes for some seconds and then remounts my home partion in read only mode. After rebooting I have lots of errors in that partition that can be repaired with fsck. Here is the output of dmesg

[164266.343653] ata1.00: exception Emask 0x0 SAct 0xf SErr 0x0 action 0x6 frozen
[164266.343662] ata1.00: failed command: WRITE FPDMA QUEUED
[164266.343671] ata1.00: cmd 61/08:00:b8:02:47/00:00:13:00:00/40 tag 0 ncq 4096 out
         res 40/00:00:00:4f:c2/00:00:00:00:00/40 Emask 0x4 (timeout)
[164266.343676] ata1.00: status: { DRDY }
[164266.343680] ata1.00: failed command: WRITE FPDMA QUEUED
[164266.343688] ata1.00: cmd 61/80:08:c0:02:47/00:00:13:00:00/40 tag 1 ncq 65536 out
         res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[164266.343692] ata1.00: status: { DRDY }
[164266.343702] ata1.00: failed command: READ FPDMA QUEUED
[164266.343709] ata1.00: cmd 60/00:10:e8:29:30/01:00:18:00:00/40 tag 2 ncq 131072 in
         res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[164266.343713] ata1.00: status: { DRDY }
[164266.343716] ata1.00: failed command: READ FPDMA QUEUED
[164266.343724] ata1.00: cmd 60/00:18:e8:2a:30/01:00:18:00:00/40 tag 3 ncq 131072 in
         res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[164266.343727] ata1.00: status: { DRDY }
[164266.343734] ata1: hard resetting link
[164267.890306] ata1: SATA link down (SStatus 0 SControl 300)
[164267.890318] ata1.00: link offline, clearing class 1 to NONE
[164267.900795] ata1: hard resetting link
[164269.713642] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[164269.715299] ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
[164269.715305] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
[164269.717562] ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
[164269.717568] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
[164269.717889] ata1.00: configured for UDMA/100
[164269.730308] ata1.00: device reported invalid CHS sector 0
[164269.730314] ata1.00: device reported invalid CHS sector 0
[164269.730319] ata1.00: device reported invalid CHS sector 0
[164269.730323] ata1.00: device reported invalid CHS sector 0
[164269.730339] sd 0:0:0:0: [sda]  
[164269.730342] Result: hostbyte=0x00 driverbyte=0x08
[164269.730345] sd 0:0:0:0: [sda]  
[164269.730347] Sense Key : 0xb [current] [descriptor]
[164269.730352] Descriptor sense data with sense descriptors (in hex):
[164269.730355]         72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00 
[164269.730368]         00 00 00 00 
[164269.730375] sd 0:0:0:0: [sda]  
[164269.730377] ASC=0x0 ASCQ=0x0
[164269.730381] sd 0:0:0:0: [sda] CDB: 
[164269.730383] cdb[0]=0x2a: 2a 00 13 47 02 b8 00 00 08 00
[164269.730395] end_request: I/O error, dev sda, sector 323420856
[164269.730401] Buffer I/O error on device sda4, logical block 37281111
[164269.730404] lost page write due to I/O error on sda4
[164269.730422] sd 0:0:0:0: [sda]  
[164269.730424] Result: hostbyte=0x00 driverbyte=0x08
[164269.730427] sd 0:0:0:0: [sda]  
[164269.730429] Sense Key : 0xb [current] [descriptor]
[164269.730433] Descriptor sense data with sense descriptors (in hex):
[164269.730436]         72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00 
[164269.730449]         00 00 00 00 
[164269.730455] sd 0:0:0:0: [sda]  
[164269.730457] ASC=0x0 ASCQ=0x0
[164269.730461] sd 0:0:0:0: [sda] CDB: 
[164269.730463] cdb[0]=0x2a: 2a 00 13 47 02 c0 00 00 80 00
[164269.730473] end_request: I/O error, dev sda, sector 323420864
[164269.730494] sd 0:0:0:0: [sda]  
[164269.730497] Result: hostbyte=0x00 driverbyte=0x08
[164269.730500] sd 0:0:0:0: [sda]  
[164269.730502] Sense Key : 0xb [current] [descriptor]
[164269.730506] Descriptor sense data with sense descriptors (in hex):
[164269.730509]         72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00 
[164269.730522]         00 00 00 00 
[164269.730528] sd 0:0:0:0: [sda]  
[164269.730530] ASC=0x0 ASCQ=0x0
[164269.730534] sd 0:0:0:0: [sda] CDB: 
[164269.730536] cdb[0]=0x28: 28 00 18 30 29 e8 00 01 00 00
[164269.730547] end_request: I/O error, dev sda, sector 405809640
[164269.730568] sd 0:0:0:0: [sda]  
[164269.730571] Result: hostbyte=0x00 driverbyte=0x08
[164269.730574] sd 0:0:0:0: [sda]  
[164269.730576] Sense Key : 0xb [current] [descriptor]
[164269.730580] Descriptor sense data with sense descriptors (in hex):
[164269.730582]         72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00 
[164269.730595]         00 00 00 00 
[164269.730601] sd 0:0:0:0: [sda]  
[164269.730603] ASC=0x0 ASCQ=0x0
[164269.730607] sd 0:0:0:0: [sda] CDB: 
[164269.730609] cdb[0]=0x28: 28 00 18 30 2a e8 00 01 00 00
[164269.730619] end_request: I/O error, dev sda, sector 405809896
[164269.730638] ata1: EH complete
[164269.730715] Aborting journal on device sda4-8.
[164269.730767] EXT4-fs error (device sda4) in ext4_reserve_inode_write:4550: Journal has aborted
[164269.738009] EXT4-fs error (device sda4) in ext4_orphan_add:2420: Journal has aborted
[164269.738401] EXT4-fs error (device sda4) in ext4_reserve_inode_write:4550: Journal has aborted
[164269.738845] EXT4-fs error (device sda4) in ext4_ext_truncate:4308: Journal has aborted
[164269.739332] EXT4-fs error (device sda4) in ext4_dirty_inode:4669: Journal has aborted
[164269.740703] EXT4-fs error (device sda4): ext4_journal_start_sb:348: 
[164269.740710] EXT4-fs error (device sda4): ext4_journal_start_sb:348: 
[164269.740711] Detected aborted journal

[164269.740716] EXT4-fs (sda4): Remounting filesystem read-only
[164269.740719] Detected aborted journal
[164270.006901] EXT4-fs error (device sda4) in ext4_da_writepages:2398: IO failure
[164270.081804] EXT4-fs (sda4): ext4_da_writepages: jbd2_start: 2862 pages, ino 12062503; err -30

Is this a sign of hard drive failure?
Thanks for any hints.

Last edited by Radfahrer (2012-11-01 09:35:15)

Offline

#2 2012-10-29 00:00:25

Trilby
Inspector Parrot
Registered: 2011-11-29
Posts: 29,546
Website

Re: [Solved] Hard Drive failure ?

Could it be the ext4 bug?

"UNIX is simple and coherent..." - Dennis Ritchie, "GNU's Not UNIX" -  Richard Stallman

Offline

#3 2012-10-29 00:03:08

cfr
Member
From: Cymru
Registered: 2011-11-27
Posts: 7,134

Re: [Solved] Hard Drive failure ?

If you haven't already, back everything you need up.

Try smartmontools to get SMART information about your disk. You should be able to get both various bits of data and run some tests. (This is if you are not using smartmontools already but I'm assuming not since you've not posted output.)

Re. Trilby's question: what is your disk set up? What mount options do you use for your home partition?

Last edited by cfr (2012-10-29 00:05:48)

CLI Paste | How To Ask Questions

Arch Linux | x86_64 | GPT | EFI boot | refind | stub loader | systemd | LVM2 on LUKS
Lenovo x270 | Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz | Intel Wireless 8265/8275 | US keyboard w/ Euro | 512G NVMe INTEL SSDPEKKF512G7L

Offline

#4 2012-10-29 08:45:25

Radfahrer
Member
Registered: 2008-04-29
Posts: 31

Re: [Solved] Hard Drive failure ?

I dont't think it is the ext4 bug, since the problem already appeared before the bug was introduced.
Mount options from fstab are:

/dev/sda4               /home           ext4            rw,relatime,data=ordered        0 2

Here is the output of smartctl -a /dev/sda that shows some errors I think

smartctl 6.0 2012-10-10 r3643 [x86_64-linux-3.6.3-1-ARCH] (local build)
Copyright (C) 2002-12, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Seagate Momentus 5400.6
Device Model:     ST9320325AS
Serial Number:    5VD328BV
LU WWN Device Id: 5 000c50 021aa19f6
Firmware Version: 0020LVM1
User Capacity:    320.072.933.376 bytes [320 GB]
Sector Size:      512 bytes logical/physical
Rotation Rate:    5400 rpm
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ATA8-ACS T13/1699-D revision 4
SATA Version is:  SATA 2.6, 3.0 Gb/s (current: 3.0 Gb/s)
Local Time is:    Mon Oct 29 09:43:34 2012 CET
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x00)	Offline data collection activity
					was never started.
					Auto Offline Data Collection: Disabled.
Self-test execution status:      (   0)	The previous self-test routine completed
					without error or no self-test has ever 
					been run.
Total time to complete Offline 
data collection: 		(    0) seconds.
Offline data collection
capabilities: 			 (0x73) SMART execute Offline immediate.
					Auto Offline data collection on/off support.
					Suspend Offline collection upon new
					command.
					No Offline surface scan supported.
					Self-test supported.
					Conveyance Self-test supported.
					Selective Self-test supported.
SMART capabilities:            (0x0003)	Saves SMART data before entering
					power-saving mode.
					Supports SMART auto save timer.
Error logging capability:        (0x01)	Error logging supported.
					General Purpose Logging supported.
Short self-test routine 
recommended polling time: 	 (   1) minutes.
Extended self-test routine
recommended polling time: 	 (  99) minutes.
Conveyance self-test routine
recommended polling time: 	 (   2) minutes.
SCT capabilities: 	       (0x103b)	SCT Status supported.
					SCT Error Recovery Control supported.
					SCT Feature Control supported.
					SCT Data Table supported.

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   118   077   034    Pre-fail  Always       -       181820050
  3 Spin_Up_Time            0x0003   100   099   000    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   097   097   020    Old_age   Always       -       3896
  5 Reallocated_Sector_Ct   0x0033   100   100   036    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000f   076   060   030    Pre-fail  Always       -       47513426
  9 Power_On_Hours          0x0032   092   092   000    Old_age   Always       -       7652 (5 84 0)
 10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       524288
 12 Power_Cycle_Count       0x0032   099   099   020    Old_age   Always       -       1904
184 End-to-End_Error        0x0032   100   100   099    Old_age   Always       -       0
187 Reported_Uncorrect      0x0032   100   100   000    Old_age   Always       -       2199023255552
188 Command_Timeout         0x0032   100   098   000    Old_age   Always       -       133146020493
189 High_Fly_Writes         0x003a   100   100   000    Old_age   Always       -       0
190 Airflow_Temperature_Cel 0x0022   074   056   045    Old_age   Always       -       26 (Min/Max 21/26)
191 G-Sense_Error_Rate      0x0032   100   100   000    Old_age   Always       -       4
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       1
193 Load_Cycle_Count        0x0032   001   001   000    Old_age   Always       -       275435
194 Temperature_Celsius     0x0022   026   044   000    Old_age   Always       -       26
195 Hardware_ECC_Recovered  0x001a   057   049   000    Old_age   Always       -       181820050
196 Reallocated_Event_Count 0x000f   093   093   030    Pre-fail  Always       -       6393 (38561 0)
197 Current_Pending_Sector  0x0012   100   100   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0010   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0

SMART Error Log Version: 1
ATA Error Count: 6 (device log contains only the most recent five errors)
	CR = Command Register [HEX]
	FR = Features Register [HEX]
	SC = Sector Count Register [HEX]
	SN = Sector Number Register [HEX]
	CL = Cylinder Low Register [HEX]
	CH = Cylinder High Register [HEX]
	DH = Device/Head Register [HEX]
	DC = Device Command Register [HEX]
	ER = Error register [HEX]
	ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.

Error 6 occurred at disk power-on lifetime: 2263 hours (94 days + 7 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  04 71 04 81 87 80 e0  Device Fault; Error: ABRT

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  a1 00 00 00 00 00 a0 00      02:30:10.876  IDENTIFY PACKET DEVICE
  ec 00 00 00 00 00 a0 00      02:30:10.876  IDENTIFY DEVICE
  00 00 00 00 00 00 00 ff      02:30:10.562  NOP [Abort queued commands]
  a1 00 00 00 00 00 a0 00      02:30:10.523  IDENTIFY PACKET DEVICE
  ec 00 00 00 00 00 a0 00      02:30:10.490  IDENTIFY DEVICE

Error 5 occurred at disk power-on lifetime: 2263 hours (94 days + 7 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  04 71 04 81 87 80 e0

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  ec 00 00 00 00 00 a0 00      02:30:10.876  IDENTIFY DEVICE
  00 00 00 00 00 00 00 ff      02:30:10.562  NOP [Abort queued commands]
  a1 00 00 00 00 00 a0 00      02:30:10.523  IDENTIFY PACKET DEVICE
  ec 00 00 00 00 00 a0 00      02:30:10.490  IDENTIFY DEVICE
  2f 00 01 10 00 00 a0 00      02:30:10.443  READ LOG EXT

Error 4 occurred at disk power-on lifetime: 2263 hours (94 days + 7 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  04 71 04 81 87 80 e0  Device Fault; Error: ABRT

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  a1 00 00 00 00 00 a0 00      02:30:10.523  IDENTIFY PACKET DEVICE
  ec 00 00 00 00 00 a0 00      02:30:10.490  IDENTIFY DEVICE
  2f 00 01 10 00 00 a0 00      02:30:10.443  READ LOG EXT
  61 00 08 ff ff ff 4f 00      02:30:10.395  WRITE FPDMA QUEUED
  61 00 08 e0 91 24 41 00      02:30:05.513  WRITE FPDMA QUEUED

Error 3 occurred at disk power-on lifetime: 2263 hours (94 days + 7 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  04 71 04 81 87 80 e0

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  ec 00 00 00 00 00 a0 00      02:30:10.490  IDENTIFY DEVICE
  2f 00 01 10 00 00 a0 00      02:30:10.443  READ LOG EXT
  61 00 08 ff ff ff 4f 00      02:30:10.395  WRITE FPDMA QUEUED
  61 00 08 e0 91 24 41 00      02:30:05.513  WRITE FPDMA QUEUED
  61 00 08 60 80 24 41 00      02:30:05.513  WRITE FPDMA QUEUED

Error 2 occurred at disk power-on lifetime: 2263 hours (94 days + 7 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  04 71 04 81 87 80 e0  Device Fault; Error: ABRT

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  2f 00 01 10 00 00 a0 00      02:30:10.443  READ LOG EXT
  61 00 08 ff ff ff 4f 00      02:30:10.395  WRITE FPDMA QUEUED
  61 00 08 e0 91 24 41 00      02:30:05.513  WRITE FPDMA QUEUED
  61 00 08 60 80 24 41 00      02:30:05.513  WRITE FPDMA QUEUED
  61 00 08 48 57 24 41 00      02:30:05.513  WRITE FPDMA QUEUED

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed without error       00%      7652         -
# 2  Short offline       Completed without error       00%      5292         -
# 3  Extended offline    Completed without error       00%      5020         -
# 4  Short offline       Completed without error       00%      5004         -

SMART Selective self-test log data structure revision number 1
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

Offline

#5 2012-10-29 12:23:58

cfr
Member
From: Cymru
Registered: 2011-11-27
Posts: 7,134

Re: [Solved] Hard Drive failure ?

The error log is probably the most telling part. That said, on my previous laptop, my hard disk survived for quite a long time after I first got errors logged so if the problem doesn't return, you might be OK for a while. (Years in my case.) But if you are having issues, which it seems you are, you might not want to wait to replace the disk. (And either way you should back everything up but especially if you decide to wait and see.)

It is definitely not the ext4 bug given your mount options. As I understand it, the bug requires the nobarrier mount option.

CLI Paste | How To Ask Questions

Arch Linux | x86_64 | GPT | EFI boot | refind | stub loader | systemd | LVM2 on LUKS
Lenovo x270 | Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz | Intel Wireless 8265/8275 | US keyboard w/ Euro | 512G NVMe INTEL SSDPEKKF512G7L

Offline

#6 2012-10-29 13:11:25

bjornoslav
Member
Registered: 2011-11-01
Posts: 137

Re: [Solved] Hard Drive failure ?

Radfahrer wrote:

196 Reallocated_Event_Count 0x000f   093   093   030    Pre-fail  Always       -       6393 (38561 0)

Possible problem with the drive electronics. Make a backup as soon as possible and replace the drive!

asus ux303la, core i5@1.6ghz, 8 gb ram, 500gb hdd, hd4400 gpu, crux x64 with openbox

Offline

#7 2012-10-29 13:47:41

brain0
Developer
From: Aachen - Germany
Registered: 2005-01-03
Posts: 1,382

Re: [Solved] Hard Drive failure ?

Trilby wrote:

Could it be the ext4 bug?

Can you people stop bringing up this bogus bug? Unless you are a crazy person, you will never see it - and there is one (1!) user in the entire world that was crazy enough to trigger it.

From the log that was posted, it was completely obvious that the problem was not related to the file system, but the hard drive itself. So even if there was a file system bug, it wouldn't even be related to this. There is a problem with either the hard drive, the controller or the cable. And later, smartctl data confirmed it was definitely the drive.

Instead of wildly speculating, could you please refrain from posting replies if you don't have the slightest idea what is going on?

Offline

#8 2012-10-29 14:44:25

Trilby
Inspector Parrot
Registered: 2011-11-29
Posts: 29,546
Website

Re: [Solved] Hard Drive failure ?

I don't know who "you people" are.  I have never seen this bug.  I was skeptical that it could be the problem, which is why I linked to the thread where the OP could check if he could fall into the small category that might be affected by it.

If it is so clear exactly what is going on, in your infinite wisdom, then by all means insult and ridicule me ... but then solve the OP's problem, because, as you imply, it is quite clear from the log.  As it is, you have done nothing to help the OP.  All you bring is insults.  Deserved or not, they serve no purpose here.

I will certainly refrain from posting any reply to an issue you may face.  But as you are so much smarter than me, you certainly wouldn't want my input anyhow.

Last edited by Trilby (2012-10-29 14:45:19)

"UNIX is simple and coherent..." - Dennis Ritchie, "GNU's Not UNIX" -  Richard Stallman

Offline

#9 2012-10-29 15:26:11

brain0
Developer
From: Aachen - Germany
Registered: 2005-01-03
Posts: 1,382

Re: [Solved] Hard Drive failure ?

Trilby wrote:

but then solve the OP's problem, because, as you imply, it is quite clear from the log.  As it is, you have done nothing to help the OP.  All you bring is insults.  Deserved or not, they serve no purpose here.

They serve a very important purpose: When someone wants help, but instead of useful information only gets unrelated and wrong information, then (s)he will never solve the problem. It is okay to speculate if the issue is unclear, but in this case, it was 100% certain what the problem was - yet you started speculating and posting completely unrelated hints. I see this a lot - and usually only when I (by accident) stumble upon a thread on the Ubuntu forums.

I am helping future OPs by making sure that when someone posts, they know the answer actually helps them.

As for this thread: The solution (as pointed out far above my post) is easy: He needs a new drive.

Offline

#10 2012-11-01 09:34:54

Radfahrer
Member
Registered: 2008-04-29
Posts: 31

Re: [Solved] Hard Drive failure ?

Thanks everyone for the help. I replaced the hard drive yesterday and everything seems to work now.

Offline

Pages: 1

Board footer

Powered by FluxBB