Dieseldes Posted June 4, 2015 Share Posted June 4, 2015 Ok so I'm running unraid on a nl54 hp microserver and it's been great now for about 3 years. For maintanance all I do is a smart check of each drive and a parity check every month. I run sab, my menu, couch potato and sickbeard and the machine holds my movies and TV series stuff mostly. I don't want to loose this stuff but it's not the end of my world if I do. I have a 6 tb wd red parity drive, 2 x 4 tb Hitachi nas drives and a seagate 4tb nas drive. I run a 250gb seagate 7200 drive as a scratch disk for sab etc and as a cache drive. So yesterday I was due my monthly parity check and just before I started it I lost an entire directory from a folder. It's not in the share on my windows pc or when I browse it on a file explorer program I often use to copy stuff too and from the server on my phone. So I ran a parity check and smart checks and all came back fine. During those tests I lost access to the main unraid Web page and also couch potatoe and sick beard. I can only see unraid now on my menu Web page. The test finished just after I got to work today so I'm vpn ed into my network and now nothing is available on the share! All 8 tb of data missing! But if I look at each disk in my file explorer program I can see the files. So hopefully it's all there as I don't backup. Yea i know. So in my menu I was able to access the system log and it's full of this. kernel: mdcmd (3043): spindown 2 (Routine) Jun 4 05:58:17 Tower kernel: mdcmd (3044): spindown 3 (Routine) Jun 4 06:17:05 Tower kernel: REISERFS error (device sdb1): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [2 54 0x0 SD] (Errors) Jun 4 07:11:52 Tower kernel: REISERFS error (device sdb1): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [2 48118 0x0 SD] (Errors) Jun 4 07:11:52 Tower last message repeated 5 times Jun 4 07:11:52 Tower kernel: REISERFS error (device sdb1): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [2 54 0x0 SD] (Errors) Jun 4 07:11:52 Tower kernel: REISERFS error (device sdb1): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [2 48118 0x0 SD] (Errors) That's a quick copy and paste on my phone. Seems to me that a drive sdb1 is faulty but none of my disks have that name. So is that my memory stick? I know almost nothing about Linux and followed guide online to setup everything. What should I do next when I get home? I need a type and press xyz type instructions. Sorry. I intend on power cycling it first? Cheers des. Link to comment
trurl Posted June 4, 2015 Share Posted June 4, 2015 kernel: mdcmd (3043): spindown 2 (Routine) Jun 4 05:58:17 Tower kernel: mdcmd (3044): spindown 3 (Routine) Jun 4 06:17:05 Tower kernel: REISERFS error (device sdb1): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [2 54 0x0 SD] (Errors) Jun 4 07:11:52 Tower kernel: REISERFS error (device sdb1): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [2 48118 0x0 SD] (Errors) Jun 4 07:11:52 Tower last message repeated 5 times Jun 4 07:11:52 Tower kernel: REISERFS error (device sdb1): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [2 54 0x0 SD] (Errors) Jun 4 07:11:52 Tower kernel: REISERFS error (device sdb1): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [2 48118 0x0 SD] (Errors) That's a quick copy and paste on my phone. Seems to me that a drive sdb1 is faulty but none of my disks have that name. So is that my memory stick? I know almost nothing about Linux and followed guide online to setup everything. What should I do next when I get home? I need a type and press xyz type instructions. Sorry. I intend on power cycling it first? Cheers des. Don't reboot! Post a complete syslog and wait for further instructions. Also a screenshot of the Main page. sdb1 can't be your flash drive, since it is FAT not REISER. Must be one of your disks. A syslog will tell us. See v5 help in my sig. Link to comment
Dieseldes Posted June 4, 2015 Author Share Posted June 4, 2015 Thanks for getting back so quickly. I will be home from work in a few hours and will try accessing the Web main page from another pc when I get home. But at the moment it's not responding when I vpn in and the only thing that is responding is sab and my menu. If my other pc also won't talk to unraid main page is there a way of getting the system log directly from the microserver? I won't power it down and will disconnect the other computers from my router so it's just the microserver and 1 other pc that I will use to figure this out. That's the easiest way for me to stop stuff getting written to the unraid box as my mediaportal setup uses this. Cheers des Link to comment
trurl Posted June 4, 2015 Share Posted June 4, 2015 ...If my other pc also won't talk to unraid main page is there a way of getting the system log directly from the microserver?... Did you See v5 help in my sig. Link to comment
Dieseldes Posted June 4, 2015 Author Share Posted June 4, 2015 Sorry i missed that while reading quickly on my phone. I am now home and cant access tower on my web browser on 2 pc,s or my phone. I can access the my menu plugin and downloaded the syslog from that. Here it is. I will read your links and await your response. Cheers Des syslog-2015-06-04.txt Link to comment
Dieseldes Posted June 4, 2015 Author Share Posted June 4, 2015 So i found this /dev/sdb1 244191092 52241904 191949188 22% /mnt/cache Seems to indicate sdb1 is my seagate cache drive. Should of known. I will run a long smart on it now.... Link to comment
Dieseldes Posted June 4, 2015 Author Share Posted June 4, 2015 I preformed a short test earlier today when I VPN'ed into my network and am running a long test now. Anyhow here are the results from the earlier test. === START OF INFORMATION SECTION === Model Family: HP 250GB SATA disk VB0250EAVER Device Model: VB0250EAVER Serial Number: Z3TLVFAN LU WWN Device Id: 5 000c50 063edcb7a Firmware Version: HPG9 User Capacity: 250,059,350,016 bytes [250 GB] Sector Size: 512 bytes logical/physical Rotation Rate: 7200 rpm Device is: In smartctl database [for details use: -P show] ATA Version is: ATA8-ACS T13/1699-D revision 6 SATA Version is: SATA 2.6, 3.0 Gb/s (current: 1.5 Gb/s) Local Time is: Thu Jun 4 17:15:18 2015 BST 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: (0x82) Offline data collection activity was completed without error. Auto Offline Data Collection: Enabled. Self-test execution status: ( 249) Self-test routine in progress... 90% of test remaining. Total time to complete Offline data collection: ( 617) seconds. Offline data collection capabilities: (0x5b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. No 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: ( 2) minutes. Extended self-test routine recommended polling time: ( 45) minutes. SCT capabilities: (0x1039) 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 0x002f 113 099 006 Pre-fail Always - 57171630 3 Spin_Up_Time 0x0023 098 097 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 098 098 020 Old_age Always - 2770 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0 7 Seek_Error_Rate 0x002f 081 060 030 Pre-fail Always - 119609368 9 Power_On_Hours 0x0032 088 088 000 Old_age Always - 10625 10 Spin_Retry_Count 0x0033 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 099 099 020 Old_age Always - 1385 180 Unknown_HDD_Attribute 0x002b 100 100 000 Pre-fail Always - 6793 183 Runtime_Bad_Block 0x0032 100 100 000 Old_age Always - 0 184 End-to-End_Error 0x0032 100 100 097 Old_age Always - 0 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0 188 Command_Timeout 0x0032 100 100 000 Old_age Always - 0 189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0 190 Airflow_Temperature_Cel 0x0022 068 054 045 Old_age Always - 32 (Min/Max 24/33) 194 Temperature_Celsius 0x0022 032 046 000 Old_age Always - 32 (0 10 0 0 0) 195 Hardware_ECC_Recovered 0x003a 058 047 000 Old_age Always - 57171630 196 Reallocated_Event_Count 0x0032 100 100 036 Old_age Always - 0 197 Current_Pending_Sector 0x0032 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Extended offline Self-test routine in progress 90% 10625 - # 2 Short offline Completed without error 00% 10622 - # 3 Short offline Completed without error 00% 9793 - # 4 Short offline Completed without error 00% 9793 - # 5 Short offline Completed without error 00% 9032 - # 6 Short offline Completed without error 00% 8301 - # 7 Short offline Completed without error 00% 7413 - # 8 Short offline Completed without error 00% 7155 - # 9 Short offline Completed without error 00% 6745 - #10 Short offline Completed without error 00% 5362 - #11 Short offline Completed without error 00% 4753 - #12 Short offline Completed without error 00% 4225 - #13 Short offline Completed without error 00% 3244 - 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. Link to comment
Dieseldes Posted June 4, 2015 Author Share Posted June 4, 2015 And the results from the long test, reported to be a pass??? SMART status Info for /dev/sdg smartctl 6.2 2013-07-26 r3841 [i686-linux-3.9.11p-unRAID] (local build) Copyright © 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: HP 250GB SATA disk VB0250EAVER Device Model: VB0250EAVER Serial Number: Z3TLVFAN LU WWN Device Id: 5 000c50 063edcb7a Firmware Version: HPG9 User Capacity: 250,059,350,016 bytes [250 GB] Sector Size: 512 bytes logical/physical Rotation Rate: 7200 rpm Device is: In smartctl database [for details use: -P show] ATA Version is: ATA8-ACS T13/1699-D revision 6 SATA Version is: SATA 2.6, 3.0 Gb/s (current: 1.5 Gb/s) Local Time is: Thu Jun 4 18:03:36 2015 BST 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: (0x82) Offline data collection activity was completed without error. Auto Offline Data Collection: Enabled. 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: ( 617) seconds. Offline data collection capabilities: (0x5b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. No 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: ( 2) minutes. Extended self-test routine recommended polling time: ( 45) minutes. SCT capabilities: (0x1039) 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 0x002f 113 099 006 Pre-fail Always - 57196726 3 Spin_Up_Time 0x0023 098 097 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 098 098 020 Old_age Always - 2770 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0 7 Seek_Error_Rate 0x002f 081 060 030 Pre-fail Always - 119609445 9 Power_On_Hours 0x0032 088 088 000 Old_age Always - 10626 10 Spin_Retry_Count 0x0033 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 099 099 020 Old_age Always - 1385 180 Unknown_HDD_Attribute 0x002b 100 100 000 Pre-fail Always - 7642 183 Runtime_Bad_Block 0x0032 100 100 000 Old_age Always - 0 184 End-to-End_Error 0x0032 100 100 097 Old_age Always - 0 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0 188 Command_Timeout 0x0032 100 100 000 Old_age Always - 0 189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0 190 Airflow_Temperature_Cel 0x0022 069 054 045 Old_age Always - 31 (Min/Max 24/33) 194 Temperature_Celsius 0x0022 031 046 000 Old_age Always - 31 (0 10 0 0 0) 195 Hardware_ECC_Recovered 0x003a 056 047 000 Old_age Always - 57196726 196 Reallocated_Event_Count 0x0032 100 100 036 Old_age Always - 0 197 Current_Pending_Sector 0x0032 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Extended offline Completed without error 00% 10626 - # 2 Short offline Completed without error 00% 10622 - # 3 Short offline Completed without error 00% 9793 - # 4 Short offline Completed without error 00% 9793 - # 5 Short offline Completed without error 00% 9032 - # 6 Short offline Completed without error 00% 8301 - # 7 Short offline Completed without error 00% 7413 - # 8 Short offline Completed without error 00% 7155 - # 9 Short offline Completed without error 00% 6745 - #10 Short offline Completed without error 00% 5362 - #11 Short offline Completed without error 00% 4753 - #12 Short offline Completed without error 00% 4225 - #13 Short offline Completed without error 00% 3244 - 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. Link to comment
trurl Posted June 4, 2015 Share Posted June 4, 2015 You have unMenu? Post a screenshot that shows your drive assignments. Read this: Check Disk Filesystems Link to comment
Dieseldes Posted June 4, 2015 Author Share Posted June 4, 2015 Yep its unmenu, not my menu as i was calling it sorry. Here is a screen dump. As i say sdb1 doesnt exist?? Reading you link now... Link to comment
Dieseldes Posted June 4, 2015 Author Share Posted June 4, 2015 Should i stop my server with "Stop" or "powerdown" Reset the server and start in maintenance mode and run the commands you linked? Sorry for the dumb questions, its embarrassing how little i know about linux stuff. Link to comment
Dieseldes Posted June 4, 2015 Author Share Posted June 4, 2015 Seems to me that my cache drive used to be sdb and somehow has moved to sdg and is causing all this confusion. Some old notes I have seem to say it was sdb! Is that even possible? Link to comment
dgaschk Posted June 4, 2015 Share Posted June 4, 2015 Of course. sdX labels are assigned at startup as disks respond. These letters must be verified after ever boot. Why would you think they are constant? Link to comment
trurl Posted June 4, 2015 Share Posted June 4, 2015 Seems to me that my cache drive used to be sdb and somehow has moved to sdg and is causing all this confusion. Some old notes I have seem to say it was sdb! Is that even possible? The drive letters get assigned in the order they respond when booting so it is possible they can change. Since V5 unRAID has kept track of drive assignments using the disk serial number. Are you on V5? That screenshot is not really showing us sdb. Can you look on some of the other unMenu screens and see if you see it? Was that the complete syslog? If so, it must have rotated. From console or telnet, what do you get with ls -la /var/log/syslog* Link to comment
Dieseldes Posted June 4, 2015 Author Share Posted June 4, 2015 Of course. sdX labels are assigned at startup as disks respond. These letters must be verified after ever boot. Why would you think they are constant? Just shows how little i know about this operating system. When i did know a bit about DOS back in the 1990's drive letters didn't change. But with with your description of how unraid works i understand how they can change. Seems to me that my cache drive used to be sdb and somehow has moved to sdg and is causing all this confusion. Some old notes I have seem to say it was sdb! Is that even possible? The drive letters get assigned in the order they respond when booting so it is possible they can change. Since V5 unRAID has kept track of drive assignments using the disk serial number. Are you on V5? That screenshot is not really showing us sdb. Can you look on some of the other unMenu screens and see if you see it? Was that the complete syslog? If so, it must have rotated. From console or telnet, what do you get with ls -la /var/log/syslog* I'm using version 5 final. Not sure of the exact final version as i cant access the unraid GUI and i dont know were else to find it. I have looked everywhere in unmenu and sdb doesn't exist. All my disks are accounted for in that screen dump i posted, none have gone AWOL. The cash drive which is now sdg is the only one thats giving issues when i try and access it directly from a windows PC. I got that syslog from unmenu. Running the command you told me says there are 3 syslogs. 2 dated today and one from February. How do i get access to them as i cant find them when i browse the flash in windows. Im reading about telnet now so i can log in with my windows pc and try and copy stuff. I realise i sound like a simpleton.... Link to comment
Dieseldes Posted June 4, 2015 Author Share Posted June 4, 2015 And with telnet. Tower login: root Linux 3.9.11p-unRAID. root@Tower:~# ls -la /var/log/syslog* -rw-r--r-- 1 root root 34733 2015-06-04 20:04 /var/log/syslog -rw-r--r-- 1 root root 2839248 2015-06-04 04:17 /var/log/syslog.1 -rw-r--r-- 1 root root 6583951 2015-02-03 04:10 /var/log/syslog.2 root@Tower:~# Link to comment
Dieseldes Posted June 4, 2015 Author Share Posted June 4, 2015 Is this any use?? root@Tower:~# ls -l /dev/disk/by-id total 0 lrwxrwxrwx 1 root root 9 2014-10-26 07:13 ata-HGST_HDN724040ALE640_PK1334PBGTHZ NX -> ../../sde lrwxrwxrwx 1 root root 10 2014-10-26 07:13 ata-HGST_HDN724040ALE640_PK1334PBGTHZ NX-part1 -> ../../sde1 lrwxrwxrwx 1 root root 9 2014-10-26 07:16 ata-HGST_HDN724040ALE640_PK1334PBH0JN 0S -> ../../sdd lrwxrwxrwx 1 root root 10 2014-10-26 07:16 ata-HGST_HDN724040ALE640_PK1334PBH0JN 0S-part1 -> ../../sdd1 lrwxrwxrwx 1 root root 9 2014-10-26 07:13 ata-ST4000VN000-1H4168_Z300VBHL -> .. /../sdc lrwxrwxrwx 1 root root 10 2014-10-26 07:13 ata-ST4000VN000-1H4168_Z300VBHL-part1 -> ../../sdc1 lrwxrwxrwx 1 root root 9 2015-06-03 21:20 ata-VB0250EAVER_Z3TLVFAN -> ../../sdg lrwxrwxrwx 1 root root 10 2015-06-03 21:20 ata-VB0250EAVER_Z3TLVFAN-part1 -> ../ ../sdg1 lrwxrwxrwx 1 root root 9 2014-10-26 07:13 ata-WDC_WD60EFRX-68MYMN0_WD-WX31D3408 887 -> ../../sdf lrwxrwxrwx 1 root root 10 2014-10-26 07:13 ata-WDC_WD60EFRX-68MYMN0_WD-WX31D3408 887-part1 -> ../../sdf1 lrwxrwxrwx 1 root root 9 2014-10-26 07:13 scsi-SATA_HGST_HDN724040A_PK1334PBGTH ZNX -> ../../sde lrwxrwxrwx 1 root root 10 2014-10-26 07:13 scsi-SATA_HGST_HDN724040A_PK1334PBGTH ZNX-part1 -> ../../sde1 lrwxrwxrwx 1 root root 9 2014-10-26 07:16 scsi-SATA_HGST_HDN724040A_PK1334PBH0J N0S -> ../../sdd lrwxrwxrwx 1 root root 10 2014-10-26 07:16 scsi-SATA_HGST_HDN724040A_PK1334PBH0J N0S-part1 -> ../../sdd1 lrwxrwxrwx 1 root root 9 2014-10-26 07:13 scsi-SATA_ST4000VN000-1H4_Z300VBHL -> ../../sdc lrwxrwxrwx 1 root root 10 2014-10-26 07:13 scsi-SATA_ST4000VN000-1H4_Z300VBHL-pa rt1 -> ../../sdc1 lrwxrwxrwx 1 root root 9 2015-06-03 21:20 scsi-SATA_VB0250EAVER_Z3TLVFAN -> ../ ../sdg lrwxrwxrwx 1 root root 10 2015-06-03 21:20 scsi-SATA_VB0250EAVER_Z3TLVFAN-part1 -> ../../sdg1 lrwxrwxrwx 1 root root 9 2014-10-26 07:13 scsi-SATA_WDC_WD60EFRX-68_WD-WX31D340 8887 -> ../../sdf lrwxrwxrwx 1 root root 10 2014-10-26 07:13 scsi-SATA_WDC_WD60EFRX-68_WD-WX31D340 8887-part1 -> ../../sdf1 lrwxrwxrwx 1 root root 9 2014-10-26 07:13 usb-SanDisk_Cruzer_Fit_4C532000070728 119385-0:0 -> ../../sda lrwxrwxrwx 1 root root 10 2014-10-26 07:13 usb-SanDisk_Cruzer_Fit_4C532000070728 119385-0:0-part1 -> ../../sda1 lrwxrwxrwx 1 root root 9 2015-06-03 21:20 wwn-0x5000c50063edcb7a -> ../../sdg lrwxrwxrwx 1 root root 10 2015-06-03 21:20 wwn-0x5000c50063edcb7a-part1 -> ../.. /sdg1 lrwxrwxrwx 1 root root 9 2014-10-26 07:13 wwn-0x5000c50064cc8579 -> ../../sdc lrwxrwxrwx 1 root root 10 2014-10-26 07:13 wwn-0x5000c50064cc8579-part1 -> ../.. /sdc1 lrwxrwxrwx 1 root root 9 2014-10-26 07:13 wwn-0x5000cca23dcb24ed -> ../../sde lrwxrwxrwx 1 root root 10 2014-10-26 07:13 wwn-0x5000cca23dcb24ed-part1 -> ../.. /sde1 lrwxrwxrwx 1 root root 9 2014-10-26 07:16 wwn-0x5000cca23dce55fd -> ../../sdd lrwxrwxrwx 1 root root 10 2014-10-26 07:16 wwn-0x5000cca23dce55fd-part1 -> ../.. /sdd1 lrwxrwxrwx 1 root root 9 2014-10-26 07:13 wwn-0x50014ee20a90f460 -> ../../sdf lrwxrwxrwx 1 root root 10 2014-10-26 07:13 wwn-0x50014ee20a90f460-part1 -> ../.. /sdf1 root@Tower:~# Link to comment
Dieseldes Posted June 4, 2015 Author Share Posted June 4, 2015 Ok so i can view the log file with telnet and am scanning it by eye. Problems started april 29th Apr 29 20:27:14 Tower kernel: ata1: exception Emask 0x10 SAct 0x0 SErr 0x90202 a ction 0xe frozen Apr 29 20:27:14 Tower kernel: ata1: irq_stat 0x00400000, PHY RDY changed Apr 29 20:27:14 Tower kernel: ata1: SError: { RecovComm Persist PHYRdyChg 10B8B } Apr 29 20:27:14 Tower kernel: ata1: hard resetting link Apr 29 20:27:18 Tower kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Apr 29 20:27:18 Tower kernel: ata1.00: failed to enable AA (error_mask=0x1) Apr 29 20:27:18 Tower kernel: ata1.00: failed to enable AA (error_mask=0x1) Apr 29 20:27:18 Tower kernel: ata1.00: configured for UDMA/100 Apr 29 20:27:18 Tower kernel: ata1: EH complete Apr 29 20:27:18 Tower kernel: sd 1:0:0:0: [sdb] Write cache: disabled, read cach e: enabled, doesn't support DPO or FUA Apr 29 21:00:28 Tower kernel: ata2.00: exception Emask 0x10 SAct 0x0 SErr 0x9020 2 action 0xe frozen Apr 29 21:00:28 Tower kernel: ata2.00: irq_stat 0x00400000, PHY RDY changed Apr 29 21:00:28 Tower kernel: ata2: SError: { RecovComm Persist PHYRdyChg 10B8B } Apr 29 21:00:28 Tower kernel: ata2.00: failed command: READ DMA EXT Apr 29 21:00:28 Tower kernel: ata2.00: cmd 25/00:80:c8:64:3e/00:03:54:00:00/e0 t ag 0 dma 458752 in Apr 29 21:00:28 Tower kernel: res 50/00:00:c7:64:3e/00:00:54:00:00/e0 E mask 0x10 (ATA bus error) mask 0x10 (ATA bus error) Apr 29 21:00:28 Tower kernel: ata2.00: status: { DRDY } Apr 29 21:00:28 Tower kernel: ata2: hard resetting link Apr 29 21:00:34 Tower kernel: ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Apr 29 21:00:34 Tower kernel: ata2.00: configured for UDMA/133 Apr 29 21:00:34 Tower kernel: ata2: EH complete Apr 30 03:40:01 Tower logger: mover started Apr 30 03:40:01 Tower logger: skipping appdata/ Apr 30 03:40:01 Tower logger: moving main share/ Then all was fine with no errors until 3rd June when it kicked off again with this. Jun 3 20:27:43 Tower kernel: end_request: I/O error, dev sdb, sector 49967984 Jun 3 20:27:43 Tower kernel: ata1: EH complete Jun 3 20:27:43 Tower kernel: ata1.00: exception Emask 0x10 SAct 0x0 SErr 0x1020 0 action 0xe frozen Jun 3 20:27:43 Tower kernel: ata1.00: irq_stat 0x00400000, PHY RDY changed Jun 3 20:27:43 Tower kernel: ata1: SError: { Persist PHYRdyChg } Jun 3 20:27:43 Tower kernel: ata1.00: failed command: WRITE DMA EXT Jun 3 20:27:43 Tower kernel: ata1.00: cmd 35/00:00:70:77:fa/00:04:02:00:00/e0 t ag 0 dma 524288 out Jun 3 20:27:43 Tower kernel: res 51/04:02:00:00:00/00:00:00:00:00/a0 E mask 0x10 (ATA bus error) Jun 3 20:27:43 Tower kernel: ata1.00: status: { DRDY ERR } Jun 3 20:27:43 Tower kernel: ata1.00: error: { ABRT } Jun 3 20:27:43 Tower kernel: ata1: hard resetting link Jun 3 20:27:47 Tower kernel: ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Jun 3 20:27:47 Tower kernel: ata1.00: failed to enable AA (error_mask=0x1) Jun 3 20:27:47 Tower kernel: ata1.00: failed to enable AA (error_mask=0x1) Jun 3 20:27:47 Tower kernel: ata1.00: configured for UDMA/33 Jun 3 20:27:47 Tower kernel: ata1: EH complete Jun 3 20:27:47 Tower kernel: ata1.00: exception Emask 0x10 SAct 0x0 SErr 0x1020 0 action 0xe frozen Jun 3 20:27:47 Tower kernel: ata1.00: irq_stat 0x00400000, PHY RDY changed Jun 3 20:27:47 Tower kernel: ata1: SError: { Persist PHYRdyChg } Jun 3 20:27:47 Tower kernel: ata1.00: failed command: WRITE DMA EXT Jun 3 20:27:47 Tower kernel: ata1.00: cmd 35/00:00:70:77:fa/00:04:02:00:00/e0 t ag 0 dma 524288 out Jun 3 20:27:47 Tower kernel: res 51/04:02:00:00:00/00:00:00:00:00/a0 E mask 0x10 (ATA bus error) Jun 3 20:28:24 Tower kernel: ata1.00: failed to enable AA (error_mask=0x1) Jun 3 20:28:24 Tower kernel: ata1.00: failed to enable AA (error_mask=0x1) Jun 3 20:28:24 Tower kernel: ata1.00: configured for UDMA/33 Jun 3 20:28:24 Tower kernel: ata1: EH complete Jun 3 20:28:24 Tower kernel: ata1.00: exception Emask 0x10 SAct 0x0 SErr 0x1020 0 action 0xe frozen Jun 3 20:28:24 Tower kernel: ata1.00: irq_stat 0x00400000, PHY RDY changed Jun 3 20:28:24 Tower kernel: ata1: SError: { Persist PHYRdyChg } Jun 3 20:28:24 Tower kernel: ata1.00: failed command: WRITE DMA EXT Jun 3 20:28:24 Tower kernel: ata1.00: cmd 35/00:00:70:7b:fa/00:04:02:00:00/e0 t ag 0 dma 524288 out Jun 3 20:28:24 Tower kernel: res 51/04:02:00:00:00/00:00:00:00:00/a0 E mask 0x10 (ATA bus error) Jun 3 20:28:24 Tower kernel: ata1.00: status: { DRDY ERR } Jun 3 20:28:24 Tower kernel: ata1.00: error: { ABRT } Jun 3 20:28:24 Tower kernel: ata1: hard resetting link Jun 3 20:28:28 Tower kernel: ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Jun 3 20:28:28 Tower kernel: ata1.00: failed to enable AA (error_mask=0x1) Jun 3 20:28:28 Tower kernel: ata1.00: failed to enable AA (error_mask=0x1) Jun 3 20:28:28 Tower kernel: ata1.00: configured for UDMA/33 Jun 3 20:28:28 Tower kernel: ata1: EH complete Jun 3 20:28:28 Tower kernel: ata1.00: exception Emask 0x10 SAct 0x0 SErr 0x1020 0 action 0xe frozen Jun 3 20:28:28 Tower kernel: ata1.00: irq_stat 0x00400000, PHY RDY changed Jun 3 20:28:28 Tower kernel: ata1: SError: { Persist PHYRdyChg } Jun 3 20:28:28 Tower kernel: ata1.00: failed command: WRITE DMA EXT Jun 3 20:28:28 Tower kernel: ata1.00: cmd 35/00:00:70:7b:fa/00:04:02:00:00/e0 t ag 0 dma 524288 out Jun 3 20:28:28 Tower kernel: res 51/04:02:00:00:00/00:00:00:00:00/a0 E mask 0x10 (ATA bus error) Jun 3 20:28:28 Tower kernel: ata1.00: status: { DRDY ERR } Jun 3 20:28:28 Tower kernel: ata1.00: error: { ABRT } Jun 3 20:28:28 Tower kernel: ata1: hard resetting link Jun 3 20:28:32 Tower kernel: ata1: SATA link down (SStatus 0 SControl 310) Jun 3 20:28:32 Tower kernel: ata1.00: link offline, clearing class 1 to NONE Jun 3 20:28:32 Tower kernel: ata1: hard resetting link Jun 3 20:28:36 Tower kernel: ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Jun 3 20:28:36 Tower kernel: ata1.00: failed to enable AA (error_mask=0x1) Jun 3 20:28:36 Tower kernel: ata1.00: failed to enable AA (error_mask=0x1) Jun 3 20:28:36 Tower kernel: ata1.00: configured for UDMA/33 Jun 3 20:28:36 Tower kernel: ata1: EH complete Jun 3 20:28:36 Tower kernel: ata1.00: exception Emask 0x10 SAct 0x0 SErr 0x1020 0 action 0xe frozen Jun 3 20:28:36 Tower kernel: ata1.00: irq_stat 0x00400000, PHY RDY changed Jun 3 20:28:36 Tower kernel: ata1: SError: { Persist PHYRdyChg } Jun 3 20:28:36 Tower kernel: ata1.00: failed command: WRITE DMA EXT Jun 3 20:28:36 Tower kernel: ata1.00: cmd 35/00:00:70:7b:fa/00:04:02:00:00/e0 t ag 0 dma 524288 out Jun 3 20:28:36 Tower kernel: res 51/04:02:00:00:00/00:00:00:00:00/a0 E mask 0x10 (ATA bus error) Jun 3 20:28:36 Tower kernel: ata1.00: status: { DRDY ERR } Jun 3 20:28:36 Tower kernel: ata1.00: error: { ABRT } Jun 3 20:28:36 Tower kernel: ata1: hard resetting link Jun 3 20:28:40 Tower kernel: ata1: SATA link down (SStatus 0 SControl 310) Jun 3 20:28:40 Tower kernel: ata1.00: link offline, clearing class 1 to NONE Jun 3 20:28:40 Tower kernel: ata1: hard resetting link Jun 3 20:28:44 Tower kernel: ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Jun 3 20:28:44 Tower kernel: ata1.00: failed to enable AA (error_mask=0x1) Jun 3 20:28:44 Tower kernel: ata1.00: failed to enable AA (error_mask=0x1) Jun 3 20:28:44 Tower kernel: ata1.00: configured for UDMA/33 Jun 3 20:28:44 Tower kernel: ata1: EH complete Jun 3 20:28:44 Tower kernel: ata1.00: exception Emask 0x10 SAct 0x0 SErr 0x1020 0 action 0xe frozen Jun 3 20:28:44 Tower kernel: ata1.00: irq_stat 0x00400000, PHY RDY changed Jun 3 20:28:44 Tower kernel: ata1: SError: { Persist PHYRdyChg } Jun 3 20:28:44 Tower kernel: ata1.00: failed command: WRITE DMA EXT Jun 3 20:28:44 Tower kernel: ata1.00: cmd 35/00:00:70:7f:fa/00:04:02:00:00/e0 t ag 0 dma 524288 out Jun 3 20:28:44 Tower kernel: res 50/00:00:6f:7f:fa/00:00:02:00:00/e0 E mask 0x10 (ATA bus error) Jun 3 20:28:44 Tower kernel: ata1.00: status: { DRDY } Jun 3 20:28:44 Tower kernel: ata1: hard resetting link Jun 3 20:28:48 Tower kernel: ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Jun 3 20:28:48 Tower kernel: ata1.00: failed to enable AA (error_mask=0x1) Jun 3 20:28:48 Tower kernel: ata1.00: failed to enable AA (error_mask=0x1) Jun 3 20:28:48 Tower kernel: ata1.00: configured for UDMA/33 Jun 3 20:28:48 Tower kernel: ata1: EH complete Jun 3 20:28:48 Tower kernel: ata1.00: exception Emask 0x10 SAct 0x0 SErr 0x1020 0 action 0xe frozen Jun 3 20:28:48 Tower kernel: ata1.00: irq_stat 0x00400000, PHY RDY changed Jun 3 20:28:48 Tower kernel: ata1: SError: { Persist PHYRdyChg } Jun 3 20:28:48 Tower kernel: ata1.00: failed command: WRITE DMA EXT Jun 3 20:28:48 Tower kernel: ata1.00: cmd 35/00:00:70:7f:fa/00:04:02:00:00/e0 t ag 0 dma 524288 out Jun 3 20:28:48 Tower kernel: res 51/04:02:00:00:00/00:00:00:00:00/a0 E mask 0x10 (ATA bus error) Jun 3 20:28:48 Tower kernel: ata1.00: status: { DRDY ERR } Jun 3 20:28:48 Tower kernel: ata1.00: error: { ABRT } Jun 3 20:28:48 Tower kernel: ata1: hard resetting link Jun 3 20:28:52 Tower kernel: ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Jun 3 20:28:52 Tower kernel: ata1.00: failed to enable AA (error_mask=0x1) Jun 3 20:28:52 Tower kernel: ata1.00: failed to enable AA (error_mask=0x1) Jun 3 20:28:52 Tower kernel: ata1.00: configured for UDMA/33 Jun 3 20:28:52 Tower kernel: ata1: EH complete Jun 3 20:28:52 Tower kernel: ata1.00: exception Emask 0x10 SAct 0x0 SErr 0x1020 0 action 0xe frozen Jun 3 20:28:52 Tower kernel: ata1.00: irq_stat 0x00400000, PHY RDY changed Jun 3 20:28:52 Tower kernel: ata1: SError: { Persist PHYRdyChg } Jun 3 20:28:52 Tower kernel: ata1.00: failed command: WRITE DMA EXT Jun 3 20:28:52 Tower kernel: ata1.00: cmd 35/00:00:70:7f:fa/00:04:02:00:00/e0 t ag 0 dma 524288 out Jun 3 20:28:52 Tower kernel: res 51/04:02:00:00:00/00:00:00:00:00/a0 E mask 0x10 (ATA bus error) Jun 3 20:28:52 Tower kernel: ata1.00: status: { DRDY ERR } Jun 3 20:28:52 Tower kernel: ata1.00: error: { ABRT } Jun 3 20:28:52 Tower kernel: ata1: hard resetting link Jun 3 20:28:56 Tower kernel: ata1: SATA link down (SStatus 0 SControl 310) Jun 3 20:28:56 Tower kernel: ata1.00: link offline, clearing class 1 to NONE Jun 3 20:28:56 Tower kernel: ata1: hard resetting link Jun 3 20:29:00 Tower kernel: ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Jun 3 20:29:00 Tower kernel: ata1.00: failed to enable AA (error_mask=0x1) Jun 3 20:29:00 Tower kernel: ata1.00: failed to enable AA (error_mask=0x1) Jun 3 20:29:00 Tower kernel: ata1.00: configured for UDMA/33 Jun 3 20:29:00 Tower kernel: ata1: EH complete Jun 3 20:29:00 Tower kernel: ata1.00: exception Emask 0x10 SAct 0x0 SErr 0x1020 0 action 0xe frozen Jun 3 20:29:00 Tower kernel: ata1.00: irq_stat 0x00400000, PHY RDY changed Jun 3 20:29:00 Tower kernel: ata1: SError: { Persist PHYRdyChg } Jun 3 20:29:00 Tower kernel: ata1.00: failed command: WRITE DMA EXT Jun 3 20:29:00 Tower kernel: ata1.00: cmd 35/00:00:70:7f:fa/00:04:02:00:00/e0 t ag 0 dma 524288 out Jun 3 20:29:00 Tower kernel: res 51/04:02:00:00:00/00:00:00:00:00/a0 E mask 0x10 (ATA bus error) Jun 3 20:29:00 Tower kernel: ata1.00: status: { DRDY ERR } Jun 3 20:29:00 Tower kernel: ata1.00: error: { ABRT } Jun 3 20:29:00 Tower kernel: ata1: hard resetting link Jun 3 20:29:04 Tower kernel: ata1: SATA link down (SStatus 0 SControl 310) Jun 3 20:29:04 Tower kernel: ata1.00: link offline, clearing class 1 to NONE Jun 3 20:29:04 Tower kernel: ata1: hard resetting link Jun 3 20:29:08 Tower kernel: ata1: SATA link down (SStatus 0 SControl 310) Jun 3 20:29:08 Tower kernel: ata1.00: link offline, clearing class 1 to NONE Jun 3 20:29:08 Tower kernel: ata1: hard resetting link Jun 3 20:29:12 Tower shfs/user: shfs_write: write: (5) Input/output error Jun 3 20:29:12 Tower kernel: ata1: SATA link down (SStatus 0 SControl 310) Jun 3 20:29:12 Tower kernel: ata1.00: link offline, clearing class 1 to NONE Jun 3 20:29:12 Tower kernel: ata1.00: disabled Jun 3 20:29:12 Tower kernel: sd 1:0:0:0: [sdb] Jun 3 20:29:12 Tower kernel: Result: hostbyte=0x00 driverbyte=0x08 Jun 3 20:29:12 Tower kernel: sd 1:0:0:0: [sdb] Jun 3 20:29:12 Tower kernel: Sense Key : 0xb [current] [descriptor] Jun 3 20:29:12 Tower kernel: Descriptor sense data with sense descriptors (in h ex): Jun 3 20:29:12 Tower kernel: 72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00 Jun 3 20:29:12 Tower kernel: 00 00 00 00 Jun 3 20:29:12 Tower kernel: sd 1:0:0:0: [sdb] Jun 3 20:29:12 Tower kernel: ASC=0x0 ASCQ=0x0 Jun 3 20:29:12 Tower kernel: sd 1:0:0:0: [sdb] CDB: Jun 3 20:29:12 Tower kernel: cdb[0]=0x2a: 2a 00 02 fa 7f 70 00 04 00 00 Jun 3 20:29:12 Tower kernel: end_request: I/O error, dev sdb, sector 49971056 Jun 3 20:29:12 Tower kernel: sd 1:0:0:0: rejecting I/O to offline device Jun 3 20:29:12 Tower kernel: sd 1:0:0:0: killing request Jun 3 20:29:12 Tower kernel: ata1: EH complete Jun 3 20:29:12 Tower kernel: sd 1:0:0:0: rejecting I/O to offline device Jun 3 20:29:12 Tower kernel: sd 1:0:0:0: [sdb] killing request Jun 3 20:29:12 Tower kernel: sd 1:0:0:0: rejecting I/O to offline device Jun 3 20:29:12 Tower shfs/user: shfs_utimens: utimes: /mnt/cache/main share/rec orded tv/Springwatch 2015 - BBC TWO HD - 2015-06-03.ts (30) Read-only file syste m Jun 3 20:29:12 Tower kernel: sd 1:0:0:0: rejecting I/O to offline device Jun 3 20:29:12 Tower last message repeated 56 times Jun 3 20:29:12 Tower kernel: Buffer I/O error on device sdb1, logical block 376 29208 Jun 3 20:29:12 Tower kernel: lost page write due to I/O error on sdb1 Jun 3 20:29:12 Tower kernel: Buffer I/O error on device sdb1, logical block 376 29219 Jun 3 20:29:12 Tower kernel: lost page write due to I/O error on sdb1 Jun 3 20:29:12 Tower kernel: Buffer I/O error on device sdb1, logical block 376 29220 Jun 3 20:29:12 Tower kernel: lost page write due to I/O error on sdb1 Jun 3 20:29:12 Tower kernel: Buffer I/O error on device sdb1, logical block 376 29224 Jun 3 20:29:12 Tower kernel: lost page write due to I/O error on sdb1 Jun 3 20:29:12 Tower kernel: Buffer I/O error on device sdb1, logical block 376 29228 Jun 3 20:29:12 Tower kernel: lost page write due to I/O error on sdb1 Jun 3 20:29:12 Tower kernel: sd 1:0:0:0: rejecting I/O to offline device Jun 3 20:29:12 Tower kernel: Buffer I/O error on device sdb1, logical block 376 29257 Jun 3 20:29:12 Tower kernel: end_request: I/O error, dev sdb, sector 49972080 Jun 3 20:29:12 Tower kernel: REISERFS warning (device sdb1): journal-837 _updat e_journal_header_block: IO error during journal replay Jun 3 20:29:12 Tower kernel: REISERFS abort (device sdb1): Write error while up dating journal header in flush_journal_list Jun 3 20:29:12 Tower kernel: REISERFS error (device sdb1): clm-6001 reiserfs_tr uncate_file: grab_tail_page failed -5 Jun 3 20:29:12 Tower kernel: REISERFS error (device sdb1): clm-6001 reiserfs_tr uncate_file: grab_tail_page failed -5 Jun 3 20:29:12 Tower kernel: ata1: exception Emask 0x10 SAct 0x0 SErr 0x40d0002 action 0xe frozen Jun 3 20:29:12 Tower kernel: ata1: irq_stat 0x00000040, connection status chang ed Jun 3 20:29:12 Tower kernel: ata1: SError: { RecovComm PHYRdyChg CommWake 10B8B DevExch } Jun 3 20:29:12 Tower kernel: ata1: hard resetting link Jun 3 20:29:12 Tower kernel: REISERFS error (device sdb1): clm-6001 reiserfs_tr uncate_file: grab_tail_page failed -5 Jun 3 20:29:12 Tower kernel: REISERFS error (device sdb1): vs-13070 reiserfs_re ad_locked_inode: i/o failure occurred trying to find stat data of [2 54 0x0 SD] Jun 3 20:29:13 Tower last message repeated 2 times Jun 3 20:29:13 Tower kernel: REISERFS error (device sdb1): clm-6001 reiserfs_tr uncate_file: grab_tail_page failed -5 Jun 3 20:29:13 Tower kernel: REISERFS error (device sdb1): clm-6001 reiserfs_tr uncate_file: grab_tail_page failed -5 Jun 3 20:29:13 Tower kernel: sd 1:0:0:0: [sdb] Stopping disk Jun 3 20:29:16 Tower kernel: ata1: SATA link down (SStatus 0 SControl 300) Jun 3 20:29:16 Tower kernel: ata1.00: link offline, clearing class 1 to NONE Jun 3 20:29:16 Tower kernel: ata1: EH complete Jun 3 20:29:16 Tower kernel: sd 1:0:0:0: [sdb] START_STOP FAILED Jun 3 20:29:16 Tower kernel: sd 1:0:0:0: [sdb] Jun 3 20:29:16 Tower kernel: Result: hostbyte=0x04 driverbyte=0x00 Jun 3 20:29:16 Tower kernel: ata1: exception Emask 0x10 SAct 0x0 SErr 0x40d0002 action 0xe frozen Jun 3 20:29:16 Tower kernel: ata1: irq_stat 0x00400040, connection status chang ed Jun 3 20:29:16 Tower kernel: ata1: SError: { RecovComm PHYRdyChg CommWake 10B8B DevExch } Jun 3 20:29:16 Tower kernel: ata1: limiting SATA link speed to 1.5 Gbps Jun 3 20:29:16 Tower kernel: ata1: hard resetting link Jun 3 20:29:20 Tower kernel: ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Jun 3 20:29:20 Tower kernel: ata1.00: failed to enable AA (error_mask=0x1) Jun 3 20:29:20 Tower kernel: ata1.00: ATA-8: VB0250EAVER, Z3TLVFAN, HPG9, max U DMA/100 Jun 3 20:29:20 Tower kernel: ata1.00: 488397168 sectors, multi 0: LBA48 NCQ (de pth 31/32) Jun 3 20:29:20 Tower kernel: ata1.00: failed to enable AA (error_mask=0x1) --More--(16%) An it continues like this. So i think those last few lines are telling as they state the serial number of the cache drive and above that it tells me " REISERFS warning (device sdb1): journal-837 _updat e_journal_header_block: IO error during journal replay" So is the file system bad on the cache drive? Its passing smart tests so hardware ok ish?? Link to comment
trurl Posted June 4, 2015 Share Posted June 4, 2015 That wiki about checking file systems assumes you are going to be dealing with the numbered array drives and it uses the md# devices so that parity gets included. In the case of the cache drive, you would use the sdx device instead. Since it looks like your cache is sdg right now, or at least sdg is not part of the parity array, then it should be OK to go to Maintenance mode and do reiserfsck --check /dev/sdg1 Make sure to include the number 1 since it needs to know what partition to use. Don't do anything else until you report the results. Not sure how long it will take. Link to comment
Dieseldes Posted June 4, 2015 Author Share Posted June 4, 2015 So i tried to use the powerdown command to restart the server in maintenance mode and it wouldn't respond. I ended up hitting control alt and delete and started it up in "safe" mode. The server is doing a parity check which i intend on stopping. Now Sdg is back as Sdb !! So obviously when i ran your command it couldnt find sdg1. I will run it with sdb1 ok.... Link to comment
Dieseldes Posted June 4, 2015 Author Share Posted June 4, 2015 Looks ok??? root@Tower:~# reiserfsck --check /dev/sdb1 reiserfsck 3.6.21 (2009 www.namesys.com) ************************************************************* ** If you are using the latest reiserfsprogs and it fails ** ** please email bug reports to [email protected], ** ** providing as much information as possible -- your ** ** hardware, kernel, patches, settings, all reiserfsck ** ** messages (including version), the reiserfsck logfile, ** ** check the syslog file for any related information. ** ** If you would like advice on using this program, support ** ** is available for $25 at www.namesys.com/support.html. ** ************************************************************* Will read-only check consistency of the filesystem on /dev/sdb1 Will put log info to 'stdout' Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes ########### reiserfsck --check started at Thu Jun 4 21:03:54 2015 ########### Replaying journal: Done. Reiserfs journal '/dev/sdb1' in blocks [18..8211]: 0 transactions replayed Checking internal tree.. finished Comparing bitmaps..finished Checking Semantic tree: finished No corruptions found There are on the filesystem: Leaves 13216 Internal nodes 86 Directories 189 Other files 2417 Data block pointers 13019599 (2217 of them are zero) Safe links 0 ########### reiserfsck finished at Thu Jun 4 21:05:18 2015 ########### root@Tower:~# Link to comment
trurl Posted June 4, 2015 Share Posted June 4, 2015 Looks OK. Maybe a cable problem or something? Is everything working OK since the reboot? Link to comment
Dieseldes Posted June 4, 2015 Author Share Posted June 4, 2015 The server is still in maint mode. Im thinking of shutting it down, and reseating each disk drive and restarting in normal mode. How does that sound? Link to comment
trurl Posted June 4, 2015 Share Posted June 4, 2015 The server is still in maint mode. Im thinking of shutting it down, and reseating each disk drive and restarting in normal mode. How does that sound? OK. You might also boot into memtest just to eliminate another thing. Link to comment
Dieseldes Posted June 4, 2015 Author Share Posted June 4, 2015 Ok i haven't tested the memory, but its ecc type so i would expect different errors if it was playing up? Anyhow here is the latest log after copying and reading some from the server. Seems ok so far with a few errors only? Thanks for the help BTW!!! syslog-2015-06-04_1.txt Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.