130 reputation
8
bio website
location
age
visits member for 3 years, 3 months
seen Mar 26 at 3:55

I like things.


Feb
1
comment Why is my HDD partition a character special device?
@TeroKilkanen You set me on the right path. I don't know why this was happening originally, but deleting /dev/sdz1 (the character device partition) and calling partprobe /dev/sdz caused the new partition to show up. Very weird, but this works.
Feb
1
revised Why is my HDD partition a character special device?
added proc partitions output
Feb
1
comment Why is my HDD partition a character special device?
@Halfgaar added the ls output to the original post. Yes, all these device entries are created automatically, I have specified no special rules and I'm not really sure how to do that.
Feb
1
awarded  Student
Feb
1
revised Why is my HDD partition a character special device?
added requested output
Feb
1
asked Why is my HDD partition a character special device?
Sep
24
awarded  Autobiographer
Jan
19
revised mdadm array fails to start at boot, bad superblock on component drive
added more output+a plea
Jan
17
comment mdadm array fails to start at boot, bad superblock on component drive
I can provide complete output tomorrow morning, but to me it indicates no issues (it's clean, has UUUUUUUUU, etc).
Jan
17
revised mdadm array fails to start at boot, bad superblock on component drive
removed info about fdisk
Jan
17
comment mdadm array fails to start at boot, bad superblock on component drive
Yes, I am indeed mounting md0 directly. I guess I was thinking that if sdX and sdXN are device and partition, md and mdN would be the same, but now that I type it out I see what you mean. I'll edit my question to just ask about the invalid superblock, thanks.
Jan
17
asked mdadm array fails to start at boot, bad superblock on component drive
Nov
14
accepted mdadm grow operation giving nonstop libata errors
Nov
14
comment mdadm grow operation giving nonstop libata errors
It seems like 530 watts should be enough for 8 HDDs, 2 SSDs, 7 case fans, a new Xeon and an ancient PCI video card, but you're right. The case was open, so I (very carefully!) unplugged the spare SSD and 4 of the fans. After the last fan was out, it the noises and libata errors stopped and the rebuild time went from 2000min to 750! All the ata errors were listed as coming from the "rebuilding" drive in mdadm --detail, so I guess that's where all the writes are happening and therefore the largest power drain. Thanks buddy, you're a life saver!
Nov
14
asked mdadm grow operation giving nonstop libata errors
May
10
awarded  Supporter
Mar
12
awarded  Excavator
Mar
12
revised Linux: how to give a user permission to restart apache?
The beginning of the post needs to mention visudo, not editing /etc/sudoers
Mar
12
suggested approved edit on Linux: how to give a user permission to restart apache?
Jan
5
awarded  Teacher