Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #230648
| From | Michael Stone <mstone@debian.org> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: old red cables cause Disk errors ... |
| Date | 2021-01-14 01:30 +0100 |
| Message-ID | <BwYGu-1Tm-3@gated-at.bofh.it> (permalink) |
| References | (3 earlier) <BwXho-VN-3@gated-at.bofh.it> <BwXhp-VN-11@gated-at.bofh.it> <BwXKp-1ll-1@gated-at.bofh.it> <BwY3L-1rA-1@gated-at.bofh.it> <BwYn8-1Nb-5@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Wed, Jan 13, 2021 at 07:03:54PM -0500, Michael Stone wrote: >On Wed, Jan 13, 2021 at 05:46:03PM -0600, Dennis Wicks wrote: >>Well, this is all very interesting! I have *two* SATALink/SATARaid >>expansion cards and neither of them have any red cables! They are at >>pci addresses 05:00 and 05:01! How do I tell which is which? > >Pull one out. :-) Sorry, couldn't resist, then didn't finish sending. If you ls -l /sys/block you should see your disk device names (sda etc) as symlinks to device paths. The last XXXX:XX:XX.X element before something like ata1 should correspond to the lspci output (so probably 0000:05:00.0 and 0000:05:01.0). If you know what disks are on what controller that will answer your question. cat /sys/block/DEVICENAME/device/wwid (where DEVICENAME is something like sda) will usually have the serial number as the last part, which can help identifying disks. If it's doing hardware raid then there's going to be a more device-specific answer. FYI, pulling one out probably won't actually help because they'll renumber.
Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Disk errors ... Dennis Wicks <wix@mgssub.com> - 2021-01-13 20:10 +0100
Re: Disk errors ... David Christensen <dpchrist@holgerdanske.com> - 2021-01-13 23:00 +0100
Re: Disk errors ... Michael Stone <mstone@debian.org> - 2021-01-13 23:40 +0100
Re: Disk errors ... David Christensen <dpchrist@holgerdanske.com> - 2021-01-14 00:00 +0100
Re: Disk errors ... Michael Howard <mike@dewberryfields.co.uk> - 2021-01-14 00:00 +0100
Re: old red cables cause Disk errors ... Felix Miata <mrmazda@earthlink.net> - 2021-01-14 00:30 +0100
Re: old red cables cause Disk errors ... Dennis Wicks <wix@mgssub.com> - 2021-01-14 00:50 +0100
Re: old red cables cause Disk errors ... Gene Heskett <gheskett@shentel.net> - 2021-01-14 01:10 +0100
Re: old red cables cause Disk errors ... Michael Stone <mstone@debian.org> - 2021-01-14 01:10 +0100
Re: old red cables cause Disk errors ... Michael Stone <mstone@debian.org> - 2021-01-14 01:30 +0100
Re: old red cables cause Disk errors ... David Christensen <dpchrist@holgerdanske.com> - 2021-01-14 01:10 +0100
Re: old red cables cause Disk errors ... Felix Miata <mrmazda@earthlink.net> - 2021-01-14 01:30 +0100
Re: Disk errors ... Michael Stone <mstone@debian.org> - 2021-01-14 00:20 +0100
Re: Disk errors ... Charles Curley <charlescurley@charlescurley.com> - 2021-01-14 01:20 +0100
Re: Disk errors ... Joe <joe@jretrading.com> - 2021-01-14 10:10 +0100
Re: Disk errors ... Dominique Dumont <dod@debian.org> - 2021-01-17 12:50 +0100
Re: Disk errors ... Gene Heskett <gheskett@shentel.net> - 2021-01-14 00:40 +0100
Re: Disk errors ... David Christensen <dpchrist@holgerdanske.com> - 2021-01-14 01:10 +0100
Re: Disk errors ... Charles Curley <charlescurley@charlescurley.com> - 2021-01-14 01:20 +0100
Re: Disk errors ... Miles Fidelman <mfidelman@meetinghouse.net> - 2021-01-14 18:00 +0100
Re: Disk errors ... Michael Stone <mstone@debian.org> - 2021-01-14 18:10 +0100
Re: Disk errors ... Miles Fidelman <mfidelman@meetinghouse.net> - 2021-01-14 18:50 +0100
Re: Disk errors ... Michael Stone <mstone@debian.org> - 2021-01-14 19:00 +0100
csiph-web