June 30, 201115 yr I upgraded my motherboard yesterday. When I powered up and re-mapped the drives unRaid says disk1 is unformatted. There is a full 2TB on that disk! I don't want to lose all that data. Anyone know what's going on here? What do I have to do to save that data? The MB is: SUPERMICRO MBD-C2SEA-O LGA 775 Intel G45.
June 30, 201115 yr I upgraded my motherboard yesterday. When I powered up and re-mapped the drives unRaid says disk1 is unformatted. There is a full 2TB on that disk! I don't want to lose all that data. Anyone know what's going on here? What do I have to do to save that data? The MB is: SUPERMICRO MBD-C2SEA-O LGA 775 Intel G45. Are you certain you did not map the parity drive to a data drive slot? It would show as un-formatted. In any case, DO NOT PRESS THE FORMAT BUTTON. DO NOT Calculate parity. In fact, un-assign the parity drive for now. (It might be your data drive) Instead, post a syslog. A disk will show as un-formatted if it is unable to be mounted as a reiserfs file system The cause for that could be any number of things. You did not even take the time to tell us what version of unRAID you are running. The actions and possible causes differ. Did you upgrade the unRAID version too, or just the motherboard?
June 30, 201115 yr Author I'm running unRaid 4.7.... I also added a new controller card: SUPERMICRO AOC-SASLP-MV8. I made a screenshot of my disk assignments before I upgraded so I could re-assign them right. Maybe I wasn't as careful as I thought when re-assigning drives to their slots. That sounds like most likely what happened. I'll check & send a syslog when I get home.
June 30, 201115 yr Try assigning the parity as a data disk. Assign all the disks as data disk and use initconfig and start the array. I bet the one that was assigned as the parity will show up as formatted, meaning you got the parity disk and a data disk swapped. Peter
July 1, 201115 yr Here is my syslog: One of your disks, /dev/sdn, has tons of media errors (un-readable sectors) It is disk1. md: import disk1: [8,208] (sdn) ST2000DL003-9VT1 5YD25Q88 size: 1953514552 Jul 1 01:25:30 Tower kernel: ata12.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Jul 1 01:25:30 Tower kernel: ata12.00: BMDMA stat 0x65 Jul 1 01:25:30 Tower kernel: ata12.00: failed command: READ DMA EXT Jul 1 01:25:30 Tower kernel: ata12.00: cmd 25/00:08:f7:2b:d2/00:00:d7:00:00/e0 tag 0 dma 4096 in Jul 1 01:25:30 Tower kernel: res 51/40:00:f7:2b:d2/40:00:d7:00:00/00 Emask 0x9 (media error) Jul 1 01:25:30 Tower kernel: ata12.00: status: { DRDY ERR } Jul 1 01:25:30 Tower kernel: ata12.00: error: { UNC } Jul 1 01:25:31 Tower kernel: ata12.00: configured for UDMA/133 Jul 1 01:25:31 Tower kernel: ata12.01: configured for UDMA/133 Jul 1 01:25:31 Tower kernel: ata12: EH complete Jul 1 01:25:34 Tower kernel: ata12.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Jul 1 01:25:34 Tower kernel: ata12.00: BMDMA stat 0x65 Jul 1 01:25:34 Tower kernel: ata12.00: failed command: READ DMA EXT Jul 1 01:25:34 Tower kernel: ata12.00: cmd 25/00:08:f7:2b:d2/00:00:d7:00:00/e0 tag 0 dma 4096 in Jul 1 01:25:34 Tower kernel: res 51/40:00:f7:2b:d2/40:00:d7:00:00/00 Emask 0x9 (media error) Jul 1 01:25:34 Tower kernel: ata12.00: status: { DRDY ERR } Jul 1 01:25:34 Tower kernel: ata12.00: error: { UNC } Jul 1 01:25:34 Tower kernel: ata12.00: configured for UDMA/133 Jul 1 01:25:34 Tower kernel: ata12.01: configured for UDMA/133 Jul 1 01:25:34 Tower kernel: ata12: EH complete Jul 1 01:25:37 Tower kernel: ata12.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Jul 1 01:25:37 Tower kernel: ata12.00: BMDMA stat 0x65 Jul 1 01:25:37 Tower kernel: ata12.00: failed command: READ DMA EXT Jul 1 01:25:37 Tower kernel: ata12.00: cmd 25/00:08:f7:2b:d2/00:00:d7:00:00/e0 tag 0 dma 4096 in Jul 1 01:25:37 Tower kernel: res 51/40:00:f7:2b:d2/40:00:d7:00:00/00 Emask 0x9 (media error) Jul 1 01:25:37 Tower kernel: ata12.00: status: { DRDY ERR } Jul 1 01:25:37 Tower kernel: ata12.00: error: { UNC } Jul 1 01:25:37 Tower kernel: ata12.00: configured for UDMA/133 Jul 1 01:25:37 Tower kernel: ata12.01: configured for UDMA/133 Jul 1 01:25:37 Tower kernel: ata12: EH complete Jul 1 01:25:41 Tower kernel: ata12.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Jul 1 01:25:41 Tower kernel: ata12.00: BMDMA stat 0x65 Jul 1 01:25:41 Tower kernel: ata12.00: failed command: READ DMA EXT Jul 1 01:25:41 Tower kernel: ata12.00: cmd 25/00:08:f7:2b:d2/00:00:d7:00:00/e0 tag 0 dma 4096 in Jul 1 01:25:41 Tower kernel: res 51/40:00:f7:2b:d2/40:00:d7:00:00/00 Emask 0x9 (media error) Jul 1 01:25:41 Tower kernel: ata12.00: status: { DRDY ERR } Jul 1 01:25:41 Tower kernel: ata12.00: error: { UNC } Jul 1 01:25:41 Tower kernel: ata12.00: configured for UDMA/133 Jul 1 01:25:41 Tower kernel: ata12.01: configured for UDMA/133 Jul 1 01:25:41 Tower kernel: ata12: EH complete Jul 1 01:25:44 Tower kernel: ata12.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Jul 1 01:25:44 Tower kernel: ata12.00: BMDMA stat 0x65 Jul 1 01:25:44 Tower kernel: ata12.00: failed command: READ DMA EXT Jul 1 01:25:44 Tower kernel: ata12.00: cmd 25/00:08:f7:2b:d2/00:00:d7:00:00/e0 tag 0 dma 4096 in Jul 1 01:25:44 Tower kernel: res 51/40:00:f7:2b:d2/40:00:d7:00:00/00 Emask 0x9 (media error) Jul 1 01:25:44 Tower kernel: ata12.00: status: { DRDY ERR } Jul 1 01:25:44 Tower kernel: ata12.00: error: { UNC } Jul 1 01:25:44 Tower kernel: ata12.00: configured for UDMA/133 Jul 1 01:25:44 Tower kernel: ata12.01: configured for UDMA/133 Jul 1 01:25:44 Tower kernel: ata12: EH complete Jul 1 01:25:48 Tower kernel: ata12.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Jul 1 01:25:48 Tower kernel: ata12.00: BMDMA stat 0x65 Jul 1 01:25:48 Tower kernel: ata12.00: failed command: READ DMA EXT Jul 1 01:25:48 Tower kernel: ata12.00: cmd 25/00:08:f7:2b:d2/00:00:d7:00:00/e0 tag 0 dma 4096 in Jul 1 01:25:48 Tower kernel: res 51/40:00:f7:2b:d2/40:00:d7:00:00/00 Emask 0x9 (media error) Jul 1 01:25:48 Tower kernel: ata12.00: status: { DRDY ERR } Jul 1 01:25:48 Tower kernel: ata12.00: error: { UNC } Jul 1 01:25:48 Tower kernel: ata12.00: configured for UDMA/133 Jul 1 01:25:48 Tower kernel: ata12.01: configured for UDMA/133 Jul 1 01:25:48 Tower kernel: sd 13:0:0:0: [sdn] Unhandled sense code You should get a smart report on that drive. Odds are it is in pretty sad shape. smartctl -a /dev/sdn Reads of that drive are failing, and it cannot even read the file-system superblock, therefore, it cannot be mounted: Jun 30 02:39:31 Tower kernel: md: disk1 read error Jun 30 02:39:31 Tower kernel: handle_stripe read error: 3620875192/1, count: 1 Jun 30 02:39:31 Tower kernel: Buffer I/O error on device md1, logical block 452609399 Jun 30 02:39:31 Tower kernel: lost page write due to I/O error on md1 Jun 30 02:39:31 Tower kernel: REISERFS warning (device md1): journal-1226 journal_read_transaction: REPLAY FAILURE, fsck required! buffer write failed Jun 30 02:39:31 Tower kernel: REISERFS warning (device md1): reiserfs-2006 journal_init: Replay Failure, unable to mount Jun 30 02:39:31 Tower kernel: REISERFS warning (device md1): sh-2022 reiserfs_fill_super: unable to initialize journal space
July 1, 201115 yr Did you perform a parity check before you swapped out motherboards? Did you drop-kick disk1 while migrating hardware?
July 1, 201115 yr Media errors are not caused by a loose cable. Those are UNC errors, unreadable sectors on the disk. The would get timeout errors or CRC errors with a bad cable.
July 1, 201115 yr Author I don't get why that disk would fail right when I upgraded my system...... Everything was fine before the upgrade. The whole reason for the upgrade was to add new faster pcie cards to replace the slower pci cards because it was going to take 60+ hours to calc parity. The motherboard was just another upgrade while I was at it. I know all the cables got switched around but that would not cause unreadable sectors. Is there any other way of retrieving the data from the drive if unRaid can't read the drive?
July 1, 201115 yr I don't get why that disk would fail right when I upgraded my system...... Everything was fine before the upgrade. The whole reason for the upgrade was to add new faster pcie cards to replace the slower pci cards because it was going to take 60+ hours to calc parity. The motherboard was just another upgrade while I was at it. I know all the cables got switched around but that would not cause unreadable sectors. Is there any other way of retrieving the data from the drive if unRaid can't read the drive? Yes, unplug the drive, but leave it assigned as the data drive. unRAID would then simulate its contents based on parity. you should be able to get to its contents that way. If it works, and can be mounted as a simulated drive, then you can attempt to stop the array, re-assign it, re-start the array, and have it re-constructed onto itself (if it is still writable) If not, you can replace it with a new drive and have the contents re-constructed onto it. Joe L.
Archived
This topic is now archived and is closed to further replies.